Bug 282048 - Plasma crash after double clicking the notifications icon, and calendar widget was giving problems
Summary: Plasma crash after double clicking the notifications icon, and calendar widge...
Status: RESOLVED DUPLICATE of bug 255437
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 01:55 UTC by anidev
Modified: 2011-11-20 22:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.65 KB, text/plain)
2011-10-06 21:50 UTC, anidev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description anidev 2011-09-15 01:55:06 UTC
Application: plasma-desktop (0.4)
KDE Platform Version: 4.6.00 (4.6.0) "release 6"
Qt Version: 4.7.1
Operating System: Linux 2.6.37.6-0.7-desktop i686
Distribution: "openSUSE 11.4 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
I clicked once on the notifications icon (the icon with an "i"), nothing came, so I double-clicked on it, and plasma crashed
- Unusual behavior I noticed:
I noticed that clicking the calendar widget in the panel did not open a calendar, even though I could get one by clicking the clock widget on my desktop, or by looking at the calendar widget on my desktop. Then I noticed that there weren't any libnotify popups coming from pidgin while chatting with someone, which is why I clicked the notifications icon. (now after restarting, I still don't get the notification popups, but the icon flashes and clicking it gives me a list of messages that came after plasma restarted)

-- Backtrace:
Application: Plasma Desktop Shell (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0xb5990710 (LWP 5876))]

Thread 3 (Thread 0xaeec7b70 (LWP 5887)):
#0  0xb5cae22b in clock_gettime () from /lib/librt.so.1
#1  0xb6ea6ae5 in do_gettime () at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb6f79726 in updateCurrentTime (this=0x8704794, tm=...) at kernel/qeventdispatcher_unix.cpp:339
#4  QTimerInfoList::timerWait (this=0x8704794, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0xb6f77f6b in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xaeec711c) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb6f7800d in timerSourcePrepare (source=0x8704760, timeout=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb5bf8a70 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#8  0xb5bf98e2 in ?? () from /lib/libglib-2.0.so.0
#9  0xb5bf9fce in g_main_context_iteration () from /lib/libglib-2.0.so.0
#10 0xb6f787b7 in QEventDispatcherGlib::processEvents (this=0x8704198, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0xb6f492bd in QEventLoop::processEvents (this=0xaeec72b0, flags=...) at kernel/qeventloop.cpp:149
#12 0xb6f494e9 in QEventLoop::exec (this=0xaeec72b0, flags=...) at kernel/qeventloop.cpp:201
#13 0xb6e4a7b9 in QThread::exec (this=0x86f84d0) at thread/qthread.cpp:490
#14 0xb6f2923d in QInotifyFileSystemWatcherEngine::run (this=0x86f84d0) at io/qfilesystemwatcher_inotify.cpp:248
#15 0xb6e4d3aa in QThreadPrivate::start (arg=0x86f84d0) at thread/qthread_unix.cpp:285
#16 0xb6dd1b05 in start_thread () from /lib/libpthread.so.0
#17 0xb618ed5e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xa7fd6b70 (LWP 5915)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb6dd6105 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb3752e17 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0xb38691a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#3  0xb3752e5f in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0xb38691a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#4  0xb6dd1b05 in start_thread () from /lib/libpthread.so.0
#5  0xb618ed5e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5990710 (LWP 5876)):
[KCrash Handler]
#7  0xffffe424 in __kernel_vsyscall ()
#8  0xb60e68df in raise () from /lib/libc.so.6
#9  0xb60e8220 in abort () from /lib/libc.so.6
#10 0xb62dd95d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#11 0xb62db6b3 in ?? () from /usr/lib/libstdc++.so.6
#12 0xb62db6ef in std::terminate() () from /usr/lib/libstdc++.so.6
#13 0xb62db8ba in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#14 0xb6f495a7 in QEventLoop::exec (this=0xbfc43f34, flags=...) at kernel/qeventloop.cpp:214
#15 0xb6f4df90 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#16 0xb6454104 in QApplication::exec () at kernel/qapplication.cpp:3719
#17 0xb25fd8aa in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#18 0x0804e531 in _start ()

Possible duplicates by query: bug 282040, bug 282039, bug 282030, bug 282025, bug 282020.

