Bug 383471 - Removing the default panel on a clean install causes dbus to not receive a reply on screen lock
Summary: Removing the default panel on a clean install causes dbus to not receive a re...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-14 00:23 UTC by witheredwitch
Modified: 2020-11-11 04:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description witheredwitch 2017-08-14 00:23:25 UTC
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.
Comment 1 Justin Zobel 2020-11-09 03:05:52 UTC
Thanks for the report.

I've tested this on Plasma from git master and cannot reproduce the issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved, thanks.
Comment 2 witheredwitch 2020-11-11 04:07:29 UTC
It's good to be marked as resolved. I don't see this issue in the more recent version I'm currently running.

pacman -Q | grep plasma
kdeplasma-addons 5.20.1-1
plasma-browser-integration 5.20.1-1
plasma-desktop 5.20.1-1
plasma-disks 5.20.1-1
plasma-framework 5.75.0-1
plasma-integration 5.20.1-1
plasma-meta 5.20-1
plasma-nm 5.20.1-1
plasma-pa 5.20.1-1
plasma-sdk 5.20.1-1
plasma-thunderbolt 5.20.1-1
plasma-vault 5.20.1-1
plasma-workspace 5.20.1.1-1
plasma-workspace-wallpapers 5.20.1-1
Comment 3 Justin Zobel 2020-11-11 04:09:03 UTC
Thanks for the update.