[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#929925: marked as done (flameshot: spamming the system journal)

Your message dated Fri, 28 Nov 2025 13:48:24 -0500
with message-id <173aa1dccf4df0f361045808b6973766354d188d.camel@debian.org>
and subject line Re: Bug#929925: flameshot: spamming the system journal
has caused the Debian Bug report #929925,
regarding flameshot: spamming the system journal
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 owner@bugs.debian.org
immediately.)


-- 
929925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929925
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: flameshot
Version: 0.6.0-11
Severity: minor

Dear Maintainer,

    When I was looking through the system journal, I found a lot of 
    flameshot entries with the same message:

    org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "unbind"
    org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "bind"
    org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "unbind"
    org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "bind"
    org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "unbind"
    ...

    # journalctl -b | rg '\[1382\]: UdevQt: unhandled device action' | wc -l
    5536

    It seems to be triggered intermittently by something that produces
    a flood of entries in seconds, though I haven't been able to pinpoint
    the exact cause.

    # journalctl -b | rg org.dharkael.Flameshot | rg '23:27:0' | wc -l
    151

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:zh (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flameshot depends on:
ii  libc6           2.28-10
ii  libgcc1         1:8.3.0-6
ii  libqt5core5a    5.11.3+dfsg1-1
ii  libqt5dbus5     5.11.3+dfsg1-1
ii  libqt5gui5      5.11.3+dfsg1-1
ii  libqt5network5  5.11.3+dfsg1-1
ii  libqt5svg5      5.11.3-2
ii  libqt5widgets5  5.11.3+dfsg1-1
ii  libstdc++6      8.3.0-6

flameshot recommends no packages.

Versions of packages flameshot suggests:
ii  ca-certificates  20190110
ii  openssl          1.1.1b-2

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 13.3.0-1

On Mon, 03 Jun 2019 11:48:40 +0000 ghost <i@ghosts.work> wrote:
> Package: flameshot
> Version: 0.6.0-11
> Severity: minor
> 
> Dear Maintainer,
> 
>     When I was looking through the system journal, I found a lot of 
>     flameshot entries with the same message:
> 
>     org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "unbind"
>     org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "bind"
>     org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "unbind"
>     org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "bind"
>     org.dharkael.Flameshot[1382]: UdevQt: unhandled device action "unbind"
>     ...
> 
>     # journalctl -b | rg '\[1382\]: UdevQt: unhandled device action' | wc -l
>     5536
> 
>     It seems to be triggered intermittently by something that produces
>     a flood of entries in seconds, though I haven't been able to pinpoint
>     the exact cause.
> 
>     # journalctl -b | rg org.dharkael.Flameshot | rg '23:27:0' | wc -l
>     151

This bug no longer appears in the new release and the new packaged version.

Thanks,
Boyuan Yang

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: