Description of problem:
it crashes with:
process 3258: arguments to dbus_message_new_method_call() were incorrect,
assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
KCrash: Application 'kbluelock' crashing...
KCrash cannot reach kdeinit, launching directly.
Version-Release number of selected component (if applicable):
always in my box.
Steps to Reproduce:
1. run kbluelock from shell
2. click the radiobox 'lock the screen if....'
I cannot seem to reproduce this bug on my F8 and I don't have a rawhide machine
I'll try to reproduce it during the week-end.
kdebluetooth seems to be incompatible with the current upstream bluez version.
I'll see if I can solve it myself (given the fact that upstream is more-or-less
Can you figure out where in the source code the failing D-Bus call is located?
Well, this doesn't crash anymore. But if i check both boxes for lock operations
and then flip-flop the bt in selected phone, it doesn't do anything, no screen
Subject: crashes --> doesn't work
eh...today is odd day number (7th) so it *crashes* again.... grrr.
same error as in inital comment.
kdebluetooth is horribly broken under F9. Seems like a compatibility problem
with that latest bluez.
As upstream is completely dead, I'm trying solve the problem myself.
Hopefully a solution will be found before F9-release. (But I'm not very optimistic.)
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Is this still an issue? Please give us an update, and even though upstream may
seam dead go ahead a report it to them and add upstream info to this report.
*** This bug has been marked as a duplicate of 447956 ***