[qubes-users] Task bar disappeared?

Scat · October 28, 2022, 4:06pm

I just had a strange experience, here is what happened:

My computer accidentally shut down as the computer became unplugged
I am not sure if I accidentally hid the task bar?

Regardless my task bar disappeared…not sure I am using the right term but I am refering to the bar, on my desktop, it was ontop of the screen. This task bar had icons for my wifi, battery, clock, etc…

I can only access my templates by left clicking on my desktop…

If my memory serves me right, I control this via the “panel” however when I go to:
Applications → System Tools->Panel

I get an error “Failed to show the preference dialog - GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable”

I found this solution:

Which brought the panel back…strange. Never had this before…

This was the solution provided on the link above:

Actually, this is the solution

@Qubes_User171 should start terminal in dom0, execute xfce4-panel. Panel will show up. Then it is needed forcibly to close the terminal regardless of the warning. The panel will disappear and reappear in a flash second. It usually happens when using context menu while on panel which somehow triggers closing the panel without the warning.

Newbie question but what command do I type in Dom0 to “execute”? Do I need to do something when they say “Then it is needed forcibly to close the terminal regardless of the warning.”?

Thanks…

Scat · October 28, 2022, 4:55pm

Update:

I typed: xfce4-panel into the Dom0 terminal
I received errors in the Dom0 terminal and as mentioned the Task bar appeared

It didn’t survive a reboot of my computer. I typed: xfce4-panel into Dom0 it appeared…

How do I fix this so it survives a reboot?

Stuart_Perkins1 · October 28, 2022, 5:52pm

...
I had a similar problem with the desktop wallpaper under Qubes 4.0. It went away after doing something similar.

Stuart

adw · October 28, 2022, 8:11pm

We have some open issues on xfce4-panel crashing:

github.com/QubesOS/qubes-issues

Xfce4-session crash on suspension after I have logged out once in dom0

opened 07:47AM - 02 Aug 22 UTC

logoerthiner1

