Bug 1837530 - Impossible to end the session while Plank is running
Summary: Impossible to end the session while Plank is running
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: plank
Version: 32
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1839674 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-19 15:22 UTC by Pasquale Iannuzzi
Modified: 2021-02-23 00:24 UTC (History)
5 users (show)

Fixed In Version: plank-0.11.89-4.20210202.git013d051.fc32 plank-0.11.89-6.20210202.git013d051.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-19 01:14:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Warning of software still running (15.65 KB, image/png)
2020-05-19 15:22 UTC, Pasquale Iannuzzi
no flags Details

Description Pasquale Iannuzzi 2020-05-19 15:22:59 UTC
Created attachment 1689915 [details]
Warning of software still running

Created attachment 1689915 [details]
Warning of software still running

After upgrading from Fedora 31 to Fedora 32 I started to experience a malfunction when I turned off or restarted the PC or simply ended the session.
Everytime I'm shown a warning, of which I attach the screenshot, in which Plank is listed as still running program that is not responding.

The same warning tells me to wait for the program to finish, but the only way to end the session is to click on the button in the warning window or to end Plank normally (since, despite the notice, it still responds to all the commands).

I have no idea how much it affects, but I use Cinnamon as a desktop environment. 

The doubt is due to the fact that trying to end the session by running command line commands such as poweroff, reboot, shutdown -h now, shutdown -r now the system immediately ends the session without showing any warning.

As well as trying to terminate Plank with commands such as kill or xkill, Plank ends instantly as it's easily terminated by clicking on the Exit from its contextual menu.

I haven't had a chance to test Plank's behavior on other desktop environments at the moment.

Comment 1 Pasquale Iannuzzi 2020-05-19 15:28:40 UTC
Trying to start Plank from the terminal, I get the following STDOUT:

[CRITICAL] [GLib-GObject] g_param_spec_boxed: assertion 'G_TYPE_IS_BOXED (boxed_type)' failed
[CRITICAL] [GLib-GObject] validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
[WARN 16:37:57.444316] [Preferences:192] '/usr/share/plank/themes/Default/dock.theme' is read-only!

If I try to start Plank in debug mode, this is the output I get:

[DEBUG] [GLib-GIO] _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
[DEBUG] [GLib] unsetenv() is not thread-safe and should not be used after threads are created
[INFO] [AbstractMain:229] Plank version: 0.11.89
[INFO] [AbstractMain:230] Kernel version: 5.6.12-300.fc32.x86_64
[INFO] [AbstractMain:231] GLib version: 2.64.2 (2.63.6)
[INFO] [AbstractMain:234] GTK+ version: 3.24.20 (3.24.14)
[INFO] [AbstractMain:237] Wnck version: 3.32.0
[INFO] [AbstractMain:238] Cairo version: 1.16.0
[INFO] [AbstractMain:239] Pango version: 1.44.7
[INFO] [AbstractMain:240] + Cairo/Gtk+ HiDPI support enabled
[INFO] [AbstractMain:245] + XInput Barriers support enabled
[INFO] [WindowControl:68] Window-manager: Mutter (Muffin)
[DEBUG] [DockletManager:204] Loading module '/usr/lib64/plank/docklets/libdocklet-applications.so'
[INFO] [DockletManager:107] Docklet 'applications' registered
[DEBUG] [DockletManager:204] Loading module '/usr/lib64/plank/docklets/libdocklet-battery.so'
[INFO] [DockletManager:107] Docklet 'battery' registered
[DEBUG] [DockletManager:204] Loading module '/usr/lib64/plank/docklets/libdocklet-clippy.so'
[INFO] [DockletManager:107] Docklet 'clippy' registered
[DEBUG] [DockletManager:204] Loading module '/usr/lib64/plank/docklets/libdocklet-clock.so'
[INFO] [DockletManager:107] Docklet 'clock' registered
[DEBUG] [DockletManager:204] Loading module '/usr/lib64/plank/docklets/libdocklet-cpumonitor.so'
[INFO] [DockletManager:107] Docklet 'cpumonitor' registered
[DEBUG] [DockletManager:204] Loading module '/usr/lib64/plank/docklets/libdocklet-desktop.so'
[INFO] [DockletManager:107] Docklet 'desktop' registered
[DEBUG] [DockletManager:204] Loading module '/usr/lib64/plank/docklets/libdocklet-trash.so'
[INFO] [DockletManager:107] Docklet 'trash' registered
[DEBUG] [GLib] setenv()/putenv() are not thread-safe and should not be used after threads are created
[DEBUG] [GLib-GIO] _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
[INFO] [AbstractMain:299] Running with 1 docks ('dock1')
[DEBUG] [DockController:80] Create dock 'dock1' (config_folder = /home/paco/.config/plank/dock1)
[DEBUG] [GLib] setenv()/putenv() are not thread-safe and should not be used after threads are created
[DEBUG] [Settings:53] Bind 'PlankDockPreferences' to '/net/launchpad/plank/docks/dock1/'
[CRITICAL] [GLib-GObject] g_param_spec_boxed: assertion 'G_TYPE_IS_BOXED (boxed_type)' failed
[CRITICAL] [GLib-GObject] validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
[WARN] [Preferences:192] '/usr/share/plank/themes/Default/dock.theme' is read-only!
[DEBUG] [Preferences:349] Loading preferences from file '/usr/share/plank/themes/Default/dock.theme'
[DEBUG] [ItemFactory:176] Loading dock elements from '/home/paco/.config/plank/dock1/launchers'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/nemo.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/xed.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/com.gexperts.Tilix.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/claws-mail.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/libreoffice-startcenter.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/vlc.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/firefox.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/deadbeef.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/google-chrome.dockitem'
[DEBUG] [Preferences:349] Loading preferences from file '/home/paco/.config/plank/dock1/launchers/gimp.dockitem'
[DEBUG] [Unity:164] Initializing LauncherEntry support
[INFO] [HideManager:616] Barriers enabled (XInput 2.3 support)
[DEBUG] [PositionManager:675] Without draw_values there is trouble ahead
[DEBUG] [Unity:141] com.canonical.Unity lost
[INFO] [DockRenderer:481] Cairo.SurfaceType: XLIB

Comment 2 Fabio Valentini 2020-05-23 12:59:16 UTC
That's interesting ... the only recent change to plank that could be related to this is that it now registers itself with the session manager, so it can automatically be restarted in case it crashes. It looks like Cinnamon interprets this as "hey, I'm still running, don't kill me", which is probably wrong.

plank is only used as a default component on the Pantheon desktop, so I have not checked whether this would also affect other, custom non-standard setups (since I can't install every DE and try if plank still works with it).

Comment 3 Pasquale Iannuzzi 2020-05-23 16:02:55 UTC
I can only imagine that it isn't an easy task to develop a program and then have to test it on all the scenarios (in this case the desktop environments) on which the software could be expected to be used.
I tried to do it testing it on three other desktop environments: Gnome 3, Mate-Compiz and Xfce.
As it was widely predictable, since Xfce isn't a fork of Gnome, the only desktop environment on which I didn't find the problem was Xfce.
The problem is instead reproducible also on Gnome Xorg (with Wayland it isn't possible to run Plank) and on Mate-Compiz.

Comment 4 Nuno Dias 2020-05-26 13:25:25 UTC
*** Bug 1839674 has been marked as a duplicate of this bug. ***

Comment 5 Fabio Valentini 2020-05-27 22:57:45 UTC
So, to summarize - you were able to reproduce this problem on:

- Cinnamon
- GNOME (X.org)
- MATE (Compiz)

But the problem did not manifest on:

- Pantheon
- Xfce

Honestly, I have no idea why the first three would behave differently

Comment 6 ilikelinux69 2021-02-01 16:34:53 UTC
Same as I made the update. I use Mate compiz  When I run plank in terminal:

[CRITICAL 13:23:29.040063] [GLib-GObject] g_param_spec_boxed: assertion 'G_TYPE_IS_BOXED (boxed_type)' failed
[CRITICAL 13:23:29.044604] [GLib-GObject] validate_pspec_to_install: assertion 'G_IS_PARAM_SPEC (pspec)' failed
[WARN 13:23:29.326739] Creating surface took WAY TOO LONG (95ms), enabled downscaling for this cache!
[WARN 13:23:35.185889] Creating surface took WAY TOO LONG (39ms), enabled downscaling for this cache!
When i force ctrl & C i get:
[WARN 13:32:12.984407] [AbstractMain:42] Caught signal (2), exiting
closes Plank.

Comment 7 ilikelinux69 2021-02-01 16:36:48 UTC
I there some command you want me to do ... do see if i get more infos ?

Comment 8 Fabio Valentini 2021-02-06 15:56:40 UTC
I have built plank with some fixes from upstream in this COPR:
https://copr.fedorainfracloud.org/coprs/decathorpe/plank-fixes/

Could you test those builds and report if they address this bug?

Comment 9 ilikelinux69 2021-02-10 10:24:53 UTC
It looks good. I can now switch of/logout as usual. Thx for help.

Comment 10 Fabio Valentini 2021-02-10 14:54:35 UTC
Thanks for testing, I'll push those plank changes as official updates then.

Comment 11 Fedora Update System 2021-02-10 15:33:37 UTC
FEDORA-2021-012f859545 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-012f859545

Comment 12 Fedora Update System 2021-02-10 15:36:17 UTC
FEDORA-2021-db5bd56651 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-db5bd56651

Comment 13 Fedora Update System 2021-02-11 02:00:10 UTC
FEDORA-2021-012f859545 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-012f859545`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-012f859545

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2021-02-11 02:23:20 UTC
FEDORA-2021-db5bd56651 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-db5bd56651`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-db5bd56651

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2021-02-19 01:14:52 UTC
FEDORA-2021-db5bd56651 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2021-02-23 00:24:55 UTC
FEDORA-2021-012f859545 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.