xfce4-panel issueshttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues2022-07-14T15:23:58Zhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/75Support StartupWMClass2022-07-14T15:23:58ZBugzilla MigrationSupport StartupWMClass## Submitted by Khazar
Assigned to **Nick Schermer**
**[Link to original bug (#10238)](https://bugzilla.xfce.org/show_bug.cgi?id=10238)**
## Description
http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest...## Submitted by Khazar
Assigned to **Nick Schermer**
**[Link to original bug (#10238)](https://bugzilla.xfce.org/show_bug.cgi?id=10238)**
## Description
http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html
Key: StartupWMClass ; Description: If specified, it is known that the application will map at least one window with the given string as its WM class or WM name hint (see the Startup Notification Protocol Specification for more details).
I want to redefine WM_CLASS(STRING) of xfce4-weather-plugin 0.8.3 to xfce4-weather-plugin or Weather Update, instead of having the constant WM_CLASS(STRING) = "wrapper", "Wrapper", by using StartupWMClass key within /usr/share/xfce4/panel/plugins/weather.desktop.
Version: 4.10.0https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/71Workspace Switcher won't show updated screen layout until clicked on2022-07-14T18:50:18ZBugzilla MigrationWorkspace Switcher won't show updated screen layout until clicked on## Submitted by haarp
Assigned to **Nick Schermer**
**[Link to original bug (#10160)](https://bugzilla.xfce.org/show_bug.cgi?id=10160)**
## Description
When monitors are added or removed via xrandr, the switcher will still show th...## Submitted by haarp
Assigned to **Nick Schermer**
**[Link to original bug (#10160)](https://bugzilla.xfce.org/show_bug.cgi?id=10160)**
## Description
When monitors are added or removed via xrandr, the switcher will still show the old layout until clicked on.
Version: 4.10.1https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/66Hidden panels move to different output than selected when disabling selected ...2022-04-06T13:55:12ZBugzilla MigrationHidden panels move to different output than selected when disabling selected output.## Submitted by ase..@..il.com
Assigned to **Nick Schermer**
**[Link to original bug (#10029)](https://bugzilla.xfce.org/show_bug.cgi?id=10029)**
## Description
Add panel, choose output-1 for it, make panel automatically hidden.
D...## Submitted by ase..@..il.com
Assigned to **Nick Schermer**
**[Link to original bug (#10029)](https://bugzilla.xfce.org/show_bug.cgi?id=10029)**
## Description
Add panel, choose output-1 for it, make panel automatically hidden.
Disable output 1.
Hidden panel moves to output-2.
Only hidden panels are affected. If the panel is set to hidden but not currently hidden(mouse over) it will not move.
Moved panels retain measurments (and position?) used in output-1.
Version: 4.10.0https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/57Configure behavior of window button left click2022-04-06T14:30:34ZBugzilla MigrationConfigure behavior of window button left click## Submitted by David M. Lloyd
Assigned to **Nick Schermer**
**[Link to original bug (#9768)](https://bugzilla.xfce.org/show_bug.cgi?id=9768)**
## Description
Presently, window buttons seem to behave in the following way. When yo...## Submitted by David M. Lloyd
Assigned to **Nick Schermer**
**[Link to original bug (#9768)](https://bugzilla.xfce.org/show_bug.cgi?id=9768)**
## Description
Presently, window buttons seem to behave in the following way. When you click on a window button, if the window is not focused, it gains focus; if it is focused, then it is minimized. However this behavior is somewhat annoying when you have focus following the mouse pointer; if you choose a window from the panel to raise that you've accidentally brushed with the mouse pointer, it is minimized instead of raised.
It would be nice if you could configure the window buttons such that when you click on a button, if the window is not raised, it is raised and focused; if it is raised but not focused it is focused; if it is raised and focused then it is minimized. This way you can raise windows easily without accidentally minimizing them. This makes sense (for me at least) because (from the panel at least) I want to raise windows far more often than I want to minimize them.
Version: 4.8.6https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/54Window titlebar appears behind top panel when having two monitors stacked on ...2022-11-14T13:11:40ZBugzilla MigrationWindow titlebar appears behind top panel when having two monitors stacked on top each other## Submitted by bra..@..il.com
**[Link to original bug (#9693)](https://bugzilla.xfce.org/show_bug.cgi?id=9693)**
## Description
Created attachment 4819
maximized window on main screen shows panel oddity when mazimized
I have a mul...## Submitted by bra..@..il.com
**[Link to original bug (#9693)](https://bugzilla.xfce.org/show_bug.cgi?id=9693)**
## Description
Created attachment 4819
maximized window on main screen shows panel oddity when mazimized
I have a multi monitor display, the center monitor is the main monitor which each display acting as an extension of this. On my main monitor I would like to have my top and bottom panels, however if I place a top panel on a monitor which has a monitor above it, maximized windows will go beyond the panel. This only happens when there is an above monitor. See screen shot for reference. Also, OS Debian wheezy, 4 monitors, xfce 4.8, xfwm.
**Attachment 4819**, "maximized window on main screen shows panel oddity when mazimized":
![Screenshot_from_2012-12-28_00_52_24](/uploads/fa9748a16f5293c79119075f9c2d2f4e/Screenshot_from_2012-12-28_00_52_24.png)
Version: 4.8.04.17.2Gaël BonithonGaël Bonithonhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/40Regression from 4.8: Broken Panel (severe bug) behaviour affecting maximized ...2022-04-04T17:03:04ZBugzilla MigrationRegression from 4.8: Broken Panel (severe bug) behaviour affecting maximized windows## Submitted by John
**[Link to original bug (#9310)](https://bugzilla.xfce.org/show_bug.cgi?id=9310)**
## Description
Created attachment 4631
Window behind the panel. Broken behaviour.
Go to panel properties ---> uncheck "Don't re...## Submitted by John
**[Link to original bug (#9310)](https://bugzilla.xfce.org/show_bug.cgi?id=9310)**
## Description
Created attachment 4631
Window behind the panel. Broken behaviour.
Go to panel properties ---> uncheck "Don't reserve space on boarders" if checked (default is unchecked as it should be). The maximized window SHOULD NOT hide behind the panel. With the current broken behaviour it is not possible to drag it out or close.
Reproduction:
1.Drag the window to tile it to the upper half (ala KDE).
2.Click to maximize the window.
3.The windows is hided behind the panel
Tested on Sabayon 10. Xfce 4.10
Don't annoy me with the questions. The bug is annoying enough. Xfce is the only sane DE. Please fix it. It has never been like that. Don't introduce regressions.
**Attachment 4631**, "Window behind the panel. Broken behaviour.":
![Screenshot2](/uploads/b0b9ac2d2848296f37b7d3ea9d53d052/Screenshot2.png)
Version: 4.10.0https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/21Launcher icons in the panel preferences/items dialog2022-04-05T15:08:04ZBugzilla MigrationLauncher icons in the panel preferences/items dialog## Submitted by Andrzej
Assigned to **Simon Steinbeiß `@ochosi`**
**[Link to original bug (#8364)](https://bugzilla.xfce.org/show_bug.cgi?id=8364)**
## Description
Currently all launcher displayed in the Panel Preferences/Items di...## Submitted by Andrzej
Assigned to **Simon Steinbeiß `@ochosi`**
**[Link to original bug (#8364)](https://bugzilla.xfce.org/show_bug.cgi?id=8364)**
## Description
Currently all launcher displayed in the Panel Preferences/Items dialog box have the same generic icon. Also, the tooltip shows only "Internal name: launcher-%d".
This is missing the most important information (from the user's perspective): "which launcher in the panel does this item corresponds to".
Ideally, the icon displayed in the Items should look the same as the icon displayed by the launcher in the panel. Also, the tooltip should mention the name of application(s) the launcher is configured to execute.
Version: Unspecifiedhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/824Applications Menu: Entire top level menu duplicated2024-03-12T14:18:57ZAlistair BuxtonApplications Menu: Entire top level menu duplicatedToday I clicked on the applications menu and everything in it appears twice.
I have never seen this happen before and I have no idea how to reproduce.
I am running panel 4.18.
![Screenshot_2024-03-12_11-51-36](/uploads/ea19364bfc24288...Today I clicked on the applications menu and everything in it appears twice.
I have never seen this happen before and I have no idea how to reproduce.
I am running panel 4.18.
![Screenshot_2024-03-12_11-51-36](/uploads/ea19364bfc24288c9c63aab61edc5e69/Screenshot_2024-03-12_11-51-36.png)https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/823Searching for "workspace" or "pager" yields no results on gitlab.xfce.org2024-03-11T22:11:34ZhobscobSearching for "workspace" or "pager" yields no results on gitlab.xfce.orgWhen searching gitlab for "workspace" or "pager", it returns [no results](https://i.imgur.com/4Mn24RI.jpeg).
It's apparently not considered an app or panel-plugin, but a component of xfce4-panel itself.
Would it be possible to add...When searching gitlab for "workspace" or "pager", it returns [no results](https://i.imgur.com/4Mn24RI.jpeg).
It's apparently not considered an app or panel-plugin, but a component of xfce4-panel itself.
Would it be possible to add an informational note somewhere, or a dummy section under panel-plugins, just to let people know where to go with Workspace/Pager issues?https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/822XFCE panel is not accessible2024-03-11T07:42:44ZEthin ProbstXFCE panel is not accessibleWhen solely using the keyboard, it is impossible to access the XFCE panel with the keyboard or even navigate it. It would be great if this could be fixed; the panel contains a lot of useful things that I'd appreciate, like not having to ...When solely using the keyboard, it is impossible to access the XFCE panel with the keyboard or even navigate it. It would be great if this could be fixed; the panel contains a lot of useful things that I'd appreciate, like not having to use the terminal just to check my battery status. (As an aside, the xfmenu that you can access via control-escape seems focused on something other than whatever the active window is, and it would be nice if it was always focused on the current window so it could give you context-specific actions.)https://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/820Clock panel applet fades when not focussed2024-03-08T08:48:56ZCiaran AnscombClock panel applet fades when not focussedPossibly other things too, but I've only noticed it with Clock as I don't use the panel for that much. I'd expect it to be readable at a glance whichever window is actually focussed, not faded.
Probably related to GTK+3 theme and how t...Possibly other things too, but I've only noticed it with Clock as I don't use the panel for that much. I'd expect it to be readable at a glance whichever window is actually focussed, not faded.
Probably related to GTK+3 theme and how things react to _NET_WM_STATE_FOCUSED. xfce4-datetime-plugin did not do this.
Attached image shows Clock (left) and Datetime (right) when panel does not have focus.
![panel](/uploads/8b450dd4a667d7013292ce17301ccb45/panel.png)https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/819Nextcloud desktop client always shows symbolic icon in Status Tray2024-03-04T17:46:53ZhaarpNextcloud desktop client always shows symbolic icon in Status TrayHi,
long-time observation here. Some apps such as the [Nextcloud desktop client](https://github.com/nextcloud/desktop) will always show the black/white symbolic icon in panel's Status Tray.
`Request symbolic icons` is disabled in the p...Hi,
long-time observation here. Some apps such as the [Nextcloud desktop client](https://github.com/nextcloud/desktop) will always show the black/white symbolic icon in panel's Status Tray.
`Request symbolic icons` is disabled in the plugin settings. Likewise, `Use monochrome icons` is disabled in Nextcloud.
On other DEs I have seen colored icons, or at least a green checkmark on the white cloud icon. This doesn't seem to show in Xfce panel.
xfce4-panel-4.19.2, nextcloud-client-3.11.1
Thanks!https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/818del2024-02-25T11:34:11ZJust Adeldeldelhttps://gitlab.xfce.org/xfce/xfce4-panel/-/issues/814Network management GUI: Create TUN/TAP, Proxy all traffic2024-02-12T10:25:07ZaissNetwork management GUI: Create TUN/TAP, Proxy all traffic* System proxy: [Wintun](https://github.com/nulldotblack/wintun)
[ligolo-ng](https://github.com/nicocha30/ligolo-ng)
[wireguard TUN](https://github.com/WireGuard/wireguard-go/tree/master/tun)
[Universal TUN/TAP driver](https://vtun.in...* System proxy: [Wintun](https://github.com/nulldotblack/wintun)
[ligolo-ng](https://github.com/nicocha30/ligolo-ng)
[wireguard TUN](https://github.com/WireGuard/wireguard-go/tree/master/tun)
[Universal TUN/TAP driver](https://vtun.info/)
[tun2socks](https://github.com/xjasonlyu/tun2socks)
[tun2proxy](https://github.com/blechschmidt/tun2proxy)
https://www.kernel.org/doc/html/v6.1/networking/tuntap.html
https://man.freebsd.org/cgi/man.cgi?query=tun
Network management GUI added option TUN
TUN acts as an agent for existing agreements, HTTP proxy HTTPS proxy SOCKS proxy
Use TUN mode to proxy all traffic throughout the system, including terminals
### Why this request?
I’m in a country where the internet is very blocked, and upgrading OS or downloading software is a hassle, github gitlab Ping over time 300ms.
In thousands of Linux and BSD distributions, there is no single system desktop environment that proxies all traffic,
I use a proxychains and it’s a terrible proxy for the terminal, very slow.https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/812errors when building from master branch2024-02-01T20:03:43Zcallmejoeerrors when building from master branchhello. trying to build to use panel on wayfire. runnning ./autogen.sh I get these errors at the end
```
parallel-tests: installing './test-driver'
panel/Makefile.am:57: error: ENABLE_X11 does not appear in AM_CONDITIONAL
panel/Makefile....hello. trying to build to use panel on wayfire. runnning ./autogen.sh I get these errors at the end
```
parallel-tests: installing './test-driver'
panel/Makefile.am:57: error: ENABLE_X11 does not appear in AM_CONDITIONAL
panel/Makefile.am:63: error: HAVE_GTK_LAYER_SHELL does not appear in AM_CONDITIONAL
plugins/systray/Makefile.am:41: error: ENABLE_X11 does not appear in AM_CONDITIONAL
wrapper/Makefile.am:25: error: ENABLE_X11 does not appear in AM_CONDITIONAL
wrapper/Makefile.am:31: error: HAVE_GTK_LAYER_SHELL does not appear in AM_CONDITIONAL
autoreconf: error: automake failed with exit status: 1
```
EDIT: i was successfully able to build it form the 4.19.2 tarball. However, when I try to run xfce4-panel I am getting the following errors:
```
xfce4-panel: Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
** Message: 20:48:18.942: Your compositor does not support the ext_workspace_manager_v1 protocol
xfce4-panel-Message: 20:48:18.959: Plugin "(null)-7" was not found and has been removed from the configuration
xfce4-panel-Message: 20:48:19.083: Plugin "(null)-43" was not found and has been removed from the configuration
xfce4-panel-Message: 20:48:19.084: Plugin "(null)-8" was not found and has been removed from the configuration
xfce4-panel-Message: 20:48:19.086: Plugin "(null)-12" was not found and has been removed from the configuration
xfce4-panel-Message: 20:48:19.087: Plugin "(null)-4" was not found and has been removed from the configuration
xfce4-panel-Message: 20:48:19.115: Plugin "(null)-10" was not found and has been removed from the configuration
(xfce4-panel:191692): Wnck-WARNING **: 20:48:19.210: libwnck is designed to work in X11 only, no valid display found
Segmentation fault (core dumped)
way@wayland ~ # ** Message: 20:48:19.416: Your compositor does not support the ext_workspace_manager_v1 protocol
(wrapper-2.0:191736): xfce4-panel-wrapper-WARNING **: 20:48:19.419: ProviderSignal call failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
```https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/811Updating panel elements (e.g. Clock or system monitor plugins) cause lag / st...2024-01-26T12:00:00ZShallrathUpdating panel elements (e.g. Clock or system monitor plugins) cause lag / stutter in video playback and gamesI have the same problem that is described in [this old issue in xfce4-systemload-plugin](https://gitlab.xfce.org/panel-plugins/xfce4-systemload-plugin/-/issues/7): Whenever something in the panel automatically updates itself, be it the s...I have the same problem that is described in [this old issue in xfce4-systemload-plugin](https://gitlab.xfce.org/panel-plugins/xfce4-systemload-plugin/-/issues/7): Whenever something in the panel automatically updates itself, be it the seconds on the clock or one of the system load graphs, I get a small stutter during video playback (YouTube) or games or the unigine-superposition benchmark.
It does not seem to matter if it comes from a built-in feature (displaying seconds on the clock) or a plugin (system monitor). Removing the system monitor plugin from the panel and disabling the seconds on the clock stopped the stuttering. Suspending the processes of the plugins with 'kill -19' also worked, but only on the plugins as the clock doesn't have its own process and I don't want to suspend the whole panel.
This is how it looks like: I let the unigine-superposition benchmark run in game mode (standing still for most constant frame times) and traced the frame times with mangohud. Displaying seconds on the clock has already been disabled but the frametime spikes produced by the clock looked just the same as these:
xfce4-systemload-plugin enabled with update interval 500ms
![Screenshot_2024-01-23_18h36m05s](/uploads/b36d2e2c0682b361e6d076df3c23e955/Screenshot_2024-01-23_18h36m05s.jpg)
xfce4-systemload-plugin removed from the panel:
![Screenshot_2024-01-23_18h35m13s](/uploads/7faf9bff1cf35935e0244c652f545a84/Screenshot_2024-01-23_18h35m13s.jpg)https://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/808Window buttons plugin: support urgency-like notifications based on xfce4-notifyd2023-12-28T07:14:14ZMichał GórnyWindow buttons plugin: support urgency-like notifications based on xfce4-notifydGTK4 has removed support for setting urgency hints on windows (sigh), and apparently:
> It was indeed dropped, and it's not coming back. The way forward is to integrate with the "startup notification" and "notifications" in general, in ...GTK4 has removed support for setting urgency hints on windows (sigh), and apparently:
> It was indeed dropped, and it's not coming back. The way forward is to integrate with the "startup notification" and "notifications" in general, in a way that can be related back to a window. E.g. a chat client that got a message would send a notification, and that would be tied to a window wanting to become active, so that the notification can be interacted with and directly focus the correct window.
>
> (https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/9#note_374512)
Would it be possible to implement this in xfce4-panel, so that we'd get some kind of urgency-like highlight for window when it sends a notification to xfce4-notifyd? I suppose the panel would then remove this highlight when the window is activated (or notification explicitly discarded?).
That said, reading from that thread, I have no clue if anyone actually figured out how to bind notifications to a specific window.https://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 Bonithon