T: bug C: desktop-linux-xfce4 P: default hardware support needs diagnosis C: power management

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release R4.1 kernel 5.18.9 ### Brief summary After I have tried logging out in dom0 in #7602, I found that each time I suspend, the screen goes to early booting screen. When I inspect in dom0 log I found out that Xfce4-session crashes. ``` dom0 systemd-coredump[42813]: Process 42261 (xfce4-session) of user 1000 dumped core. Stack trace of thread 42261: #0 0x0000599648a8b9d9 xfsm_manager_dbus_suspend (xfce4-session + 0x279d9) #1 0x00007ce2d3630af0 ffi_call_unix64 (libffi.so.6 + 0x6af0) #2 0x00007ce2d36302ab ffi_call (libffi.so.6 + 0x62ab) #3 0x00007ce2d421438d g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x1438d) #4 0x00007ce2d421388a g_closure_invoke (libgobject-2.0.so.0 + 0x1388a) #5 0x00007ce2d4225e7e signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x25e7e) #6 0x0000599648a80a5c _xfsm_dbus_manager_skeleton_handle_method_call (xfce4-session + 0x1ca5c) #7 0x00007ce2d4384ff1 g_dbus_interface_method_dispatch_helper (libgio-2.0.so.0 + 0x12bff1) #8 0x00007ce2d436abe2 call_in_idle_cb (libgio-2.0.so.0 + 0x111be2) #9 0x00007ce2d412345b g_idle_dispatch (libglib-2.0.so.0 + 0x4e45b) #10 0x00007ce2d412778f g_main_context_dispatch (libglib-2.0.so.0 + 0x5278f) #11 0x00007ce2d4127b18 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52b18) #12 0x00007ce2d4127e33 g_main_loop_run (libglib-2.0.so.0 + 0x52e33) #13 0x00007ce2d485c99d gtk_main (libgtk-3.so.0 + 0x25c99d) #14 0x0000599648a7a7e1 main (xfce4-session + 0x167e1) #15 0x00007ce2d3f0e082 __libc_start_main (libc.so.6 + 0x27082) #16 0x0000599648a7aa6e _start (xfce4-session + 0x16a6e) Stack trace of thread 42311: #0 0x00007ce2d3fdd86f __poll (libc.so.6 + 0xf686f) #1 0x00007ce2d4127aae g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52aae) #2 0x00007ce2d4127be3 g_main_context_iteration (libglib-2.0.so.0 + 0x52be3) #3 0x00007ce2d4127c31 glib_worker_main (libglib-2.0.so.0 + 0x52c31) #4 0x00007ce2d41517f2 g_thread_proxy (libglib-2.0.so.0 + 0x7c7f2) #5 0x00007ce2d40bc432 start_thread (libpthread.so.0 + 0x9432) #6 0x00007ce2d3fe86d3 __clone (libc.so.6 + 0x1016d3) Stack trace of thread 42312: #0 0x00007ce2d3fdd86f __poll (libc.so.6 + 0xf686f) #1 0x00007ce2d4127aae g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52aae) #2 0x00007ce2d4127e33 g_main_loop_run (libglib-2.0.so.0 + 0x52e33) #3 0x00007ce2d437b6aa gdbus_shared_thread_func (libgio-2.0.so.0 + 0x1226aa) #4 0x00007ce2d41517f2 g_thread_proxy (libglib-2.0.so.0 + 0x7c7f2) #5 0x00007ce2d40bc432 start_thread (libpthread.so.0 + 0x9432) #6 0x00007ce2d3fe86d3 __clone (libc.so.6 + 0x1016d3) Stack trace of thread 42313: #0 0x00007ce2d3fe313d syscall (libc.so.6 + 0xfc13d) #1 0x00007ce2d4176616 g_cond_wait_until (libglib-2.0.so.0 + 0xa1616) #2 0x00007ce2d40f74a1 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x224a1) #3 0x00007ce2d40f7ae6 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x22ae6) #4 0x00007ce2d4152199 g_thread_pool_thread_proxy (libglib-2.0.so.0 + 0x7d199) #5 0x00007ce2d41517f2 g_thread_proxy (libglib-2.0.so.0 + 0x7c7f2) #6 0x00007ce2d40bc432 start_thread (libpthread.so.0 + 0x9432) #7 0x00007ce2d3fe86d3 __clone (libc.so.6 + 0x1016d3) ``` Also core from xss-lock ``` dom0 systemd-coredump[42826]: Process 42604 (xss-lock) of user 1000 dumped core. Stack trace of thread 42604: #0 0x00007731255dcfc2 g_logv (libglib-2.0.so.0 + 0x59fc2) #1 0x00007731255dd233 g_log (libglib-2.0.so.0 + 0x5a233) #2 0x0000646ff4771be5 screensaver_event_cb (xss-lock + 0x4be5) #3 0x0000646ff4771cdf xcb_event_dispatch (xss-lock + 0x4cdf) #4 0x00007731255d578f g_main_context_dispatch (libglib-2.0.so.0 + 0x5278f) #5 0x00007731255d5b18 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52b18) #6 0x00007731255d5e33 g_main_loop_run (libglib-2.0.so.0 + 0x52e33) #7 0x0000646ff4770ecd main (xss-lock + 0x3ecd) #8 0x00007731253a3082 __libc_start_main (libc.so.6 + 0x27082) #9 0x0000646ff477102e _start (xss-lock + 0x402e) Stack trace of thread 42623: #0 0x000077312547286f __poll (libc.so.6 + 0xf686f) #1 0x00007731255d5aae g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52aae) #2 0x00007731255d5e33 g_main_loop_run (libglib-2.0.so.0 + 0x52e33) #3 0x00007731258296aa gdbus_shared_thread_func (libgio-2.0.so.0 + 0x1226aa) #4 0x00007731255ff7f2 g_thread_proxy (libglib-2.0.so.0 + 0x7c7f2) #5 0x000077312529a432 start_thread (libpthread.so.0 + 0x9432) #6 0x000077312547d6d3 __clone (libc.so.6 + 0x1016d3) Stack trace of thread 42614: #0 0x000077312547286f __poll (libc.so.6 + 0xf686f) #1 0x00007731255d5aae g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52aae) #2 0x00007731255d5be3 g_main_context_iteration (libglib-2.0.so.0 + 0x52be3) #3 0x00007731255d5c31 glib_worker_main (libglib-2.0.so.0 + 0x52c31) #4 0x00007731255ff7f2 g_thread_proxy (libglib-2.0.so.0 + 0x7c7f2) #5 0x000077312529a432 start_thread (libpthread.so.0 + 0x9432) #6 0x000077312547d6d3 __clone (libc.so.6 + 0x1016d3) Stack trace of thread 42616: #0 0x000077312547813d syscall (libc.so.6 + 0xfc13d) #1 0x0000773125624616 g_cond_wait_until (libglib-2.0.so.0 + 0xa1616) #2 0x00007731255a54a1 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x224a1) #3 0x00007731255a5ae6 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x22ae6) #4 0x0000773125600199 g_thread_pool_thread_proxy (libglib-2.0.so.0 + 0x7d199) #5 0x00007731255ff7f2 g_thread_proxy (libglib-2.0.so.0 + 0x7c7f2) #6 0x000077312529a432 start_thread (libpthread.so.0 + 0x9432) #7 0x000077312547d6d3 __clone (libc.so.6 + 0x1016d3) ``` ### Steps to reproduce 1. log out in dom0 after booting up machine 2. suspend ### Expected behavior suspension does not make any process in dom0 crash ### Actual behavior xfce4-session and sometimes xss-lock crashes.

github.com/QubesOS/qubes-issues

xfce4-panel crashes when certain window closes by itself on enabling window grouping

opened 05:32PM - 31 Aug 22 UTC

logoerthiner1

T: bug C: desktop-linux-xfce4 P: default needs diagnosis

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release R4.1 kernel 5.15.57 ### Brief summary I have enabled window grouping in xfce4-panel so for example all terminal windows of one certain VM is grouped into one term. By chance I have found that, when I open the window group on the taskbar, and when one window exits by itself, a few operations can make xfce4-panel crash and restart. ``` systemd-coredump[63659]: Process 63635 (xfce4-panel) of user 1000 dumped core. Stack trace of thread 63635: #0 0x0000763c1cc11d4c xfce_tasklist_button_button_press_event (libtasklist.so + 0xbd4c) #1 0x0000763c2114571b _gtk_marshal_BOOLEAN__BOXED (libgtk-3.so.0 + 0x40471b) #2 0x0000763c2086988a g_closure_invoke (libgobject-2.0.so.0 + 0x1388a) #3 0x0000763c2087c423 signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x26423) #4 0x0000763c208823be g_signal_emit_valist (libgobject-2.0.so.0 + 0x2c3be) #5 0x0000763c20882c63 g_signal_emit (libgobject-2.0.so.0 + 0x2cc63) #6 0x0000763c210ee5e4 gtk_widget_event_internal.part.0 (libgtk-3.so.0 + 0x3ad5e4) #7 0x0000763c20f9ccf0 propagate_event (libgtk-3.so.0 + 0x25bcf0) #8 0x0000763c20f9e9d3 gtk_main_do_event (libgtk-3.so.0 + 0x25d9d3) #9 0x0000763c20c73ef9 _gdk_event_emit (libgdk-3.so.0 + 0x3def9) #10 0x0000763c20ca8a06 gdk_event_source_dispatch (libgdk-3.so.0 + 0x72a06) #11 0x0000763c2077d78f g_main_context_dispatch (libglib-2.0.so.0 + 0x5278f) #12 0x0000763c2077db18 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52b18) #13 0x0000763c2077de33 g_main_loop_run (libglib-2.0.so.0 + 0x52e33) #14 0x0000763c20f9d99d gtk_main (libgtk-3.so.0 + 0x25c99d) #15 0x000059d7726859c7 main (xfce4-panel + 0x179c7) #16 0x0000763c20443082 __libc_start_main (libc.so.6 + 0x27082) #17 0x000059d772685f9e _start (xfce4-panel + 0x17f9e) Stack trace of thread 63637: #0 0x0000763c2051286f __poll (libc.so.6 + 0xf686f) #1 0x0000763c2077daae g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52aae) #2 0x0000763c2077dbe3 g_main_context_iteration (libglib-2.0.so.0 + 0x52be3) #3 0x0000763c2077dc31 glib_worker_main (libglib-2.0.so.0 + 0x52c31) #4 0x0000763c207a77f2 g_thread_proxy (libglib-2.0.so.0 + 0x7c7f2) #5 0x0000763c202cf432 start_thread (libpthread.so.0 + 0x9432) #6 0x0000763c2051d6d3 __clone (libc.so.6 + 0x1016d3) Stack trace of thread 63639: #0 0x0000763c2051286f __poll (libc.so.6 + 0xf686f) #1 0x0000763c2077daae g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x52aae) #2 0x0000763c2077de33 g_main_loop_run (libglib-2.0.so.0 + 0x52e33) #3 0x0000763c209d16aa gdbus_shared_thread_func (libgio-2.0.so.0 + 0x1226aa) #4 0x0000763c207a77f2 g_thread_proxy (libglib-2.0.so.0 + 0x7c7f2) #5 0x0000763c202cf432 start_thread (libpthread.so.0 + 0x9432) #6 0x0000763c2051d6d3 __clone (libc.so.6 + 0x1016d3) ``` Not sure whether this is the same as #7721. I also notice #7602 later, but I cannot relate #7602 with this bug. ### Steps to reproduce 1. Enable "window grouping": In System Tools - Panel - Items - Window Buttons - Edit the current selected item - Window Grouping - Always 2. Open 5 terminals in the same VM. They should form one window group. 3. Enter the line "sleep 3;exit" in one terminal; within the 3 seconds, click on the window group at the taskbar 4. Wait until the terminal exits by itself, and either click on the panel, or click on the ghost window term, or click to another window, or etc. (This step is not stable - basically every mentioned choice has 50% chance to crash xfce4-panel) ### Expected behavior xfce4-panel does not crash ### Actual behavior xfce4-panel crashes

Ulrich_Windl · November 5, 2022, 11:52pm

Update:
- I typed: xfce4-panel into the Dom0 terminal
- I received errors in the Dom0 terminal and as mentioned the Task bar
appeared

It didn't survive a reboot of my computer. I typed: xfce4-panel into Dom0
it appeared...

...
I had a similar problem with the desktop wallpaper under Qubes 4.0. It went away after doing something similar.

For a working journaled filesystem I'd expect that only items that were changed while the power failed would disappear (when the incomplete transaction is undone). Looks like some bug.
Maybe your disks use local caching or some other volatile write-back cache (known to fail with journaled filesystems)?

Regards,
Ulrich

Demi · November 6, 2022, 12:06am

It will only fail if one of the following is true:

1. The filesystem does not properly issue FLUSH and/or FUA commands.
2. The disk does not properly implement these commands.
3. Qubes OS is not properly issuing fsync().
- --
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab