Bug 264555 - Plasma crash right after login
Summary: Plasma crash right after login
Status: RESOLVED DUPLICATE of bug 255437
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-27 23:59 UTC by Marc Schiffbauer
Modified: 2011-11-21 09:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (12.33 KB, text/plain)
2011-03-01 12:53 UTC, Vaso
Details
New crash information added by DrKonqi (4.49 KB, text/plain)
2011-06-12 10:02 UTC, Joachim Mairböck
Details
New crash information added by DrKonqi (5.02 KB, text/plain)
2011-09-16 07:16 UTC, Joachim Mairböck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Schiffbauer 2011-01-27 23:59:41 UTC
Application: plasma-desktop (0.4)
KDE Platform Version: 4.6.00 (4.6.0) (Compiled from sources)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

I just logged in, entered my kwallet password and clicked on the notification area to view last message: crash

-- Backtrace:
Application: Plasma-Desktop-Umgebung (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0x7f8ab1810780 (LWP 8263))]

Thread 2 (Thread 0x7f8a95ae7700 (LWP 8292)):
#0  0x00007f8aaee916f3 in poll () from /lib/libc.so.6
#1  0x00007f8aabca77a4 in g_main_context_poll (context=0x2aa7b00, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3093
#2  g_main_context_iterate (context=0x2aa7b00, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2775
#3  0x00007f8aabca7cdd in g_main_context_iteration (context=0x2aa7b00, may_block=1) at gmain.c:2843
#4  0x00007f8ab04b16a6 in QEventDispatcherGlib::processEvents (this=0x2aa01c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#5  0x00007f8ab0484342 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#6  0x00007f8ab0484724 in QEventLoop::exec (this=0x7f8a95ae6dc0, flags=) at kernel/qeventloop.cpp:201
#7  0x00007f8ab0390f2d in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#8  0x00007f8ab0464538 in QInotifyFileSystemWatcherEngine::run (this=0x2a96620) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007f8ab0393ebe in QThreadPrivate::start (arg=0x2a96620) at thread/qthread_unix.cpp:285
#10 0x00007f8ab0101e1c in start_thread () from /lib/libpthread.so.0
#11 0x00007f8aaee9be1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f8ab1810780 (LWP 8263)):
[KCrash Handler]
#6  0x00007f8aaededee5 in raise () from /lib/libc.so.6
#7  0x00007f8aaedef896 in abort () from /lib/libc.so.6
#8  0x00007f8aaf1fda9d in __gnu_cxx::__verbose_terminate_handler () at /var/tmp/portage/sys-devel/gcc-4.5.2/work/gcc-4.5.2/libstdc++-v3/libsupc++/vterminate.cc:93
#9  0x00007f8aaf1fbcd6 in __cxxabiv1::__terminate (handler=<value optimized out>) at /var/tmp/portage/sys-devel/gcc-4.5.2/work/gcc-4.5.2/libstdc++-v3/libsupc++/eh_terminate.cc:39
#10 0x00007f8aaf1fbd03 in std::terminate () at /var/tmp/portage/sys-devel/gcc-4.5.2/work/gcc-4.5.2/libstdc++-v3/libsupc++/eh_terminate.cc:49
#11 0x00007f8aaf1fbe55 in __cxxabiv1::__cxa_rethrow () at /var/tmp/portage/sys-devel/gcc-4.5.2/work/gcc-4.5.2/libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x00007f8ab0484873 in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007f8ab048879b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#14 0x00007f8aa1433c58 in kdemain (argc=1, argv=0x20d7fa0) at /var/tmp/portage/kde-base/plasma-workspace-4.6.9999/work/plasma-workspace-4.6.9999/plasma/desktop/shell/main.cpp:118
#15 0x0000000000407659 in launch (argc=1, _name=0x20c5968 "/usr/bin/plasma-desktop", args=<value optimized out>, cwd=0x0, envc=<value optimized out>, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b62e "0") at /var/tmp/portage/kde-base/kdelibs-4.6.9999/work/kdelibs-4.6.9999/kinit/kinit.cpp:730
#16 0x00000000004081a7 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.6.9999/work/kdelibs-4.6.9999/kinit/kinit.cpp:1222
#17 0x00000000004088b5 in handle_requests (waitForPid=0) at /var/tmp/portage/kde-base/kdelibs-4.6.9999/work/kdelibs-4.6.9999/kinit/kinit.cpp:1415
#18 0x00000000004094c7 in main (argc=4, argv=0x7fff8cb78398, envp=0x7fff8cb783c0) at /var/tmp/portage/kde-base/kdelibs-4.6.9999/work/kdelibs-4.6.9999/kinit/kinit.cpp:1903

Possible duplicates by query: bug 264142, bug 264076, bug 261118, bug 256202, bug 255227.

Reported using DrKonqi
Comment 1 Vaso 2011-03-01 12:53:42 UTC
Created attachment 57587 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.1

- What I was doing when the application crashed:
I just log in and got the crash. But this situation is not so often as crashes after log out (about 1 to 20).

-- Backtrace (Reduced):
#8  0xb6134845 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#9  0xb6132765 in __cxxabiv1::__terminate (handler=0xb61346f0 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:39
#10 0xb61327a2 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:49
#11 0xb61333a5 in __cxxabiv1::__cxa_pure_virtual () at ../../../../libstdc++-v3/libsupc++/pure.cc:50
#12 0xb686df90 in QGraphicsItem::sceneBoundingRect (this=0x86c74b8) at graphicsview/qgraphicsitem.cpp:4787
Comment 2 Joachim Mairböck 2011-06-12 10:02:35 UTC
Created attachment 60924 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.6.4 (4.6.4) using Qt 4.7.3

- What I was doing when the application crashed:
Today plasma crashed even twice in a row on login. This is the second crash, I clicked the first one away.

-- Backtrace (Reduced):
#10 0xb617095d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#11 0xb616e6b3 in __cxxabiv1::__terminate (handler=0xb6170810 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:39
#12 0xb616e6ef in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:49
#13 0xb616e8ba in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#14 0xb6de0d57 in QEventLoop::exec (this=0xbfe5e904, flags=...) at kernel/qeventloop.cpp:214
Comment 3 Joachim Mairböck 2011-09-16 07:16:31 UTC
Created attachment 63678 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.4

- What I was doing when the application crashed:
plasma-desktop crashes nearly every time on login. I usually have to restart it manually (using KRunner) because DrKonqi doesn't show up. 
- Unusual behavior I noticed:
You have to restart plasma after all the KDE initialization is done, or it will crash again.

This time, DrKonqi showed on the first on the first crash and automatically restarted plasma. Though that was too early, and it crashed again, again without DrKonqi (the first DrKonqi still open).

Restarting plasma after some time from KRunner, it didn't crash any more, like expected.

-- Backtrace (Reduced):
#10 0xb621695d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#11 0xb62146b3 in __cxxabiv1::__terminate (handler=0xb6216810 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:39
#12 0xb62146ef in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:49
#13 0xb62148ba in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#14 0xb6e8ff47 in QEventLoop::exec (this=0xbfc945a4, flags=...) at kernel/qeventloop.cpp:214
Comment 4 Joachim Mairböck 2011-11-19 17:05:28 UTC
I have some new findings concerning this bug: Plasma crashes only if I have an active network connection when starting KDE, regardless whether it is wired or wireless. I usually just use WiFi, so I have no wired connection. I have now disabled "connect automatically" on the connection, but set it as system connection. So, directly after booting, there is no active connection and Plasma does not crash. I connect to the wireless network after Plasma has initialized fully, so it still doesn't crash. However, when I logout and log in again, Plasma will crash on login, because the network remains active, also during KDE startup.
Comment 5 Aaron J. Seigo 2011-11-21 09:14:08 UTC

*** This bug has been marked as a duplicate of bug 255437 ***