https://bugzilla.novell.com/show_bug.cgi?id=250299 ------- Comment #1 from lavrinenko_alex@mail.ru 2007-03-01 10:46 MST ------- Created an attachment (id=121870) --> (https://bugzilla.novell.com/attachment.cgi?id=121870&action=view) 1st user desktop with BT browser error after pairing timeout -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=250299 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kde-maintainers@suse.de |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=250299 dgollub@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #3 from dgollub@novell.com 2007-03-05 02:11 MST ------- kbluetoothd register always as default passkey agent. There is only one default passkey agent allowed. I guess the session of your wife was started first. And your kbluetoothd session doesn't act as default passkey agent... This is quite tricky to solve... in meantime i would recommend to only load one instance of kbluetoothd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=250299 ------- Comment #5 from dgollub@novell.com 2007-03-22 09:03 MST ------- You are right... i try to implement that kbluetoothd and bluez-gnome passkey agents will unregister if the session got inactive. So active session can register as default passkey agent. Could you create a new bug ticket and list a collected multi-session problems like the pin dialog and mediamanger dialog issues... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=250299#c7 Martin Burnicki changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.burnicki@meinberg.de --- Comment #7 from Martin Burnicki 2007-09-20 23:52:07 MST --- This seems to be a general (KDE ?)problem, not only a bluetooth thing. If 2 or more KDE sessions are have been started then there are temporarily problems to assign unique events to the associated session. For example if a DVD has been inserted into the drive it may be impossible to eject it from the same session because KDE or whatever claims the DVD was still used in the other sessions, though this is certainly not the case. This only happens under some circumstances (depending on the application ?), and the only thing you can do in this case is run "eject /dev/dvd" as root. This works for me if I can login as root but other users don't have a way to eject the DVD. Another similar thing is if I insert a flash card into the card reader to move some photographs from the flash disk to the hard disk. In some cases the card is mounted using a user account of another KDE session, so the other user is the owner of the files on the flash disk. I can copy the file, but I'm unable to remove them from the flash disk. This has been observed in openSUSE 10.2 with current patches and recent KDE version from the optional repos. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.