On Fri, Aug 23, 2019 at 10:30 AM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Mon, Aug 19, 2019 at 1:54 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello,
executed "dnf update" after about 15 days of inactivity.
Updates has brought in kernel 5.2.8-200.fc30.x86_64
But after reboot the system is not able to detect (in the sense of no monitor connection at all seen) when connecting a 24" Dell monitor using an usb-c to hdmi adapter on my laptop and then connecting an HDMI-to-dvi cable to the monitor, that I normally used before.
Tried to reboot two times without effect.
As soon as I restart with previous kernel 5.1.20-300.fc30.x86_64, external monitor detection and usage is ok again.
This is in default Gnome environment and Wayland.
Eg in gnome terminal I have:
$ loginctl show-session 2 -p Type
Type=wayland
and
$ echo $WAYLAND_DISPLAY
wayland-0

Anyone else with similar problems?
If you point me on how to get related log lines in journal in both working and not working configurations, I can get more info.
Seen on several threads that with Xwayland and gnome-shell not so easy to see startup log files...



[snip] 

In the mean time I opened this bugzilla:

I see at least two other new messages with problems related to external monitors... 

Unfortunately the problem still persisted across all kernel updates and also with latest kernel installed today: kernel-5.2.15-200.fc30.x86_64
Currently I'm forced to use the latest 5.1 kernel that I downloaded and used before updating to 5.2: kernel-5.1.20-300.fc30.x86_64
Verified also on 2 other external monitors with same effect. All 3 were Dell Monitors, even if quite different models, I don't know if this can make any difference
No feedback on bugzilla page yet and no other posters.. if anyone also has this kind of problem is invited to post there so to get more attention
Of course this is with i915 kernel module and possibly other ones, like nouveau and what used for Amd gpu, are working ok with external monitors and 5.2 kernels

Thanks,
 
Gianluca