4:39 a.m.
Hi,
I have forgotten whether I'm running gdm or kdm, and I've forgotten
where to look to find out, but since the last system update I did two
days ago, when the display manager is displaying the list of user who
can log in, cursor movements and mouse movements lag something cronic,
but when I log into the desktop response goes back to normal. Has anyone
else noticed this?
regards,
Steve
4:47 a.m.
On 02/26/18 18:39, Stephen Morris wrote:
I have forgotten whether I'm running gdm or kdm, and I've
forgotten where to
look to find out, but since the last system update I did two days ago, when the
display manager is displaying the list of user who can log in, cursor movements and
mouse movements lag something cronic, but when I log into the desktop response goes
back to normal. Has anyone else noticed this?
ll /etc/systemd/system/display-manager.service will point to what you're using.
All is well here using sddm
--
A motto of mine is: When in doubt, try it out
2:37 p.m.
On 26/2/18 9:50 pm, Ed Greshko wrote:
On 02/26/18 18:47, Ed Greshko wrote:
> ll /etc/systemd/system/display-manager.service will point to what you're
using.
systemctl status display-manager
also will tell you
Thanks Ed, that tells me I'm using gdm. I might be getting confused with
Ubuntu, but I thought there was a .conf file somewhere that held the
specification of the default display manager that could easily be edited
to swap between any of the available display managers that you happen to
have installed.
The issue I have with the lag, is when I use the mouse to drag the mouse
pointer over the list of users, the highlighting process lags that badly
that highlighting of users in the list gets skipped, and if I use the
arrow keys to cycle backwards and forwards through the list of 5 users,
it takes approx. 10 to 15 seconds for before each user gets highlighted.
Also having selected the user to login with, in my case my userid, and
gotten the password prompt, I only use a short password being 5
characters long, I can type the entire password and press enter to
action it, before the display manager displays to mask representing the
first character of the password, having displayed the first mask
character, it waits for a little while then displays the second mask
character, waits for a little while and then displays the last 3 mask
characters all at once.
I don't know if this is part of this issue or not, but having entered my
password, the system then displays a "black screen" for a period of time
before displaying the screen with the KDE logo on it to indicate that
KDE is starting up, but whatever that "black screen" is, the production
of that screen is enough to send my monitor into power saving mode until
just before the KDE logo screen is eventually displayed.
I'm not using sddm because when I tried it, I didn't like its
presentation layer, and the same applies to kdm.
regards,
Steve
>
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
3:37 p.m.
On 28/2/18 7:46 am, Joe Zeff wrote:
On 02/27/2018 12:37 PM, Stephen Morris wrote:
>
> I'm not using sddm because when I tried it, I didn't like its
> presentation layer, and the same applies to kdm.
Have you tried lightdm?
If I remember correctly, I think in F25 or F26 lightdm was the display
manager used by default, and I moved away from that a long time ago, and
if I remember correctly, I moved away from it because I had trouble
getting it to work properly with Gnome and KDE, but I don't remember
exactly what the issue was.
regards,
Steve
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
5:24 p.m.
On 02/28/18 05:37, Stephen Morris wrote:
If I remember correctly, I think in F25 or F26 lightdm was the display manager used
by default
No.
It depended on the "spin" or Desktop you installed. If you installed
"Workstation" aka GNOME it has always been gdm. If you installed the KDE spin
it
was originally kdm. Now, with KDE4, aka plasma, it is sddm.
--
A motto of mine is: When in doubt, try it out
5:11 p.m.
On 02/28/18 04:37, Stephen Morris wrote:
I might be getting confused with Ubuntu, but I thought there was a
.conf file
somewhere that held the specification of the default display manager that could
easily be edited to swap between any of the available display managers that you
happen to have installed.
With the advent of systemd there hasn't been a configuration file for a long time.
It is extremely easy to switch between DM's.
systemctl --force enable gdm or kdm, or sddm, or lightdm or whatever.
--
A motto of mine is: When in doubt, try it out
3:16 p.m.
On 28/2/18 10:11 am, Ed Greshko wrote:
On 02/28/18 04:37, Stephen Morris wrote:
> I might be getting confused with Ubuntu, but I thought there was a .conf file
> somewhere that held the specification of the default display manager that could
> easily be edited to swap between any of the available display managers that you
> happen to have installed.
With the advent of systemd there hasn't been a configuration file for a long time.
It is extremely easy to switch between DM's.
systemctl --force enable gdm or kdm, or sddm, or lightdm or whatever.
Thanks Ed, I switched from gdm to kdm by the following:
sudo systemctl disable gdm.service
sudo systemctl enable kdm.service
With kdm I don't get the issue, so to try and debug where/what the issue
is I switched back to gdm which as expected exhibited the issue again.
To eliminate the old issue of gdm and kde not functioning together
properly I started up gnome (both gnome, I assume with wayland, and
gnome for xorg). It appeared from this that the system update I did that
prompted this mail has stuffed gnome on my system. The gnome session I
started was running the wrong resolution, it wasn't running the
resolution it was on the last time I used gnome, the horrific lag that
gdm was getting the gnome desktop was as well, and when I eventually was
able to start konsole for the shell as I always do, the konsole session
went haywire with things like randomly single keypresses storming that
key across the screen. Despite all this I was able to start top, which
highlighted that Gnome-Shell was using 450 - 800 % of the cpu, so it
looks like the updated stuffed gnome-shell on my system, but I'm not
sure that that explains the desktop resolution being destroyed. The next
question with this is how, as a starting point do we get Gnome-Shell fixed.
regards,
Steve
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
3:45 p.m.
On 03/01/18 05:16, Stephen Morris wrote:
On 28/2/18 10:11 am, Ed Greshko wrote:
> On 02/28/18 04:37, Stephen Morris wrote:
>> I might be getting confused with Ubuntu, but I thought there was a .conf file
>> somewhere that held the specification of the default display manager that could
>> easily be edited to swap between any of the available display managers that you
>> happen to have installed.
>
> With the advent of systemd there hasn't been a configuration file for a long
time.
> It is extremely easy to switch between DM's.
>
> systemctl --force enable gdm or kdm, or sddm, or lightdm or whatever.
Thanks Ed, I switched from gdm to kdm by the following:
sudo systemctl disable gdm.service
sudo systemctl enable kdm.service
I prefer less typing, but that works as well.
The next question with this is how, as a starting point do we get Gnome-Shell fixed.
I don't use gnome. Hopefully someone else can assist. Yet, nobody else is
complaining so it is probably something with your particular setup.
--
A motto of mine is: When in doubt, try it out
3:56 p.m.
On 01/03/18 08:45, Ed Greshko wrote:
On 03/01/18 05:16, Stephen Morris wrote:
> On 28/2/18 10:11 am, Ed Greshko wrote:
>> On 02/28/18 04:37, Stephen Morris wrote:
>>> I might be getting confused with Ubuntu, but I thought there was a .conf
file
>>> somewhere that held the specification of the default display manager that
could
>>> easily be edited to swap between any of the available display managers that
you
>>> happen to have installed.
>>
>> With the advent of systemd there hasn't been a configuration file for a long
time.
>> It is extremely easy to switch between DM's.
>>
>> systemctl --force enable gdm or kdm, or sddm, or lightdm or whatever.
>
> Thanks Ed, I switched from gdm to kdm by the following:
>
> sudo systemctl disable gdm.service
>
> sudo systemctl enable kdm.service
I prefer less typing, but that works as well.
>
> The next question with this is how, as a starting point do we get Gnome-Shell fixed.
>
I don't use gnome. Hopefully someone else can assist. Yet, nobody else is
complaining so it is probably something with your particular setup.
I should say that I also noticed this recently. Not using gdm:
$ systemctl status display-manager
* lxdm.service - LXDM (Lightweight X11 Display Manager)
HTH
--
Eyal Lebedinsky (fedora(a)eyal.emu.id.au)
2242
days inactive
2244
days old
10 comments
5 participants
participants (5)
-
Ed Greshko -
Ed Greshko -
Eyal Lebedinsky -
Joe Zeff -
Stephen Morris