[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#997968: kde-config-sddm: SDDM Background is set incorrect (filename only, without path)



Package: kde-config-sddm
Followup-For: Bug #997968

Hi Patrick,

thanks for that hint, I may got mislead by this and the case, that if I re-open the SDDM settings
and click 'Change Background' the default? image gets shown and not the currently configured one.

So I think this report should be closed, and I will check again for the wrong image shown in the
'Change Background'-window. And report this issue separately.

PS: And setting a full path is even harmful, as the source background file is deleted from the
filesystem once it is changed to another file.

br m


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (504, 'unstable'), (503, 'testing'), (502, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-3-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kde-config-sddm depends on:
ii  libc6                       2.32-4
ii  libkf5archive5              5.86.0-1
ii  libkf5authcore5             5.86.0-1
ii  libkf5configcore5           5.86.0-1
ii  libkf5configgui5            5.86.0-1
ii  libkf5coreaddons5           5.86.0-1
ii  libkf5i18n5                 5.86.0-1
ii  libkf5kcmutils5             5.86.0-1
ii  libkf5quickaddons5          5.86.0-1
ii  libkf5widgetsaddons5        5.86.0-1
ii  libqt5core5a                5.15.2+dfsg-12
ii  libqt5gui5                  5.15.2+dfsg-12
ii  libqt5qml5                  5.15.2+dfsg-8
ii  libqt5widgets5              5.15.2+dfsg-12
ii  libstdc++6                  11.2.0-10
ii  qml-module-qtquick-layouts  5.15.2+dfsg-8
ii  qml-module-qtquick2         5.15.2+dfsg-8

kde-config-sddm recommends no packages.

kde-config-sddm suggests no packages.

-- no debconf information


Reply to: