| Summary: | Plasma repeatedly crashes after login | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Marcin Gil <marcin.gil> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | f.verdoja, marcin.gil, pfmiller, thomas, woljew |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Marcin Gil
2011-11-25 17:12:50 UTC
*** Bug 287571 has been marked as a duplicate of this bug. *** *** Bug 287585 has been marked as a duplicate of this bug. *** Created attachment 66090 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4
- What I was doing when the application crashed:
Logged in, restarted plasma-desktop several times via KRunner.
KDE Platform Version 4.7.3
Ubuntu: 11.10 Oneiric Ocelot
-- Backtrace (Reduced):
#6 0x00007fd733bae3a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007fd733bb1b0b in __GI_abort () at abort.c:92
[...]
#12 0x00007fd730e1302e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007fd730e17789 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007fd733f581a3 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
likely due to a third party plasmoid (or possibly akonaid integration) not loading and throwing an exception. the backtrace, however, does not tell us anything about what is happening as all it says is "an exception was thrown at a bad time", though the mentioned cause is what every of these situations we've investigated has turned out to be. so .. i recommend removing your plasma-desktop*rc files in ~/.kde/share/config and starting again Created attachment 66235 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4
- What I was doing when the application crashed:
Removed all of ~/.kde/share/config/plasma-desktop* files and logged in.
Plasma-desktop still constantly crashing.
-- Backtrace (Reduced):
#6 0x00007feaf87c13a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007feaf87c4b0b in __GI_abort () at abort.c:92
[...]
#12 0x00007feaf5a2602e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007feaf5a2a789 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007feaf8b6b1a3 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
could be the akonadi bug that was fixed recently (calendar integration had an issue, which the clock uses by default). the backtrace is still unhelpful, however. *** Bug 288703 has been marked as a duplicate of this bug. *** Created attachment 66678 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4
- What I was doing when the application crashed:
Using Firefox, not related.
- Unusual behavior I noticed:
The connection to my remote ownCloud CalDAV resource kept timing out and sending notifications. After 6-7 plasma-desktop crashed.
-- Backtrace (Reduced):
#6 0x00007f10077603a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f1007763b0b in __GI_abort () at abort.c:92
[...]
#12 0x00007f10049c502e in QEventLoop::exec (this=<optimized out>, flags=<optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007f10049c9789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#14 0x00007f1007b0a1a3 in kdemain (argc=1, argv=0x7fff84914398) at ../../../../plasma/desktop/shell/main.cpp:120
Looking thru .xsession-errors I can see a lot of: akonadi_davgroupware_resource_7(2047)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: "" akonadi_davgroupware_resource_7(2047)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "RFC822" akonadi_davgroupware_resource_7(2047)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was: "" akonadi_davgroupware_resource_7(2047)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item id = 115872 Storage collection id 192 parentCollectionId = -23278 akonadi_davgroupware_resource_7(2047)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: "" akonadi_davgroupware_resource_7(2047)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "RFC822" akonadi_davgroupware_resource_7(2047)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was: "" I was used to have the same issue, it was really annoing, it was solved after I removed all my calendar from Kontact (Korganizer). I'm telling this because Aaron said there was a bug in calendar integration that is solved; so perhaps installing the latest version of akonadi could solve this issue. |