Bug#1110743: xfce4-panel does not show after upgrade to Trixie
Package: xfce4-panel
Version: 4.20.4-1
Severity: important
X-Debbugs-Cc: debianbugreport_20240411+sane@cobbaut.be
Dear Maintainer,
* What led up to the situation?
I had a working Debian Bookworm with XFCE and xfce-panel on top. I upgraded to
Trixie (using apt).
After log on the xfce-panel flickers invisibly about five times in less than a
second. Then there is just the one desktop, but no panel.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried starting it from a terminal. It flickers invisibly for a second.
Here is the output:
```
$ xfce4-panel
Floating point exception
(wrapper-2.0:8026): xfce4-panel-wrapper-WARNING **: 19:01:56.309:
ProviderSignal call failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply:
Message recipient disconnected from message bus without replying
(wrapper-2.0:8021): xfce4-panel-wrapper-WARNING **: 19:01:56.309:
ProviderSignal call failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply:
Message recipient disconnected from message bus without replying
(wrapper-2.0:8026): Gdk-WARNING **: 19:01:56.312: The program 'wrapper-2.0'
received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 198 error_code 3 request_code 18 (core protocol) minor_code
0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
(wrapper-2.0:8021): Gdk-WARNING **: 19:01:56.313: The program 'wrapper-2.0'
received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 198 error_code 3 request_code 18 (core protocol) minor_code
0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
```
I also tried "apt reinstall xfce4-panel xfce4", no difference.
I also tried removing ~/.config/xfce, no difference.
* What was the outcome of this action?
Cannot start the XFCE panel.
Everything else seems to work (terminal, thunar, mpv, firefox, thunderbird...).
* What outcome did you expect instead?
I would expect to see my xfce-panel.
-- System Information:
Debian Release: 13.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.38+deb13-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xfce4-panel depends on:
ii exo-utils 4.20.0-1
ii libatk1.0-0t64 2.56.2-1
ii libc6 2.41-12
ii libcairo2 1.18.4-1+b1
ii libdbusmenu-gtk3-4 18.10.20180917~bzr492+repack1-4
ii libexo-2-0 4.20.0-1
ii libgarcon-1-0 4.20.0-1
ii libgarcon-gtk3-1-0 4.20.0-1
ii libgdk-pixbuf-2.0-0 2.42.12+dfsg-4
ii libglib2.0-0t64 2.84.3-1
ii libgtk-3-0t64 3.24.49-3
ii libgtk-layer-shell0 0.9.0-2
ii libpango-1.0-0 1.56.3-1
ii libpangocairo-1.0-0 1.56.3-1
ii libwayland-client0 1.23.1-3
ii libwnck-3-0 43.2-1
ii libx11-6 2:1.8.12-1
ii libxext6 2:1.3.4-1+b3
ii libxfce4panel-2.0-4 4.20.4-1
ii libxfce4ui-2-0 4.20.1-1
ii libxfce4util7 4.20.1-1
ii libxfce4windowing-0-0 4.20.2-1
ii libxfconf-0-3 4.20.0-1
xfce4-panel recommends no packages.
xfce4-panel suggests no packages.
-- no debconf information
Reply to: