Created attachment 901851 [details] Traceback at the crash point $ rpm -qf /usr/bin/mutter /usr/bin/Xvnc /usr/bin/vncviewer /usr/bin/xterm mutter-3.10.4-2.fc20.x86_64 tigervnc-server-minimal-1.3.0-14.fc20.x86_64 tigervnc-1.3.0-14.fc20.x86_64 xterm-297-1.fc20.x86_64 $ Xvnc -extension RANDR -geometry 800x600 -rfbauth ~/.vnc/passwd :14 & $ vncviewer -passwd ~/.vnc/passwd :14 & $ DISPLAY=:14 xterm& Now inside the terminal: $ mutter Xlib: extension "RANDR" missing on display ":14". Xlib: extension "RANDR" missing on display ":14". Xlib: extension "RANDR" missing on display ":14". Xlib: extension "RANDR" missing on display ":14". Xlib: extension "RANDR" missing on display ":14". Xlib: extension "RANDR" missing on display ":14". Segmentation fault (core dumped) As to why one would want to disable the RANDR extension... if the extension is present then mutter immediately resizes the Xvnc session to 1920x1200 which is somewhat unfriendly.
I have also encountered this issue on Fedora 20. The reason I was disabling xrandr was because I have a 4K monitor and wanted to run it as a single screen at 60Hz rather than 2 separate screens.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.
$ rpm -qf /usr/bin/mutter /usr/bin/Xvnc /usr/bin/vncviewer /usr/bin/xterm mutter-3.16.2-1.fc22.x86_64 tigervnc-server-minimal-1.4.3-8.fc22.x86_64 tigervnc-1.4.3-8.fc22.x86_64 xterm-314-1.fc22.x86_64 Still crashes on F22. It crashes at: center_pointer (backend=0x61b0b0 [MetaBackendX11]) at backends/meta-backend.c:104 104 meta_backend_warp_pointer (backend, because meta_monitor_manager_get_monitor_infos() returns NULL and it's trying to dereference that.
Crashes on RV100 QY [Radeon 7000/VE] on F23 too with mutter-3.17.90-1.fc23.x86_64 (see https://retrace.fedoraproject.org/faf/problems/1097750/)
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
$ rpm -qf /usr/bin/mutter /usr/bin/Xvnc /usr/bin/vncviewer /usr/bin/xterm mutter-3.20.3-1.fc24.x86_64 tigervnc-server-minimal-1.6.0-6.fc24.x86_64 tigervnc-1.6.0-6.fc24.x86_64 xterm-323-1.fc24.x86_64 Crashes at: center_pointer (backend=0x5555557728d0) at backends/meta-backend.c:113 113 primary->rect.y + primary->rect.height / 2); same reason as before.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
Updating bug to F26 $ rpm -q mutter mutter-3.24.4-1.fc26.x86_64 Thread 1 "mutter" received signal SIGSEGV, Segmentation fault. center_pointer (backend=0x55555576d0e0) at backends/meta-backend.c:133 133 primary->rect.y + primary->rect.height / 2);
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.