Hi, Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
regards, Steve
On 1/25/21 9:51 PM, Stephen Morris wrote:
Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Check the /var/log/Xorg.?.log files.
On 27/1/21 01:40, Ian Pilcher wrote:
On 1/25/21 9:51 PM, Stephen Morris wrote:
Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Check the /var/log/Xorg.?.log files.
I'm currently logged in with Gnome user Xorg and in /var/log there is no Xorg files of any sort. Is the Xorg.?.log files stored elsewhere in F33 now?
regards, Steve
On 1/26/21 3:26 PM, Stephen Morris wrote:
On 27/1/21 01:40, Ian Pilcher wrote:
On 1/25/21 9:51 PM, Stephen Morris wrote:
Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Check the /var/log/Xorg.?.log files.
I'm currently logged in with Gnome user Xorg and in /var/log there is no Xorg files of any sort. Is the Xorg.?.log files stored elsewhere in F33 now?
Try looking in ~/.local/share/xorg
On 27/1/21 10:29, Samuel Sieb wrote:
On 1/26/21 3:26 PM, Stephen Morris wrote:
On 27/1/21 01:40, Ian Pilcher wrote:
On 1/25/21 9:51 PM, Stephen Morris wrote:
Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Check the /var/log/Xorg.?.log files.
I'm currently logged in with Gnome user Xorg and in /var/log there is no Xorg files of any sort. Is the Xorg.?.log files stored elsewhere in F33 now?
Try looking in ~/.local/share/xorg
Thankyou, I found the log files there. Looking at xorg.0.log.old the only error I could find was an fsetmode error, but I'm not sure what that means when gnome with xorg runs quite happily.
regards, Steve
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 27/01/2021 07:44, Stephen Morris wrote:
On 27/1/21 10:29, Samuel Sieb wrote:
On 1/26/21 3:26 PM, Stephen Morris wrote:
On 27/1/21 01:40, Ian Pilcher wrote:
On 1/25/21 9:51 PM, Stephen Morris wrote:
Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Check the /var/log/Xorg.?.log files.
I'm currently logged in with Gnome user Xorg and in /var/log there is no Xorg files of any sort. Is the Xorg.?.log files stored elsewhere in F33 now?
Try looking in ~/.local/share/xorg
Thankyou, I found the log files there. Looking at xorg.0.log.old the only error I could find was an fsetmode error, but I'm not sure what that means when gnome with xorg runs quite happily.
What display manager are you using? gdm, sddm, other?
On 27/1/21 10:55, Ed Greshko wrote:
On 27/01/2021 07:44, Stephen Morris wrote:
On 27/1/21 10:29, Samuel Sieb wrote:
On 1/26/21 3:26 PM, Stephen Morris wrote:
On 27/1/21 01:40, Ian Pilcher wrote:
On 1/25/21 9:51 PM, Stephen Morris wrote:
Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Check the /var/log/Xorg.?.log files.
I'm currently logged in with Gnome user Xorg and in /var/log there is no Xorg files of any sort. Is the Xorg.?.log files stored elsewhere in F33 now?
Try looking in ~/.local/share/xorg
Thankyou, I found the log files there. Looking at xorg.0.log.old the only error I could find was an fsetmode error, but I'm not sure what that means when gnome with xorg runs quite happily.
What display manager are you using? gdm, sddm, other?
Thanks Ed. I think I'm using gdm for my display manager. I've forgotten the command to find out because I don't use it regularly. Just a bit of additional information, after the last update nothing has changed and when the plasma start fails I tried to use alt-F2 to get to a login prompt to look at the Xorg log file but krunner also fails so it won't swap. All of the apps that are failing are all failing with a Segmentation Fault. I'll reply to Rex's thread but I am using Vmware Player to run Fedora.
regards, Steve
On 29/1/21 09:19, Stephen Morris wrote:
On 27/1/21 10:55, Ed Greshko wrote:
On 27/01/2021 07:44, Stephen Morris wrote:
On 27/1/21 10:29, Samuel Sieb wrote:
On 1/26/21 3:26 PM, Stephen Morris wrote:
On 27/1/21 01:40, Ian Pilcher wrote:
On 1/25/21 9:51 PM, Stephen Morris wrote: > Three days ago I did a dnf system upgrade to apply all > available Fedora updates. I have now tried to start Plasma under > Xorg, but it now refuses to start with a crash in ksplashqml, > and if I press ctrl-alt-delete to try to logout the > ksmserver-greeter also crashes. Plasma under Wayland runs quite > happily albeit without resolution scaling. Gnome under Wayland > runs fine without scaling and Gnome under Xorg also runs fine. > How do I determine why the apps are failing with Plasma under > Xorg now?
Check the /var/log/Xorg.?.log files.
I'm currently logged in with Gnome user Xorg and in /var/log there is no Xorg files of any sort. Is the Xorg.?.log files stored elsewhere in F33 now?
Try looking in ~/.local/share/xorg
Thankyou, I found the log files there. Looking at xorg.0.log.old the only error I could find was an fsetmode error, but I'm not sure what that means when gnome with xorg runs quite happily.
What display manager are you using? gdm, sddm, other?
Thanks Ed. I think I'm using gdm for my display manager. I've forgotten the command to find out because I don't use it regularly. Just a bit of additional information, after the last update nothing has changed and when the plasma start fails I tried to use alt-F2 to get to a login prompt to look at the Xorg log file but krunner also fails so it won't swap. All of the apps that are failing are all failing with a Segmentation Fault. I'll reply to Rex's thread but I am using Vmware Player to run Fedora.
Hi Ed, just further to this, I worked out what command to issue and I am indeed running gdm as my display manager.
regards, Steve
regards, Steve
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 29/01/2021 06:37, Joe Zeff wrote:
On 1/28/21 3:19 PM, Stephen Morris wrote:
Thanks Ed. I think I'm using gdm for my display manager.
If you're using gnome you're probably using gdm, as it's the default.
It depends on how the system was installed. e.g. My system was initially installed from the KDE spin. So even though I then installed the Gnome Desktop I'm still running sddm as the display manager. Not a good idea to assume.
Some folks are having a problem after updates to sddm and running on VMware products.
https://bugzilla.redhat.com/show_bug.cgi?id=1919696
The OP's problem would appear to be unrelated.
On 1/28/21 3:50 PM, Ed Greshko wrote:
On 29/01/2021 06:37, Joe Zeff wrote:
On 1/28/21 3:19 PM, Stephen Morris wrote:
Thanks Ed. I think I'm using gdm for my display manager.
If you're using gnome you're probably using gdm, as it's the default.
It depends on how the system was installed. e.g. My system was initially installed from the KDE spin. So even though I then installed the Gnome Desktop I'm still running sddm as the display manager. Not a good idea to assume.
And that's why I said "probably."
Stephen Morris wrote:
Hi, Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Fwiw, I believe this is being tracked by this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1919696
What video driver do you use? Are you using autologin feature?
I ask because a good number of folks I've heard from so far are using vmware and/or autologin. I've personally been unable to reproduce it.
-- Rex
On 28/1/21 02:43, Rex Dieter wrote:
Stephen Morris wrote:
Hi, Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Fwiw, I believe this is being tracked by this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1919696
What video driver do you use? Are you using autologin feature?
I ask because a good number of folks I've heard from so far are using vmware and/or autologin. I've personally been unable to reproduce it.
Thanks Rex. I am using Vmware to run Fedora. I'm not sure what driver I'm using because like with the display manager I'm using, I've forgotten the command to find out as I don't use it all the time. My issue is slightly different to the bug in that I am using gdm, and I am getting popups about apps getting segmentation faults. I did notice in the bug report that a patch had been developed and someone reporting that it fixed his issue, and I've noticed this morning that there are more updates, so they may have released the patch, and if so I'll see if it rectifies my issue as well.
regards, Steve
-- Rex _______________________________________________ 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 Fri, Jan 29, 2021 at 10:15:12AM +1100, Stephen Morris wrote:
On 28/1/21 02:43, Rex Dieter wrote:
Stephen Morris wrote:
Hi, Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press ctrl-alt-delete to try to logout the ksmserver-greeter also crashes. Plasma under Wayland runs quite happily albeit without resolution scaling. Gnome under Wayland runs fine without scaling and Gnome under Xorg also runs fine. How do I determine why the apps are failing with Plasma under Xorg now?
Fwiw, I believe this is being tracked by this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1919696
What video driver do you use? Are you using autologin feature?
I ask because a good number of folks I've heard from so far are using vmware and/or autologin. I've personally been unable to reproduce it.
Thanks Rex. I am using Vmware to run Fedora. I'm not sure what driver I'm using because like with the display manager I'm using, I've forgotten the command to find out as I don't use it all the time. My issue is slightly different to the bug in that I am using gdm, and I am getting popups about apps getting segmentation faults. I did notice in the bug report that a patch had been developed and someone reporting that it fixed his issue, and I've noticed this morning that there are more updates, so they may have released the patch, and if so I'll see if it rectifies my issue as well.
Similar here:
I have linux on a VM on Virtual Box on OS X, and my KDE session is not starting up.
I haven't found any errors logged so far.
Per bug comment https://bugzilla.redhat.com/show_bug.cgi?id=1919696#c12, I'm about to try the fix that was pushed to updates-testing.
-- Patrick
On Fri, Jan 29, 2021 at 04:09:19PM -0800, Patrick Mansfield via users wrote:
Per bug comment https://bugzilla.redhat.com/show_bug.cgi?id=1919696#c12, I'm about to try the fix that was pushed to updates-testing.
The update to sddm-0.19.0-5.fc33.x86_64 fixed my problem :)
Per the bug, installed via:
sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b71b8a85c8
-- Patrick
On 30 Jan 2021, at 00:21, Patrick Mansfield via users users@lists.fedoraproject.org wrote:
On Fri, Jan 29, 2021 at 04:09:19PM -0800, Patrick Mansfield via users wrote:
Per bug comment https://bugzilla.redhat.com/show_bug.cgi?id=1919696#c12, I'm about to try the fix that was pushed to updates-testing.
The update to sddm-0.19.0-5.fc33.x86_64 fixed my problem :)
Per the bug, installed via:
sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b71b8a85c8
This does not fix it for my VM. The error I see is shown here for sddh-helper.
[root@vmf33 ~]# systemctl status sddm ● sddm.service - Simple Desktop Display Manager Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2021-02-01 21:55:10 GMT; 38s ago Docs: man:sddm(1) man:sddm.conf(5) Main PID: 936 (sddm) Tasks: 4 (limit: 5828) Memory: 84.6M CPU: 444ms CGroup: /system.slice/sddm.service ├─936 /usr/bin/sddm └─939 /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{1d9c11bc-e8fa-4d8c-90d4-0a5b075f32bc} -backgrou>
Feb 01 21:55:10 vmf33.chelsea.private systemd[1]: Started Simple Desktop Display Manager. Feb 01 21:55:11 vmf33.chelsea.private sddm-helper[945]: pam_unix(sddm-greeter:session): session opened for user sddm(ui> Feb 01 21:55:15 vmf33.chelsea.private sddm[936]: Auth: sddm-helper exited with 11
There is a thread on the Fedora KDE list about this issue, but without a solution so far.
Barry
-- Patrick _______________________________________________ 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 2/2/21 08:58, Barry Scott wrote:
On 30 Jan 2021, at 00:21, Patrick Mansfield via users users@lists.fedoraproject.org wrote:
On Fri, Jan 29, 2021 at 04:09:19PM -0800, Patrick Mansfield via users wrote:
Per bug comment https://bugzilla.redhat.com/show_bug.cgi?id=1919696#c12, I'm about to try the fix that was pushed to updates-testing.
The update to sddm-0.19.0-5.fc33.x86_64 fixed my problem :)
Per the bug, installed via:
sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b71b8a85c8
This does not fix it for my VM. The error I see is shown here for sddh-helper.
[root@vmf33 ~]# systemctl status sddm ● sddm.service - Simple Desktop Display Manager Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2021-02-01 21:55:10 GMT; 38s ago Docs: man:sddm(1) man:sddm.conf(5) Main PID: 936 (sddm) Tasks: 4 (limit: 5828) Memory: 84.6M CPU: 444ms CGroup: /system.slice/sddm.service ├─936 /usr/bin/sddm └─939 /usr/libexec/Xorg -nolisten tcp -auth /var/run/sddm/{1d9c11bc-e8fa-4d8c-90d4-0a5b075f32bc} -backgrou>
Feb 01 21:55:10 vmf33.chelsea.private systemd[1]: Started Simple Desktop Display Manager. Feb 01 21:55:11 vmf33.chelsea.private sddm-helper[945]: pam_unix(sddm-greeter:session): session opened for user sddm(ui> Feb 01 21:55:15 vmf33.chelsea.private sddm[936]: Auth: sddm-helper exited with 11
There is a thread on the Fedora KDE list about this issue, but without a solution so far.
Barry
For me systemctl status gdm gives: gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago Main PID: 1221 (gdm) Tasks: 3 (limit: 19120) Memory: 5.5M CPU: 280ms CGroup: /system.slice/gdm.service └─1221 /usr/sbin/gdm
Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display Manager... Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager. Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: unable to locate daemon control file Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: stashed password to try later in open session Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process -1267 was already dead.
What I'm not sure at the moment is how to find out what process -1267 is.
regards, Steve
-- Patrick _______________________________________________ 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 03/02/2021 14:09, Stephen Morris wrote:
For me systemctl status gdm gives: gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago Main PID: 1221 (gdm) Tasks: 3 (limit: 19120) Memory: 5.5M CPU: 280ms CGroup: /system.slice/gdm.service └─1221 /usr/sbin/gdm
Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display Manager... Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager. Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: unable to locate daemon control file Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: stashed password to try later in open session Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process -1267 was already dead.
What I'm not sure at the moment is how to find out what process -1267 is.
The bugzillas referenced so far have been against sddm. Your issues seem unrelated.
There have been fixes to sddm to address those issues. You may wish to try sddm instead of gdm to see if you still have issues. The most current sddm is still in updates-testing. So, if you wan to give it a try....
dnf --enablerepo updates-testing update sddm systemctl --now enable sddm
The reboot....
On 3/2/21 19:08, Ed Greshko wrote:
On 03/02/2021 14:09, Stephen Morris wrote:
For me systemctl status gdm gives: gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago Main PID: 1221 (gdm) Tasks: 3 (limit: 19120) Memory: 5.5M CPU: 280ms CGroup: /system.slice/gdm.service └─1221 /usr/sbin/gdm
Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display Manager... Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager. Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: unable to locate daemon control file Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: stashed password to try later in open session Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process -1267 was already dead.
What I'm not sure at the moment is how to find out what process -1267 is.
The bugzillas referenced so far have been against sddm. Your issues seem unrelated.
There have been fixes to sddm to address those issues. You may wish to try sddm instead of gdm to see if you still have issues. The most current sddm is still in updates-testing. So, if you wan to give it a try....
dnf --enablerepo updates-testing update sddm systemctl --now enable sddm
The reboot....
Thanks Ed, I might try that. I don't like the sddm interface, but if it means plasma works properly then I might have to put up with it. I don't like the Gnome desktop interface, in my view it doesn't work properly.
regards, Steve
On 3/2/21 19:08, Ed Greshko wrote:
On 03/02/2021 14:09, Stephen Morris wrote:
For me systemctl status gdm gives: gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago Main PID: 1221 (gdm) Tasks: 3 (limit: 19120) Memory: 5.5M CPU: 280ms CGroup: /system.slice/gdm.service └─1221 /usr/sbin/gdm
Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display Manager... Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager. Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: unable to locate daemon control file Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: stashed password to try later in open session Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process -1267 was already dead.
What I'm not sure at the moment is how to find out what process -1267 is.
The bugzillas referenced so far have been against sddm. Your issues seem unrelated.
There have been fixes to sddm to address those issues. You may wish to try sddm instead of gdm to see if you still have issues. The most current sddm is still in updates-testing. So, if you wan to give it a try....
dnf --enablerepo updates-testing update sddm systemctl --now enable sddm
The reboot....
Hi Ed, I issued the two commands and first one worked but the second one didn't. The second command said it couldn't create the display-manager symlink because it already existed and was linked to gdm.service. I then made the mistake of issuing the command systemctl disable gdm and that blew Fedora out of the water. I rebooted but the display manager wouldn't start. I then used ctrl+alt+F2 to get a login prompt, logged in, and issued the command systemctl disable display-manager and then systemctl enable sddm and rebooted, but sddm would not start. I logged back in again at a login prompt and issued the command systemctl status display-manager and it said sddm was active but sddm-helper failed with exit-11. Hence at the moment I have switched back to gdm which runs fine.
regards, Steve
On 9/2/21 22:14, Stephen Morris wrote:
On 3/2/21 19:08, Ed Greshko wrote:
On 03/02/2021 14:09, Stephen Morris wrote:
For me systemctl status gdm gives: gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago Main PID: 1221 (gdm) Tasks: 3 (limit: 19120) Memory: 5.5M CPU: 280ms CGroup: /system.slice/gdm.service └─1221 /usr/sbin/gdm
Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display Manager... Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager. Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: unable to locate daemon control file Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: stashed password to try later in open session Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process -1267 was already dead.
What I'm not sure at the moment is how to find out what process -1267 is.
The bugzillas referenced so far have been against sddm. Your issues seem unrelated.
There have been fixes to sddm to address those issues. You may wish to try sddm instead of gdm to see if you still have issues. The most current sddm is still in updates-testing. So, if you wan to give it a try....
dnf --enablerepo updates-testing update sddm systemctl --now enable sddm
The reboot....
Hi Ed, I issued the two commands and first one worked but the second one didn't. The second command said it couldn't create the display-manager symlink because it already existed and was linked to gdm.service. I then made the mistake of issuing the command systemctl disable gdm and that blew Fedora out of the water. I rebooted but the display manager wouldn't start. I then used ctrl+alt+F2 to get a login prompt, logged in, and issued the command systemctl disable display-manager and then systemctl enable sddm and rebooted, but sddm would not start. I logged back in again at a login prompt and issued the command systemctl status display-manager and it said sddm was active but sddm-helper failed with exit-11. Hence at the moment I have switched back to gdm which runs fine.
I installed kdm to try that and the starting of plasma through kdm gets the same failures as it does when started through gdm.
regards, Steve
regards, Steve
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 09/02/2021 19:14, Stephen Morris wrote:
On 3/2/21 19:08, Ed Greshko wrote:
On 03/02/2021 14:09, Stephen Morris wrote:
For me systemctl status gdm gives: gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago Main PID: 1221 (gdm) Tasks: 3 (limit: 19120) Memory: 5.5M CPU: 280ms CGroup: /system.slice/gdm.service └─1221 /usr/sbin/gdm
Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display Manager... Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager. Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: unable to locate daemon control file Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: stashed password to try later in open session Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process -1267 was already dead.
What I'm not sure at the moment is how to find out what process -1267 is.
The bugzillas referenced so far have been against sddm. Your issues seem unrelated.
There have been fixes to sddm to address those issues. You may wish to try sddm instead of gdm to see if you still have issues. The most current sddm is still in updates-testing. So, if you wan to give it a try....
dnf --enablerepo updates-testing update sddm systemctl --now enable sddm
The reboot....
Hi Ed, I issued the two commands and first one worked but the second one didn't. The second command said it couldn't create the display-manager symlink because it already existed and was linked to gdm.service.
Ooops.... Sorry about that. I forgot to add the -f or --force parameter
I then made the mistake of issuing the command systemctl disable gdm and that blew Fedora out of the water. I rebooted but the display manager wouldn't start. I then used ctrl+alt+F2 to get a login prompt, logged in, and issued the command systemctl disable display-manager and then systemctl enable sddm and rebooted, but sddm would not start. I logged back in again at a login prompt and issued the command systemctl status display-manager and it said sddm was active but sddm-helper failed with exit-11.
That think that was one of the errors noted in one of the BZ's. Can't find it at the moment.
What version of sddm is now installed?
rpm -q sddm
sddm-0.19.0-6.fc33 is the latest.
Hence at the moment I have switched back to gdm which runs fine.
So, you can run the KDE desktop using gdm as the display-manager? If that works, I suppose you can stay with it. Or, maybe bring up your issue on the KDE list would be a good idea.
On 9/2/21 22:40, Ed Greshko wrote:
On 09/02/2021 19:14, Stephen Morris wrote:
On 3/2/21 19:08, Ed Greshko wrote:
On 03/02/2021 14:09, Stephen Morris wrote:
For me systemctl status gdm gives: gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-02-03 13:37:47 AEDT; 3h 27min ago Main PID: 1221 (gdm) Tasks: 3 (limit: 19120) Memory: 5.5M CPU: 280ms CGroup: /system.slice/gdm.service └─1221 /usr/sbin/gdm
Feb 03 13:37:46 localhost.localdomain systemd[1]: Starting GNOME Display Manager... Feb 03 13:37:47 localhost.localdomain systemd[1]: Started GNOME Display Manager. Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: unable to locate daemon control file Feb 03 13:38:34 localhost.localdomain gdm-password][1837]: gkr-pam: stashed password to try later in open session Feb 03 13:38:54 localhost.localdomain gdm[1221]: Gdm: Child process -1267 was already dead.
What I'm not sure at the moment is how to find out what process -1267 is.
The bugzillas referenced so far have been against sddm. Your issues seem unrelated.
There have been fixes to sddm to address those issues. You may wish to try sddm instead of gdm to see if you still have issues. The most current sddm is still in updates-testing. So, if you wan to give it a try....
dnf --enablerepo updates-testing update sddm systemctl --now enable sddm
The reboot....
Hi Ed, I issued the two commands and first one worked but the second one didn't. The second command said it couldn't create the display-manager symlink because it already existed and was linked to gdm.service.
Ooops.... Sorry about that. I forgot to add the -f or --force parameter
I then made the mistake of issuing the command systemctl disable gdm and that blew Fedora out of the water. I rebooted but the display manager wouldn't start. I then used ctrl+alt+F2 to get a login prompt, logged in, and issued the command systemctl disable display-manager and then systemctl enable sddm and rebooted, but sddm would not start. I logged back in again at a login prompt and issued the command systemctl status display-manager and it said sddm was active but sddm-helper failed with exit-11.
That think that was one of the errors noted in one of the BZ's. Can't find it at the moment.
What version of sddm is now installed?
rpm -q sddm
sddm-0.19.0-6.fc33 is the latest.
I've checked the version of sddm and it is sddm-0.19.0-6.fc33.x86_64.
Hence at the moment I have switched back to gdm which runs fine.
So, you can run the KDE desktop using gdm as the display-manager? If that works, I suppose you can stay with it. Or, maybe bring up your issue on the KDE list would be a good idea.
Sorry, I meant gdm now runs, but plasma still fails under gdm. How do I access the KDE list?
regards, Steve
On Tue, Feb 9, 2021, 19:50 Stephen Morris samorris@netspace.net.au wrote:
Sorry, I meant gdm now runs, but plasma still fails under gdm. How do I access the KDE list?
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-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/kde@lists.fedoraproject.or https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.orgg
On 9/2/21 23:18, Ed Greshko wrote:
On Tue, Feb 9, 2021, 19:50 Stephen Morris <samorris@netspace.net.au mailto:samorris@netspace.net.au> wrote:
Sorry, I meant gdm now runs, but plasma still fails under gdm. How do I access the KDE list?kde mailing list --� kde@lists.fedoraproject.org mailto:kde@lists.fedoraproject.org To unsubscribe send an email to� kde-leave@lists.fedoraproject.org mailto:kde-leave@lists.fedoraproject.org Fedora Code of Conduct:� https://docs.fedoraproject.org/en-US/project/code-of-conduct/ https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:� https://fedoraproject.org/wiki/Mailing_list_guidelines https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:� https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.or https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.orgg
Thanks Ed, I'll subscribe to that list and see what responses I get. Just as additional info, I tried using kdm as the display-manager, but that made no difference Plasma with Xorg still failed.
regards, Steve
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
Stephen Morris wrote:
On 28/1/21 02:43, Rex Dieter wrote:
Stephen Morris wrote:
Hi, Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press
...
Thanks Rex. I am using Vmware to run Fedora
It's a mesa bug after all, tracked here,
https://bugzilla.redhat.com/show_bug.cgi?id=1921523#c7
-- Rex
On 17/2/21 15:32, Rex Dieter wrote:
Stephen Morris wrote:
On 28/1/21 02:43, Rex Dieter wrote:
Stephen Morris wrote:
Hi, Three days ago I did a dnf system upgrade to apply all available Fedora updates. I have now tried to start Plasma under Xorg, but it now refuses to start with a crash in ksplashqml, and if I press
...
Thanks Rex. I am using Vmware to run Fedora
It's a mesa bug after all, tracked here,
Thanks Rex, I had a look at that bug report and I am on Mesa 20.3.4, but if it still happens with Mesa 21rc2, then presumably it happens in 20.3.4 as well. One responder to the track is saying they were able to revert back to an older version but I'm not sure how to do that, plus it appears to not be possible in the current repositories, as if I issue the command dnf info mesa-dri* the versions listed are the x64 and i686 versions of 20.3.4. Do you happen to know, is mesa only used with Xorg? I'm asking this because it's plasma with Xorg that fails, plasma with Wayland seems to run fine albeit the desktop doesn't seem to scale.
regards, Steve
-- Rex _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-
Barry Scott -
Ed Greshko -
Ian Pilcher -
Joe Zeff -
Patrick Mansfield -
Rex Dieter -
Samuel Sieb -
Stephen Morris