xfce4-panel issueshttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues2023-05-11T09:49:44Zhttps://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/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/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/11Allow for opening directories via double click2023-04-29T16:49:13ZBugzilla MigrationAllow for opening directories via double click## Submitted by Mathias Brodala
Assigned to **Nick Schermer**
**[Link to original bug (#7484)](https://bugzilla.xfce.org/show_bug.cgi?id=7484)**
## Description
I am aware that this is not a regular behavior of GTK applications but...## Submitted by Mathias Brodala
Assigned to **Nick Schermer**
**[Link to original bug (#7484)](https://bugzilla.xfce.org/show_bug.cgi?id=7484)**
## Description
I am aware that this is not a regular behavior of GTK applications but from my POV it adds to the convenience factor in this case: entries in the directory menu should be double-clickable which in turn would open the clicked menu.
Currently one always needs to open the submenu of a directory entry to be able to open it. if amount of directories within a directory is huge then you have to travel across the whole desktop in the worst case if you are not using keyboard navigation.
Thus the feature mentioned above could be one way of improving usability here.
Version: Unspecifiedhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/705Hovering over panel items with mouse button pressed?2023-04-29T16:41:34ZGeorg SchwarzHovering over panel items with mouse button pressed?With a horizontal xfce4 panel on top of the screen, is it possible to (horizontally) hover over the different items (widgets) in the panel with the left mouse button pressed and the pull-down menu of the pull-down menu of the item gettin...With a horizontal xfce4 panel on top of the screen, is it possible to (horizontally) hover over the different items (widgets) in the panel with the left mouse button pressed and the pull-down menu of the pull-down menu of the item getting into the mouse focus gets opened and closes when the mouse pointer moves over a different icon? I can open the menu of an item with the mouse button, but when I move the mouse pointer away it stays open and no other menu can be opened. This is probably not a bug, but still it would be nice to be able to change that behavior.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/336"Pin to Panel" option on "Window Buttons" right click menu.2023-04-15T15:25:41Z49studebaker"Pin to Panel" option on "Window Buttons" right click menu.Could you add a "Pin to Panel" option on "Window Buttons" right click menu?Could you add a "Pin to Panel" option on "Window Buttons" right click menu?https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/616New behaviour of panel auto-hiding has no option to configure delay2023-04-14T17:24:44ZFlashwalkerNew behaviour of panel auto-hiding has no option to configure delayNew behaviour of panel auto-hiding has non-configurable delay
Where is no option/toggle to disable panel auto-hiding delayNew behaviour of panel auto-hiding has non-configurable delay
Where is no option/toggle to disable panel auto-hiding delayhttps://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/710(Wayland) Focus not work when panel has launched2023-04-07T21:41:57ZGhost User(Wayland) Focus not work when panel has launched![a](/uploads/99895d35073baa7c9340f8da468b8945/a.png)
Sway 1.8
xfce4-panel git
when panel is launched, i can't focused any window![a](/uploads/99895d35073baa7c9340f8da468b8945/a.png)
Sway 1.8
xfce4-panel git
when panel is launched, i can't focused any windowhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/704Focust lost when a notification occurs2023-04-07T21:41:51ZHazegardFocust lost when a notification occursHello
When tools such as:
- https://github.com/ErikReider/SwayNotificationCenter
- https://github.com/francma/wob
- https://github.com/dunst-project/dunst
displays a popup, the focus on the currently active window is lost:
![croppe...Hello
When tools such as:
- https://github.com/ErikReider/SwayNotificationCenter
- https://github.com/francma/wob
- https://github.com/dunst-project/dunst
displays a popup, the focus on the currently active window is lost:
![cropped2](https://user-images.githubusercontent.com/11147206/213935398-881e3155-88c0-4626-90f5-9521546826d1.gif)
This behavior only happens when xfce4-panel is running.
I tried to remove all elmeents of the bar, but the focus is still lost.
I am currently on Wayland using Labwc.https://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/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/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/392Systray icon freezes after message/alert2023-03-31T19:23:57ZSunyataZeroSystray icon freezes after message/alert### Background
I'm developing PyQt applications and am using Qt's [QSystemTrayIcon.showMessage function](https://doc.qt.io/qt-5/qsystemtrayicon.html#showMessage)
### Problem
The system tray icon chosen for the application is not resto...### Background
I'm developing PyQt applications and am using Qt's [QSystemTrayIcon.showMessage function](https://doc.qt.io/qt-5/qsystemtrayicon.html#showMessage)
### Problem
The system tray icon chosen for the application is not restored after a message/alert has been shown. Instead the icon after a message/alert popup (for example an "i" inside a circle) continues to be the icon in the systray
### Expected behaviour
After the timeout given (maybe 15 seconds) the systray icon should be restored to the one chosen for the application
(This is what happens for other desktop environments that i've used: LXDE and LXQt)
### Instances of this issue
I've only seen this problem in Qt applications, not for example in the wireless network indicator in the systray
This is not just a problem in my own applications though, also the official PyQt5 examples have the same issue
### System
XUbuntu 20.04 (64 bit)4.17.0Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/209Switching desktops on workspace switcher with mouse wheel goes out of order2023-03-30T21:59:12ZBugzilla MigrationSwitching desktops on workspace switcher with mouse wheel goes out of order## Submitted by JtS
Assigned to **Nick Schermer**
**[Link to original bug (#15154)](https://bugzilla.xfce.org/show_bug.cgi?id=15154)**
## Description
Overview: More detailed restatement of summary.
Scrolling through desktops ...## Submitted by JtS
Assigned to **Nick Schermer**
**[Link to original bug (#15154)](https://bugzilla.xfce.org/show_bug.cgi?id=15154)**
## Description
Overview: More detailed restatement of summary.
Scrolling through desktops on the workplace switcher goes in an out-of-order fashion with 2 rows.
Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the bug. Include any special setup steps.
1) Set workplace switcher to 2 rows (right click on panel -> Panel -> Panel Preferences -> Items -> select Workplace Switcher -> "Edit currently selected item" -> set # of rows to 2).
2) Place cursor over the 1st workspace in the workspace switcher on the panel
3) Scroll down with the mouse scroll wheel
Actual Results: What the application did after performing the above steps.
Workspaces will scroll in the wrong order. It will be 1-3-2-4
Expected Results: What the application should have done, were the bug not present.
The workspace should scroll in correct order of workspaces, 1-2-3-4
Build Date & Hardware: Date and hardware of the build in which you first encountered the bug.
Build Xfce 4.12 on Ubuntu 18.10
Additional Builds and Platforms: Whether or not the bug takes place on other platforms (or browsers, if applicable).
No additional builds or platforms tested
Additional Information: Any other useful information.
It does not happen if I make the workspace switcher 1 row and scroll - this scrolls in correct order.
Version: 4.13.04.17.2Gaë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/512Panel border not configurable2023-03-26T17:42:57ZTrent McPheronPanel border not configurableHi there. So I went to [the forums](https://forum.xfce.org/viewtopic.php?id=15112) for this first, but I am not sure that anyone on the forums can help me; I think this might be a bug or a regression compared to the panel behavior in 4.1...Hi there. So I went to [the forums](https://forum.xfce.org/viewtopic.php?id=15112) for this first, but I am not sure that anyone on the forums can help me; I think this might be a bug or a regression compared to the panel behavior in 4.14. Well, a regression depending on perspective. In 4.14, you get the border only if you're in "none (system style)" mode, and you get no border with solid color and background image. Now you *always* get the border, and the border itself is not configurable. Not even this profoundly overbearing CSS can get rid of it:
```css
.xfce4-panel, .xfce4-panel frame, .xfce4-panel frame > border {
margin: 0px;
border-width: 0px;
border-style: none;
border-left: 0px none;
border-right: 0px none;
border-top: 0px none;
border-bottom: 0px none;
}
```
However, the GTK inspector does let me manipulate the property that controls this undesired behavior:
![20210723-224023](/uploads/6dd463f0565d4db1d4c875cf62647db3/20210723-224023.png)
I set that to 0 and I got my previous behavior back. But I'm not going to do that every time I start XFCE, and I don't think I can script it. I can see how some people might actually want the border to appear, but I built my system's look-and-feel around the fact that it didn't appear. I style active tasklist buttons to blend into maximized GTK windows. And I actually had window placement rules in Devilspie and picom rules based on the fact that 1080 - 26 = the height of maximized windows is 1054. *was*, rather; The forced border makes the panel take up 27px instead.
Can we get an Xfconf preference for this, maybe?4.17.1Gaël BonithonGaël Bonithon