| Summary: | Getting no lock when starting | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Patrick Carabin <Patrick.Carabin> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | Patrick.Carabin |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 4.11.11 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Patrick Carabin
2015-11-03 11:34:24 UTC
Created attachment 95417 [details]
New crash information added by DrKonqi
plasma-desktop (4.11.11) on KDE Platform 4.13.3 using Qt 4.8.6
- What I was doing when the application crashed:
starting Linux, and kDE, after some hours, Login as normal user
-- Backtrace (Reduced):
#7 QPainterPrivate::attachPainterPrivate (q=0xbffa9988, pdev=0x0) at painting/qpainter.cpp:245
#8 0x02c5928c in QPainter::QPainter (this=0xbffa9988, pd=0x0) at painting/qpainter.cpp:1504
#9 0x02d0c6b0 in QRasterWindowSurface::beginPaint (this=0xad9f458, rgn=...) at painting/qwindowsurface_raster.cpp:152
#10 0x02d28d16 in beginPaint (toCleanIsInTopLevelCoordinates=true, returnInfo=0xbffa9a18, windowSurface=0xad9f458, widget=<optimized out>, toClean=..., this=<optimized out>) at painting/qbackingstore.cpp:379
#11 QWidgetBackingStore::sync (this=this@entry=0xad9dec0) at painting/qbackingstore.cpp:1304
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham |