Summary: | KScreen crashes when pressing the "switch displays button" | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | Jens Rutschmann <Jens.Rutschmann> |
Component: | kded | Assignee: | Alex Fiestas <afiestas> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | grave | CC: | dvratil, peshkoff |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 1.0 | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
debugging output during crash
terminal output |
Description
Jens Rutschmann
2013-03-28 21:18:02 UTC
Can you try with KScreen 0.1 RC1 ? I'm pretty sure we fixed this issue already. thanks ! Hi Alex, I did the following: - uninstalled live git versions of kscreen & libkscreen - installed 0.0.81 - setup loading using the dbus commands - reboot machine (monitor unplugged) - deleted user kscreen config files on VT - logged in to KDE - opened system settings -> kscreen is loading automatically - plugged in monitor -> nothing happened - press XF86Display -> nothing happened - in Konsole launched "kscreen-console outputs" -> ext monitor is switched on, desktop expands - pressed XF86Display -> crash, same backtrace for the crashing thread as above. Seems there are two separate issues here: 1) the crash when pressing XF86Display 2) Missing plugging events. Are those supposed to work with the nvidia binary driver at all? One more thing wrt. to plugging events: I kept "kscreen-console monitor" running in Konsole and there was nothing printed when plugging in / out the monitor. I suspect this should actually output something. (in reply to comment #2) > 2) Missing plugging events. Are those supposed to work with the nvidia binary driver at all? (In reply to comment #3) > One more thing wrt. to plugging events: > > I kept "kscreen-console monitor" running in Konsole and there was nothing > printed when plugging in / out the monitor. I suspect this should actually > output something. Works for me usually. On rare occasions it's necessary to run "xrandr" from another terminal manually to force X server to request current configuration from drivers. Or restart kscreen-console (we do the same query for current config as xrandr on startup). I have another problem with kded4, but looks like it's sooner of all related to this one. - almost same setup: kde 4.10.1 build from sources using gentoo packages - same utility causes problem at kde startup, but I get malloc() error from glibc instead segfault ~/.xsession-errors contains the following: startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... kbuildsycoca4(30001) KBuildSycoca::checkTimestamps: checking file timestamps kbuildsycoca4(30001) KBuildSycoca::checkTimestamps: timestamps check ok kbuildsycoca4(30001) kdemain: Emitting notifyDatabaseChanged () *** glibc detected *** kdeinit4: kded4 [kdeinit]: malloc(): memory corruption: 0x00000000013ccf10 *** We are going to need more feedback to fix this, please provide the following: -execute kdebugdialog and enable: kded, kscreen, ksrandr -kquitapp kded -kded4 -Reproduce the crash In the output you shoudl see text containing the word KSrandr, if you don't see it try to logout/login. Thanks ! Created attachment 79646 [details]
debugging output during crash
As requested I've reproduced the crash with debugging turned on.
I've attached the konsole history (with a lot of output from networkmanagement, kio and kmix removed).
Let me know if you need anything else. Btw. in kdebugdialog there was no 'kscreen' entry, just 'kscreen-console', so I've enabled that one.
The log should show traces from me pressing the switch displays button directly after enabling kscreen - without crashing (multiple times, there was no visible reaction).
The crash could be reproduced after I suspended and resumed and then pressed the button again (search for 'UPowerSuspendJob')
Thanks for looking into this,
Jens
Is it possible that you are docking your laptop? Can you please attach the output of: kscreen-console bug with each of your setup? Thanks Created attachment 80220 [details]
terminal output
Hi Alex,
attached is the full output from konsole, below are the commands i've executed for a short overview.
I could no longer reliably reproduce the crash, but I've update kernel to 3.9.4 and nvidia-drivers to 319.23 in the meantime. The black screen error no longer appears as well.
Concerning kscreen functionality, there were only visible changes when i launched "kscreen-konsole bug". There was no reaction at all when plugging in the vga connector.
Hope this helps anyway, let me know if you need more info.
--------------------------------------------------------------------
echo currently the external vga display is NOT attached
echo these kded modules are loaded right now:
qdbus org.kde.kded /kded org.kde.kded.loadedModules
echo now i am startin kscreen
qdbus org.kde.kded /kded org.kde.kded.loadModule kscreen
echo the laptop screen is working as usual, deskop is not expanded
kscreen-console bug
echo nothing changed so far, now i am attachting the external vga display
echo external display is attached, no visible change so far
kscreen-console bug
echo now the external display is switched on and the desktop is expanded and displayed correctly
kscreen-console bug
echo now i am detaching the external display again
echo display is detached, half of desktop is displayed on internal display, desktop is still expanded
kscreen-console bug
echo desktop is now resized to the internal display
echo attaching external screen again
echo as before, no change in desktop, external display still switched off
echo these kded modules are loaded right now:
qdbus org.kde.kded /kded org.kde.kded.loadedModules
echo now i will try the Fn+F7 hotkey
echo nothing happened, trying a few times more ...
echo nothing changed
xev
(killed xev using mouse)
kscreen-console bug
echo now external display is on, desktop expanded
echo after hitting Fn+F7 a few times it started to work, WTF ....
echo i using the button i can now cycle between internal-only, internal-clones-external (with the bigger resoultion of the ext.) and external-only
echo now only internal display is active, suspending ...
echo resumed ...
echo still only the internal display is active
echo pressing button again ...
echo -> cloned output
echo these kded modules are loaded right now:
qdbus org.kde.kded /kded org.kde.kded.loadedModules
echo seems something restarted kded ... maybe suspend ?
I'm 99% certain we fixed this bug in 46033acb774327e4b12ff182a314ce4ba9031b4d released with the latest RC. If you can reproduce the crash while using version 0.0.92 please feel free to reopen the bug. Thanks ! |