Application: bluedevil-audio (1.3.0) KDE Platform Version: 4.10.5 "release 1" Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.16-desktop x86_64 Distribution: "openSUSE 12.3 (x86_64)" -- Information about the crash: I used the headset correctly then I click on "disconnect sink device" and from that I cannot reconnect to the device because I'm facing everytime a Segmentation fault. I cannot even remove the thevice because I face a Segmentation fault error...... The crash can be reproduced every time. -- Backtrace: Application: Programma di supporto per l'audio via Bluetooth (bluedevil-audio), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 AudioHelper::AudioHelper (this=0xb5eb60, address=...) at /usr/src/debug/bluedevil-1.3/src/actionplugins/audio/helper/audiohelper.cpp:46 #6 0x0000000000402b81 in main (argc=2, argv=0x7fffc70e5b58) at /usr/src/debug/bluedevil-1.3/src/actionplugins/audio/helper/main.cpp:49 This bug may be a duplicate of or related to bug 264933. Possible duplicates by query: bug 264933. Reported using DrKonqi
Created attachment 82333 [details] New crash information added by DrKonqi bluedevil-audio (1.3.0) on KDE Platform 4.10.5 "release 1" using Qt 4.8.4 Now on starting session, I have directly a segmentation fault errror. How can I address this issue? -- Backtrace (Reduced): #5 AudioHelper::AudioHelper (this=0x7b6580, address=...) at /usr/src/debug/bluedevil-1.3/src/actionplugins/audio/helper/audiohelper.cpp:46 #6 0x0000000000402b81 in main (argc=3, argv=0x7fffc3f7cd18) at /usr/src/debug/bluedevil-1.3/src/actionplugins/audio/helper/main.cpp:49
Sorry for the late reply :/ Are you compiling bluedevil yourself? If so, are you sure the plugins are being installed in a place where kbuildsycoca finds them? From what I see, bluedevil is unable to find the plugin that comes with "audiohelper", then it crashes. Thanks !
Hello, no I used packaging provided by SuSe, meanwhile I upgraded to opensuse 13.1 and I didn't retried to map a bluedevil audio device.
This crash can't happen on 2.0 anymore since we do not have these plugins. Bug fixed!