xfce4-panel issueshttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues2022-04-05T10:51:28Zhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/368Client Side Decoration (CSD) Windows seem bigger to panels, so they auto-hide...2022-04-05T10:51:28ZJean Franco Amoni RodríguezClient Side Decoration (CSD) Windows seem bigger to panels, so they auto-hide with no need```
- MX Linux 19.3 (Debian 10 Buster)
- XFCE 4.14
- GTK 3.24.5
```
If a `non-CSD` window is almost touching an `intelli-hiding` panel, it will not hide until the window overlap it, however, if the window is being `CSD`, so the panel wi...```
- MX Linux 19.3 (Debian 10 Buster)
- XFCE 4.14
- GTK 3.24.5
```
If a `non-CSD` window is almost touching an `intelli-hiding` panel, it will not hide until the window overlap it, however, if the window is being `CSD`, so the panel will hide even when the window is too away from the panel to touch it.
I know this is panels-related, but I don't know how much related to any XFCE-subproject because I can replicate this behavior with the `Plank` panel too.
You can test it with the `XFCE Terminal` (`non-CSD`) and `Tilix` (`CSD`), or toggling the `Firefox`'s `[ ] Title Bar` feature in the `Customize` page.
Here is a video demonstration:
https://youtu.be/5MwDkECInWAXfce 4.16Simon SteinbeißSimon Steinbeißhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/338Window frames are drawn incorrectly on CSD windows2022-04-18T20:49:49ZMichael AlexsanderWindow frames are drawn incorrectly on CSD windowsThis was noticeable before, and much more so now that CSD is used a lot more on the DE:
![Screenshot_from_2020-09-04_20-52-03](/uploads/bdb76307b5b50040f9f21ec2f4856b73/Screenshot_from_2020-09-04_20-52-03.png)This was noticeable before, and much more so now that CSD is used a lot more on the DE:
![Screenshot_from_2020-09-04_20-52-03](/uploads/bdb76307b5b50040f9f21ec2f4856b73/Screenshot_from_2020-09-04_20-52-03.png)Xfce 4.16Simon SteinbeißSimon Steinbeißhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/633[Bug] Adding an URL icon to the panel strips characters2022-09-17T10:52:09ZGhost User[Bug] Adding an URL icon to the panel strips charactersWhen creating an URL icon on the desktop and opening it, everything works fine. When adding the same URL icon to the panel and opening from the panel, characters such as %3A get stripped in the browser to just A or %40 to 0, but opening ...When creating an URL icon on the desktop and opening it, everything works fine. When adding the same URL icon to the panel and opening from the panel, characters such as %3A get stripped in the browser to just A or %40 to 0, but opening the icon properties in the panel reveals that the URL hasn't changed there, it changes in the browser after being opened.
I'm running:
OpenSUSE Tumbleweed 20220915
Xfce 4.16.1
Mozilla Firefox 104.0.2Xfce 4.18Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/821Option to set border width of PanelItembar widget.2024-03-16T11:25:12ZZetta1 Reid0Option to set border width of PanelItembar widget.An option to set the border size of the PanelItembar widget, since there is currently no way of setting the space between the window borders and the panel plugins themselves except for settings smaller icon size manually, and that doesn'...An option to set the border size of the PanelItembar widget, since there is currently no way of setting the space between the window borders and the panel plugins themselves except for settings smaller icon size manually, and that doesn't even work if the plugin doesn't use it. It can't be done even in CSS. Setting padding/margin both on .xfce4-panel and .xfce4-panel:first-child (the PanelItembar widget) doesn't do anything, and border properties don't actually add space around the children.
So basically this is the desired effect, on the right you can see the wnck pager plugin witch would normally be exactly filled to panel end:
![19_33_36_587__7.03.2024](/uploads/93a6ed1982339f1f87f0a0cb61698644/19_33_36_587__7.03.2024.png)4.19.4Zetta1 Reid0Zetta1 Reid0https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/809don't close prefernces when opening profiles via button2024-03-28T18:51:25Zpl aadon't close prefernces when opening profiles via buttonWhen you click `backup and restore` button in the panel preferences:
- the panel profiles dialogue opens (expected)
- the panel preferences dialogue closes (???)
The original dialogue should stay open. Rationale:
- if restoring, addit...When you click `backup and restore` button in the panel preferences:
- the panel profiles dialogue opens (expected)
- the panel preferences dialogue closes (???)
The original dialogue should stay open. Rationale:
- if restoring, additional configurations are often needed since not everything gets included in the saved version (like with external plugins). So need to return to the preferences dialogue after.
- backing up is something you might typically do when making changes, maybe even *before* making changes. There is utility to switching back and forth.
- it's good to make backups and user shouldn't be discouraged. Having the button there is very convenient.
- it is not predictable that opening one thing closes another. They are not mutually exclusive.
Of course as a workaround the two applications can be opened separately and that will work fine. :D4.19.4Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/806panel core dumps when Workspace Switcher is using Miniature View appearance.2023-12-12T22:02:49ZMyk Dowlingpanel core dumps when Workspace Switcher is using Miniature View appearance.Hi, I've been having my xfce4-panel core dump for a few months when the screensaver kicks in. If I start the panel from a terminal session, I can see these messages when it crashes:
```
(xfce4-panel:62576): Gtk-CRITICAL **: 10:40:45.158...Hi, I've been having my xfce4-panel core dump for a few months when the screensaver kicks in. If I start the panel from a terminal session, I can see these messages when it crashes:
```
(xfce4-panel:62576): Gtk-CRITICAL **: 10:40:45.158: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(xfce4-panel:62576): Gtk-WARNING **: 10:40:45.160: Attempting to add a widget with type WnckPager to a XfcePagerPlugin, but as a GtkBin subclass a XfcePagerPlugin can only contain one widget at a time; it already contains a widget of type WnckPager
(xfce4-panel:62576): libpager-CRITICAL **: 10:40:45.160: pager_plugin_style_updated: assertion 'gtk_widget_is_toplevel (toplevel)' failed
(xfce4-panel:62576): Gtk-WARNING **: 10:40:45.160: Attempting to add a widget with type WnckPager to a XfcePagerPlugin, but as a GtkBin subclass a XfcePagerPlugin can only contain one widget at a time; it already contains a widget of type WnckPager
(xfce4-panel:62576): libpager-CRITICAL **: 10:40:45.160: pager_plugin_style_updated: assertion 'gtk_widget_is_toplevel (toplevel)' failed
**
Wnck:ERROR:../libwnck/libwnck/pager.c:593:wnck_pager_size_request: assertion failed: (pager->priv->screen != NULL)
Bail out! Wnck:ERROR:../libwnck/libwnck/pager.c:593:wnck_pager_size_request: assertion failed: (pager->priv->screen != NULL)
Aborted (core dumped)
```
<details>
<summary>Here's the core dump info:</summary>
```
$ coredumpctl info -q 62576
PID: 62576 (xfce4-panel)
UID: <my-uid-from-ldap> (me)
GID: <my-gid-from-ldap> (usergroup)
Signal: 6 (ABRT)
Timestamp: Sun 2023-11-26 10:40:45 AEDT (54s ago)
Command Line: xfce4-panel
Executable: /usr/bin/xfce4-panel
Control Group: /user.slice/user-<my-uid-from-ldap>.slice/session-2.scope
Unit: session-2.scope
Slice: user-<my-uid-from-ldap>.slice
Session: 2
Owner UID: <my-uid-from-ldap> (me)
Boot ID: 36d921f477c54cbd98cf830f97b5752c
Machine ID: fb3c04514e8248138ebddd814f222f3e
Hostname: forge
Storage: /var/lib/systemd/coredump/core.xfce4-panel.10001.36d921f477c54cbd98cf830f97b5752c.62576.170095564500000>
Size on Disk: 2.5M
Message: Process 62576 (xfce4-panel) of user <my-uid-from-ldap> dumped core.
Stack trace of thread 62576:
#0 0x00007fce3765983c n/a (libc.so.6 + 0x8e83c)
#1 0x00007fce37609668 raise (libc.so.6 + 0x3e668)
#2 0x00007fce375f1542 abort (libc.so.6 + 0x26542)
#3 0x00007fce379fb0ee n/a (libglib-2.0.so.0 + 0x1e0ee)
#4 0x00007fce37a5c1d0 g_assertion_message_expr (libglib-2.0.so.0 + 0x7f1d0)
#5 0x00007fce38833380 n/a (libwnck-3.so.0 + 0x14380)
#6 0x00007fce388333c8 n/a (libwnck-3.so.0 + 0x143c8)
#7 0x00007fce38291fe2 n/a (libgtk-3.so.0 + 0x291fe2)
#8 0x00007fce38292a1f gtk_widget_get_preferred_width (libgtk-3.so.0 + 0x292a1f)
#9 0x00007fce3408245f n/a (libpager.so + 0x445f)
#10 0x00007fce38291fe2 n/a (libgtk-3.so.0 + 0x291fe2)
#11 0x00007fce38292a1f gtk_widget_get_preferred_width (libgtk-3.so.0 + 0x292a1f)
#12 0x000055e4344eeac5 n/a (xfce4-panel + 0x1fac5)
#13 0x00007fce38291fe2 n/a (libgtk-3.so.0 + 0x291fe2)
#14 0x00007fce38292a1f gtk_widget_get_preferred_width (libgtk-3.so.0 + 0x292a1f)
#15 0x000055e4344fe28b n/a (xfce4-panel + 0x2f28b)
#16 0x00007fce38291c81 n/a (libgtk-3.so.0 + 0x291c81)
#17 0x00007fce38292b72 gtk_widget_get_preferred_width_for_height (libgtk-3.so.0 + 0x292b72)
#18 0x00007fce38409877 n/a (libgtk-3.so.0 + 0x409877)
#19 0x00007fce3835fcd4 n/a (libgtk-3.so.0 + 0x35fcd4)
#20 0x00007fce38364677 n/a (libgtk-3.so.0 + 0x364677)
#21 0x00007fce37b5cb73 n/a (libgobject-2.0.so.0 + 0x33b73)
#22 0x00007fce37b5cc77 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33c77)
#23 0x00007fce37b5cd34 g_signal_emit (libgobject-2.0.so.0 + 0x33d34)
#24 0x00007fce38106cd9 n/a (libgtk-3.so.0 + 0x106cd9)
#25 0x00007fce37b5cb73 n/a (libgobject-2.0.so.0 + 0x33b73)
#26 0x00007fce37b5cc77 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33c77)
#27 0x00007fce37b5cd34 g_signal_emit (libgobject-2.0.so.0 + 0x33d34)
#28 0x00007fce37f47e03 n/a (libgdk-3.so.0 + 0x40e03)
#29 0x00007fce37f346ae n/a (libgdk-3.so.0 + 0x2d6ae)
#30 0x00007fce37a383ee n/a (libglib-2.0.so.0 + 0x5b3ee)
#31 0x00007fce37a36f69 n/a (libglib-2.0.so.0 + 0x59f69)
#32 0x00007fce37a95327 n/a (libglib-2.0.so.0 + 0xb8327)
#33 0x00007fce37a37b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
#34 0x00007fce381ecf6f gtk_main (libgtk-3.so.0 + 0x1ecf6f)
#35 0x000055e4344e139d main (xfce4-panel + 0x1239d)
#36 0x00007fce375f2cd0 n/a (libc.so.6 + 0x27cd0)
#37 0x00007fce375f2d8a __libc_start_main (libc.so.6 + 0x27d8a)
#38 0x000055e4344e1905 _start (xfce4-panel + 0x12905)
Stack trace of thread 62577:
#0 0x00007fce376d973d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fce37a902b7 g_cond_wait (libglib-2.0.so.0 + 0xb32b7)
#2 0x00007fce37a021b4 n/a (libglib-2.0.so.0 + 0x251b4)
#3 0x00007fce37a6aa7e n/a (libglib-2.0.so.0 + 0x8da7e)
#4 0x00007fce37a689f5 n/a (libglib-2.0.so.0 + 0x8b9f5)
#5 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 62578:
#0 0x00007fce376cdf6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007fce37a95276 n/a (libglib-2.0.so.0 + 0xb8276)
#2 0x00007fce37a35162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007fce37a351b2 n/a (libglib-2.0.so.0 + 0x581b2)
#4 0x00007fce37a689f5 n/a (libglib-2.0.so.0 + 0x8b9f5)
#5 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 62667:
#0 0x00007fce376d973d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fce1aac6fb1 n/a (librsvg-2.so.2 + 0x2c6fb1)
#2 0x00007fce1a896733 n/a (librsvg-2.so.2 + 0x96733)
#3 0x00007fce1a8963d0 n/a (librsvg-2.so.2 + 0x963d0)
#4 0x00007fce1a9bdff8 n/a (librsvg-2.so.2 + 0x1bdff8)
#5 0x00007fce1a9bacda n/a (librsvg-2.so.2 + 0x1bacda)
#6 0x00007fce1a9bb243 n/a (librsvg-2.so.2 + 0x1bb243)
#7 0x00007fce1aac6665 n/a (librsvg-2.so.2 + 0x2c6665)
#8 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 62666:
#0 0x00007fce376d973d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fce1aac6fb1 n/a (librsvg-2.so.2 + 0x2c6fb1)
#2 0x00007fce1a896733 n/a (librsvg-2.so.2 + 0x96733)
#3 0x00007fce1a8963d0 n/a (librsvg-2.so.2 + 0x963d0)
#4 0x00007fce1a9bdff8 n/a (librsvg-2.so.2 + 0x1bdff8)
#5 0x00007fce1a9bacda n/a (librsvg-2.so.2 + 0x1bacda)
#6 0x00007fce1a9bb243 n/a (librsvg-2.so.2 + 0x1bb243)
#7 0x00007fce1aac6665 n/a (librsvg-2.so.2 + 0x2c6665)
#8 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 62668:
#0 0x00007fce376d973d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fce1aac6fb1 n/a (librsvg-2.so.2 + 0x2c6fb1)
#2 0x00007fce1a896733 n/a (librsvg-2.so.2 + 0x96733)
#3 0x00007fce1a8963d0 n/a (librsvg-2.so.2 + 0x963d0)
#4 0x00007fce1a9bdff8 n/a (librsvg-2.so.2 + 0x1bdff8)
#5 0x00007fce1a9bacda n/a (librsvg-2.so.2 + 0x1bacda)
#6 0x00007fce1a9bb243 n/a (librsvg-2.so.2 + 0x1bb243)
#7 0x00007fce1aac6665 n/a (librsvg-2.so.2 + 0x2c6665)
#8 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 62671:
#0 0x00007fce376d973d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fce1aac6fb1 n/a (librsvg-2.so.2 + 0x2c6fb1)
#2 0x00007fce1a896733 n/a (librsvg-2.so.2 + 0x96733)
#3 0x00007fce1a8963d0 n/a (librsvg-2.so.2 + 0x963d0)
#4 0x00007fce1a9bdff8 n/a (librsvg-2.so.2 + 0x1bdff8)
#5 0x00007fce1a9bacda n/a (librsvg-2.so.2 + 0x1bacda)
#6 0x00007fce1a9bb243 n/a (librsvg-2.so.2 + 0x1bb243)
#7 0x00007fce1aac6665 n/a (librsvg-2.so.2 + 0x2c6665)
#8 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 62669:
#0 0x00007fce376d973d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fce1aac6fb1 n/a (librsvg-2.so.2 + 0x2c6fb1)
#2 0x00007fce1a896733 n/a (librsvg-2.so.2 + 0x96733)
#3 0x00007fce1a8963d0 n/a (librsvg-2.so.2 + 0x963d0)
#4 0x00007fce1a9bdff8 n/a (librsvg-2.so.2 + 0x1bdff8)
#5 0x00007fce1a9bacda n/a (librsvg-2.so.2 + 0x1bacda)
#6 0x00007fce1a9bb243 n/a (librsvg-2.so.2 + 0x1bb243)
#7 0x00007fce1aac6665 n/a (librsvg-2.so.2 + 0x2c6665)
#8 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 62579:
#0 0x00007fce376cdf6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007fce37a95276 n/a (libglib-2.0.so.0 + 0xb8276)
#2 0x00007fce37a37b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
#3 0x00007fce37c9d14c n/a (libgio-2.0.so.0 + 0x11214c)
#4 0x00007fce37a689f5 n/a (libglib-2.0.so.0 + 0x8b9f5)
#5 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#6 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 62670:
#0 0x00007fce376d973d syscall (libc.so.6 + 0x10e73d)
#1 0x00007fce1aac6fb1 n/a (librsvg-2.so.2 + 0x2c6fb1)
#2 0x00007fce1a896733 n/a (librsvg-2.so.2 + 0x96733)
#3 0x00007fce1a8963d0 n/a (librsvg-2.so.2 + 0x963d0)
#4 0x00007fce1a9bdff8 n/a (librsvg-2.so.2 + 0x1bdff8)
#5 0x00007fce1a9bacda n/a (librsvg-2.so.2 + 0x1bacda)
#6 0x00007fce1a9bb243 n/a (librsvg-2.so.2 + 0x1bb243)
#7 0x00007fce1aac6665 n/a (librsvg-2.so.2 + 0x2c6665)
#8 0x00007fce376579eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007fce376db7cc n/a (libc.so.6 + 0x1107cc)
ELF object binary architecture: AMD x86-64
```
</details>
Changing the Appearance setting of my Workspace Switcher to "Buttons" instead of "Miniature View" prevents the crash when my screensaver kicks in.4.18.6Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/804Launcher: adding additional firefox launchers duplicates options in right-cli...2023-11-26T15:59:00ZcastilmaLauncher: adding additional firefox launchers duplicates options in right-click menuToday I added another firefox launcher to directly start another firefox profile.
I noticed, this new launcher had 6 firefox specific entries in the right-click menu.
They are (translated by me) "New window", "New private window", "Open ...Today I added another firefox launcher to directly start another firefox profile.
I noticed, this new launcher had 6 firefox specific entries in the right-click menu.
They are (translated by me) "New window", "New private window", "Open profile manager", repeated twice.
I was surprised, so I removed and readded the firefox launchers and tried to to see whether that fixes it.
It does not. Now I have a firefox Launcher with 3 repetitions of the 3 entries and one with 2 repetitions.
Version: `xfce4-panel 4.18.5 (Xfce 4.18)`
![xfce-launcher-cut](/uploads/7957fbaaba91af785269bd122e773dbe/xfce-launcher-cut.png)
(I used a different logo for the left launcher but switched it for privacy reasons to the default image. Before I switched the logo, it had 6 repetitions (18 entries). Changing the logo removed 3 repetitions. Now I switched back to the personalized logo and there are still 3 repititons. Maybe this helps locating the error?)4.18.6Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/798Enormous timeout in Clock plug-in2023-10-23T20:45:30ZSteve GrahamEnormous timeout in Clock plug-inxfce4-panel was taking 18 seconds to start on my fast, 16-core i7 box. When I enabled PANEL_DEBUG, it turned out that the Clock plugin was waiting for all of that time "xfce4-panel(clock): trying to instantiate logind sleep monitor".
Aft...xfce4-panel was taking 18 seconds to start on my fast, 16-core i7 box. When I enabled PANEL_DEBUG, it turned out that the Clock plugin was waiting for all of that time "xfce4-panel(clock): trying to instantiate logind sleep monitor".
After the long wait, it then reported "libclock-Message: 15:56:17.194: could not get proxy for org.freedesktop.login1" and "(xfce4-panel:18336): libclock-WARNING **: 15:56:17.195: could not instantiate a sleep monitor" before allowing start-up to continue.
My Devuan Linux box does not run logind. (An Xorg user session is started with startx.)
I removed the Clock plug-in from the panel, closed the panel and restarted. Starting of the panel was instantaneous.4.18.6Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/790Pager: Row settings not respected across multiple pagers on same desktop2023-09-12T22:38:33ZPaul ReedPager: Row settings not respected across multiple pagers on same desktopI have one logical X screen split across two monitors; because of this, I've got two Xfce panels (one on each monitor).
This seems to work, except when it comes to the Pager: upon startup, the first pager to load will respect the row se...I have one logical X screen split across two monitors; because of this, I've got two Xfce panels (one on each monitor).
This seems to work, except when it comes to the Pager: upon startup, the first pager to load will respect the row setting (which I have set to 2; I have 2 Xfce workspaces as well); the pager in the second panel, however, will always display with one row.
If I right-click on the pager that has the incorrect number of rows displayed, and bring up its properties page, the number of rows is set to 2; if I reduce it to 1 and increase it back to 2, the pagers on _both_ panels will redraw twice, once with one row, and finally (both) with two rows. This is expected behavior (to me, anyway), and ultimately gets me what I want (2 rows the pagers on both panels/both monitors).
But it's annoying to have to do that upon every X startup... and it's not clear to me why the second panel isn't drawing with the correct number of rows on startup. I did peruse the code, and I see there's a a concept of a `master_plugin` for the pager, and additional pagers should get their row settings from this `master_plugin` (https://gitlab.xfce.org/xfce/xfce4-panel/-/blob/master/plugins/pager/pager.c#L231-235), but this isn't happening for some reason.
I did a little `g_warning()` debugging, and I didn't get too far, but it does look like the two panels are fighting each other for configuring the workspace (the first panel sets the rows to 2 in the libwnck code; the second panel tries to do the same, but libwnck returns various failures; the second pager then doesn't seem to update its internal state to have multiple rows, so you always get the default 1-row).
4.18.x and 4.19.x both have this issue.4.18.5Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/789Workspace Switcher uses wrong aspect ratio with Compiz (issue #119 still kick...2023-11-06T17:26:24ZFerdinandWorkspace Switcher uses wrong aspect ratio with Compiz (issue #119 still kicking)[Issue 119](https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/119) which was closed with [commit 8f310b86](https://gitlab.xfce.org/xfce/xfce4-panel/-/commit/8f310b868646036b6eb1694005b667f22229b0b1) seems to still exist to some degree.
...[Issue 119](https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/119) which was closed with [commit 8f310b86](https://gitlab.xfce.org/xfce/xfce4-panel/-/commit/8f310b868646036b6eb1694005b667f22229b0b1) seems to still exist to some degree.
The following three screenshots from Archlinux, using xfce-panel 4.18.4, illustrates the issue:
**Xfce panel with 4 workspaces**, using xfwm4
<details><summary>Screenshot 1</summary>
![Screenshot 1](https://i.imgur.com/eUqbA0b.jpeg "Screenshot 1")
</details>
**Switching to Compiz 0.9.14.2** still gives 4 workspaces, but they are compressed into the space of one of the previous four workspaces (Compiz version 0.8.18 has the same issue)
<details><summary>Screenshot 2</summary>
![Screenshot 2](https://i.imgur.com/T6AIMO9.jpeg "Screenshot 2")
</details>
**Switching back to xfwm4 again**, there is now only one workspace, not distorted, same size as in screenshot 1
<details><summary>Screenshot 3</summary>
![Screenshot 3](https://i.imgur.com/8qKfQXW.jpeg "Screenshot 3")
</details>
I'm not sure if the fault is with xfce-panel or Compiz, but something is amiss with the workspace management.4.18.5Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/784Workspace Switcher Miniature View not Updated After Display Settings Change2023-09-12T18:30:05ZFrashWorkspace Switcher Miniature View not Updated After Display Settings ChangeThe miniature view of the plugin does not get updated after display settings changes. The problem arises when the change is reset.
There are multiple ways how I can recreate the issuse:
### Plug in a Second Monitor
When I plug in a se...The miniature view of the plugin does not get updated after display settings changes. The problem arises when the change is reset.
There are multiple ways how I can recreate the issuse:
### Plug in a Second Monitor
When I plug in a second monitor with my thunderbolt dock, the miniature view gets double the size in the horizontal direction.
When i plug out the dock, the size of the miniature view stays the same.
### Rotate the Screen
When the rotation of the monitor is changed in the display settings, for example to left rotation, the user has 10 seconds to keep the configuration after clicking apply. After the timeout has run out and the settings change back to the previous configuration the miniature view does not get updated.
With a non-rotated screen my miniature view looks like this after the above procedure on a 16:9 monitor:
![image](/uploads/ead3ee3bd2258f859aad4c554d1061ae/image.png)
The miniature view with 4 workspaces (and open applications on them) shows still a rotated display.4.18.5Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/779Clock plugin format support double lines2023-08-04T08:06:23Z海天鹰Clock plugin format support double lines%a %_m/%d\n%R
```
Fri 8/04
13:20
```%a %_m/%d\n%R
```
Fri 8/04
13:20
```4.17.4YOGESH KAUSHIKYOGESH KAUSHIKhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/767Increase idle timeout to eliminate log spam2024-01-23T21:32:58ZMichael RIncrease idle timeout to eliminate log spamxfconf#28 created a 5-minute idle timeout for xfconfd but since the Xfce panel saves its settings every 10 minutes xfconfd is being continually reactivated, resulting in dbus adding two lines to the syslog/journal each time. This "noise...xfconf#28 created a 5-minute idle timeout for xfconfd but since the Xfce panel saves its settings every 10 minutes xfconfd is being continually reactivated, resulting in dbus adding two lines to the syslog/journal each time. This "noise" makes it difficult to see the important stuff and unnecessarily increases the size of the syslog/journal. It would be great if the delay could be increased to 15+ minutes.4.18.5Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/764high system load / unresponsive system when placed in "intelligently" hidden ...2023-07-08T16:16:45ZBugzilla Migrationhigh system load / unresponsive system when placed in "intelligently" hidden panel## Submitted by gon..@..mx.net
Assigned to **Florian Rivoal**
**[Link to original bug (#14315)](https://bugzilla.xfce.org/show_bug.cgi?id=14315)**
## Description
A very high system load occurs up to the point that the system becom...## Submitted by gon..@..mx.net
Assigned to **Florian Rivoal**
**[Link to original bug (#14315)](https://bugzilla.xfce.org/show_bug.cgi?id=14315)**
## Description
A very high system load occurs up to the point that the system becomes unresponsive if the verve plugin is used.
The behaviour is confirmed in Xubuntu 16.04 and the upcoming Xubuntu 18.04.
To reproduce the behaviour do:
1. create an second, empty panel and move it to the bottom of the desktop
2. place the verve command line within the panel
-> Note: up to this point the behaviour is alright when using the verve command line
3. configure the panel to hide "intelligently" and close all config dialogs
4. try to use the verve command line
The result should be high processor load and a flickering mouse pointer and panel.
I just had to hard reset my machine, because it stalled.4.18.5Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/756clock: One-second offset from real time2023-09-14T05:18:51ZGaël Bonithonclock: One-second offset from real timeOriginal bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036819
xfce4-panel 4.18.4/4.19.1
When seconds display is selected in the settings, an offset of several tenths of a second is often present at the start, and then...Original bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036819
xfce4-panel 4.18.4/4.19.1
When seconds display is selected in the settings, an offset of several tenths of a second is often present at the start, and then increases until it reaches one second. Two seconds then pass at once, with more or less precise readjustment, and so on.4.18.5Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/747actions: Implement fallback methods if org.xfce.SessionManager is not available2023-05-21T09:40:31ZGaël Bonithonactions: Implement fallback methods if org.xfce.SessionManager is not availableBy using XfceSystemd and XfceConsolekit now shared in libxfce4util. For locking there is now `org.xfce.SessionManager.Lock` and XfceScreensaver in libxfce4ui. See also https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/39.By using XfceSystemd and XfceConsolekit now shared in libxfce4util. For locking there is now `org.xfce.SessionManager.Lock` and XfceScreensaver in libxfce4ui. See also https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/39.Xfce 4.20https://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/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 Bonithon