xfce4-panel issueshttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues2023-04-11T07:32:26Zhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/732[Wayland] Keyboard grab not released by panel (plugins)2023-04-11T07:32:26Zsimplejack-src[Wayland] Keyboard grab not released by panel (plugins)Hello,
[Follow up to discussion with @Tamaranch]
When running on Wayland (Wayfire 0.7.5) I noticed my lockscreen is unable to receive keyboard input (after I've clicked a panel plugin, doesn't matter what gets focus after that point th...Hello,
[Follow up to discussion with @Tamaranch]
When running on Wayland (Wayfire 0.7.5) I noticed my lockscreen is unable to receive keyboard input (after I've clicked a panel plugin, doesn't matter what gets focus after that point the locksreen doesn't get input then) on the output that xfce4-panel exists on. Bit of debugging later determined its because of (in `wrapper/wrapper-plug-wayland:174`):
```
gtk_layer_set_keyboard_mode (GTK_WINDOW (plug), GTK_LAYER_SHELL_KEYBOARD_MODE_ON_DEMAND);
```
Now I know Wayfire (and wlroots as the backend alone) doesn't support `on_demand` keyboard interactivity (introduced in version 4 of the wlr_layer_shell protocol). Last I checked, (they could have fixed the bug by now) the versioning API wasn't working properly (such that you couldn't reliably check if the backend compositor actually supported this new mode).
So before I look into a proper fix* I was wondering why the above call is made? i.e. Why does the plugin try to receive keyboard interactivity?
*Currently thinking the best method might be to acquire and release keyboard interactivity is the best best
Thanks,https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/731Window Buttons / Tasklist sorting by Group Title & Timestamp is broken2023-04-08T11:14:26ZCraig SandersWindow Buttons / Tasklist sorting by Group Title & Timestamp is brokenI have "_Group windows by application_" checked with a sorting order of "_Group title and timestamp_".
Up until 4.18, that worked fine, exactly as I wanted. The oldest window was at the bottom, making it easy to select. I rely on this ...I have "_Group windows by application_" checked with a sorting order of "_Group title and timestamp_".
Up until 4.18, that worked fine, exactly as I wanted. The oldest window was at the bottom, making it easy to select. I rely on this to find my most commonly used browser windows, new windows tend to be transient while the ones I use the most stick around and end up at the bottom of the list.
When I upgraded to 4.18 in January, the oldest window moved to the top of the list, i.e. the sort order was reversed. An annoying change, but I got used to it quickly enough.
Today, after upgrading to 4.18.2, the oldest window moved back to the bottom of the list. OK, fine, I can get used to that again (in fact, I prefer it - although, really, there ought to be an option for Ascending vs Descending sort for the timestamp. And probably for the title too).
So far, so good.
The problem is that any new windows are placed below the oldest window - so the more new windows I open, the harder it is to find that oldest window. It may as well be random. It's certainly not ordered by timestamp.
This is probably a leftover from when the list was sorted with oldest at the top - it makes sense to add new windows to the bottom in that case. When sorted with oldest at the bottom, though, new windows should be added to the top.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/730tasklist: Crash when closing an app window with window grouping enabled2023-05-19T16:26:48ZGaël Bonithontasklist: Crash when closing an app window with window grouping enabledxfce4-panel 4.18.3, not sure yet how to reproduce this, see https://forum.xfce.org/viewtopic.php?pid=71556
```
Core was generated by `xfce4-panel'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fd22f737706 in gtk...xfce4-panel 4.18.3, not sure yet how to reproduce this, see https://forum.xfce.org/viewtopic.php?pid=71556
```
Core was generated by `xfce4-panel'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fd22f737706 in gtk_widget_get_visible (widget=0x2b) at ../gtk/gtk/gtkwidget.c:9126
Downloading source file /usr/src/debug/gtk3/build/../gtk/gtk/gtkwidget.c
9126 g_return_val_if_fail (GTK_IS_WIDGET (widget), FALSE);
[Current thread is 1 (Thread 0x7fd22dac15c0 (LWP 1868))]
(gdb) backtrace
#0 0x00007fd22f737706 in gtk_widget_get_visible (widget=0x2b) at ../gtk/gtk/gtkwidget.c:9126
#1 0x00007fd22daacd36 in xfce_tasklist_group_button_child_visible_changed (group_child=0x561f4413aad0)
at /usr/src/debug/xfce4-panel/xfce4-panel-4.18.3/plugins/tasklist/tasklist-widget.c:4399
#2 0x00007fd22f06f210 in g_closure_invoke
(closure=0x561f43fcd490, return_value=0x0, n_param_values=1, param_values=0x7fff475c1b30, invocation_hint=0x7fff475c1ab0)
at ../glib/gobject/gclosure.c:832
#3 0x00007fd22f09d2f8 in signal_emit_unlocked_R.isra.0
(node=node@entry=0x561f43f99fe0, detail=detail@entry=0, instance=instance@entry=0x561f440d64b0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff475c1b30) at ../glib/gobject/gsignal.c:3802
#4 0x00007fd22f08d095 in g_signal_emit_valist
(instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff475c1cd0)
at ../glib/gobject/gsignal.c:3555
#5 0x00007fd22f08d324 in g_signal_emit (instance=instance@entry=0x561f440d64b0, signal_id=<optimized out>, detail=detail@entry=0)
at ../glib/gobject/gsignal.c:3612
#6 0x00007fd22f73d66e in gtk_widget_dispose (object=0x561f440d64b0) at ../gtk/gtk/gtkwidget.c:12166
#7 0x00007fd22f07d531 in g_object_run_dispose (object=0x561f440d64b0) at ../glib/gobject/gobject.c:1448
#8 0x00007fd22f72d38a in gtk_widget_destroy (widget=<optimized out>) at ../gtk/gtk/gtkwidget.c:4780
#9 0x00007fd22daa8683 in xfce_tasklist_window_removed (screen=<optimized out>, window=0x561f444fddb0, tasklist=0x561f44038290)
at /usr/src/debug/xfce4-panel/xfce4-panel-4.18.3/plugins/tasklist/tasklist-widget.c:1995
#10 0x00007fd22f06dca6 in g_cclosure_marshal_VOID__OBJECTv
(closure=0x561f44042820, return_value=<optimized out>, instance=0x561f4410f0a0, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x561f4410fde0) at ../glib/gobject/gmarshal.c:1910
#11 0x00007fd22f08d23c in _g_closure_invoke_va
(param_types=0x561f4410fde0, n_params=<optimized out>, args=0x7fff475c2000, instance=0x561f4410f0a0, return_value=0x0, closure=0x561f44042820) at ../glib/gobject/gclosure.c:895
#12 g_signal_emit_valist (instance=0x561f4410f0a0, signal_id=257, detail=<optimized out>, var_args=var_args@entry=0x7fff475c2000)
at ../glib/gobject/gsignal.c:3462
#13 0x00007fd22f08d324 in g_signal_emit (instance=<optimized out>, signal_id=signal_id@entry=257, detail=detail@entry=0)
at ../glib/gobject/gsignal.c:3612
#14 0x00007fd22fd4cb12 in emit_window_closed (window=0x561f444fddb0, screen=0x561f4410f0a0) at ../libwnck/libwnck/screen.c:2218
#15 update_client_list (screen=0x561f4410f0a0) at ../libwnck/libwnck/screen.c:1561
--Type <RET> for more, q to quit, c to continue without paging--c
#16 do_update_now (screen=0x561f4410f0a0) at ../libwnck/libwnck/screen.c:2133
#17 0x00007fd22fd4d888 in update_idle (data=<optimized out>) at ../libwnck/libwnck/screen.c:2156
#18 0x00007fd22ef6a53b in g_main_dispatch (context=0x561f43f78b70) at ../glib/glib/gmain.c:3460
#19 g_main_context_dispatch (context=0x561f43f78b70) at ../glib/glib/gmain.c:4200
#20 0x00007fd22efc7219 in g_main_context_iterate.constprop.0 (context=0x561f43f78b70, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4276
#21 0x00007fd22ef69c7f in g_main_loop_run (loop=0x561f44121080) at ../glib/glib/gmain.c:4479
#22 0x00007fd22f5d8e4f in gtk_main () at ../gtk/gtk/gtkmain.c:1329
#23 0x0000561f427ff3a5 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/xfce4-panel/xfce4-panel-4.18.3/panel/main.c:382
```4.18.4Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/729Implicit declaration of gdk_wayland_display_query_registry when GTK+ is built...2023-04-06T18:18:37ZMichał GórnyImplicit declaration of gdk_wayland_display_query_registry when GTK+ is built without Wayland supportWhen GTK+ is built with Wayland support disabled (`-Dwayland_backend=false`), xfce4-panel fails to build with the following warning/error (depending on how the compiler treats implicit declarations; building with `--disable-wayland-clien...When GTK+ is built with Wayland support disabled (`-Dwayland_backend=false`), xfce4-panel fails to build with the following warning/error (depending on how the compiler treats implicit declarations; building with `--disable-wayland-client --disable-gtk-layer-shell`):
```
panel-application.c: In function ‘panel_application_init’:
panel-application.c:249:13: warning: implicit declaration of function ‘gdk_wayland_display_query_registry’ [-Wimplicit-function-declaration]
249 | if (! gdk_wayland_display_query_registry (display, "zwlr_foreign_toplevel_manager_v1"))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
panel-application.c:249:13: warning: nested extern declaration of ‘gdk_wayland_display_query_registry’ [-Wnested-externs]
```
Original bug report: https://bugs.gentoo.org/9038024.19.2Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/728External plugins on Wayland visible when another application is fullscreen2023-04-07T18:49:27Zsimplejack-srcExternal plugins on Wayland visible when another application is fullscreenHello,
When using xfce4-panel with external plugins (pulseaudio, notes, genmon, etc.) the icons (and text in the case of genmon) are still visible when another application is fullscreen.
Source code wise I see xfce4-panel is making use...Hello,
When using xfce4-panel with external plugins (pulseaudio, notes, genmon, etc.) the icons (and text in the case of genmon) are still visible when another application is fullscreen.
Source code wise I see xfce4-panel is making use of gtk-layer-shell (when supported by the compositor, which my compositor [Wayfire] does support). It seems that plugins are initialized (and generally stay at the OVERLAY level) and in the 'wrapper_' files (do external plugins use this?) there's a check to demote the layer of the plugins to TOP if the active window is determined to be fullscreen.
Given the above, I've two questions:
1.) Do external plugins use the 'wrapper_' files in their build? And thus is the fullscreen check not working correctly?
2.) Why is the default layer-shell layer OVERLAY? I understand that plugins are trying to be rendered on top of the panel, but couldn't the same be achieved using two different lower layers? i.e. Panel defaults to BOTTOM, plugins default to TOP (or they could both use the same layer and make the assumption that later spawned surfaces will default to occluding the backing panel)
Thanks,4.19.0Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/727Workspace Switcher scroll orientation keeps changing2023-03-30T21:59:11ZJosh VenturaWorkspace Switcher scroll orientation keeps changingHi friends,
I notice that for several versions of xfce4-panel, the workspace switcher would switch to the workspace above when scrolling up, and to the workspace below when scrolling down. Since I have horizontal scrolling on my mouse, ...Hi friends,
I notice that for several versions of xfce4-panel, the workspace switcher would switch to the workspace above when scrolling up, and to the workspace below when scrolling down. Since I have horizontal scrolling on my mouse, I appreciated this change as it gave me mouse access to four adjacent workspaces instead of two.
The behavior before this was simply to switch to the previous workspace number. So scrolling vertically in workspace 2 would take you to workspace 1 (up) or 3 (down). This behavior has recently resumed in 4.18.2.
It would be cool if this behavior were configurable. Alternatively, it would be cool if I could select the position of each workspace arbitrarily, but this sounds like a far more involved feature that offers little value over simply being able to map mouse scroll events to workspace switch actions, or even more simply, selecting the behavior of vertical scrolling between numerical and vertical selection.
Thanks for your consideration! (And for your ongoing efforts in maintaining this software.)
I am happy to assign a bounty to this issue, if there is a mechanism or channel for that.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/726ayatana-webmail icon in xfce4-panel (state bar plugin) is not refreshed2023-04-02T21:11:27ZEwan Le Bideauayatana-webmail icon in xfce4-panel (state bar plugin) is not refreshedWhen ayatana-webmail is installed and configured, new mail notifications are working great (visual and sound), but the mail icon in the xfce4-panel plugin is not refreshed, unless yo do "xfce4-panel -r". Tested under Manjaro and Debian 1...When ayatana-webmail is installed and configured, new mail notifications are working great (visual and sound), but the mail icon in the xfce4-panel plugin is not refreshed, unless yo do "xfce4-panel -r". Tested under Manjaro and Debian 11 with xfce 4.18.4.18.4Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/725External plugins unavailable, 4.18 & 4.192023-03-29T22:09:29ZSimon DedmanExternal plugins unavailable, 4.18 & 4.19After upgrading to 4.18 and now 4.19 due to [this](https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/151), no [external plugins](https://docs.xfce.org/panel-plugins/start) are available in Items > Add New Items. [Ostensibly](https://docs...After upgrading to 4.18 and now 4.19 due to [this](https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/151), no [external plugins](https://docs.xfce.org/panel-plugins/start) are available in Items > Add New Items. [Ostensibly](https://docs.xfce.org/xfce/xfce4-panel/add-new-items) these may need to be installed separately (see last line) but there's no info on how to do that (if indeed I need to do so, vs this being a bug). They're definitely not included as folders in the [build](https://gitlab.xfce.org/xfce/xfce4-panel/-/tree/master/plugins), and there [doesn't appear to be](https://gitlab.xfce.org/xfce) a separate xfce4-panel-plugins.
Any guidance appreciated. Per the other thread, my panel is now missing various background-running application icons e.g. audio control, bluetooth, Dropbox, NAS version of dropbox, redshift icon, psensors & memory sensor, network manager, possibly others.
Thanks!https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/724Remove the 1px border2024-03-07T18:25:18ZFlashwalkerRemove the 1px borderI have 1 px border on xfce4.18 panel at one side.
So if i set panel size to 44px i get actually 45px.
How can i get rid of this border?I have 1 px border on xfce4.18 panel at one side.
So if i set panel size to 44px i get actually 45px.
How can i get rid of this border?https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/723Enhancements: Panel options: Keep panel below; Not reserve space2023-03-26T17:32:54ZFlashwalkerEnhancements: Panel options: Keep panel below; Not reserve space**Enhancements**:
Add options to settings for:
- option for keep the panel below all windows below
- option for not reserve desktop space**Enhancements**:
Add options to settings for:
- option for keep the panel below all windows below
- option for not reserve desktop spacehttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/722Places plugin sometimes needs two clicks to open2023-03-22T23:53:56ZBugzilla MigrationPlaces plugin sometimes needs two clicks to open## Submitted by haarp
Assigned to **Andrzej**
**[Link to original bug (#15772)](https://bugzilla.xfce.org/show_bug.cgi?id=15772)**
## Description
Sometimes the first click (press-and-releasse) on the places plugin in my panel does...## Submitted by haarp
Assigned to **Andrzej**
**[Link to original bug (#15772)](https://bugzilla.xfce.org/show_bug.cgi?id=15772)**
## Description
Sometimes the first click (press-and-releasse) on the places plugin in my panel does nothing. A second click is needed to actually open it. Unfortunately I cannot reproduce this yet, it appears to be happening somewhat randomly.
Version: 1.8.0https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/721Enhancement: Add toggle option to switch between column or row-first order pl...2023-06-23T19:09:19ZBrian SteerEnhancement: Add toggle option to switch between column or row-first order placement of entries in task listWhen using a multi row panel, window entries in the task list are currently first ordered vertically by column, before making use of the horizontal space. I would like to be able to change it so that they will instead order first in the ...When using a multi row panel, window entries in the task list are currently first ordered vertically by column, before making use of the horizontal space. I would like to be able to change it so that they will instead order first in the horizontal direction. That is, they would populate the first row, and only after filling that would they then start to spill over to the second row.
Forum thread: https://forum.xfce.org/viewtopic.php?id=16592
Thank you for your attention!https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/720Desktop actions menu is missing if launcher is menu2023-03-17T13:13:35ZFlashwalkerDesktop actions menu is missing if launcher is menuDesktop actions menu (for `[Desktop Action SOME_ACTION]` entries in .desktop file) is missing if launcher is menu (multiple launchers)
xfce4.18Desktop actions menu (for `[Desktop Action SOME_ACTION]` entries in .desktop file) is missing if launcher is menu (multiple launchers)
xfce4.184.18.3Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/719Incorrect rendering in vertical/deskbar panels2023-03-10T15:01:33ZLeXofLeviafanIncorrect rendering in vertical/deskbar panelsStarting from `xfce4-panel` **v4.19**, when placed in a _deskbar_ (or _vertical_) panel, the systemload plugin bars ignore panel width and render into an arbitrary size.
I.e., unless the only row that's enabled is Uptime Monitor, what I...Starting from `xfce4-panel` **v4.19**, when placed in a _deskbar_ (or _vertical_) panel, the systemload plugin bars ignore panel width and render into an arbitrary size.
I.e., unless the only row that's enabled is Uptime Monitor, what I see in the panel looks like this:
![image](/uploads/776f8877cc2ece990b27967d11669788/image.png)
In order to see the plugin properly, the panel needs to be stretched to about triple of that width:
![image](/uploads/cc03c9afff0be490febdca4e6242ea31/image.png)4.19.1Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/718Plugin configuration is permanently lost upon intermittent plugin load failure2024-03-26T15:58:25ZMichael BüschPlugin configuration is permanently lost upon intermittent plugin load failureIf a panel plugin load fails, the plugin configuration is lost, dropped or corrupted.
That's especially bad, if the load failure is only intermittent.
For the origin of this issue, please see this sub thread:
https://gitlab.xfce.org/xfc...If a panel plugin load fails, the plugin configuration is lost, dropped or corrupted.
That's especially bad, if the load failure is only intermittent.
For the origin of this issue, please see this sub thread:
https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/151#note_66646
Expected behavior: The plugin configuration shall always be preserved. It shall only be deleted upon user request. If a any fatal error is detected during panel startup, it shall not write to the configuration.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/717Feature Request: Directory Plugin: Sorting file names and folder names in the...2023-02-25T19:46:02ZGeorge HillFeature Request: Directory Plugin: Sorting file names and folder names in the same sequence.
Please let me first say that I _love_ XFCE!
As to my feature request: I like the Directory plugin.
I am able to make it display both files and folders by setting the "File Pattern" to "*".
However, it sorts folders first, before any ...
Please let me first say that I _love_ XFCE!
As to my feature request: I like the Directory plugin.
I am able to make it display both files and folders by setting the "File Pattern" to "*".
However, it sorts folders first, before any files.
I would like to have the option to sort folders and files in the same sequence.
Could you please add that as a preference?
Thank you!https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/716The panel is not hidden after drag-n-drop2023-03-05T09:40:24ZFlashwalkerThe panel is not hidden after drag-n-dropIf i set 'Always hide' for panel, and then i drag-n-drop some file on the launcher in that panel,
after that the panel stays on top of all applications and is no longer hidden.
xfce4-panel, libxfce4ui-2-0:
4.18.1-1~bpo22.04If i set 'Always hide' for panel, and then i drag-n-drop some file on the launcher in that panel,
after that the panel stays on top of all applications and is no longer hidden.
xfce4-panel, libxfce4ui-2-0:
4.18.1-1~bpo22.044.18.3Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/715Xfce-panel doesn't show button hints2023-02-26T07:12:30ZArthur D.Xfce-panel doesn't show button hintsXfce-panel doesn't show hints when placed horizontally at the bottom of the screen with option "Automatically hide panel" set to "Never".
By hints I mean the text that should appear above the buttons and other panel elements when you ho...Xfce-panel doesn't show hints when placed horizontally at the bottom of the screen with option "Automatically hide panel" set to "Never".
By hints I mean the text that should appear above the buttons and other panel elements when you hover mouse cursor over them.
I use xfce4-panel 4.18.1-1 from Debian Testing.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/714Segfault under Xwayland2023-02-17T09:39:31ZDemi Marie ObenourSegfault under XwaylandIf I run `xfce4-panel` under [my Wayland compositor][1], I get:
```
(xfce4-panel:19437): dbind-WARNING **: 17:14:29.676: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate r...If I run `xfce4-panel` under [my Wayland compositor][1], I get:
```
(xfce4-panel:19437): dbind-WARNING **: 17:14:29.676: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: activation request failed: unit is masked.
xfce4-panel: Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
(xfce4-panel:19437): Wnck-WARNING **: 17:14:29.816: libwnck is designed to work in X11 only, no valid display found
(xfce4-panel:19437): Wnck-CRITICAL **: 17:14:29.817: wnck_screen_get_active_window: assertion 'WNCK_IS_SCREEN (screen)' failed
(xfce4-panel:19437): GLib-GObject-WARNING **: 17:14:29.849: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'
(xfce4-panel:19437): Gdk-CRITICAL **: 17:14:29.850: gdk_x11_display_error_trap_pop: assertion 'GDK_IS_X11_DISPLAY (display)' failed
(xfce4-panel:19437): Wnck-WARNING **: 17:14:29.973: libwnck is designed to work in X11 only, no valid display found
(xfce4-panel:19437): Wnck-CRITICAL **: 17:14:29.974: wnck_handle_get_screen: assertion 'display != NULL' failed
(xfce4-panel:19437): Wnck-CRITICAL **: 17:14:29.974: wnck_screen_get_windows: assertion 'WNCK_IS_SCREEN (screen)' failed
(xfce4-panel:19437): GLib-GObject-WARNING **: 17:14:29.974: invalid (NULL) pointer instance
(xfce4-panel:19437): GLib-GObject-CRITICAL **: 17:14:29.975: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(xfce4-panel:19437): GLib-GObject-WARNING **: 17:14:29.975: invalid (NULL) pointer instance
(xfce4-panel:19437): GLib-GObject-CRITICAL **: 17:14:29.975: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(xfce4-panel:19437): GLib-GObject-WARNING **: 17:14:29.975: invalid (NULL) pointer instance
(xfce4-panel:19437): GLib-GObject-CRITICAL **: 17:14:29.975: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(xfce4-panel:19437): GLib-GObject-WARNING **: 17:14:29.976: invalid (NULL) pointer instance
(xfce4-panel:19437): GLib-GObject-CRITICAL **: 17:14:29.976: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(xfce4-panel:19437): GLib-GObject-WARNING **: 17:14:29.976: invalid (NULL) pointer instance
(xfce4-panel:19437): GLib-GObject-CRITICAL **: 17:14:29.976: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(xfce4-panel:19437): Wnck-WARNING **: 17:14:30.025: libwnck is designed to work in X11 only, no valid display found
(xfce4-panel:19437): Wnck-CRITICAL **: 17:14:30.025: wnck_handle_get_screen: assertion 'display != NULL' failed
(xfce4-panel:19437): GLib-GObject-WARNING **: 17:14:30.025: invalid (NULL) pointer instance
(xfce4-panel:19437): GLib-GObject-CRITICAL **: 17:14:30.025: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(xfce4-panel:19437): Gtk-WARNING **: 17:14:30.106: GtkSocket: only works under X11
(xfce4-panel:19437): Gdk-CRITICAL **: 17:14:30.106: gdk_x11_window_get_xid: assertion 'GDK_IS_X11_WINDOW (window)' failed
(xfce4-panel:19437): GLib-GObject-WARNING **: 17:14:30.106: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'
zsh: segmentation fault (core dumped) xfce4-panel
```
[1]: https://github.com/DemiMarie/qubes-waylandhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/713A way to delay the startup of one of the plugin modules2023-02-15T18:49:03ZMatthew MorycinskiA way to delay the startup of one of the plugin modulesIs it at all possible to delay startup of one or more of the plugin modules? Sometimes there are race conditions that need to be corrected.
In my particular case, Mailwatch complains until it can connect to the mail server, because the ...Is it at all possible to delay startup of one or more of the plugin modules? Sometimes there are race conditions that need to be corrected.
In my particular case, Mailwatch complains until it can connect to the mail server, because the "server" is another application (Protonmail Bridge) that takes a while to start. I'd rather delay the module's startup than pollute Mailwatch's log with spurious alerts.
I see /usr/share/xfce4/panel/plugins/mailwatch.desktop, but there is no way to invoke bash with a sleep command in it, because mailwatch is a library file, not a command.
Thanks