Your message dated Tue, 15 Apr 2025 13:01:35 +0900
with message-id <20250415130135.784ecb26@jet>
and subject line Re: bibata-cursor-theme: Reply
has caused the Debian Bug report #1102328,
regarding bibata-cursor-theme: Cursor loading animations is broken and static
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.)
--
1102328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102328
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bibata-cursor-theme
Version: 2.0.6-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
A recent update to Debian Testing broke the rainbow wheel loading animation on
all Bibata cursors.
I'm using GNOME. No other cursors besides Adwaita are installed.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.21-amd64 (SMP w/12 CPU threads; PREEMPT)
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 bibata-cursor-theme depends on:
ii hicolor-icon-theme 0.18-2
bibata-cursor-theme recommends no packages.
bibata-cursor-theme suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: tags -1 unreproducible
It seems that it has nothing to do with this package,
so close it.
Regards,
On Mon, 14 Apr 2025 11:54:16 -0500
Fainche <[email protected]> wrote:
> Package: bibata-cursor-theme
> Followup-For: Bug #1102328
> X-Debbugs-Cc: [email protected]
>
> Dear Maintainer,
>
> This can be closed, it's fixed now. The problem was apparently in a
> different package.
--- End Message ---
