[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 177183] KBluetooth4 SIGSEGV when inserting usb bluetooth dongle
From:       Holly <kate_baggins () yahoo ! ca>
Date:       2008-12-17 2:31:26
Message-ID: 20081217023126.86EF9133D3 () immanuel ! kde ! org
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=177183


Holly kate_baggins yahoo ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kate_baggins@yahoo.ca




--- Comment #7 from Holly <kate_baggins yahoo ca>  2008-12-17 03:31:24 ---
I have the same problem. I also can't get the debugging to work... but anyway,
I have no KBluetooth in the system tray and it crashes when it starts. However,
runnng the command that Audrey lists above without the dongle plugged in, I get
the following:

~$ /usr/bin/kblueplugd                                             
No BT device found                                                              
waiting for bt device (un)plug events ...

Okay, working good so far, nothing in the system tray... then I plug in the
dongle and boom! It does this:

bt dev added: /org/bluez/hci0 # of devices: 1                                   
kbluetooth4(6881) Solid::Control::ManagerBasePrivate::loadBackend: Backend
loaded:  "BlueZ"                                                                
KCrash: Application 'kbluetooth4' crashing...
sock_file=/home/kalinda/.kde/socket-Tardis/kdeinit4__0
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
kbluetooth4(6873): Communication problem with  "kbluetooth4" , it probably
crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "

ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 214, in
maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/bin/kblueplugd", line 42, in slotAdapterAdded
    distutils.spawn.spawn(kbtcmd)
  File "/usr/lib/python2.5/distutils/spawn.py", line 37, in spawn
    _spawn_posix(cmd, search_path, dry_run=dry_run)
  File "/usr/lib/python2.5/distutils/spawn.py", line 167, in _spawn_posix
    (cmd[0], exit_status)
DistutilsExecError: command 'kbluetooth4' failed with exit status 255

This what happens when I run KBluetooth4 without the dongle:

~$ kbluetooth4
kbluetooth4(6892) Solid::Control::ManagerBasePrivate::loadBackend: Backend
loaded:  "BlueZ"
KCrash: Application 'kbluetooth4' crashing...
sock_file=/home/kalinda/.kde/socket-Tardis/kdeinit4__0
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.
kbluetooth4(6891): Communication problem with  "kbluetooth4" , it probably
crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "

I know that's probably useless, but it won't run a better backtrace even though
I installed the debug packages for Kubuntu's Nightly Neon (it does the same in
Beta 1). Running it with gdb isn't helpful, either.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic