Your message dated Tue, 11 Mar 2025 13:23:46 +0900
with message-id <20250311132346.48545bbb@jet>
and subject line Re: budgie-desktop: after logging to budgie desktop, taskbar
becomes unresponsive
has caused the Debian Bug report #1050554,
regarding budgie-desktop: after logging to budgie desktop, taskbar becomes
unresponsive
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1050554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050554
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: budgie-desktop
Version: 10.8-2
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
Just logging into budgie desktop and wait for minutes.
* What exactly did you do (or not do) that was effective (or
ineffective)?
1. Just logging into budgie desktop environment
2. Launch some applications
3. Work on something else for minutes
Then taskbar becomes unresponsive suddenly.
* What was the outcome of this action?
After logging to budgie desktop, the following strange behavior occurs.
- taskbar becomes unresponsible
- shortcut key (windows key) also doesn't work, so it fails to access
menu.
- clicking each icon on taskbar also doesn't work, so it can't launch
application at all.
Just after logging in, taskbar is responsive, so if you launch terminal
at that time, you can shutdown/reboot from terminal, but if not,
there is no way to shutdown/reboot.
journalctl reports something wrong with budgie-panel:
Aug 26 17:04:19 jet budgie-panel[3805]: gtk_container_remove:
assertion 'GTK_IS_WIDGET (widget)' failed Aug 26 17:04:19 jet
budgie-panel[3805]: gtk_container_remove: assertion 'GTK_IS_WIDGET
(widget)' failed Aug 26 17:04:19 jet budgie-panel[3805]:
gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed Aug
26 17:04:19 jet budgie-panel[3805]: gtk_container_remove: assertion
'GTK_IS_WIDGET (widget)' failed Aug 26 17:04:19 jet
budgie-panel[3805]: gtk_container_remove: assertion 'GTK_IS_WIDGET
(widget)' failed Aug 26 17:04:19 jet budgie-panel[3805]:
gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
* What outcome did you expect instead?
No responsible situation will be solved.
I have a concern that this behavior may not reproducible
because it can't be reproduced easily on clean virtual machine
(unstable).
so any advice is welcome.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (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 budgie-desktop depends on:
ii budgie-control-center 1.3.0-1
ii budgie-core 10.8-2
ii dconf-cli 0.40.0-4
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4
ii network-manager-gnome 1.32.0-3
ii xdotool 1:3.20160805.1-5
Versions of packages budgie-desktop recommends:
ii budgie-desktop-view 1.2.1-1
ii gir1.2-budgie-1.0 10.8-2
ii gir1.2-budgieraven-1.0 10.8-2
Versions of packages budgie-desktop suggests:
ii arc-theme 20221218-1
ii gnome-bluetooth-sendto 42.6-1
ii gnome-terminal 3.48.2-1
ii nautilus 44.2.1-2
ii papirus-icon-theme 20230801-1
ii slick-greeter 1.8.1-0.1
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags -1 unreproducible
Not reproducible with recent budgie-desktop, so close it.
--- End Message ---
