Bug 284552 - Error removing bluetooth device (headset)
Summary: Error removing bluetooth device (headset)
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kshareddatacache (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-10-20 15:09 UTC by Bruno Medeiros
Modified: 2018-10-27 03:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Medeiros 2011-10-20 15:09:55 UTC
Application: bluedevil-audio (0.1)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

I was getting trouble tring to connect my Bluetoothe headset, so I decided to remove and add it again. I went to 'Configure Bluetooth' screen, clicked on my headset and pressed the 'remove' button, and got this error :(

-- Backtrace:
Application: Bluetooth Audio Helper (bluedevil-audio), signal: Segmentation fault
[KCrash Handler]
#6  malloc_consolidate (av=0x7fb5c6b9c1c0) at malloc.c:5155
#7  0x00007fb5c687bdff in malloc_consolidate (av=0x7fb5c6b9c1c0) at malloc.c:5115
#8  _int_malloc (av=0x7fb5c6b9c1c0, bytes=3331) at malloc.c:4373
#9  0x00007fb5c687e77d in __GI___libc_malloc (bytes=3331) at malloc.c:3660
#10 0x00007fb5c7c0ea9a in QByteArray::QByteArray (this=0x7fff6de9ba30, data=0x7fb5bdb5e020 "", size=3299) at tools/qbytearray.cpp:1306
#11 0x00007fb5c825d7d1 in KSharedDataCache::find (this=<optimized out>, key=<optimized out>, destination=0x7fff6de9bae0) at ../../kdecore/util/kshareddatacache.cpp:1515
#12 0x00007fb5c890bea9 in KIconLoaderPrivate::findCachedPixmapWithPath (this=0xbffb30, key=..., data=..., path=...) at ../../kdeui/icons/kiconloader.cpp:860
#13 0x00007fb5c890c1c1 in KIconLoader::loadIcon (this=0xc18840, _name=<optimized out>, group=KIconLoader::Desktop, size=48, state=0, overlays=..., path_store=0x0, canReturnNull=false) at ../../kdeui/icons/kiconloader.cpp:1222
#14 0x00007fb5c8903a6f in KIconEngine::pixmap (this=<optimized out>, size=..., mode=<optimized out>, state=<optimized out>) at ../../kdeui/icons/kiconengine.cpp:104
#15 0x00007fb5c714e0a5 in QIcon::pixmap (this=<optimized out>, size=<optimized out>, mode=<optimized out>, state=<optimized out>) at image/qicon.cpp:676
#16 0x00007fb5b96836c1 in ?? () from /usr/lib/kde4/bluedevilaudioactionplugin.so
#17 0x00007fb5b9682e01 in ?? () from /usr/lib/kde4/bluedevilaudioactionplugin.so
#18 0x00007fb5c7d06eba in QMetaObject::activate (sender=0xd077c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#19 0x00007fb5c7d0ef7f in QSingleShotTimer::timerEvent (this=0xd077c0) at kernel/qtimer.cpp:308
#20 0x00007fb5c7d0a789 in QObject::event (this=0xd077c0, e=<optimized out>) at kernel/qobject.cpp:1181
#21 0x00007fb5c70a4424 in notify_helper (e=0x7fff6de9c5d0, receiver=0xd077c0, this=0xb8fce0) at kernel/qapplication.cpp:4486
#22 QApplicationPrivate::notify_helper (this=0xb8fce0, receiver=0xd077c0, e=0x7fff6de9c5d0) at kernel/qapplication.cpp:4458
#23 0x00007fb5c70a9291 in QApplication::notify (this=0x7fff6de9c8d0, receiver=0xd077c0, e=0x7fff6de9c5d0) at kernel/qapplication.cpp:4365
#24 0x00007fb5c895d1e6 in KApplication::notify (this=0x7fff6de9c8d0, receiver=0xd077c0, event=0x7fff6de9c5d0) at ../../kdeui/kernel/kapplication.cpp:311
#25 0x00007fb5c7cf3afc in QCoreApplication::notifyInternal (this=0x7fff6de9c8d0, receiver=0xd077c0, event=0x7fff6de9c5d0) at kernel/qcoreapplication.cpp:787
#26 0x00007fb5c7d20d62 in sendEvent (event=0x7fff6de9c5d0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#27 QTimerInfoList::activateTimers (this=0xb93190) at kernel/qeventdispatcher_unix.cpp:603
#28 0x00007fb5c7d1e514 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#29 0x00007fb5c37a5a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007fb5c37a6258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007fb5c37a6429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007fb5c7d1eed6 in QEventDispatcherGlib::processEvents (this=0xb73cd0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#33 0x00007fb5c714c07e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#34 0x00007fb5c7cf2cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#35 0x00007fb5c7cf2ef7 in QEventLoop::exec (this=0x7fff6de9c860, flags=...) at kernel/qeventloop.cpp:201
#36 0x00007fb5c7cf7789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#37 0x0000000000402933 in ?? ()
#38 0x00007fb5c682330d in __libc_start_main (main=0x4024e0, argc=2, ubp_av=0x7fff6de9cbb8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6de9cba8) at libc-start.c:226
#39 0x000000000040299d in _start ()

Possible duplicates by query: bug 233226.

Reported using DrKonqi
Comment 1 Alex Fiestas 2012-04-22 03:52:02 UTC
The bug is within kdelibs for sure, not even a mention of bluedevil in the bt.
Comment 2 Michael Pyne 2012-04-22 16:01:37 UTC
Looking at the backtrace it seems that the cache may be corrupt...

For the reporter, can you try removing the file "/var/tmp/kdecache-$USER/icon-cache.kcache"? (Where $USER is whatever your login userid is).

After removing the file restart the KDE session so it can be recreated.
Comment 3 Christoph Feck 2012-04-22 19:33:50 UTC
> The bug is within kdelibs for sure, not even a mention of bluedevil in the bt.

There is, #16 and #17, but this is irrelevant here.

> Looking at the backtrace it seems that the cache may be corrupt...

Nope, the crash happens in malloc, which means the memory is corrupt, not the cache files. If the crash is reproducible, we would need a valgrind log.
Comment 4 Bruno Medeiros 2012-04-24 02:38:38 UTC
I still have the system and the bluetooth headset, but I did a fresh install. Is it worth trying to reproduce?
Comment 5 Andrew Crouthamel 2018-09-23 02:42:50 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 03:45:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!