Package: smuxi-frontend-gnome Version: 1.0.7-5 Severity: important When I get a notification while I'm not im my smuxi window, if I immediately click on the highlighted channel, then the application freezes and I have no other choice than to kill it.
If I first click in a non-highlighted channel, and then click on the highlighted channel, then everything works as usual. This is very annoying... -- System Information: Debian Release: bullseye/sid APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages smuxi-frontend-gnome depends on: ii libdbus-glib2.0-cil 0.6.0-1 ii libdbus2.0-cil 0.8.1-2 ii libglade2.0-cil 2.12.40-3 ii libglib2.0-0 2.64.3-1 ii libglib2.0-cil 2.12.40-3 ii libgtk2.0-0 2.24.32-4 ii libgtk2.0-cil 2.12.40-3 ii libgtkspell0 2.0.16-1.3 ii liblog4net1.2-cil 1.2.10+dfsg-7 ii libmessagingmenu12.10-cil 1.0.1-1 ii libmono-corlib4.5-cil 6.8.0.105+dfsg-3 ii libmono-posix4.0-cil 6.8.0.105+dfsg-3 ii libmono-system-core4.0-cil 6.8.0.105+dfsg-3 ii libmono-system-web4.0-cil 6.8.0.105+dfsg-3 ii libmono-system4.0-cil 6.8.0.105+dfsg-3 ii libnotify0.4-cil 0.4.0~r3032-7 ii librsvg2-common 2.48.4+dfsg-1 ii mono-runtime 6.8.0.105+dfsg-3 ii smuxi-engine 1.0.7-5 Versions of packages smuxi-frontend-gnome recommends: ii gnome-shell [notification-daemon] 3.36.2-1 ii notification-daemon 3.20.0-4 ii ssh-askpass-gnome [ssh-askpass] 1:8.2p1-4 smuxi-frontend-gnome suggests no packages. -- no debconf information
