Description of problem: Not sure about the root cause, it just happened while my session was starting in Xfce... Version-Release number of selected component: xfce4-settings-4.10.1-2.fc20 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: xfsettingsd --display :0.0 --sm-client-id 258d08f6a-6fd8-4cc6-b7e5-879d8193abec crash_function: handle_error executable: /usr/bin/xfsettingsd kernel: 3.11.0-0.rc1.git3.1.fc20.x86_64 runlevel: N 5 uid: 1005 Truncated backtrace: Thread no. 1 (8 frames) #4 handle_error at xcb_io.c:213 #5 handle_response at xcb_io.c:325 #7 _XiGetExtensionVersionRequest at XGetVers.c:93 #8 _XiGetExtensionVersion at XGetVers.c:116 #9 XGetExtensionVersion at XGetVers.c:71 #10 xfce_pointers_helper_init at pointers.c:129 #11 g_type_create_instance at gtype.c:1868 #12 g_object_new_internal at gobject.c:1743 Potential duplicate: bug 867455
Created attachment 777130 [details] File: backtrace
Created attachment 777131 [details] File: cgroup
Created attachment 777132 [details] File: core_backtrace
Created attachment 777133 [details] File: dso_list
Created attachment 777134 [details] File: environ
Created attachment 777135 [details] File: limits
Created attachment 777136 [details] File: maps
Created attachment 777137 [details] File: open_fds
Created attachment 777138 [details] File: proc_pid_status
Created attachment 777139 [details] File: var_log_messages
this might be related to https://bugzilla.redhat.com/show_bug.cgi?id=867455 at fc18 and upstream: https://bugzilla.xfce.org/show_bug.cgi?id=9680
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
Changed bios to use nv PCIe as master gpu vs onboard Intel 4000 to resolve multi-head no display problem. Now multi-head works but xfce setting crashes after login. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: xfsettingsd crash_function: handle_error executable: /usr/bin/xfsettingsd kernel: 3.11.10-300.fc20.x86_64 package: xfce4-settings-4.10.1-3.fc20 reason: Process /usr/bin/xfsettingsd was killed by signal 5 (SIGTRAP) runlevel: 3 5 type: CCpp uid: 1000
This is surely related to dual screen setting.
Another user experienced a similar problem: During startup of xfce at boot time, this crash occured reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: xfsettingsd crash_function: handle_error executable: /usr/bin/xfsettingsd kernel: 3.14.4-200.fc20.x86_64 package: xfce4-settings-4.10.1-3.fc20 reason: xfsettingsd killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Yes, I was also running on a dual screen setup.
Another user experienced a similar problem: abrt message happened at startup. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: xfsettingsd --display :0.0 --sm-client-id 280d640d9-67cd-4d4b-b723-26c4b892d548 crash_function: handle_error executable: /usr/bin/xfsettingsd kernel: 3.14.5-200.fc20.x86_64 package: xfce4-settings-4.10.1-3.fc20 reason: xfsettingsd killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
From what I have noticed, this happens everytime when I boot with laptop in docking station with external monitor connected. When I have removed laptop from docking station (aka disconnected external monitor) and loged out and in, it did not happened.
This bug occurs every time it is used fxce desktop and an external display is plugged to the computer. In this case, the feature "click by touching the touchpad" is disabled and can no longer be activated.
I tried to manually reinit the xfsettings daemon and got: [sbunciak@sbunciak ~]$ xfsettingsd --replace [sbunciak@sbunciak ~]$ (xfsettingsd:2479): Gdk-ERROR **: 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 142 error_code 8 request_code 139 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.)
For me it works when running "xfsettingsd --sync". So debugging it may not be as easy as the message suggests...
abrt showed this https://bugzilla.redhat.com/show_bug.cgi?id=1169347 as duplicity
Just ran into this on a (mostly) fresh Fedora 21 install after I rebooted after installing the propietary nvidia driver. I also have a dual-head setup, although I almost always leave my 2nd screen disabled. I'm guessing this might have something to do with display output enumeration?
I forgot to add; - This crash kept occuring every time on login - When I created a new user and logged in with that, the bug did not appear at all - I was able to stop the crash from happening on my normal user account by fiddling with my display settings (toggling them on and off) and then manually starting xfsettingsd, I think, I'm not sure what I did and in what order exactly, but it did stop the crash from happening. One remaining issue is that the display names in the display settings dialog are swapped now, if I toggle the "Use this output" setting for my "Dell Inc. 24\"" display, the Samsung display gets toggled instead of my Dell display
can we have the latest and greatest XFCE4.12 please pretty please ? they mention better support for displays here : http://www.xfce.org/download/changelogs/4.12 I will happily test with 4k and 2560x1440 monitors connected ;)
We are busy integrating it into rawhide now and soon hope to land it in f22. After that we will see if we can make a f21 update that is not disruptive. Testing in rawhide and f22 very welcome.
I'm reestructuring my hardwares so for while I'm only running F21 on physical hosts, rawhide only on VMs. Also I can't remember if I reported this bug against an old macbook (dvi) or a dell laptop(hdmi or vga), I need to double check. I'll keep this bug in my list and I will provide an update soon.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.