Hi folks!
We have a somewhat-worrying proposed blocker for F22:
https://bugzilla.redhat.com/show_bug.cgi?id=1218787
it appears that after a successful installation of Workstation on the affected system, GDM-on-Wayland fails to start correctly but also does not fall through (as it should) to GDM-on-X, leaving the user with a black screen and no obvious way to proceed. This is obviously a bad bug, but so far it has only been observed on one test system (a Macbook Pro 8,2) by one tester. A few other testers have tried to reproduce on other hybrid graphics systems, but have not been able to.
It would be very helpful to get some more data here. If anyone has a hybrid graphics laptop and can spare some space (or perhaps attach an external drive) for a test F22 install, can you please try installing F22 Workstation TC3 and creating a user:
https://dl.fedoraproject.org/pub/alt/stage/22_TC3/Workstation/x86_64/iso/Fed... Live-Workstation-x86_64-22-TC3.iso
then boot the installed system, and see if GDM appears correctly? Thanks.
Note there is a different bug which causes GDM-on-Wayland to flicker on some hardware:
https://bugzilla.redhat.com/show_bug.cgi?id=1218688
that's something different, and is a bit further along in the diagnosis/fix process, so we probably don't need further reports of that one (though once a fix arrives, it'd be good to have folks test it).
If you find you seem to be affected by the bug, please add your details to the report. If you test and find you're *not* affected by the bug - you see GDM properly - please reply to one of the mailing lists, so we can get some idea of the proportions of affected vs. non-affected testers. Thanks a lot for your help, folks!
Fedora-Live-Workstation-x86_64-22-TC3.iso installed without problems using an external USB drive on my Macbook Pro with 15-inch Retina Display. I logged on using GNOME with Wayland for the user created during installation - no problem.
That said, the system appears fragile, and network configuration looks like it will be a challenge. Some of that may be peculiar Apple hardware; even the wired Ethernet has issues. Still, this is much better than my last attempt with an early F22 Beta, which would not boot after installation.
POR was required after USB wi-fi and wired Ethernet (through Lightning connection dongle) plug events, which I suppose might be related to unsupported Apple hardware issues.
nm-connection-editor fails to save connection data with complaints like these:
[root@localhost rynx]# nm-connection-editor
(nm-connection-editor:2395): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
(nm-connection-editor:2395): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
(nm-connection-editor:2395): GLib-GObject-WARNING **: The property GtkTreeView:rules-hint is deprecated and shouldn't be used anymore. It will be removed in a future version. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
(nm-connection-editor:2395): GLib-GObject-WARNING **: The property GtkMisc:yalign is deprecated and shouldn't be used anymore. It will be removed in a future version.
(nm-connection-editor:2395): GLib-GObject-WARNING **: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
(nm-connection-editor:2395): GLib-GObject-WARNING **: The property GtkButton:xalign is deprecated and shouldn't be used anymore. It will be removed in a future version.
(nm-connection-editor:2395): GLib-GObject-WARNING **: The property GtkWidget:margin-left is deprecated and shouldn't be used anymore. It will be removed in a future version.
(nm-connection-editor:2395): GLib-GObject-WARNING **: The property GtkAlignment:left-padding is deprecated and shouldn't be used anymore. It will be removed in a future version. Error creating proxy: The connection is closed (g-io-error-quark, 18) Error creating proxy: The connection is closed (g-io-error-quark, 18) Error creating proxy: The connection is closed (g-io-error-quark, 18) Error creating proxy: The connection is closed (g-io-error-quark, 18) Error creating proxy: The connection is closed (g-io-error-quark, 18)
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi Security: Invalid Wi-Fi security
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi Security: Invalid Wi-Fi security
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi Security: Invalid Wi-Fi security
(nm-connection-editor:2395): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
(nm-connection-editor:2395): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi Security: Invalid Wi-Fi security
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi Security: Invalid Wi-Fi security
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi: 802-11-wireless.ssid: property is missing
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi Security: Invalid Wi-Fi security
** (nm-connection-editor:2395): WARNING **: Invalid setting Wi-Fi Security: Invalid Wi-Fi security
(nm-connection-editor:2395): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
(nm-connection-editor:2395): dconf-WARNING **: failed to commit changes to dconf: The connection is closed [root@localhost rynx]# nm-connection-editor
(nm-connection-editor:2428): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.
(nm-connection-editor:2428): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.
(nm-connection-editor:2428): GLib-GObject-WARNING **: The property GtkTreeView:rules-hint is deprecated and shouldn't be used anymore. It will be removed in a future version. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. [root@localhost rynx]#
On 14/05/15 01:01 PM, Adam Williamson wrote:
Hi folks!
We have a somewhat-worrying proposed blocker for F22:
https://bugzilla.redhat.com/show_bug.cgi?id=1218787
it appears that after a successful installation of Workstation on the affected system, GDM-on-Wayland fails to start correctly but also does not fall through (as it should) to GDM-on-X, leaving the user with a black screen and no obvious way to proceed. This is obviously a bad bug, but so far it has only been observed on one test system (a Macbook Pro 8,2) by one tester. A few other testers have tried to reproduce on other hybrid graphics systems, but have not been able to.
It would be very helpful to get some more data here. If anyone has a hybrid graphics laptop and can spare some space (or perhaps attach an external drive) for a test F22 install, can you please try installing F22 Workstation TC3 and creating a user:
https://dl.fedoraproject.org/pub/alt/stage/22_TC3/Workstation/x86_64/iso/Fed... Live-Workstation-x86_64-22-TC3.iso
then boot the installed system, and see if GDM appears correctly? Thanks.
Note there is a different bug which causes GDM-on-Wayland to flicker on some hardware:
https://bugzilla.redhat.com/show_bug.cgi?id=1218688
that's something different, and is a bit further along in the diagnosis/fix process, so we probably don't need further reports of that one (though once a fix arrives, it'd be good to have folks test it).
If you find you seem to be affected by the bug, please add your details to the report. If you test and find you're *not* affected by the bug - you see GDM properly - please reply to one of the mailing lists, so we can get some idea of the proportions of affected vs. non-affected testers. Thanks a lot for your help, folks!
I have a hybrid laptop AMD-Quad Core A10 Kaveri and Dual Radeon GPU. GDM on Wayland runs smoothly other than know issues like Drag and Drop. I think the issue is possibly on Intel based hybrid laptop. Prior to beta and thanks to the team work notably halfline, GDM on X bug was fixed.
-
Adam Williamson -
Luya Tshimbalanga -
Richard Ryniker