On 2/3/18 4:45 am, Jon LaBadie wrote:
I had very slow logins from sddm and lightdm. Not as bad from gdm, but still not good.
My culprit was staring an Xvnc server gnome session from my Mate autostart. Clue was 50 gnome processes I owned after logging into a Mate session.
jl
My issue starts with gdm, with gnome shell taking up to 800% of the cpu and causing, ctrl+alt+F2 to switch to another login to time out, and if I launch gnome from gdm the issue with gnome shell continues and causes gnome itself to lag. If I log into kde from gdm instead of logging into gnome the performance issue ceases and things go back to normal. If I use kdm as the display manager, launching kde does not cause any performance issues, and, if I launch gnome from kdm there are no performance issues either, with gnome shell running normally and not thrashing the cpu, so from my perspective the issue is gdm. The next question is how do I fix it?
regards,
Steve
On 03/04/18 08:25, Stephen Morris wrote:
My issue starts with gdm, with gnome shell taking up to 800% of the cpu and causing, ctrl+alt+F2 to switch to another login to time out, and if I launch gnome from gdm the issue with gnome shell continues and causes gnome itself to lag. If I log into kde from gdm instead of logging into gnome the performance issue ceases and things go back to normal. If I use kdm as the display manager, launching kde does not cause any performance issues, and, if I launch gnome from kdm there are no performance issues either, with gnome shell running normally and not thrashing the cpu, so from my perspective the issue is gdm. The next question is how do I fix it?
Are you running GNOME under wayland or Xorg?
Could be this. https://bugzilla.redhat.com/show_bug.cgi?id=1517330
On 4/3/18 11:37 am, Ed Greshko wrote:
On 03/04/18 08:25, Stephen Morris wrote:
My issue starts with gdm, with gnome shell taking up to 800% of the cpu and causing, ctrl+alt+F2 to switch to another login to time out, and if I launch gnome from gdm the issue with gnome shell continues and causes gnome itself to lag. If I log into kde from gdm instead of logging into gnome the performance issue ceases and things go back to normal. If I use kdm as the display manager, launching kde does not cause any performance issues, and, if I launch gnome from kdm there are no performance issues either, with gnome shell running normally and not thrashing the cpu, so from my perspective the issue is gdm. The next question is how do I fix it?
Are you running GNOME under wayland or Xorg?
Could be this. https://bugzilla.redhat.com/show_bug.cgi?id=1517330
Thanks Ed, I tried Gnome under Wayland and Xorg and as documented in the problem description, even though gnome shell lags with gdm, when gnome under Xorg is started the lag disappears. The only difference in my case is that the issue was not caused by upgrading from F26 to F27, which the problem description seems to be indicating, it was working fine in F27, until an update I put on caused the issue. If as indicated in the problem description the gnome-shell issue only happens under Wayland, does that mean that gdm runs under Wayland, and if so is there any way to change that functionality to get gdm to run under Xorg until the Wayland issue is resolved?
regards,
Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 03/04/18 09:57, Stephen Morris wrote:
Thanks Ed, I tried Gnome under Wayland and Xorg and as documented in the problem description, even though gnome shell lags with gdm, when gnome under Xorg is started the lag disappears. The only difference in my case is that the issue was not caused by upgrading from F26 to F27, which the problem description seems to be indicating, it was working fine in F27, until an update I put on caused the issue. If as indicated in the problem description the gnome-shell issue only happens under Wayland, does that mean that gdm runs under Wayland, and if so is there any way to change that functionality to get gdm to run under Xorg until the Wayland issue is resolved?
Yes, the login screen of gdm runs under wayland by default
Edit the file /etc/gdm/custom.conf accordingly
[daemon] # Uncoment the line below to force the login screen to use Xorg #WaylandEnable=false
On 04/03/2018 13:39, Ed Greshko wrote:
On 03/04/18 09:57, Stephen Morris wrote:
Thanks Ed, I tried Gnome under Wayland and Xorg and as documented in the problem description, even though gnome shell lags with gdm, when gnome under Xorg is started the lag disappears. The only difference in my case is that the issue was not caused by upgrading from F26 to F27, which the problem description seems to be indicating, it was working fine in F27, until an update I put on caused the issue. If as indicated in the problem description the gnome-shell issue only happens under Wayland, does that mean that gdm runs under Wayland, and if so is there any way to change that functionality to get gdm to run under Xorg until the Wayland issue is resolved?
Yes, the login screen of gdm runs under wayland by default
Edit the file /etc/gdm/custom.conf accordingly
[daemon] # Uncoment the line below to force the login screen to use Xorg #WaylandEnable=false
Thanks Ed, I made that change and it rectified the lagging issues with gdm and gnome. Now to work out why dkms hasn't compiled the nvidia driver under the new kernel.
regards,
Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 03/04/18 16:16, Stephen Morris wrote:
Thanks Ed, I made that change and it rectified the lagging issues with gdm and gnome. Now to work out why dkms hasn't compiled the nvidia driver under the new kernel.
FWIW, the lagging issues may be a byproduct of your video driver.
Anyway, while I use the nVidia drivers I get mine from rpmfusion and dkms isn't used with their packages. So, you may have to seek help from wherever you've obtained your drivers.
On 4/3/18 9:02 pm, Ed Greshko wrote:
On 03/04/18 16:16, Stephen Morris wrote:
Thanks Ed, I made that change and it rectified the lagging issues with gdm and gnome. Now to work out why dkms hasn't compiled the nvidia driver under the new kernel.
FWIW, the lagging issues may be a byproduct of your video driver.
Anyway, while I use the nVidia drivers I get mine from rpmfusion and dkms isn't used with their packages. So, you may have to seek help from wherever you've obtained your drivers.
Thanks Ed. I haven't worked out why dkms did compile only the nvidia drivers (unless its because I don't have the metadata package to track kernel updates for the repositories binary drivers), my wifi driver and mouse driver were compiled normally for the new kernel.
It is possible the video driver is the culprit, the repository has been a little slow in the past providing support for Wayland, this could explain why it happened with a system update, but having said that I don't see why older versions of the driver would work fine but this version not, unless Gnome Shell uses features that have only just been provided in the new version.
As a matter of interest, which version of the nvidia drivers are you using?
regards,
Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 03/05/18 04:18, Stephen Morris wrote:
As a matter of interest, which version of the nvidia drivers are you using?
390.25-3 And I don't use wayland as performance in KDE is horrible
On 5/3/18 7:36 am, Ed Greshko wrote:
On 03/05/18 04:18, Stephen Morris wrote:
As a matter of interest, which version of the nvidia drivers are you using?
390.25-3 And I don't use wayland as performance in KDE is horrible
From the negativo17 repositories I'm using the source code for the same version, with all the Xorg-x11 packages uninstalled because of conflicts between them and the nvidia packages I do have installed.
Also as a matter of interest, I don't have any performance issues under KDE at the moment, how do I determine whether KDE is using Xorg or Wayland when, unlike for Gnome where the display managers provide a Gnome Classic, Gnome for Xorg and a Gnome entry (which is the Wayland entry if Wayland is enabled under Gnome), for KDE they only provide an entry for Plasma and Plasma Media Center.
I also thought that Fedora was moving/had moved to Wayland as its default rather than Xorg?
regards,
Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 03/06/18 05:08, Stephen Morris wrote:
On 5/3/18 7:36 am, Ed Greshko wrote:
On 03/05/18 04:18, Stephen Morris wrote:
As a matter of interest, which version of the nvidia drivers are you using?
390.25-3 And I don't use wayland as performance in KDE is horrible
From the negativo17 repositories I'm using the source code for the same version, with all the Xorg-x11 packages uninstalled because of conflicts between them and the nvidia packages I do have installed.
You should then be taking all your nVidia related issues to the negativo17 support group.
Also as a matter of interest, I don't have any performance issues under KDE at the moment, how do I determine whether KDE is using Xorg or Wayland when, unlike for Gnome where the display managers provide a Gnome Classic, Gnome for Xorg and a Gnome entry (which is the Wayland entry if Wayland is enabled under Gnome), for KDE they only provide an entry for Plasma and Plasma Media Center.
In order to use wayland with KDE you need to install plasma-workspace-wayland. It is not installed by default at this time.
You can determine if you're using wayland by "env | grep DIS". If you're running under wayland you'd see something similar to
WAYLAND_DISPLAY=wayland-0
in the result
I also thought that Fedora was moving/had moved to Wayland as its default rather than Xorg?
Only gnome at this time.
-
Ed Greshko -
Ed Greshko -
Stephen Morris