Fedora Account System
Red Hat Associate
Red Hat Customer
I have Fedora40 and Fedora41, Gnome (Wayland) My terminal is PC105, Canadian French layout The problem began with F40 With Wayland, I can let the system timeout and lock the keyboard, and slightly thereafter, power suspend takes place. If the suspend interval is 15 minutes(for example), and I touch the keyboard in within the 15 minutes suspend, I will likely recover all - If however, the timeout following a suspend exceeds the suspend value, and I touch the keyboard to restore the system, all but the terminal will repower. NO TERMINAL. The system works with X11 My config X370 8 core cpu, 16gigs ram, current F40 or F41(Rawhide), using Wayland. If I switch to x11, there is absolutely no problem. Terminal and keyboard and system resume as anticipated. My keyboard layout is Canadian French, (Microsoft device). Reproducible: Always Steps to Reproduce: 1. Please read description 2. 3. Actual Results: Terminal lockup after suspend with Wayland, but not with X11 Expected Results: X11 type of power resume after suspend. Read description
Further to the above The GPU is: AMD ATI Radeon RX 580 2048SP With Xorg and Fed40, there is no issue. With Wayland, the return from suspend becomes a reboot Fedora Rawhide 41 is Wayland, even though the login interface icon selected is xorg.
Hi Adam J This is my post on the Fedoraforum.org website. I am using Rawhide(F41 in xorg mode), However, with Fedora 40, and Rawhide, if I select Wayland as the interface, I am not able to restart my video adapter if I let the system do a "standby timeout". What I have ended up having to do is "hitting the old "system reset button" to force a reboot. Both Fed40 and Fed41, with xorg option, on my hardware work flawlessly. Is xorg going to be wiped from Fedora Rawhide? (F41) Some other info Standard 1920x1080 6o fps interface. Graphics AMD Radeon "RX 580 2048SP"
Wayland is just a protocol specification in XML and the low-level C library that deals with the protocol. This issue here is a bug not with the protocol itself but with either your compositor or desktop environment's implementation of the Wayland protocol and surrounding functionality. Which desktop environment do you use so we can reassign appropriately?
Ahm my bad, comment 0 says GNOME. So the issue is that your terminal anish after a suspend, is that correct? Can you plase attach the journalct logs, most likely the terminal process died.
I am using Gnome Fedora 40 and likewise Gnome on Rawhide (Fedora 41). Salut Olivier. English, or French for posts. Olivier, would you be more specific about the journaltctl logs. Location and name. I am not a system level admin, but I do write code in C. You have my email for direct contact. It will be more expedient to communicate with test files for me to try, by using direct contact.
I will setup a KDE environment if that will be more useful. (Rawhide KDE exclusive).
Olivier mon courriel est chez yahoo.com. Utilizez tout en miniscule: mon nom du famille, suivi par 'l' .
I'd rather we keep the communication in English and through bugzilla for reference (that might help others facing the same issue). What I am after is the output of the the journalctl command taken on the system after the issue occurs. For example: 1/ Reboot your system (so we start afresh) 2/ Start a terminal 3/ Suspend you system 4/ Resume (to reproduce the issue) 5/ Run the command: journalctl -b | xz - > journalctl-b.xz hopefully, that will give some indication as to where the issue lies.
Salut Olivier Voici quelques informations supplementaires. I installed Suse Tumbleweed -- same problem. Monitor will not unlock. Suse leap156 (latest version) -- no issue. Fedora 39 had no Wayland issue with monitor unlocking, nor does SUSE leap156 Since my graphics card works with x11, I am almost 100% certain the issue is with Wayland. Bonne Journée
Saw your comment to me after I responded. Will respond with info requested within 12 hrs.
Created attachment 2037592 [details] Olivier requested attachment created as: Journalctl journalctl -b | xz - > journalctl-b.xz As requested journalctl -b | xz - > journalctl-b.xz journalctl -b.xz
One more (trivial comment). With the gnome right corner powrswitch menu suspend/Restart/Poweroff/logout. Selecting suspend works immediately to create the problem The logfile was obtained from selecting suspend from that menu.
Hello Olivier Yesterday, There was an update of the kernel for Fedora 40. Following some testing of this update to kernel: 6.9.4.200.fc40x86_64 . A fix appeared to be included therein. My testing has been successful. The suspend lockout issue I report appears resolvd. I will wait a few days of testing and if I have no other issues, I will close this issue Thank you for your help. I sincerely appreciate your efforts. Leslie
The same bug applies to Rawhide. I will be checking it out as well. L.
This bug is fully resolved with Fedora40, As of the 20240618 Issue remains with Fedora 41 Rawhide, also as of 20240618
Today is 1 July 2024 This bug, as mentioned in post precedent, was resolved for Fedora 40. I am testing with Fedora 41 Rawhide, and the bugfix has not been implemented with Rawhide 41. Again, symptoms. Logout from a Rawhide session. Wait until the suspend occurs (or signal suspend). on my system, with suspend, power to terminal is removed. but on activating a mouse or keypress, to exit suspend, terminal power is not restored. It requires a reboot. Please check with Olivier Fourdan about his findings.
Humm, I cannot find any obvious issue with the journalctl logs provided. It seems GDM starts as Wayland but the user session is running Xorg. Anyhow, if the behavior varies with the version for the kernel, chances are this could be kernel indeed, even though I fail to see any obvious kernel problem reported in the journal. So, just to be sure if I understand correctly, the issue occurs with the GDM login screen, once suspended and resumed, the display does not light up? By terminal, you mean the monitor? Does it help to switch to a text console (ctrl-alt-F4 for example) and back?
Hi Olivier I am testing Rawhide/gnome, current version. The issue is with Rawhide, not with Gnome 40 To check further, I will do a "clean fresh Rawhide" installation to determine if the issue is still open. If it works, I will close this bug report I will use Fedora-Workstation-Live-x86_64-Rawhide-20240704.n.0.iso
Olivier, Thank you for following up. The bug fix that was incorporated into Fedora 40, is now in Rawhide. This is no longer an issue. I am marking this closed. Oh yes, by the way, the graphics card is from AMD. and it may have been a contributor to the issue.