Bug 491301 - plasma x11, kde session login very slow
Summary: plasma x11, kde session login very slow
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Session Management (other bugs)
Version First Reported In: 6.1.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-05 13:33 UTC by Philippe ROUBACH
Modified: 2024-09-10 11:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2024-08-05 13:33:10 UTC
I use by default plasma X11
I get an user1 and an user2

In the past, using plasma X11 by default for a second user is not a problem.
Recently, if I switch from user1(staying open) to user2 when opening a kde session, it is very long, 1 or 2 mn.
With plasma Wayland for user2, there is no problem.

Also, I note this :
- for plasma x11, user1, user2 :
in display settings, the global scale increment is 6.5%.
I remember it was 5 %
- for plasma wayland, user1, user2 :
in display settings, the global scale increment is 5%.
I remember it was 6.5 %

there's a kind of inversion of the scale increment.

It seems that certain wayland plasma parameters are applied to x11 plasma and vice versa.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240801
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.2-1-default (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

I try to create a user3 then same problem.
Also there is no more any sound device for user2 and user3.
also there is no more any device in colord management.
Comment 1 Nate Graham 2024-08-05 17:53:13 UTC
Can you describe exactly what you're doing to trigger this issue using Steps To Reproduce?
Comment 2 Philippe ROUBACH 2024-08-05 18:26:39 UTC
plasma x11 by default
user1 is my default and current user.

open user1 kde session
switch to user2
open user2 kde session.

that' all.
Comment 3 Nate Graham 2024-08-05 18:32:23 UTC
Please describe exactly *how* you're doing those things, since there are multiple ways to do them.
Comment 4 Philippe ROUBACH 2024-08-08 09:04:03 UTC
In user1 KDE session
in application launcher menu in "Session" click on "change user"

The list of users is displayed.

Select user2 and fill the password.

A KDE session is opening for user2.
Comment 5 J.O. Aho 2024-08-11 09:37:11 UTC
I have a similar experience, but not during login (this tend to work for me quite fine)
Plasma: 6.1.4
KDE Framework: 24.05.2
Pipewire: 1.2.2
Kernel: 6.10.3 (arch)
nVidia: 555.58.02
Audio device: Starship/Matisse HD Audio Controller (pro audio selected in pipewire)

Have two X11 sessions (User1 and User2, login with User1 first, then switch user from kde menu and login with User2), switch between them in one of two ways:
1. Use "Switch User" from the KDE start menu
2. Use the ctrl-alt-fX key combination


Effect for me:
The volume icon in the panel is "crossed out", everything is laggish and sudden freezes from time to time until the volume icon is back to normal. This normally takes up to a minute, sometimes it's take just a few seconds, which makes me think it's an timed even than handles something instead of listening to an event. For me this didn't happen until pipewire 1.2.1 and Plasma 6.1.3 (got those at the same time).

From xsession-errors:
QRhiGles2: Context is lost.
Graphics device lost, cleaning up scenegraph and releasing RHI
org.kde.pulseaudio: No object for name "auto_null"
org.kde.pulseaudio: No object for name "auto_null.monitor"
QRhiGles2: Context is lost.
Graphics device lost, cleaning up scenegraph and releasing RHI
org.kde.pulseaudio: No object for name "alsa_output.pci-0000_29_00.4.pro-output-0"
...
org.kde.pulseaudio: No object for name "auto_null.monitor"
(when the previous row is written, everything is back to normal)

when using strace on plasmashell I get a lot of following:
read(4, "\2\0\0\0\0\0\0\0", 8)          = 8
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
poll([{fd=4, events=POLLIN}, {fd=27, events=POLLIN}, {fd=29, events=POLLIN}, {fd=30, events=POLLIN}, {fd=32, events=POLLIN}, {fd=59, events=POLLIN}, {fd=60, events=POLLIN}, {fd=61, events=POLLPRI}, {fd=62, events=POLLIN}, {fd=63, events=POLLIN}, {fd=69, events=POLLIN}, {fd=70, events=POLLIN}], 12, 4) = 2 ([{fd=4, revents=POLLIN}, {fd=59, revents=POLLIN}])

Not sure if this is related to Philippe's issue or not, but feels quite similar.
Comment 6 Philippe ROUBACH 2024-08-11 10:10:32 UTC
For user2 I tried to reinit pipewire with "systemctl --user restart pipewire.service ". This does not fix the sound problem.
Comment 7 Philippe ROUBACH 2024-09-10 11:28:35 UTC
I nistalled again opensuse tumbleweed