https://bugs.kde.org/show_bug.cgi?id=505926
--- Comment #2 from doms...@proton.me --- (In reply to Nate Graham from comment #1) > Can you attach an SVG wallpaper file that causes the crash for you? Thanks for the reply. TL;DR: I don´t think this can be a screen locker issue anymore and if nobody else has any issues, is probably not worth to look into. For anybody still interested, the situation just got stranger: Since the debian theme folders contain multiple SVGs for different resolutions, I wanted to make sure to attach the exact one which is actually used. But whenever I manually selected one of the SVGs, everything works fine, the lock screen loads and the background is shown. After more testing, moving files around etc. this is what happens: - the segfault seems to occur exclusively for some of the default options in the plasma settings under screen locking / appearance - manually selecting (via + Add..) the exact same SVGs from the corresponding theme folders does not result in a segfault - not all default themes are affected, but about half of the ones included with debian trixie are (i.e. Ceratopsian, futurePrototype, Joy, Lines) - when moving the SVGs from an affected theme out of the way and replacing them with SVGs from a working theme, does not segfault (lockscreen shows other themes SVGs) Other observations: On some kscreenlocker_greet runs (with --testing) the following messages where shown: kf.coreaddons: Cache is inaccessible /home/dominik/.cache/plasma_theme_breeze-dark.kcache kf.coreaddons: Deleting corrupted cache "/home/dominik/.cache/plasma_theme_breeze-dark.kcache" kf.coreaddons: Cache is inaccessible /home/dominik/.cache/plasma_theme_breeze-dark.kcache kf.coreaddons: Even a brand-new cache starts off corrupted, something is seriously wrong. :-( kf.coreaddons: Couldn't establish file backed memory mapping, will fallback to anonymous memory This run though did not segfault but the lockscreen was shown and worked as expected. Manually deleting the plasma_theme_breeze_dark.kcache file also did not fix the issue when an affected default theme is selected. Since kscreenlocker_greet can show any SVG perfectly fine when selected manually, I don't think there is anything wrong here. I don´t really know what to make out of this anymore, there seems to be a very specific constellation required to trigger the issue. Also no matter what I tried, I could not reproduce it on another debian trixie machine. -- You are receiving this mail because: You are watching all bug changes.
