Bug 228231 - Plasma desktop crashed after closing an plasma notification
Summary: Plasma desktop crashed after closing an plasma notification
Status: RESOLVED DUPLICATE of bug 219036
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: 2010-02-23 20:09 UTC by Tobias Roeser
Modified: 2010-02-23 20:26 UTC (History)
1 user (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 Tobias Roeser 2010-02-23 20:09:52 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.00 (KDE 4.4.0) (Compiled from sources)
Qt Version: 4.6.1
Operating System: Linux 2.6.32-gentoo-r5 i686
Distribution (Platform): Gentoo Packages

-- Information about the crash:
I have plasma notifaction configured to not auto hide new information. I connected to another WLAN with Wicd which itself notified me when it successfully established the connection. About 20 second later (while reading something in Konqueror) I decided to click the close-button of the plasma notification (the botton right corner passive popup). Then plasma desktop crashed.

I read something in the backtrace about the weather applet, but I do not have it enabled on the desktop nor the taskbar panel.

 -- Backtrace:
Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0xa7820ef0 in QString::~QString() () from /usr/lib/kde4/ion_bbcukmet.so
#7  0xa780fb01 in UKMETIon::reset() () from /usr/lib/kde4/ion_bbcukmet.so
#8  0xa782f260 in WeatherEngine::triggerReset() const () from /usr/lib/kde4/plasma_engine_weather.so
#9  0xa78314f7 in WeatherEngine::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/kde4/plasma_engine_weather.so
#10 0xb6e3e90f in QMetaObject::cast(QObject*) const () from /usr/lib/qt4/libQtCore.so.4
#11 0xb6e4c8cf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt4/libQtCore.so.4
#12 0xb6e538ea in QSingleShotTimer::timeout() () from /usr/lib/qt4/libQtCore.so.4
#13 0xb6e539e3 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /usr/lib/qt4/libQtCore.so.4
#14 0xb6e497a0 in QObject::event(QEvent*) () from /usr/lib/qt4/libQtCore.so.4
#15 0xb659da3b in ?? () from /usr/lib/qt4/libQtGui.so.4
#16 0xb65a603d in ?? () from /usr/lib/qt4/libQtGui.so.4
#17 0xb71154ee in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#18 0xb6e39b25 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/qt4/libQtCore.so.4
#19 0xb6e66a78 in QTimerInfoList::activateTimers() () from /usr/lib/qt4/libQtCore.so.4
#20 0xb6e63480 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/qt4/libQtCore.so.4
#21 0xb5def02e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb5df2221 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#23 0xb5df2382 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb6e631de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/qt4/libQtCore.so.4
#25 0xb663e26e in ?? () from /usr/lib/qt4/libQtGui.so.4
#26 0xb6e383bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/qt4/libQtCore.so.4
#27 0xb6e387c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/qt4/libQtCore.so.4
#28 0xb6e3abbf in QCoreApplication::exec() () from /usr/lib/qt4/libQtCore.so.4
#29 0xb659dad0 in ?? () from /usr/lib/qt4/libQtGui.so.4
#30 0xb44f59e9 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#31 0x0804e4f1 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#32 0x0804ea8d in handle_launcher_request(int, char const*) ()
#33 0x0804f035 in handle_requests(int) ()
#34 0x0804fd47 in main ()

Possible duplicates by query: bug 221647, bug 220164, bug 219036.

Reported using DrKonqi
Comment 1 Jonathan Thomas 2010-02-23 20:26:39 UTC

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