Registered Member
|
Hi,
when I attach or disconnect a monitor, no configuration dialog shows up. Only when I open the system settings->display or run xrandr from command line, the configure dialog shows up. I have an Intel 945 integrated graphics card and I am running X.Org X Server 1.7.6 on a current Arch Linux with KDE SC 4.4.3 from Chakra repositories. Also, when I listen for a dbus signal from Kephal, either of those signals (screenAdded, screenRemoved) is emitted only after opening the display configuration or running xrandr as mentioned above. Any ideas as to what is causing that delay? |
Administrator
|
Interesting. Do you keep "krandrtray" running?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
No, normally I don't have it running. I have tried it today.
When I have everything setup properly and disconnect the external monitor while running krandrtray, no configuration dialog shows up. After reconnecting, my external monitor is back in the previous state. However if I disconnect, right click on krandrtray (I do not have to select anything in the menu, opening the menu is enough), screen flickers a bit. Now if I reconnect the external monitor, plasma desktop does not seem to be available on the other screen (no wallpaper, unable to open a context menu), my cursor can however go there anyway (I can see it on the external monitor). Again, if I right click krandrtray, wallpaper and the rest of my desktop does show up on the external monitor. So to sum it up, instead of removing a screen, it just removes plasma from the screen and it does so only after right-clicking krandrtray. This behavior might be related to the fact, that the coordinates of the external monitor are (0,0) while the notebook lcd is (0,1024) (lcd is below the external monitor). Oh, one more interesting finding. Left clicking krandrtray while having external monitor connected, disables the external monitor (a mouse cursor still can escape the notebook lcd, the external monitor however receives no signal). |
Administrator
|
Ok, it certainly seems as if your system is either not sending KDE the events ( intel driver bug ), or there is a bug in KDE.
Unfortunately I don't know how Kephal monitors the system for changes such as new monitors...
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]