Bug 294134 - plasma-desktop crashes after login if a USB pendrive is attached
Summary: plasma-desktop crashes after login if a USB pendrive is attached
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: 4.8.0
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-15 09:30 UTC by pierigno
Modified: 2013-05-29 05:24 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (8.42 KB, text/plain)
2012-02-15 17:34 UTC, Theofilos Intzoglou
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pierigno 2012-02-15 09:30:31 UTC
Application: plasma-desktop (0.4)
KDE Platform Version: 4.8.00 (4.8.0
Qt Version: 4.8.0
Operating System: Linux 3.2.0-sabayon x86_64
Distribution: "Sabayon Linux amd64 8"

-- Information about the crash:
- What I was doing when the application crashed:
I've stopped my laptop,
inserted a USB pendrive,
restarted laptop,
logged in

plasma-desktop crases soon after loading. It's possibile however
to restart by means of krunner (Alt+F2)


- Unusual behavior I noticed:
Soon after login I'm able to see the taskbar getting repainted two times
with the device-notifier menu raised up, then the KCrashHandler appear and notifies me of plasma-desktop crash.


reproducibility: always, following the aferomentioned steps.

-- Backtrace:
Application: Shell del desktop di Plasma (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd257921780 (LWP 8915))]

Thread 3 (Thread 0x7fd230fcf700 (LWP 8921)):
#0  0x00007fd254f15ec3 in poll () from /lib64/libc.so.6
#1  0x00007fd251f17648 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007fd251f17b0d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007fd256571d56 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007fd2565419e2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#5  0x00007fd256541c37 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#6  0x00007fd256440007 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4
#7  0x00007fd25652147f in QInotifyFileSystemWatcherEngine::run() () from /usr/lib64/qt4/libQtCore.so.4
#8  0x00007fd25644302b in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007fd2561abe6c in start_thread () from /lib64/libpthread.so.0
#10 0x00007fd254f1ea0d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fd22bfff700 (LWP 8922)):
#0  0x00007fd2561afd4c in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x00007fd249db2ce2 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtScript.so.4
#2  0x00007fd249db2d19 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtScript.so.4
#3  0x00007fd2561abe6c in start_thread () from /lib64/libpthread.so.0
#4  0x00007fd254f1ea0d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fd257921780 (LWP 8915)):
[KCrash Handler]
#6  0x00007fd25655b35d in QObject::~QObject() () from /usr/lib64/qt4/libQtCore.so.4
#7  0x00007fd24963c3e9 in QDeclarativeBoundSignal::~QDeclarativeBoundSignal() () from /usr/lib64/qt4/libQtDeclarative.so.4
#8  0x00007fd2565550b5 in QObjectPrivate::deleteChildren() () from /usr/lib64/qt4/libQtCore.so.4
#9  0x00007fd25655b32c in QObject::~QObject() () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007fd249557e25 in QDeclarativePrivate::QDeclarativeElement<QDeclarativeItem>::~QDeclarativeElement() () from /usr/lib64/qt4/libQtDeclarative.so.4
#11 0x00007fd25655bc08 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#12 0x00007fd2556b5df4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#13 0x00007fd2556bac73 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#14 0x00007fd257327cb6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#15 0x00007fd256542bfc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#16 0x00007fd25654649a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007fd2565718c3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4
#18 0x00007fd251f1713d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fd251f17938 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fd251f17b0d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fd256571cef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00007fd2557590ee in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtGui.so.4
#23 0x00007fd2565419e2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#24 0x00007fd256541c37 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#25 0x00007fd256546795 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#26 0x00007fd242dd5e43 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so
#27 0x00000000004073a4 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#28 0x0000000000408486 in handle_launcher_request(int, char const*) [clone .isra.15] ()
#29 0x00000000004089af in handle_requests(int) ()
#30 0x00000000004098de in main ()

Reported using DrKonqi
Comment 1 Theofilos Intzoglou 2012-02-15 17:34:02 UTC
Created attachment 68830 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0

- What I was doing when the application crashed:
I can reproduce it also here on a x86 system. I had my external usb hard drive connected when logging in to kde when this crash appeared. It happens everytime.

-- Backtrace (Reduced):
#7  0xb6d340d8 in QObject::~QObject() () from /usr/lib/qt4/libQtCore.so.4
#8  0xb192531b in QDeclarativeBoundSignal::~QDeclarativeBoundSignal() () from /usr/lib/qt4/libQtDeclarative.so.4
#9  0xb1925372 in QDeclarativeBoundSignal::~QDeclarativeBoundSignal() () from /usr/lib/qt4/libQtDeclarative.so.4
#10 0xb6d2e931 in QObjectPrivate::deleteChildren() () from /usr/lib/qt4/libQtCore.so.4
#11 0xb6d340a1 in QObject::~QObject() () from /usr/lib/qt4/libQtCore.so.4
Comment 2 Björn Pfeiffer 2012-02-19 04:55:07 UTC
I also can reproduce this. Plasma crashes, if a usb-stick is inserted during login. 
Kde is 4.8, on sabayon. 
Here is a trace: http://pastebin.sabayon.org/pastie/8373 (tracebacks seem to vary on this one).
Comment 3 Mihai Sorin Dobrescu 2012-02-22 10:08:49 UTC
In my case, it crashes randomly when a mobile HDD on USB is also removed by ejecting it. But not always, just sometimes.
Comment 4 Mihai Sorin Dobrescu 2012-02-26 12:24:59 UTC
Apparently, there is a behavior specific to the file system:
- when NTFS, it crashes after login when already attached, but doesn't crash when I attach the device after the login
- when ext3/4, it crashes in all the cases
Comment 5 Martin Flöser 2013-05-29 05:24:24 UTC
Thank you for this crash report and helping to improve our software. 
Unfortunately we were not able to work on this specific report yet. Nowadays 
the version this crash was reported against is no longer maintained and this 
makes it very difficult to work on this report as the source code might have 
changed and the information in the backtrace is no longer valid.

Also it is quite likely that this problem got fixed in a later version. Crash 
reports are very often reported multiple times.

If you are able to reproduce this crash with the latest version of KDE Plasma 
(4.10.3) please reopen this report and adjust the version information in the 
dropdown above and please also include a new backtrace as generated by the 
crash reporting tool. Please also make sure that the steps on how to reproduce 
the crash are precise and correct. Thank you!