Bug 460729 - (Miscellaneous) SDDM and Wayland session bugs, plasma-nm issues
Summary: (Miscellaneous) SDDM and Wayland session bugs, plasma-nm issues
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: regression, wayland-only
Depends on:
Blocks:
 
Reported: 2022-10-19 20:06 UTC by Sumi
Modified: 2022-10-20 20:23 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sumi 2022-10-19 20:06:33 UTC
SUMMARY
After switching to Debian Testing, i've noticed that SDDM on login puts the OS to sleep (with sleep enabled)  instead of going straight to Plasma, even though i have an external monitor connected, and when i first log in from boot SDDM kicks me back to login prompt most of the time, after the second login attempt Plasma Wayland finally starts.

But the worst thing happens when the system wakes up, because when that happens the Wayland session is completely corrupted, the same thing happens if i switch to a TTY and then go back to the Plasma session, possibly it's a Mesa thing, although i doubt it because this doesn't happen in GNOME Wayland.

When starting the Plasma session there is a chance that the NetworkManager service will stop working, from what i could check it seems that this happens when SDDM is the primary display manager, a while ago the NetworkManager service was renamed, so that could explain that bug.

STEPS TO REPRODUCE
1. From boot, log in to Plasma Wayland
2. SDDM kicks you back to the login prompt
3.  If the OS enter in sleep mode, wake it up, there is a chance that the Wayland session will start but with corrupted graphics.
*Alternatively
1. Switch to any TTY
2. Then back to Plasma

OBSERVED RESULT
Corrupt graphics and possibly duplicate sessions which cannot be closed by conventional means, making it impossible to shut down the computer if there is a sleep process, and plasma-nm stops working until i restart the NetworkManager service

EXPECTED RESULT
System should not enter to sleep on login, graphics should not get corrupted, Wayland session should always start, and the Network Manager applet should not stop working.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.4
Kernel Version: 5.19.0-2-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 2 × AMD Turion(tm) II Dual-Core Mobile M520
Memory: 3.6 GiB of RAM
Graphics Processor: AMD RS880
Manufacturer: Hewlett-Packard
Product Name: HP Pavilion dv4 Notebook PC
System Version: 049D210000241210000020000

$ inxi -G
Graphics:
  Device-1: AMD RS880M [Mobility Radeon HD 4225/4250] driver: radeon
    v: kernel
  Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
    compositor: kwin_wayland driver: X: loaded: radeon
    unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon
    resolution: 1440x900~60Hz
  OpenGL: renderer: AMD RS880 (DRM 2.50.0 / 5.19.0-2-amd64 LLVM 14.0.6)
    v: 3.3 Mesa 22.2.0

ADDITIONAL INFORMATION
I could send videos and screenshots showing the bugs later, since i'm a bit busy right now, i have to clarify that the lid of the laptop is closed at all times and I have an external monitor connected, important to clarify that the lid is closed at all times and i have an external monitor connected, and despite the inconvenience, KDE Plasma on Wayland is the fastest compositing desktop in this ATI, so that's a good sign.
Comment 1 Nate Graham 2022-10-20 20:23:07 UTC
Thanks for the bug report! Unfortunately this bug reports multiple distinct issues, which will make it not actionable. See https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more explanation.

Can you ask you to open a new bug report for each specific issue? Thanks again!

Also note that SDDM is not a KDE project, so bugs should be reported at https://github.com/sddm/sddm/issues