kbluetooth4 crashed with SIGSEGV in QObject::event()

[Luke Plant]

Binary package hint: kdebluetooth

Crashed occurred after resuming from hibernate.

Let me guess what will happen now:

1) No-one will do anything about this bug, though it's obviously affecting other people (e.g. bug 321856)
2) In a few days, there will be some updates to packages, which means that the packages listed in this bug report will be considered obsolete.
3) Someone will close this bug as "invalid", due to those obsolete packages, even though my system was fully up to date when I filed the report, and even though the updates to those packages have probably got *nothing* to do with kbluetooth.

If that happens, I'm going to start to get annoyed, and insist on re-opening the bug until it gets some *sensible* attention. I currently feel like this is some big joke: "we've provided you with this nice application that collects crash information and encourages you to file bug reports, but actually we are just going to wait a few days until we can find a reason to ignore them, the only point of the whole exercise being to waste your time".

</rant>

ProblemType: Crash
Architecture: i386
Disassembly: 0x9000010:
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
ExecutablePath: /usr/bin/kbluetooth4
Package: kdebluetooth 1:0.3-0ubuntu2
ProcCmdline: kbluetooth4
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebluetooth
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libQtDBus.so.4
 ?? () from /usr/lib/libQtDBus.so.4
 ?? () from /usr/lib/libQtDBus.so.4
 QObject::event () from /usr/lib/libQtCore.so.4
Title: kbluetooth4 crashed with SIGSEGV in QObject::event()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? () from /usr/lib/libQtDBus.so.4
?? () from /usr/lib/libQtDBus.so.4
?? () from /usr/lib/libQtDBus.so.4
QObject::event () from /usr/lib/libQtCore.so.4

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libmysqlclient15off: installed version 5.1.30really5.0.75-0ubuntu6, latest version: 5.1.30really5.0.75-0ubuntu7
libtheora0: installed version 1.0~beta3-1, latest version: 1.0-2
python2.6: installed version 2.6.1-0ubuntu9, latest version: 2.6.1-1ubuntu1
python-minimal: installed version 2.6.1-0ubuntu1, latest version: 2.6.1-0ubuntu2
lsb-base: installed version 3.2-20ubuntu3, latest version: 3.2-20ubuntu4
python: installed version 2.6.1-0ubuntu1, latest version: 2.6.1-0ubuntu2
libglib2.0-0: installed version 2.19.8-0ubuntu1, latest version: 2.19.10-0ubuntu1
libsoprano4: installed version 2.2.1+dfsg-0ubuntu1, latest version: 2.2.2+dfsg.1-1ubuntu1
soprano-daemon: installed version 2.2.1+dfsg-0ubuntu1, latest version: 2.2.2+dfsg.1-1ubuntu1
mysql-common: installed version 5.1.30really5.0.75-0ubuntu6, latest version: 5.1.30really5.0.75-0ubuntu7
lsb-release: installed version 3.2-20ubuntu3, latest version: 3.2-20ubuntu4
libc6: installed version 2.9-0ubuntu12, latest version: 2.9-4ubuntu2
libxine1-plugins: installed version None, latest version: 1.1.16.1-2ubuntu1
python2.6-minimal: installed version 2.6.1-0ubuntu9, latest version: 2.6.1-1ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Luke Plant (spookylukey)]

None of those packages is relevant to this problem. I'm reverting to 'New', for the reasons described in my rant above.

[Luke Plant (spookylukey)]

Please do not change back to 'invalid' without actually looking at this bug and having a decent reason.

[Jonathan Thomas (echidnaman)]

Could you install kdebase-workspace-dbg and obtain a backtrace as per the instructions documented here? https://wiki.ubuntu.com/Backtrace.

Btw, a developer never touched this bug or the other bug you linked to. The automatic bug reporter wasn't able to make sense of the crash data and closed the bug report. Nobody was trying to find an excuse to close anything.

[Luke Plant (spookylukey)]

I realise that it was an automated service, I thought it might be semi-automated and have *some* human guidance, and, at the end of the day, it is a human who put that service in place. The problem is that the service isn't intelligent enough to do its job properly, so it has the same overall affect, and leaves the same impression, as a human being who is just wasting your time and not giving you enough information to file a helpful bug report, which is extremely frustrating. I could keep updating my packages, as it suggests, until I'm blue in the face, and it still won't produce a useful backtrace.

So anyway, thanks for your attention, sorry for my rant, but the current way these bugs are handled is really not helpful.

[Egbert van der Wal (eggie)]

In order to prevent my repport on this from becoming automatically tagged invalid as well, I'll just second this one. I get KBluetoothd crashes all the times, sometimes it even seems to result from me thinking about using the bluetooth adapter. All in all kbluetoothd seems to be VERY unstable and seems to crash whenever there is some kind of 'bad karma' forcefield influencing it's behaviour. I cannot pinpoint an exact reason for it to crash but I get this apport warnings about every time I boot my computer, and most of them are about kbluetooth.

[Luke Plant (spookylukey)]

I've installed the package and obtained a backtrace as requested, but looking at it I don't think the backtrace is any more useful than the one mentioned. It doesn't seem there are debug symbols for the libQtDBus.so.4 library.

The crash happens when I return from suspend, BTW. I started gdb and attached, then suspended, on resume it had crashed.

[Jonathan Thomas (echidnaman)]

One of the dupes was actually able to get a backtrace. This is bug 320614.