Hide Forgot
Description of problem: Running multiple X screens. Main is :1.0 and alt is :1.1 . Running Mate. If I run: DISPLAY=:1.1 xterm & marco dies, and the screen starts blinking rapidly until I then startup compiz (which is what I want on the main display, anyway). In older Fedoras, I could then just start marco or whatever on :1.1 ... this still doesn't work and marco just re-crashes. Version-Release number of selected component: marco-1.16.0-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: marco crash_function: gdk_window_has_impl executable: /usr/bin/marco global_pid: 25820 kernel: 4.8.15-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: 3 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (10 frames) #0 gdk_window_has_impl at gdkwindow.c:668 #1 _gdk_window_has_impl at gdkwindow.c:669 #2 gdk_x11_window_get_xid at gdkwindow-x11.c:5560 #3 meta_ui_create_frame_window at ui/ui.c:443 #4 meta_window_ensure_frame at core/frame.c:101 #5 meta_window_new_with_attrs at core/window.c:673 #6 meta_window_new at core/window.c:222 #7 event_callback at core/display.c:2253 #8 filter_func at ui/ui.c:281 #9 gdk_event_apply_filters at gdkeventsource.c:79
Created attachment 1237475 [details] File: backtrace
Created attachment 1237476 [details] File: cgroup
Created attachment 1237477 [details] File: core_backtrace
Created attachment 1237478 [details] File: dso_list
Created attachment 1237479 [details] File: environ
Created attachment 1237480 [details] File: exploitable
Created attachment 1237481 [details] File: limits
Created attachment 1237482 [details] File: maps
Created attachment 1237483 [details] File: mountinfo
Created attachment 1237484 [details] File: namespaces
Created attachment 1237485 [details] File: open_fds
Created attachment 1237486 [details] File: proc_pid_status
Created attachment 1237487 [details] File: var_log_messages
*** Bug 1484169 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.