Xfce Forum

Sub domains
 

You are not logged in.

#1 2013-11-02 18:58:47

n_t
Member
Registered: 2013-11-02
Posts: 6

xfsettingsd Unhappy with Monitor Resolution and Bombing Out

If I boot my laptop with a HDMI monitor plugged in XFCE will recognise the monitor and display the UI. However, it will reset at least my theme and keyboard settiings with what looks like the xfce defaults.

If I boot without plugging in the monitor, and then plug in the monitor once my user session has started, I can use ArandR to send output to the HDMI monitor and all my settings remain in-tact whilst the screen works perfectly. So for now I have a work around but I really want to fix it.

What I'd like is to know where I should be looking to diagnose a problem like this?

I am running a fully upto-date arch linux install running bare metal. Xfce was installed using the Arch Package Manager. My machine is a dell laptop running an i5 Sandy Bridge from around 2010.

Any help would be really appreciated. I did have a scan through the forums but could not find a similar post.

Last edited by n_t (2013-11-05 17:44:08)

Offline

#2 2013-11-04 17:38:27

n_t
Member
Registered: 2013-11-02
Posts: 6

Re: xfsettingsd Unhappy with Monitor Resolution and Bombing Out

I looked in the logs and found the following. The first few lines indicate that it wasn't able to match up the size of the plugged in monitor

Nov 04 17:34:26 nickT_Arch systemd[1]: Started Authorization Manager.
Nov 04 17:34:26 nickT_Arch slim[265]: (xfsettingsd:834): xfsettingsd-WARNING **: Unknown mode '1920x1080 @ 30.0' for output HDMI1.
Nov 04 17:34:26 nickT_Arch slim[265]: The program 'xfsettingsd' received an X Window System error.
Nov 04 17:34:26 nickT_Arch slim[265]: This probably reflects a bug in the program.
Nov 04 17:34:26 nickT_Arch slim[265]: The error was 'BadMatch (invalid parameter attributes)'.
Nov 04 17:34:26 nickT_Arch slim[265]: (Details: serial 143 error_code 8 request_code 140 minor_code 7)
Nov 04 17:34:26 nickT_Arch slim[265]: (Note to programmers: normally, X errors are reported asynchronously;
Nov 04 17:34:26 nickT_Arch slim[265]: that is, you will receive the error a while after causing it.
Nov 04 17:34:26 nickT_Arch slim[265]: To debug your program, run it with the --sync command line
Nov 04 17:34:26 nickT_Arch slim[265]: option to change this behavior. You can then get a meaningful
Nov 04 17:34:26 nickT_Arch slim[265]: backtrace from your debugger if you break on the gdk_x_error() function.)

It looks like the above causes xfsettingsd to crash. Because when I run it, I get the following:

(xfsettingsd:1508): xfsettingsd-WARNING **: Unknown mode '1920x1080 @ 30.0' for output HDMI1.

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 144 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.)

Last edited by n_t (2013-11-04 17:41:55)

Offline

Board footer

Powered by FluxBB