Summary: | Plasma desktop crash | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Pedro Brandao <pmbrandao> |
Component: | scriptengines | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | asraniel, pmbrandao |
Priority: | NOR | ||
Version First Reported In: | 4.7.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Pedro Brandao
2011-10-14 13:26:50 UTC
Created attachment 64517 [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
This is the stacktrace just after it crashed. This definitevely occurs after GCalendar trying to connect. This time the plasma-desktop recovered and is now running.
-- Backtrace (Reduced):
#6 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2077
#7 0x00007f3ccb56984e in QString::realloc (this=0x4105a68, alloc=9) at /usr/include/x86_64-linux-gnu/bits/string3.h:52
#8 0x00007f3ccb569e09 in utf16 (this=0x4105a68) at tools/qstring.cpp:4845
#9 QString::utf16 (this=0x4105a68) at tools/qstring.cpp:4841
#10 0x00007f3ccb56f861 in QString::toUcs4 (this=0x4105a68) at tools/qstring.cpp:3720
Thank you for this crash report and helping to improve our software. Unfortunately we were not able to work on this specific report yet. Nowadays the version this crash was reported against is no longer maintained and this makes it very difficult to work on this report as the source code might have changed and the information in the backtrace is no longer valid. Also it is quite likely that this problem got fixed in a later version. Crash reports are very often reported multiple times. If you are able to reproduce this crash with the latest version of KDE Plasma (4.10.3) please reopen this report and adjust the version information in the dropdown above and please also include a new backtrace as generated by the crash reporting tool. Please also make sure that the steps on how to reproduce the crash are precise and correct. Thank you! |