Summary: | Automatic Report after crash | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | karsten.bier |
Component: | kded | Assignee: | Daniel Vrátil <dvratil> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aacid, aaugusto, auxsvr, ccampeanu, chrismarine, dvratil, ethouris, heri+kde, marko.gabriel.cz, rasasi78, saiarcot895, tcicirello1974 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 1.0.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kscreen/9a4f36f6973d6f9d712b6b3b1ff30f868d9910b9 | Version Fixed In: | 5.2.2 |
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
karsten.bier
2013-11-03 11:30:00 UTC
*** Bug 328174 has been marked as a duplicate of this bug. *** Created attachment 85473 [details]
New crash information added by DrKonqi
kded4 (4.12.3) on KDE Platform 4.12.3 using Qt 4.8.4
- What I was doing when the application crashed:
Kded was not responding for some reason, after killing it Xorg froze using 100% CPU. kded crashed after restarting kdm and logging in.
-- Backtrace (Reduced):
#6 KScreen::Mode::size (this=0x0) at /usr/src/debug/libkscreen-1.0.2/src/mode.cpp:102
#7 0xaedf2891 in Generator::biggestOutput (this=0x9b77790, outputs=...) at /usr/src/debug/kscreen-1.0.2.1/kded/generator.cpp:474
[...]
#9 0xaedf5141 in Generator::laptop (this=this@entry=0x9b77790, outputs=...) at /usr/src/debug/kscreen-1.0.2.1/kded/generator.cpp:354
#10 0xaedf5ab3 in Generator::idealConfig (this=0x9b77790) at /usr/src/debug/kscreen-1.0.2.1/kded/generator.cpp:88
#11 0xaeded0cf in KScreenDaemon::applyIdealConfig (this=this@entry=0x9c3bbb0) at /usr/src/debug/kscreen-1.0.2.1/kded/daemon.cpp:118
Created attachment 86137 [details]
New crash information added by DrKonqi
kded4 (4.13.0) on KDE Platform 4.13.0 using Qt 4.8.6
- What I was doing when the application crashed:
I was starting KDE from the command line (sudo service kdm start). Everything seems to have started up correctly, except notifications are not in KDE, but instead in Ubuntu's Unity (so bubbles in the top-right corner appear for notifications).
-- Backtrace (Reduced):
#6 KScreen::Mode::size (this=this@entry=0x0) at /build/buildd/libkscreen-1.0.2/src/mode.cpp:102
#7 0x00007f31823cd249 in Generator::biggestOutput (this=this@entry=0x21f7130, outputs=...) at /build/buildd/kscreen-1.0.2.1/kded/generator.cpp:474
#8 0x00007f31823cdb90 in Generator::laptop (this=this@entry=0x21f7130, outputs=...) at /build/buildd/kscreen-1.0.2.1/kded/generator.cpp:354
#9 0x00007f31823cf9eb in Generator::idealConfig (this=0x21f7130) at /build/buildd/kscreen-1.0.2.1/kded/generator.cpp:88
#10 0x00007f31823c7307 in KScreenDaemon::applyIdealConfig (this=this@entry=0x20acda0) at /build/buildd/kscreen-1.0.2.1/kded/daemon.cpp:118
*** Bug 333839 has been marked as a duplicate of this bug. *** *** Bug 333380 has been marked as a duplicate of this bug. *** FWIW this is not so hard to reproduce if while starting Plasma (i.e. while the splash screen with icons is there) i switch back and forth a few times between X and a VT. Created attachment 87647 [details]
New crash information added by DrKonqi
kded4 (4.11.5) on KDE Platform 4.11.5 using Qt 4.8.5
- What I was doing when the application crashed:ç
The laptop was starting, the I log into the KDE wm and the service crashed
-- Backtrace (Reduced):
#6 KScreen::Mode::size (this=this@entry=0x0) at /usr/src/debug/libkscreen-1.0.2/src/mode.cpp:102
#7 0x00007f87b6b415f9 in Generator::biggestOutput (this=this@entry=0x1e8d900, outputs=...) at /usr/src/debug/kscreen-1.0.2.1/kded/generator.cpp:474
#8 0x00007f87b6b41f50 in Generator::laptop (this=this@entry=0x1e8d900, outputs=...) at /usr/src/debug/kscreen-1.0.2.1/kded/generator.cpp:354
#9 0x00007f87b6b43ddb in Generator::idealConfig (this=0x1e8d900) at /usr/src/debug/kscreen-1.0.2.1/kded/generator.cpp:88
#10 0x00007f87b6b3b6b7 in KScreenDaemon::applyIdealConfig (this=this@entry=0x1d404d0) at /usr/src/debug/kscreen-1.0.2.1/kded/daemon.cpp:118
Bump here with kdelibs 4.13.3 and kscreen 1.0.2 on Debian sid. Same backtrace. *** Bug 337939 has been marked as a duplicate of this bug. *** *** Bug 340492 has been marked as a duplicate of this bug. *** *** Bug 340631 has been marked as a duplicate of this bug. *** This should be fixed with the KScreen 1.0.5 release. Can you confirm? Git commit 9a4f36f6973d6f9d712b6b3b1ff30f868d9910b9 by Dan Vrátil. Committed on 06/03/2015 at 13:30. Pushed by dvratil into branch 'Plasma/5.2'. KDED: Make Generator maximally fool-proof This change adds lots of checks (and asserts for devs) on validity of the configs, outputs and modes and makes sure that we never try to dereference a null pointer from outputs or modes. Also renames some variables to make the code cleaner and easier to understand. Related: bug 326499, bug 326120, bug 33716 FIXED-IN: 5.2.2 M +183 -84 kded/generator.cpp M +9 -7 kded/generator.h http://commits.kde.org/kscreen/9a4f36f6973d6f9d712b6b3b1ff30f868d9910b9 *** Bug 343792 has been marked as a duplicate of this bug. *** |