Hi, Which configuration file identifies which display manager is being used, and which configuration file identifies which desktop that dm will launch? The issue I have is, I have the Fedora Astronomy spin at F32 level. I think it is starting SDDM at boot time and defaulting to start KDE. When I put on the system update two updates ago, the "start menu" refused to display any entries when clicked on. There was a subsequent system update after that, and when I put that on KDE refused to start, so in order to get a running system I eventually got the desktop to set its desktop drop down to Gnome (Wayland), and was able to get Gnome to eventually start. The issue this caused is now the desktop drop down will not show any entries other then Gnome (Wayland) to be able to try and start KDE again. I am running F32 in a Windows 10 hosted Virtualbox VM.
regards, Steve
On 04/11/2020 17:24, Stephen Morris wrote:
Hi, Which configuration file identifies which display manager is being used, and which configuration file identifies which desktop that dm will launch? The issue I have is, I have the Fedora Astronomy spin at F32 level. I think it is starting SDDM at boot time and defaulting to start KDE. When I put on the system update two updates ago, the "start menu" refused to display any entries when clicked on. There was a subsequent system update after that, and when I put that on KDE refused to start, so in order to get a running system I eventually got the desktop to set its desktop drop down to Gnome (Wayland), and was able to get Gnome to eventually start. The issue this caused is now the desktop drop down will not show any entries other then Gnome (Wayland) to be able to try and start KDE again. I am running F32 in a Windows 10 hosted Virtualbox VM.
To see what Display Manager you're running.....
systemctl status display-manager
What desktops are available to sddm and other display managers are located in
/usr/share/xsessions and /usr/share/wayland-sessions
--- The key to getting good answers is to ask good questions.
On 4/11/20 10:25 pm, Ed Greshko wrote:
On 04/11/2020 17:24, Stephen Morris wrote:
Hi, Which configuration file identifies which display manager is being used, and which configuration file identifies which desktop that dm will launch? The issue I have is, I have the Fedora Astronomy spin at F32 level. I think it is starting SDDM at boot time and defaulting to start KDE. When I put on the system update two updates ago, the "start menu" refused to display any entries when clicked on. There was a subsequent system update after that, and when I put that on KDE refused to start, so in order to get a running system I eventually got the desktop to set its desktop drop down to Gnome (Wayland), and was able to get Gnome to eventually start. The issue this caused is now the desktop drop down will not show any entries other then Gnome (Wayland) to be able to try and start KDE again. I am running F32 in a Windows 10 hosted Virtualbox VM.
To see what Display Manager you're running.....
systemctl status display-manager
What desktops are available to sddm and other display managers are located in
/usr/share/xsessions and /usr/share/wayland-sessions
Thanks Ed, that is exactly what I was looking for. Using systemctl I was able to change the desktop to LightDM, and while doing this found it is not a good idea to use systemctl to stop the current DM before enabling and starting the new DM. I've also used the dnf group install to reinstall the KDE Plasma Workspaces, KDE Applications, KDE multimedia and KDE Office groups to see if that rectifies the KDE issues. I also had desktop icons in KDE for Thunderbird Daily and Firefox Nightly and whatever the updates were that caused the KDE issues also corrupted those two desktop entries so that they would not start the corresponding applications.
regards, Steve
The key to getting good answers is to ask good questions.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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/users@lists.fedoraproject.org
On 5/11/20 2:07 pm, Stephen Morris wrote:
On 4/11/20 10:25 pm, Ed Greshko wrote:
On 04/11/2020 17:24, Stephen Morris wrote:
Hi, Which configuration file identifies which display manager is being used, and which configuration file identifies which desktop that dm will launch? The issue I have is, I have the Fedora Astronomy spin at F32 level. I think it is starting SDDM at boot time and defaulting to start KDE. When I put on the system update two updates ago, the "start menu" refused to display any entries when clicked on. There was a subsequent system update after that, and when I put that on KDE refused to start, so in order to get a running system I eventually got the desktop to set its desktop drop down to Gnome (Wayland), and was able to get Gnome to eventually start. The issue this caused is now the desktop drop down will not show any entries other then Gnome (Wayland) to be able to try and start KDE again. I am running F32 in a Windows 10 hosted Virtualbox VM.
To see what Display Manager you're running.....
systemctl status display-manager
What desktops are available to sddm and other display managers are located in
/usr/share/xsessions and /usr/share/wayland-sessions
Thanks Ed, that is exactly what I was looking for. Using systemctl I was able to change the desktop to LightDM, and while doing this found it is not a good idea to use systemctl to stop the current DM before enabling and starting the new DM. I've also used the dnf group install to reinstall the KDE Plasma Workspaces, KDE Applications, KDE multimedia and KDE Office groups to see if that rectifies the KDE issues.
The reinstall of all these KDE groups did not rectify the KDE issue, so I've uninstalled all the KDE groups and I'll start with the KDE Plasma Workspace group first to see how that goes, although having uninstalled all the KDE Groups that were installed the Konsole app was still installed, so I'm not sure all of KDE has actually been uninstalled.
I also had desktop icons in KDE for Thunderbird Daily and Firefox Nightly and whatever the updates were that caused the KDE issues also corrupted those two desktop entries so that they would not start the corresponding applications.
It wasn't only the icons that were corrupted, the actual applications were as well. I've reinstalled those and got access back to all my mails again which was fortunate because I needed them to pay a bill.
regards, Steve
regards, Steve
The key to getting good answers is to ask good questions.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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/users@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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/users@lists.fedoraproject.org
On 05/11/2020 11:07, Stephen Morris wrote:
found it is not a good idea to use systemctl to stop the current DM before enabling and starting the new DM.
For future reference, the best way to change to a different DM is to use
systemctl --force enable (DM to switch to)
Then reboot.
--- The key to getting good answers is to ask good questions.
On 5/11/20 10:50 pm, Ed Greshko wrote:
On 05/11/2020 11:07, Stephen Morris wrote:
found it is not a good idea to use systemctl to stop the current DM before enabling and starting the new DM.
For future reference, the best way to change to a different DM is to use
systemctl --force enable (DM to switch to)
Thanks Ed, I didn't know about that option. I finally got all of KDE removed, and then installed the KDE Plasma Workspaces Group but that did not rectify the KDE issue. I got a notification that F33 was available so I upgraded to F33, found that the install of F33 did not upgrade grub to actually boot from the installed F33 kernel, and booted into gnome from gdm to ensure that gnome was still bootable, and found that the Wayland scaling issue to 4k resolution is still present in F33. Having verified that Gnome was working I tried KDE and KDE now appears to be working, the kicker is now usable, so it looks like whatever the F32 updates did to cause the KDE failures were rectified with F33.
regards, Steve
Then reboot.
The key to getting good answers is to ask good questions.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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/users@lists.fedoraproject.org