Hello Everyone, I've been looking at updating my two computers from F42 to F43 Beta. I managed to get one done but have hit a few snags. I've looked for some bugs but haven't found any so figured I'd check in here first.
1. First things, when using the dnf system-upgrade method, both devices failed with Problem: installed package gnome-classic-session-xsession-48.3- 1.fc42.noarch requires gnome-classic-session = 48.3-1.fc42, but none of the providers can be installed - gnome-classic-session-48.3-1.fc42.noarch does not belong to a distupgrade repository - problem with installed package I don't know if I manually installed that myself but when I go to remove it, it lists gnat@iridium:~$ sudo dnf remove gnome-classic-session Package Arch Version Repository Size Removing: gnome-classic-session Removing dependent packages: gnome-classic-session-xsession Removing unused dependencies: gnome-shell-extension-apps-menu gnome-shell-extension-common gnome-shell-extension-launch-new-instance gnome-shell-extension-places-menu gnome-shell-extension-window-list Seems maybe important but I don't know. Is this a bug or should I just remove it? If it is a bug, I didn't find one filed already, but I can file one against that component. 2. One of the devices, I then turned to the Software app to do the upgrade. That happened to work. However, because of the issue with dracut making much larger initrd files, the creation of that file failed silently and the system wouldn't boot. I could boot using the older F42 kernels and removed one of them and then ran dracut manually to get the F43 kernel bootable. I don't know if a bug should be filed against some component when the kernel being installed can't get an initrd built. Should that be handled more gracefully? 3. In F43, there are issues with keyboard focus. When hitting the "windows" key, I've become accustomed to being able to just start typing and it starts searching immediately. Now when the system first boots/logs in or when hitting the window key, typing does nothing without using the mouse to target the input search field at the top of the screen. Is this a known bug? I wasn't sure how to find it as I don't really know what component is at fault there. Thanks in advance for anyone who responds to help on these issues. Sincerely, -- Nathanael -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