Reported using DrKonqi
Comment 1 anidev 2011-09-17 15:35:26 UTC
OK, this is ridiculous. This happens every day now. Clicking the notifications icon show a list of notifications; I close, try to open it again, Plasma crashes. Same thing happens with kickoff and the devices icon (icon with usb sign on it), except instead of crashing, the menu simply does not open again. This has not happened before, must be some update. Here is another backtrace from a crash that just happened:

Application: Plasma Desktop Shell (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0xb5867710 (LWP 3827))]

Thread 3 (Thread 0xaed9db70 (LWP 4006)):
#0  0xb6cac45d in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0
#1  0xb5acf39b in g_main_context_release () from /lib/libglib-2.0.so.0
#2  0xb5ad0ade in ?? () from /lib/libglib-2.0.so.0
#3  0xb5ad0fce in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0xb6e4f7b7 in QEventDispatcherGlib::processEvents (this=0x86b4b08, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0xb6e202bd in QEventLoop::processEvents (this=0xaed9d2b0, flags=...) at kernel/qeventloop.cpp:149
#6  0xb6e204e9 in QEventLoop::exec (this=0xaed9d2b0, flags=...) at kernel/qeventloop.cpp:201
#7  0xb6d217b9 in QThread::exec (this=0x8664f40) at thread/qthread.cpp:490
#8  0xb6e0023d in QInotifyFileSystemWatcherEngine::run (this=0x8664f40) at io/qfilesystemwatcher_inotify.cpp:248
#9  0xb6d243aa in QThreadPrivate::start (arg=0x8664f40) at thread/qthread_unix.cpp:285
#10 0xb6ca8b05 in start_thread () from /lib/libpthread.so.0
#11 0xb6065d5e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xa7eb7b70 (LWP 4224)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb6cad105 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb3629e17 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0xb37401a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#3  0xb3629e5f in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0xb37401a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#4  0xb6ca8b05 in start_thread () from /lib/libpthread.so.0
#5  0xb6065d5e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5867710 (LWP 3827)):
[KCrash Handler]
#7  0xffffe424 in __kernel_vsyscall ()
#8  0xb5fbd8df in raise () from /lib/libc.so.6
#9  0xb5fbf220 in abort () from /lib/libc.so.6
#10 0xb61b495d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#11 0xb61b26b3 in ?? () from /usr/lib/libstdc++.so.6
#12 0xb61b26ef in std::terminate() () from /usr/lib/libstdc++.so.6
#13 0xb61b28ba in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#14 0xb6e205a7 in QEventLoop::exec (this=0xbfae9bb4, flags=...) at kernel/qeventloop.cpp:214
#15 0xb6e24f90 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#16 0xb632b104 in QApplication::exec () at kernel/qapplication.cpp:3719
#17 0xb24d48aa in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#18 0x0804e531 in _start ()


Plasma crashed at least 2 other times between the time this bug was reported and now.
Comment 2 anidev 2011-10-06 21:50:29 UTC
Created attachment 64294 [details]
New crash information added by DrKonqi

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

- What I was doing when the application crashed:
This is almost exactly the same as the other bug this is attached to (which I also reported). Basically, clicking on an icon (usually notifications, comics, power; usually not system tray, links, or kickoff) brings up its related screen; the comics for the comic widget, the stuff in a shelf, the list of previous notifications, etc. The problem is that after closing that, trying to open it up again does not work, and after repeatedly clicking the icon, plasma crashes. I don't think this happens all the time, but it does happen often enough to become really annoying.

- Unusual behavior I noticed:
As I said above, clicking an icon brings up the associated submenu screen, and closing it and attempting to reopen it either crashes plasma, or simply does not open the submenu.

-- Backtrace (Reduced):
#14 0xb6e565a7 in QEventLoop::exec (this=0xbfe7a5a4, flags=...) at kernel/qeventloop.cpp:214
#15 0xb6e5af90 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#16 0xb6361104 in QApplication::exec () at kernel/qapplication.cpp:3719
#17 0xb250b8aa in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#18 0x0804e531 in _start ()
Comment 3 Beat Wolf 2011-11-20 22:02:00 UTC

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