xfce4-panel issueshttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues2023-05-15T20:41:36Zhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/746Random crashes2023-05-15T20:41:36ZSimon RusinovRandom crashesxfce4-panel crashes randomly when working in Intellij IDEA.
Here's the log
[xfce4-panel.log](/uploads/402cac06484074e028f90f5bae1aa653/xfce4-panel.log)xfce4-panel crashes randomly when working in Intellij IDEA.
Here's the log
[xfce4-panel.log](/uploads/402cac06484074e028f90f5bae1aa653/xfce4-panel.log)https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/745Panel crash after open vkcube-wayland2023-05-11T09:49:44ZMuhammad Akbar Yanuar MantariPanel crash after open vkcube-waylandDistro: openSUSE Tumbleweed
Version: [xfce4-panel-4.19.1+git.21.a3fab8eb](https://build.opensuse.org/package/show/home:mantarimay:xfce:rat/xfce4-panel) / [libxfce4windowing-4.19.2+git.11.5bdda56](https://build.opensuse.org/package/show/...Distro: openSUSE Tumbleweed
Version: [xfce4-panel-4.19.1+git.21.a3fab8eb](https://build.opensuse.org/package/show/home:mantarimay:xfce:rat/xfce4-panel) / [libxfce4windowing-4.19.2+git.11.5bdda56](https://build.opensuse.org/package/show/home:mantarimay:xfce:rat/libxfce4windowing)
Compositor: labWC (wlroots)
Steps to reproduce
1. open vkcube-wayland
2. crash
<details><summary>gdb result</summary>
```
#0 0x00007ffff7d4cb9e in xfw_window_wayland_get_gicon (window=0x555555b68680 [XfwWindowWayland])
at /usr/src/debug/libxfce4windowing-4.19.2+git.11.5bdda56/libxfce4windowing/xfw-window-wayland.c:224
wwindow = 0x555555b68680 [XfwWindowWayland]
gicon = <optimized out>
#1 0x00007ffff7d46d2b in xfw_window_get_gicon (window=window@entry=0x555555b68680 [XfwWindowWayland])
at /usr/src/debug/libxfce4windowing-4.19.2+git.11.5bdda56/libxfce4windowing/xfw-window.c:578
klass = 0x555555696c90
priv = 0x555555b68660
__func__ = "xfw_window_get_gicon"
#2 0x00007ffff7d46dcb in xfw_window_get_icon (window=0x555555b68680 [XfwWindowWayland], size=16, scale=scale@entry=1)
at /usr/src/debug/libxfce4windowing-4.19.2+git.11.5bdda56/libxfce4windowing/xfw-window.c:544
gicon = <optimized out>
priv = 0x555555b68660
__func__ = "xfw_window_get_icon"
#3 0x00007fffe6e64dd1 in xfce_tasklist_button_icon_changed (window=window@entry=0x555555b68680 [XfwWindowWayland], child=child@entry=0x555555b68c30)
at /usr/src/debug/xfce4-panel-4.19.1+git.21.a3fab8eb/plugins/tasklist/tasklist-widget.c:2761
context = 0x5555557bebd0 [GtkStyleContext]
pixbuf = <optimized out>
surface = <optimized out>
tasklist = 0x5555557652d0 [XfceTasklist]
icon_size = 16
scale_factor = 1
old_width = -1
old_height = -1
__func__ = "xfce_tasklist_button_icon_changed"
#4 0x00007fffe6e69117 in xfce_tasklist_button_new (tasklist=0x5555557652d0 [XfceTasklist], window=0x555555b68680 [XfwWindowWayland])
at /usr/src/debug/xfce4-panel-4.19.1+git.21.a3fab8eb/plugins/tasklist/tasklist-widget.c:3711
child = 0x555555b68c30
child = <optimized out>
group_child = 0x0
found = <optimized out>
__func__ = "xfce_tasklist_window_added"
#5 xfce_tasklist_window_added (screen=<optimized out>, window=0x555555b68680 [XfwWindowWayland], tasklist=0x5555557652d0 [XfceTasklist])
at /usr/src/debug/xfce4-panel-4.19.1+git.21.a3fab8eb/plugins/tasklist/tasklist-widget.c:1874
child = <optimized out>
group_child = 0x0
found = <optimized out>
__func__ = "xfce_tasklist_window_added"
#9 0x00007ffff708abfc in <emit signal 0x7ffff7d4f667 "window-opened" on instance 0x5555558469d0 [XfwScreenWayland]>
(instance=instance@entry=0x5555558469d0, detailed_signal=detailed_signal@entry=0x7ffff7d4f667 "window-opened") at ../gobject/gsignal.c:3664
var_args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7fffffffdd90, reg_save_area = 0x7fffffffdca0}}
detail = <optimized out>
--Type <RET> for more, q to quit, c to continue without paging--
signal_id = 210
itype = 0x5555556e8a70 [XfwScreenWayland]
__func__ = "g_signal_emit_by_name"
#6 0x00007ffff7070448 in g_closure_invoke (closure=0x5555556c8dd0, return_value=0x0, n_param_values=2, param_values=0x7fffffffdaa0, invocation_hint=0x7fffffffda20)
at ../gobject/gclosure.c:832
marshal = 0x7ffff7073960 <g_cclosure_marshal_VOID__OBJECT>
marshal_data = 0x0
in_marshal = 0
real_closure = 0x5555556c8db0
__func__ = "g_closure_invoke"
#7 0x00007ffff70834fe in signal_emit_unlocked_R
(node=node@entry=0x555555730020, detail=detail@entry=0, instance=instance@entry=0x5555558469d0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffffffdaa0) at ../gobject/gsignal.c:3812
tmp = <optimized out>
handler = 0x555555a60720
accumulator = 0x0
emission = {next = 0x0, instance = 0x5555558469d0, ihint = {signal_id = 210, detail = 0, run_type = (G_SIGNAL_RUN_FIRST | G_SIGNAL_ACCUMULATOR_FIRST_RUN)}, state = EMISSION_RUN, chain_type = 0x4 [void]}
class_closure = 0x5555556e80e0
handler_list = 0x555555a60720
return_accu = 0x0
accu = {g_type = 0x0, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
signal_id = 210
max_sequential_handler_number = 4898
return_value_altered = <optimized out>
#8 0x00007ffff708a82e in g_signal_emit_valist
(instance=instance@entry=0x5555558469d0, signal_id=signal_id@entry=210, detail=<optimized out>, var_args=var_args@entry=0x7fffffffdc58) at ../gobject/gsignal.c:3565
instance_and_params = <optimized out>
signal_return_type = <optimized out>
param_values = <optimized out>
node = <optimized out>
i = <optimized out>
n_params = <optimized out>
__func__ = "g_signal_emit_valist"
#10 0x00007ffff7d4c42f in toplevel_done (wl_toplevel=<optimized out>, data=0x555555b68680)
at /usr/src/debug/libxfce4windowing-4.19.2+git.11.5bdda56/libxfce4windowing/xfw-window-wayland.c:622
screen = 0x5555558469d0
window = 0x555555b68680 [XfwWindowWayland]
#11 toplevel_done (data=0x555555b68680, wl_toplevel=<optimized out>) at /usr/src/debug/libxfce4windowing-4.19.2+git.11.5bdda56/libxfce4windowing/xfw-window-wayland.c:616
--Type <RET> for more, q to quit, c to continue without paging--
window = 0x555555b68680 [XfwWindowWayland]
#12 0x00007ffff6bff8d2 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#13 0x00007ffff6bfc24f in ffi_call_int (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>)
at ../src/x86/ffi64.c:673
classes = {X86_64_INTEGER_CLASS, 32767, 4139755868, 32767}
stack = <optimized out>
argp = 0x7fffffffddb0 ""
arg_types = <optimized out>
gprcount = 2
ssecount = <optimized out>
ngpr = 1
nsse = 0
i = <optimized out>
avn = <optimized out>
flags = <optimized out>
reg_args = <optimized out>
#14 0x00007ffff6bfee96 in ffi_call (cif=0x7fffffffdf70, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>) at ../src/x86/ffi64.c:710
arg_types = 0x7fffffffdf90
i = <optimized out>
nargs = 2
max_reg_struct_size = <optimized out>
#15 0x00007ffff7f84a23 in wl_closure_invoke.constprop () at /lib64/libwayland-client.so.0
#16 0x00007ffff7f85203 in dispatch_event.isra () at /lib64/libwayland-client.so.0
#17 0x00007ffff7f85494 in wl_display_dispatch_queue_pending () at /lib64/libwayland-client.so.0
#18 0x00007ffff7ca2e84 in _gdk_wayland_display_queue_events (display=<optimized out>) at ../gdk/wayland/gdkeventsource.c:201
display_wayland = <optimized out>
source = 0x5555555ed5f0
__func__ = "_gdk_wayland_display_queue_events"
#19 0x00007ffff7c719a9 in gdk_display_get_event (display=0x5555555ccaf0 [GdkWaylandDisplay]) at ../gdk/gdkdisplay.c:442
__func__ = "gdk_display_get_event"
#20 0x00007ffff7ca9ab2 in gdk_event_source_dispatch (base=<optimized out>, callback=<optimized out>, data=<optimized out>) at ../gdk/wayland/gdkeventsource.c:120
source = <optimized out>
display = 0x5555555ccaf0 [GdkWaylandDisplay]
event = <optimized out>
#21 0x00007ffff6f6f8d8 in g_main_dispatch (context=0x5555555da790) at ../glib/gmain.c:3460
dispatch = 0x7ffff7ca9aa0 <gdk_event_source_dispatch>
prev_source = 0x0
begin_time_nsec = 0
was_in_call = 0
user_data = 0x0
callback = 0x0
cb_funcs = 0x0
--Type <RET> for more, q to quit, c to continue without paging--
cb_data = 0x0
need_destroy = <optimized out>
source = 0x5555555ed5f0
current = 0x5555555da9c0
i = 0
__func__ = "g_main_dispatch"
#22 g_main_context_dispatch (context=0x5555555da790) at ../glib/gmain.c:4200
#23 0x00007ffff6f6fce8 in g_main_context_iterate (context=0x5555555da790, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4276
max_priority = 2147483647
timeout = 157
some_ready = 1
nfds = <optimized out>
allocated_nfds = 5
fds = 0x555555b639c0
#24 0x00007ffff6f6ff9f in g_main_loop_run (loop=loop@entry=0x55555574e350) at ../glib/gmain.c:4479
__func__ = "g_main_loop_run"
#25 0x00007ffff75f68fd in gtk_main () at ../gtk/gtkmain.c:1329
loop = 0x55555574e350
#26 0x000055555556b0a8 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/xfce4-panel-4.19.1+git.21.a3fab8eb/panel/main.c:388
context = <optimized out>
error = 0x0
dbus_service = 0x5555556d6e60 [PanelDBusService]
succeed = <optimized out>
remote_succeed = 21845
i = <optimized out>
signums = {2, 3, 15, 6, 10}
error_msg = <optimized out>
sm_client = 0x55555571e8f0
```
</details>https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/744Xfce-Notes-Plugin not matching the correct icon2023-05-03T20:20:11Zs3idaniXfce-Notes-Plugin not matching the correct iconThe Xfce-Notes-Plugin appear on the panel with wrong icon until hover the mouse pointer over the launcher area or reload panel.
What I've done:
- Change the plugin position.
- `update-icon-caches /usr/share/icons/*`
- Remove the entire ...The Xfce-Notes-Plugin appear on the panel with wrong icon until hover the mouse pointer over the launcher area or reload panel.
What I've done:
- Change the plugin position.
- `update-icon-caches /usr/share/icons/*`
- Remove the entire panel and recreate it.
And.. Back to the same issue on reboot.
I'm running **Xubuntu 20.04** with **Xfce 4.14.3**
![xfce-panel-issue](/uploads/26ab0232345efa4689434a52131e099a/xfce-panel-issue.png)https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/743Utilize more mouse button actions in Directory Menu2023-04-29T16:49:37Zdrws rwxUtilize more mouse button actions in Directory MenuIn Directory Menu plugin's dropdown menu currently only the left mouse click is utilized for opening files. Directories are shown upon mouse hovering and cannot be opened in file explorer, except if the additional _Open Folder_ menu entr...In Directory Menu plugin's dropdown menu currently only the left mouse click is utilized for opening files. Directories are shown upon mouse hovering and cannot be opened in file explorer, except if the additional _Open Folder_ menu entry is enabled. This is a feature request to utilize more mouse button actions in Directory Menu, for instance:
1. Double (left) click on a (sub)directory to open it in a file explorer (working regardless of whether _Open Folder_ entry is enabled).
2. Middle click on a (sub)directory to open it in a terminal emulator (working regardless of whether _Open in Terminal_ entry is enabled).
3. Right click on a file or a (sub)directory to show the right-click menu (as on the desktop).
This feature request also supersedes and extends the 12-year old #11 - see number 1 in the list above.
Additionally, number 1 and 2 could be implemented in the plugin icon as well to act on the top-level directory.
The middle-click on an ordinary file action is not listed above since I couldn't find a good use for it, just mentioning it as a food for thought.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/742Mouse hovering over multiple Directory Menu plugins2023-04-29T17:19:03Zdrws rwxMouse hovering over multiple Directory Menu pluginsWhen going through multiple Directory Menu plugins in the panel user has to click twice (see #741) on each one to display its contents. Even if #741 is implemented, one click for each plugin instance (folder) will still be required.
Thi...When going through multiple Directory Menu plugins in the panel user has to click twice (see #741) on each one to display its contents. Even if #741 is implemented, one click for each plugin instance (folder) will still be required.
This is a feature request to allow opening additional Directory Menu menus upon mouse hovering in case one is already opened. It would allow user to quickly go through multiple top-level folders in a fast and familiar way (the same way that subfolders are accessed).https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/741One click too many when a plugin is shown and another one is clicked on2023-04-29T17:23:34Zdrws rwxOne click too many when a plugin is shown and another one is clicked onWhen a certain panel plugin is clicked on and opened (Calendar or Directory Menu for example) and user wants to open a different one, **two** clicks are required for that. The first one for closing the current menu and the second one for...When a certain panel plugin is clicked on and opened (Calendar or Directory Menu for example) and user wants to open a different one, **two** clicks are required for that. The first one for closing the current menu and the second one for opening the new one. A more practical behavior would be if only one click was required (on the newly selected plugin icon) to both close the current one and open the next one at once.
The Whisker Menu plugin actually already solved that, requiring only a single click to open another panel plugin even when its menu is opened. The best solution would probably be to transfer its solution to a more general part of the code so it applies to all plugins (and possibly between panels as well).https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/740xfce4-panel tasklist crash several times a day.2023-05-15T20:45:17ZHamed Sabetixfce4-panel tasklist crash several times a day.I can't say what exactly causes the crash but it's very annoying and happens several times a day.
ArchLinux 6.2.12-arch1-1
xfce4-panel v4.18.3
~/.xsession-errors
```
(xfce4-panel:1121): libtasklist-CRITICAL **: 10:06:02.090: tasklist-w...I can't say what exactly causes the crash but it's very annoying and happens several times a day.
ArchLinux 6.2.12-arch1-1
xfce4-panel v4.18.3
~/.xsession-errors
```
(xfce4-panel:1121): libtasklist-CRITICAL **: 10:06:02.090: tasklist-widget.c:4490 (xfce_tasklist_group_button_sort): expression 'group_child->type == CHILD_TYPE_GROUP' failed.
[3195:3195:0427/100628.196875:ERROR:interface_endpoint_client.cc(695)] Message 0 rejected by interface blink.mojom.WidgetHost
(xfce4-panel:1121): libtasklist-CRITICAL **: 10:06:49.363: tasklist-widget.c:4490 (xfce_tasklist_group_button_sort): expression 'group_child->type == CHILD_TYPE_GROUP' failed.
(xfce4-panel:1121): libtasklist-CRITICAL **: 10:06:49.424: tasklist-widget.c:4490 (xfce_tasklist_group_button_sort): expression 'group_child->type == CHILD_TYPE_GROUP' failed.
(wrapper-2.0:1148): GLib-GObject-CRITICAL **: 10:07:00.073: ../glib/gobject/gsignal.c:2778: instance '0x56331fbf56c0' has no handler with id '61'
(wrapper-2.0:1150): GLib-GObject-CRITICAL **: 10:07:00.089: ../glib/gobject/gsignal.c:2778: instance '0x558bb4ae72f0' has no handler with id '61'
weather-Message: 10:07:01.163: getting https://api.met.no/weatherapi/locationforecast/2.0/classic?lat=35.698002&lon=51.411499&altitude=1178
```
dmesg:
```
[ 5195.384837] xfce4-panel[1121]: segfault at fffff753 ip 00007fbf1a167da8 sp 00007ffeeb077500 error 4 in libtasklist.so[7fbf1a165000+c000] likely on CPU 6 (core 3, socket 0)
[ 5195.384868] Code: 48 8d 0d 2b a4 00 00 48 8d 15 9c 92 00 00 48 8d 3d f9 9d 00 00 ff 25 77 3a 01 00 0f 1f 80 00 00 00 00 53 48 8b 57 08 48 89 fb <83> ba 98 00 00 00 04 75 07 5b c3 0f 1f 44 00 00 48 8b 7f 50 48 8d
```https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/739starting alacarte , menulibre on any other menu editor from applications menu...2023-07-16T18:38:59Zfadi123gostarting alacarte , menulibre on any other menu editor from applications menu propertiesI wish I could start a menu editor from this window.
![Screenshot_2023-04-26_15-35-33](/uploads/c00d6692eeb21dbea8e2e517792ed652/Screenshot_2023-04-26_15-35-33.png)I wish I could start a menu editor from this window.
![Screenshot_2023-04-26_15-35-33](/uploads/c00d6692eeb21dbea8e2e517792ed652/Screenshot_2023-04-26_15-35-33.png)https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/738Hide delay for autohide panels: Default should be "no delay", allow to config...2023-05-15T20:53:23ZKlaus KuscheHide delay for autohide panels: Default should be "no delay", allow to configure delayUp to now, autohide panels went away immediately when the mouse left the panel area.
Now, the panels are hidden with a one second delay. This is very annoying.
1.) Please make the old non-delay behaviour default again, this is a regress...Up to now, autohide panels went away immediately when the mouse left the panel area.
Now, the panels are hidden with a one second delay. This is very annoying.
1.) Please make the old non-delay behaviour default again, this is a regression!
2.) If there is a delay, please make it configurable, at least on/off, preferably in millisconds.
Reasons why this is so annoying:
I have three autohide panels (top, bottom, left) and most of my windows are maximized.
1.) If I want to click something in a window near the screen border
(e.g. the top menu, the search field at the bottom, a list item in a leftside menu or file/dir tree, ...)
or e.g. want to drag the window by its title bar,
and move the mouse a little bit too far, the panel opens and covers what I wanted to click.
I have to wait one second until the thing I wanted to click becomes visible again.
2.) Most of my windows are maximized.
Whenever I bring a window to the front or un-minimize it by clicking its panel window-button,
I have to wait one second until the window I just selected becomes fully visible and clickable.
Unfortunately, in most cases the panel with the window buttons covers the "interesting" areas of the maximized window I just selected to work with.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/737right click menu for xfce application menu2023-04-22T18:40:32Zfadi123goright click menu for xfce application menuI wish there was a right click menu for xfce application menu items similar to the ones in whisker menu. they should feature entries such as add to desktop , add to panel and edit appliction..![right_click](/uploads/787ece34a430200b1ebb4...I wish there was a right click menu for xfce application menu items similar to the ones in whisker menu. they should feature entries such as add to desktop , add to panel and edit appliction..![right_click](/uploads/787ece34a430200b1ebb47066bc35b18/right_click.png)
A right click menu for application menu as well , some people still like to use application menu.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/736clipman plugin multiplying icon (XFCE panel rendering/painting issues)2023-04-21T16:53:02ZArtem S. Tashkinovclipman plugin multiplying icon (XFCE panel rendering/painting issues)I've just upgraded from Fedora 37 to 38 and now the clipman plugin icon is multiplying.
To the left of it I have the sensors plugin with two data sources.
Right mouse clicking these redundant icons does nothing, i.e. this is something ...I've just upgraded from Fedora 37 to 38 and now the clipman plugin icon is multiplying.
To the left of it I have the sensors plugin with two data sources.
Right mouse clicking these redundant icons does nothing, i.e. this is something which doesn't belong to either of these two plugins. I've no idea what's going on.
![panel](/uploads/3337e632ecab28acccc60a6b39d02cef/panel.png)
This is a little later:
![panel2](/uploads/fc27f51d76f440cb4f8b784243c28d18/panel2.png)
So, something is rendering something where it shouldn't.
Here's a full list of enabled plugins:
![panel-settings](/uploads/762b8e4c3e9dd992fe5517c9ecca2d65/panel-settings.png)https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/735xfce4-panel shows a pile of overlapping pop-ups "unexpectedly left the panel"...2023-04-21T15:07:15ZSebastian Pippingxfce4-panel shows a pile of overlapping pop-ups "unexpectedly left the panel" every other time I log in to XHi! :wave:
I'm a happy user of XFCE, thanks for making XFCE and sharing it as Open Source! :pray:
When I log into X about every second time, xfce4-panel shows a pile of overlapping pop-ups saying "Plugin [..] unexpectedly left the pane...Hi! :wave:
I'm a happy user of XFCE, thanks for making XFCE and sharing it as Open Source! :pray:
When I log into X about every second time, xfce4-panel shows a pile of overlapping pop-ups saying "Plugin [..] unexpectedly left the panel" — screenshot below — that force me to either
- click "Execute" multiple times or
- do "pkill -9 xfce4-panel && xfce4-panel &" on a terminal.
If that could be solved, that would be fantastic.
For potential causes I can think of:
- use of some de-facto dependency before its available,
- use of a non-monotonic clock and NTP/clock updates hitting at the same time, and/or
- some other race condition.
Thanks and best
Sebastian
![xfce_panel_Screenshot_20210821_150914](/uploads/d1523a8280948f93553d0333e9368214/xfce_panel_Screenshot_20210821_150914.png)
PS: This is ticket https://bugs.gentoo.org/810850 in Gentoo Linux if of interest.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/734[Feature Request] Launcher 'checked' button behaviour2023-04-16T22:06:24Zsimplejack-src[Feature Request] Launcher 'checked' button behaviourHello,
Would it be possible to have a configuration option (xfconf/GUI setting) to have the builtin `Launcher` plugin behave like a checked/toggle button with respect to the command it spawns? In particular, when this mode is active, wh...Hello,
Would it be possible to have a configuration option (xfconf/GUI setting) to have the builtin `Launcher` plugin behave like a checked/toggle button with respect to the command it spawns? In particular, when this mode is active, when the button is clicked the command is spawned and so long as the spawn was successful and the child process remains alive the button transitions to the toggled/checked state. When the child process dies the button transitions back to its untoggled/unchecked state.
Adding this behavior to the launcher plugin (while I'm suggesting it as an optional setting, it could be made the default) brings it more inline with the behavior of other xfce4-panel plugins (both internal and external). Namely, the ability to provide visual feedback to the user concerning the spawned command (a CSS state/style could even set if the spawn failed, allowing the button to be flashed red or some such, however, this transition/action should be implemented in the users CSS theme).
Implementation wise, the groundwork looks to already be in place. Should be a matter of creating a `CheckedButton/ToggleButton` and using `xfce_spawn_on_screen_with_child_watch`.
Thanks,https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/733Mailwatch hangs and traps when opening Properties2023-04-13T11:25:40ZDale WMailwatch hangs and traps when opening PropertiesMail Watcher periodically stops updating. Opening Properties and clicking on Edit will cause a trap. MailWatch then restarts and continues normal operation, showing correct info with mouse hover over it.
From kern.log:
kernel: [417277.9...Mail Watcher periodically stops updating. Opening Properties and clicking on Edit will cause a trap. MailWatch then restarts and continues normal operation, showing correct info with mouse hover over it.
From kern.log:
kernel: [417277.934203] traps: panel-5-mailwat[2251] trap int3 ip:7fb5ef80eca7 sp:7ffe8090cd20 error:0 in libglib-2.0.so.0.6600.8[7fb5ef7d2000+88000]
What an int 3 is doing in any release code should raise a few eyebrows. Not good!https://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/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/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 space