| Summary: | Blank screen when connect through VNC with gnome | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Aaron Lu <aaron.lwe> |
| Component: | wayland | Assignee: | Owen Taylor <otaylor> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | ajax, antonio.montagnani, fmuellner, otaylor, petasisg |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:19:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Aaron Lu
2016-11-25 02:10:42 UTC
I should probably also list wayland related package information: [aaron@xps13 ~]$ rpm -qa |grep wayland libwayland-server-1.12.0-1.fc25.x86_64 ibus-wayland-1.5.14-3.fc25.x86_64 mesa-libwayland-egl-12.0.3-3.fc25.x86_64 libwayland-cursor-1.12.0-1.fc25.x86_64 xorg-x11-server-Xwayland-1.19.0-0.8.rc2.fc25.x86_64 gnome-session-wayland-session-3.22.1-2.fc25.x86_64 libwayland-client-1.12.0-1.fc25.x86_64 It seems to be the same problem as: https://fedoraproject.org/wiki/Common_F25_bugs#vino-crash-wayland If so, feel free to close this bug and I'll use Xorg to work around this issue. BTW, the below messages seem to be emitted when vnc client established the vnc session. [78563.998626] show_signal_msg: 183 callbacks suppressed [78563.998632] gnome-session-f[24470]: segfault at 0 ip 00007f17ecf9b879 sp 00007fff2fcbb0c0 error 4 in libgtk-3.so.0.2200.5[7f17eccbd000+6f6000] I am also having the same problem, gnome does not start under tigervnc. I have tried various things, as described here: http://forums.fedoraforum.org/showthread.php?t=312691 The problem seems to be gnome-shell, which does not start. Individual applications seem to work. gnome-shell writes on terminal: /usr/bin/gnome-shell -r (gnome-shell:3463): Gjs-WARNING **: JS ERROR: Error: Argument 'string' (type utf8) may not be null _pack_variant@resource:///org/gnome/gjs/modules/overrides/GLib.js:104 _pack_variant@resource:///org/gnome/gjs/modules/overrides/GLib.js:151 @resource:///org/gnome/gjs/modules/overrides/GLib.js:261 _proxyInvoker@resource:///org/gnome/gjs/modules/overrides/Gio.js:78 _makeProxyMethod/<@resource:///org/gnome/gjs/modules/overrides/Gio.js:124 LoginManagerSystemd<.getCurrentSessionProxy@resource:///org/gnome/shell/misc/loginManager.js:123 wrapper@resource:///org/gnome/gjs/modules/lang.js:178 ScreenShield<._init@resource:///org/gnome/shell/ui/screenShield.js:533 wrapper@resource:///org/gnome/gjs/modules/lang.js:178 _Base.prototype._construct@resource:///org/gnome/gjs/modules/lang.js:110 Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/lang.js:213 _initializeUI@resource:///org/gnome/shell/ui/main.js:167 start@resource:///org/gnome/shell/ui/main.js:125 @<main>:1 ** Message: Execution of main.js threw exception: JS_EvaluateScript() failed And I also have the segfault of libgtk, as already mentioned. (In reply to George Petasis from comment #4) > The problem seems to be gnome-shell, which does not start. Individual > applications seem to work. gnome-shell writes on terminal: > > /usr/bin/gnome-shell -r > > [...] > > LoginManagerSystemd<.getCurrentSessionProxy@resource:///org/gnome/shell/misc/ > loginManager.js:123 This error is due to XDG_SESSION_ID not being set. On a system where logind is used for session management, this should not happen. 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. |