https://bugs.kde.org/show_bug.cgi?id=383471
Bug ID: 383471
Summary: Removing the default panel on a clean install causes
dbus to not receive a reply on screen lock
Product: plasmashell
Version: master
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Panel
Assignee: plasma-b...@kde.org
Reporter: witheredwi...@gmail.com
Target Milestone: 1.0
When removing the default panel launching the screensaver and some dialog
boxes, specifially in the systems settings menus, will not receive a reply from
dbus.
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not
receive a reply.
Steps to reproduce:
1. Follow the basic arch install guide with pacstrap of base and create a new
user.
2. Install plasma, a desktop manager, and appropriate drivers (tested with
nouveau and nvidia proprietary drivers separately)
Tested with SDDM and plasma, SDDM and plasma-desktop, SDDM and plasma-meta,
LXDM and plasma, LXDM and plasma-meta, GDM and plasma, GDM and plasma-meta on
two different systems with the same behavior.
3. reboot
4a. systemctl start sddm.service
OR
4b. systemctl start gdm.service
OR
4c. systemctl start lxdm.service
and login with plasma
5a. ctrl+alt+L
OR
5b. qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock
At this point every is working as expected.
6. Unlock the screen
7. Delete the default panel.
8. Reboot
This is the point when the errors start.
9. Attemp either 5a or 5b
5b will print the error kicked back by dbus.
Various dialog boxes will also hang, such as confirmation of removing icons
from the desktop.
uname -a
Linux workshop 4.12.6-1-ARCH #1 SMP PREEMPT Sat Aug 12 09:16:22 CEST 2017
x86_64 GNU/Linux
pacman -Q | grep plasma
kdeplasma-addons 5.10.4-1
plasma-desktop 5.10.4-1
plasma-framework 5.36.0-2
plasma-integration 5.10.4-1
plasma-meta 5.10-1
plasma-nm 5.10.4-1
plasma-pa 5.10.4-1
plasma-sdk 5.10.4-1
plasma-workspace 5.10.4-2
plasma-workspace-wallpapers 5.10.4-1
Deleting the home folder settings to restore the plasma desktop to default
settings with the panel does stop the problem from happening, but with the
panel still there. The problem started a bit over a month ago for me. Before
discovering removing the panel was what was triggering the problem, I installed
on another disk, downgraded systemd and the kernel to before I started seeing
the errors, tried other DM/DE/driver combinations, and installed on an entirely
separate system. Having the default panel there seems to be loading something
that isn't loaded when the panel is removed, but I haven't been able to figure
out what it is.
--
You are receiving this mail because:
You are watching all bug changes.
