Version-Release number of selected component: xfdesktop-4.13.2-20.fc29 Additional info: reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: xfdesktop crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/xfdesktop journald_cursor: s=2682d9519b3c4e818e5621611d2cad7c;i=2db21;b=61fb112fb1b84e20a03f6333af01c0ed;m=6111bf2e2d;t=57ac90ae9b4e5;x=deee4c109a4b3a9e kernel: 4.18.17-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_fundamentally_a at gtype.c:4023 #1 g_object_ref at gobject.c:3212 #2 g_task_new at gtask.c:698 #3 g_input_stream_real_read_async at ginputstream.c:1383 #4 g_input_stream_read_async at ginputstream.c:633 #5 xfce_backdrop_file_input_stream_ready_cb at xfce-backdrop.c:2013 #6 async_ready_callback_wrapper at ginputstream.c:532 #7 g_task_return_now at gtask.c:1148 #8 complete_in_idle_cb at gtask.c:1162 #14 gtk_main at gtkmain.c:1323
Created attachment 1506443 [details] File: backtrace
Created attachment 1506444 [details] File: cgroup
Created attachment 1506445 [details] File: core_backtrace
Created attachment 1506446 [details] File: cpuinfo
Created attachment 1506447 [details] File: dso_list
Created attachment 1506448 [details] File: environ
Created attachment 1506449 [details] File: exploitable
Created attachment 1506450 [details] File: limits
Created attachment 1506451 [details] File: maps
Created attachment 1506452 [details] File: mountinfo
Created attachment 1506453 [details] File: open_fds
Created attachment 1506454 [details] File: proc_pid_status
This bug was detected 8:33 AM PST 11/24/2018 and bug 1656579 was detected at 8:28 PM PST 11/24/2018. I just thought this close to 12 hours difference in detection was interesting.
Similar problem has been detected: This occurred a couple minutes after I logged in from xscreensaver. Other than that, I don't know what caused this to happen. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 240f7b40e-8779-43ac-b3be-fb414928b633 crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/xfdesktop journald_cursor: s=4fc33c98ac2f432e895d7159936df6f7;i=7d62;b=ed7d45e6519145199be6cdcc67d71074;m=801286c6c4;t=57ed2e2d8c67c;x=13eaba9ff2634463 kernel: 4.19.10-300.fc29.x86_64 package: xfdesktop-4.13.2-20.fc29 reason: xfdesktop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I am also getting this exact error regularly (2x daily) on my x86_64 system. I am running an AMD Ryzen 1800x. I have been running identical component versions on a ppc64le Power 8 system, multiple Arm32 instances, and several Arm64 instances, none of which generate this same system freeze and error.
Similar problem has been detected: I logged in a couple minutes before this issue occured from xscreensaver. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 240f7b40e-8779-43ac-b3be-fb414928b633 crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/xfdesktop journald_cursor: s=4fc33c98ac2f432e895d7159936df6f7;i=113f7;b=ed7d45e6519145199be6cdcc67d71074;m=e8f8abc085;t=57f3bc8fdc03e;x=526766727d6f3639 kernel: 4.19.10-300.fc29.x86_64 package: xfdesktop-4.13.2-20.fc29 reason: xfdesktop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: logging in with X2Go reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: xfdesktop crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/xfdesktop journald_cursor: s=9a0156b7822847678c6ce075498a19c0;i=19bcfe66;b=8e6cbe1ff9f9468aa2884bd090e46012;m=2499274b4b0;t=580b90ca1b6d9;x=2c02ab56637d6d83 kernel: 4.19.10-300.fc29.x86_64 package: xfdesktop-4.13.2-20.fc29 reason: xfdesktop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 6416
Similar problem has been detected: I just moved my mouse after turning on both my monitors before logging in with xscreensaver and I got a message that this crashed. Also, my multi-monitor settings in xfce4-display-settings had "Mirror displays" dashed and position of monitors changed. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 294659ae1-e268-44b2-beeb-b797419385c9 crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/xfdesktop journald_cursor: s=5cee89a16fe74a1d9b20ea325ac2e5fe;i=25f23;b=d7811a910f4245afb64fe2136cc23b50;m=136544be2f;t=58102dc5dceed;x=a7ffb6db6e7df508 kernel: 4.20.4-200.fc29.x86_64 package: xfdesktop-4.13.2-20.fc29 reason: xfdesktop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Crash occurs when x2goclient window is resized. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: xfdesktop --display :50.0 --sm-client-id 22cc09248-0003-4166-82f6-b6b96151fd11 crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/xfdesktop journald_cursor: s=8871f201a2f04d3d9b5d75289fc04437;i=1945d;b=88fc78f4b253484e81666c034308d4fe;m=44036c0a;t=58128a170f8bf;x=bc3b8acda43bd3bf kernel: 4.20.6-200.fc29.x86_64 package: xfdesktop-4.13.2-20.fc29 reason: xfdesktop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happened when another HDMI device switched on and the input from the HDMI switcher attached to both the PC and it switched to that device. Steps: 1. Another HDMI using device switched on (PS3 doing the usual late nite update check) 2. Causing the auto HDMI switch connected to that device and the PC to switch the outputted input from the PC to the PS3 3. That is exactly when the error occured. It IS repeatable in this case, it happened again when another HDMI device (PS4) turned on to do it's update some minutes later. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 2cc38781c-c5e1-40e9-b0ef-9ffaf8bc6f56 crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/xfdesktop journald_cursor: s=8666fd0e038a421cab115e0ff7288fde;i=c13c;b=047c7787541c4c2c952ac813d5a2cb91;m=7bbfe014e;t=581d917c3ad0d;x=c0bf56fab649e4e6 kernel: 4.20.7-200.fc29.x86_64 package: xfdesktop-4.13.2-20.fc29 reason: xfdesktop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
My guess is that the crash happens because xfdesktop thinks the screen isn't there anymore for some reason, or if in my case you're using an HDMI switch box and inputs get switched. I can manually cause the bug, just by manually switching my HDMI splitter to a different input. It doesn't really do anything other than to have the bug-reporting notification to pop up. One moment while I check some Nvidia settings... I just checked and it doesn't matter whether one has Auto syncing on or manually restricted to the single monitor in the Nvidia control panel.
After reading the other comments I remember now that I too had problably moved the mouse to wake the monitor which had gotten to sleep mode before. For some reason, when the screen comes back, the xfce4-display-settings application is always started.
I have the same issue as mentioned in comment #19 When I resize the desktop in x2go client, xfdesktop crashes and restarts. It doesn't happen every single time. It seems to need some applications to be open to happen. Partial stack trace: Stack trace of thread 21246: #0 0x00007eff33808e09 g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0) #1 0x00007eff337e9317 g_object_ref (libgobject-2.0.so.0) #2 0x00007eff338bea7e g_task_new (libgio-2.0.so.0) #3 0x00007eff33893fd3 n/a (libgio-2.0.so.0) #4 0x00007eff33892fdb g_input_stream_read_async (libgio-2.0.so.0) #5 0x0000556d48db330d n/a (xfdesktop) #6 0x00007eff33893d5e n/a (libgio-2.0.so.0) #7 0x00007eff338be834 n/a (libgio-2.0.so.0) #8 0x00007eff338be86d n/a (libgio-2.0.so.0) #9 0x00007eff336fc97b n/a (libglib-2.0.so.0) #10 0x00007eff3370006d g_main_context_dispatch (libglib-2.0.so.0) #11 0x00007eff33700438 n/a (libglib-2.0.so.0) #12 0x00007eff33700762 g_main_loop_run (libglib-2.0.so.0) #13 0x00007eff33f01b6d gtk_main (libgtk-3.so.0) #14 0x0000556d48dbb94b n/a (xfdesktop) #15 0x0000556d48dbbb6a n/a (xfdesktop) #16 0x00007eff336fc9d3 n/a (libglib-2.0.so.0) #17 0x00007eff336fe3a4 n/a (libglib-2.0.so.0) #18 0x00007eff33700118 g_main_context_dispatch (libglib-2.0.so.0) #19 0x00007eff33700438 n/a (libglib-2.0.so.0) #20 0x00007eff337004d0 g_main_context_iteration (libglib-2.0.so.0) #21 0x00007eff338d2d25 g_application_run (libgio-2.0.so.0) #22 0x0000556d48dab16c main (xfdesktop) #23 0x00007eff334ed413 __libc_start_main (libc.so.6) #24 0x0000556d48dab1ae _start (xfdesktop)
I've logged this at what I think is upstream: https://bugzilla.xfce.org/show_bug.cgi?id=15152
I'm not seeing these anymore with: xfdesktop-4.13.3-1.fc29.x86_64 Previously users connecting with x2go and resizing their screen would see this crash and xfdesktop restarting. With 4.13.3 I'm not seeing the crash/restart anymore.
xfdesktop-4.13.4-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-40d6024781
xfdesktop-4.13.4-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-40d6024781
xfdesktop-4.13.4-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.