On Friday, 20 August, 2010 @04:38 zulu, JD scribed:
$ ps -ef | grep blue
root 1200 1 0 18:30 ?00:00:00 /usr/sbin/bluetoothd
--udev
jd1441 1230 0 18:31 ?00:00:00
bluetooth-applet
It is the gnome applet that does not show up after I log in.
Just to
Hi,
If I boot up while the usb bluetooth is plugged in,
I do not see the bluetooth icon on the bar (Gnome desktop).
But if I unplug it and replug it back in, the icon
appears and then I can use the laptop mouse pad
to click it and connect to the bluetooth mouse.
Is this the expected or normal
JD writes:
Hi,
If I boot up while the usb bluetooth is plugged in,
I do not see the bluetooth icon on the bar (Gnome desktop).
But if I unplug it and replug it back in, the icon
appears and then I can use the laptop mouse pad
to click it and connect to the bluetooth mouse.
Is this the
On 08/19/2010 03:51 PM, JD wrote:
Hi,
If I boot up while the usb bluetooth is plugged in,
I do not see the bluetooth icon on the bar (Gnome desktop).
But if I unplug it and replug it back in, the icon
appears and then I can use the laptop mouse pad
to click it and connect to the
On 08/19/2010 03:51 PM, JD wrote:
Hi,
If I boot up while the usb bluetooth is plugged in,
I do not see the bluetooth icon on the bar (Gnome desktop).
But if I unplug it and replug it back in, the icon
appears and then I can use the laptop mouse pad
to click it and connect to the
On 08/19/2010 04:05 PM, jack craig wrote:
On 08/19/2010 03:51 PM, JD wrote:
Hi,
If I boot up while the usb bluetooth is plugged in,
I do not see the bluetooth icon on the bar (Gnome desktop).
But if I unplug it and replug it back in, the icon
appears and then I can use the laptop
On Thursday, 19 August, 2010 @22:51 zulu, JD scribed:
Is this the expected or normal behaviour?
Which bluetooth manager are you using?
I recall at least 2 - bluez and blueman.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
On 08/19/2010 08:31 PM, Darr wrote:
On Thursday, 19 August, 2010 @22:51 zulu, JD scribed:
Is this the expected or normal behaviour?
Which bluetooth manager are you using?
I recall at least 2 - bluez and blueman.
$ ps -ef | grep blue
root 1200 1 0 18:30 ?00:00:00
