Bug 221647 - Crash on wakeup due to bbc uk ION
Summary: Crash on wakeup due to bbc uk ION
Status: RESOLVED DUPLICATE of bug 219036
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-weather (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-07 13:59 UTC by Emil Sedgh
Modified: 2010-02-27 14:20 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Emil Sedgh 2010-01-07 13:59:24 UTC
Version:            (using Devel)
Compiler:          gcc 
OS:                Linux
Installed from:    Compiled sources

Most of the times that systems wakes up from a suspend, plasma crashes.
I have a weather widget on panel and here is the backtrace:

Thread 1 (Thread 0xb54aa980 (LWP 3705)):
[KCrash Handler]
#6  0xa5f0b66e in QBasicAtomicInt::deref() () from /home/emilsedgh/kde/lib/kde4/ion_bbcukmet.so
#7  0xa5f0d6bf in QString::~QString() () from /home/emilsedgh/kde/lib/kde4/ion_bbcukmet.so
#8  0xa5f0df50 in WeatherData::ForecastInfo::~ForecastInfo() () from /home/emilsedgh/kde/lib/kde4/ion_bbcukmet.so
#9  0xa5f0a801 in UKMETIon::reset() () from /home/emilsedgh/kde/lib/kde4/ion_bbcukmet.so
#10 0xa5f17f99 in WeatherEngine::triggerReset() const () from /home/emilsedgh/kde/lib/kde4/plasma_engine_weather.so
#11 0xa5f191bc in WeatherEngine::qt_metacall(QMetaObject::Call, int, void**) () from /home/emilsedgh/kde/lib/kde4/plasma_engine_weather.so
#12 0xb6a0ca65 in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /home/emilsedgh/kde/lib/libQtCore.so.4
#13 0xb6a1bdf1 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /home/emilsedgh/kde/lib/libQtCore.so.4
#14 0xb6a22d77 in ?? () from /home/emilsedgh/kde/lib/libQtCore.so.4
#15 0xb6a22e9c in ?? () from /home/emilsedgh/kde/lib/libQtCore.so.4
#16 0xb6a182c4 in QObject::event(QEvent*) () from /home/emilsedgh/kde/lib/libQtCore.so.4
#17 0xb5f21d4c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /home/emilsedgh/kde/lib/libQtGui.so.4
#18 0xb5f2951d in QApplication::notify(QObject*, QEvent*) () from /home/emilsedgh/kde/lib/libQtGui.so.4
#19 0xb6d7a3ed in KApplication::notify(QObject*, QEvent*) () from /home/emilsedgh/kde/lib/libkdeui.so.5
#20 0xb6a076db in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /home/emilsedgh/kde/lib/libQtCore.so.4
#21 0xb6a3754e in ?? () from /home/emilsedgh/kde/lib/libQtCore.so.4
#22 0xb6a33b77 in ?? () from /home/emilsedgh/kde/lib/libQtCore.so.4
#23 0xb57c3e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0xb57c7623 in ?? () from /lib/libglib-2.0.so.0
#25 0xb57c77a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0xb6a33841 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /home/emilsedgh/kde/lib/libQtCore.so.4
#27 0xb5fdc765 in ?? () from /home/emilsedgh/kde/lib/libQtGui.so.4
#28 0xb6a05d2a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /home/emilsedgh/kde/lib/libQtCore.so.4
#29 0xb6a06172 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /home/emilsedgh/kde/lib/libQtCore.so.4
#30 0xb6a08889 in QCoreApplication::exec() () from /home/emilsedgh/kde/lib/libQtCore.so.4
#31 0xb5f21de7 in QApplication::exec() () from /home/emilsedgh/kde/lib/libQtGui.so.4
#32 0xb376ee11 in kdemain () from /home/emilsedgh/kde/lib/libkdeinit4_plasma-desktop.so
#33 0x0804eb18 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#34 0x0804f287 in handle_launcher_request(int, char const*) ()
#35 0x0804fbe5 in handle_requests(int) ()
#36 0x08050602 in main ()
Comment 1 Jonathan Thomas 2010-01-07 21:19:35 UTC

*** This bug has been marked as a duplicate of bug 220722 ***
Comment 2 Dario Andres 2010-02-27 14:20:51 UTC
Fixed for KDE SC 4.4.1: bug 219036. Regards

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