Hello,
I have an Intel Skull NUC, model NUC6i7KYK, with Intel video adapter
00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics 580 (rev 09)
detailed specs here:
It is connected to a Dell U2515H:
It was initially installed with F29 (with Wayland disabled in /etc/gdm/custom.conf) and used resolution always being 2560x1440.
Almost when F30 was released I upgraded and no problems until today.
When powering on I see no user icons in gdm.
So I switched to sddm and lxdm and there I was able to see my users login, but both trying Gnome session and Mate session it seems I don't see the top bars.
While in Mate with Alt+F2 I opened a terminal window and executed xdpyinfo.
Strangely it reported a not possible resolution....
screen #0:
dimensions: 5120x1440 pixels (1354x381 millimeters)
resolution: 96x96 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0x162
depth of root window: 24 planes
dimensions: 5120x1440 pixels (1354x381 millimeters)
resolution: 96x96 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0x162
depth of root window: 24 planes
So I decided to force 2560x1440 with this file, named 00-monitor.conf and put into directory /etc/X11/xorg.conf.d
After reboot still gdm is not able to show me any user icons (perhaps it doesn't use the conf file), and again using lxdm and sddm and choosing Gnome session I don't see top bar and other things.
Instead, i can use without any problem Mate and now I can see the top bar and correctly use the session.
Opening xdpyinfo from a terminal I correctly get what forced:
screen #0:
dimensions: 2560x1440 pixels (677x381 millimeters)
resolution: 96x96 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0x162
depth of root window: 24 planes
dimensions: 2560x1440 pixels (677x381 millimeters)
resolution: 96x96 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
root window id: 0x162
depth of root window: 24 planes
Things above let me think about a problem in Gnome itself, impacting gdm too..
Yesterday evening while connected I updated as from this log, without rebooting:
And I think this update generated the problem, because this evening after booting I had it.
I tried to switch to a terminal and update again and I got these packages' updates:
and reboot but still the problem is here...
Anyone experimented this?
Thanks
Gianluca
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
