Hi Aurélien,
thank you for your quick reply.
There are many people running testing and/or unstable, me included, for whom
this bug doesn't happen. So we'll need a bit more analysis if we want to get it
fixed.
Could you try creating a new user (without an existing $HOME directory) on one
of the machines where you see the bug and report back if the new user still has
the issue ?
I created a new user via `adduser` and the problem persisted for it.
Interestingly, that user had a black background and not some default
background image. The .xsession-errors contains some complaints about missing
/home/kdetest.config/kdedefaults, but I did not try to resolve this.
Also can you find anything meaningful in the system log at the time where you
right click or during the load of the user session ?
The section of my .xsession-erros for today:
Xsession: X session started for mgoerner at Mi 14. Dez 09:18:06 CET 2022
dbus-update-activation-environment: setting
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting
XAUTHORITY=/home/mgoerner/.Xauthority
localuser:mgoerner being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
The .xsession-errors for the new created user:
Xsession: X session started for kdetest at Mi 14. Dez 11:58:00 CET 2022
dbus-update-activation-environment: setting
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1002/bus
dbus-update-activation-environment: setting DISPLAY=:1
dbus-update-activation-environment: setting
XAUTHORITY=/home/kdetest/.Xauthority
localuser:kdetest being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
QIODevice::read (QFile, "/home/kdetest/.config/kdedefaults/package"):
device not open
QDBusConnection: error: could not send signal to service "" path
"//home/kdetest/.config/kdedefaults/kdeglobals" interface "org.kde.kconfig.notify" member
"ConfigChanged": Invalid object path: //home/kdetest/.config/kdedefaults/kdeglobals
QDBusConnection: error: could not send signal to service "" path
"//home/kdetest/.config/kdedefaults/kdeglobals" interface "org.kde.kconfig.notify" member
"ConfigChanged": Invalid object path: //home/kdetest/.config/kdedefaults/kdeglobals
QDBusConnection: error: could not send signal to service "" path
"//home/kdetest/.config/kdedefaults/kdeglobals" interface "org.kde.kconfig.notify" member
"ConfigChanged": Invalid object path: //home/kdetest/.config/kdedefaults/kdeglobals
QDBusConnection: error: could not send signal to service "" path
"//home/kdetest/.config/kdedefaults/kcminputrc" interface "org.kde.kconfig.notify" member
"ConfigChanged": Invalid object path: //home/kdetest/.config/kdedefaults/kcminputrc
QDBusConnection: error: could not send signal to service "" path
"//home/kdetest/.config/kdedefaults/kwinrc" interface "org.kde.kconfig.notify" member
"ConfigChanged": Invalid object path: //home/kdetest/.config/kdedefaults/kwinrc
QDBusConnection: error: could not send signal to service "" path
"//home/kdetest/.config/kdedefaults/kwinrc" interface "org.kde.kconfig.notify" member
"ConfigChanged": Invalid object path: //home/kdetest/.config/kdedefaults/kwinrc
QPixmap: QGuiApplication must be created before calling defaultDepth().
QPixmap: QGuiApplication must be created before calling defaultDepth().
Neither `journalctl` nor `sudo journalctl` show anything of interest after
right clicking somewhere. Are there other logs I should have a look at?
Lastly if you could have a look at the upstream bugs.kde.org platform and
look for a similar bug report that would be useful. I'll have a look too when
I can.
I will do so and report if I find something.
Best
Max Görner
