From: Bastien Nocera <hadess@hadess.net>
To: BlueZ Hackers <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] [PATCH] Better startup under KDE
Date: Mon, 20 Aug 2007 13:17:10 +0100 [thread overview]
Message-ID: <1187612230.26239.79.camel@cookie.hadess.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
Heya,
This patch comes from a KDE user via:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247284
This makes the bluetooth applet startup after the panel, and disable
startup notification (as it doesn't support it).
Cheers
--
Bastien Nocera <hadess@hadess.net>
[-- Attachment #2: bluez-gnome-applet-better-kde-startup.patch --]
[-- Type: text/x-patch, Size: 513 bytes --]
Index: applet/bluetooth-applet.desktop.in
===================================================================
RCS file: /cvsroot/bluez/gnome/applet/bluetooth-applet.desktop.in,v
retrieving revision 1.1
diff -u -p -r1.1 bluetooth-applet.desktop.in
--- applet/bluetooth-applet.desktop.in 3 Apr 2007 08:09:01 -0000 1.1
+++ applet/bluetooth-applet.desktop.in 20 Aug 2007 12:15:12 -0000
@@ -8,3 +8,5 @@ Terminal=false
Type=Application
Categories=
OnlyShowIn=GNOME;
+StartupNotify=false
+X-KDE-autostart-after=panel
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-08-20 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 12:17 Bastien Nocera [this message]
2007-08-24 12:30 ` [Bluez-devel] [PATCH] Better startup under KDE Marcel Holtmann
2007-08-24 14:07 ` Bastien Nocera
2007-08-24 14:27 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1187612230.26239.79.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.