You are not logged in.
Hello,
I am using XFCE4 and Slim on my laptop and usually only use the laptop screen.
When I bring it to work I use an extra display and extend the desktop to it.
If I connect the screen before X starts, it expands on the two screens and I lose my keyboard shortcuts (although I still see them in the configuration panels) but not the custom keys I have set to switch desktops for example.
If I start on one screen, login to XFCE and then plug the second screen and set it up via nvidia-settings, I can use my keyboard shortcuts.
Any ideas on how to fix this?
Thanks!
Offline
A quick shot in the dark....When you start with both monitors connected, is "xfsettingsd" running? If it is, try restarting it:
killall xfsettingsd && xfsettingsd &
...and if not, start it up.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
xfsettingsd is indeed not started when logging in with dual screens.
But when trying to run it, I get an error:
$ xfsettingsd --no-daemon
The program 'xfsettingsd' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 133 error_code 8 request_code 140 minor_code 7)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
I'll restart slim with only one screen and see if I get the same error.
Offline
OK no need to restart slim to check that.
I disabled the second screen and started xfsettingsd without any error.
If I then enable the second screen, xfsettingsd continues running fine.
If I stop it, I can't start it again and get the error above.
$ pacman -Q xfce4-settings
xfce4-settings 4.10.1-1
I am using Archlinux and all packages are up-todate.
Also I don't see any error in the Xorg log.
Offline
OK so I found something searching the BadMatch issue : https://lists.pld-linux.org/mailman/pip … 51318.html
Turns out I just needed to modify /etc/xdg/autostart/xfsettingsd.desktop to execute xfsettingsd --sync by default.
Shouldn't that option be used by default for xfsettingsd?
Offline
Try using this command to start xfsettingsd in multi-monitor mode to see if it gives you more relevant debug info:
XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon
Edit: sorry, ninja'd.
Last edited by ToZ (2014-03-17 13:52:28)
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
OK so I found something searching the BadMatch issue : https://lists.pld-linux.org/mailman/pip … 51318.html
Turns out I just needed to modify /etc/xdg/autostart/xfsettingsd.desktop to execute xfsettingsd --sync by default.
Shouldn't that option be used by default for xfsettingsd?
Maybe file a bug report?
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
There isn't much more information:
$ XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon
xfce4-settings(xsettings): _XSETTINGS_S0 registered on screen 0
xfce4-settings(xsettings): 26 settings changed (serial=0, len=1020)
xfce4-settings(xsettings): resource manager (xft) changed (len=117)
The program 'xfsettingsd' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 132 error_code 8 request_code 140 minor_code 7)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Edit: And here is what I get with the --sync option:
$ XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon --sync
xfce4-settings(xsettings): _XSETTINGS_S0 registered on screen 0
xfce4-settings(xsettings): 26 settings changed (serial=0, len=1020)
xfce4-settings(xsettings): resource manager (xft) changed (len=117)
xfce4-settings(pointers): initialized xi 2.3
xfce4-settings(keyboards): initialized xkb 1.0
xfce4-settings(keyboards): set auto repeat on
xfce4-settings(keyboards): set key repeat (delay=500, rate=50)
xfce4-settings(keyboards): set numlock on
xfce4-settings(accessibility): stickykeys disabled
xfce4-settings(accessibility): slowkeys disabled
xfce4-settings(accessibility): bouncekeys disabled
xfce4-settings(accessibility): mousekeys disabled
xfce4-settings(keyboard-shortcuts): 18 shortcuts loaded
xfce4-settings(keyboard-layout): set model to "thinkpad60"
xfce4-settings(keyboard-layout): set layouts to "fr,us"
xfce4-settings(keyboard-layout): set variant to ","
xfce4-settings(fontconfig): monitoring 34 paths
xfce4-settings(workspaces): 4 desktop names set from xfconf
Last edited by MonsieurJax (2014-03-17 13:55:27)
Offline
Well I guess I should have started there
https://bugzilla.xfce.org/show_bug.cgi?id=10322
Thanks for the help, I'll just bump the bug report
Offline
[ Generated in 0.010 seconds, 7 queries executed - Memory usage: 555.48 KiB (Peak: 572.33 KiB) ]