Confirming if some KSystemlog entries for kwin_x11 mean something need to be addressed (or not)

Support KDE Plasma
1

As a new Linux user (settled on Manjaro KDE Plasma), I’m really grateful for finding/using both KSysGuard and KSystemlog, as they give me some insight in to what’s going on behind the scenes in different ways.

Now typically, key words like error, bad, and damage usually give cause for alarm… yet the application(s) (as far as I can tell) seems to be working just fine.

So are messages like this in KSystemlog “expected”/normal… or is there an issue lurking that needs to be looked into?

2021-07-19 6:22 P.M.	systemd	Started LibreOffice Writer - Word Processor.
2021-07-19 6:22 P.M.	kwin_x11	qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 46763, resource id: 104857601, major code: 15 (QueryTree), minor code: 0
2021-07-19 6:22 P.M.	kwin_x11	kwin_core: XCB error: 152 (BadDamage), sequence: 48634, resource id: 16217766, major code: 143 (DAMAGE), minor code: 2 (Destroy)
2021-07-19 6:22 P.M.	kwin_x11	kwin_core: XCB error: 152 (BadDamage), sequence: 49885, resource id: 16217798, major code: 143 (DAMAGE), minor code: 2 (Destroy)
2021-07-19 6:22 P.M.	kwin_x11	kwin_core: XCB error: 152 (BadDamage), sequence: 50556, resource id: 16217810, major code: 143 (DAMAGE), minor code: 2 (Destroy)
2021-07-19 6:22 P.M.	kwin_x11	kwin_core: XCB error: 152 (BadDamage), sequence: 53056, resource id: 16217843, major code: 143 (DAMAGE), minor code: 2 (Destroy)
2021-07-19 6:22 P.M.	kwin_x11	qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55060, resource id: 132120998, major code: 18 (ChangeProperty), minor code: 0
2021-07-19 6:22 P.M.	systemd	app-libreoffice\x2dwriter-bd143eeea42d4230bb075b4d192615a1.scope: Deactivated successfully.

Perhaps these are potential kwin_x11 bug reports in the making? If so, how would I do that? I saw a reference in another post to DDG bug file <application>, but don’t know what that means, and there are no man pages for DDG or bug.

And are there any additional commands I could run that would pull out more details above what KSystemlog is reporting?

2

  • DDG = Abbreviation for https://DuckDuckGo.com.
    The tutorial you’re talking about has been updated as that was indeed not clear, please verify if this is clearer now:

  • In contrast to the ksystemlog GUI program, the journalctl CLI program has a more fine-tuned parameter to find out what is what:

    --priority=
        Filter output by message priorities or priority ranges. Takes
        either a single numeric or textual log level (i.e. between
        0/"emerg" and 7/"debug"), or a range of numeric/text log levels in
        the form FROM..TO. The log levels are the usual syslog log levels
        as documented in syslog(3), i.e.  "emerg" (0), "alert" (1),
        "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6),
        "debug" (7). If a single log level is specified, all messages with
        this log level or a lower (hence more important) log level are
        shown. If a range is specified, all messages within the range are
        shown, including both the start and the end value of the range.
        This will add "PRIORITY=" matches for the specified priorities.

  • Examples:

    journalctl --system --boot=0 --priority=err

    will give you all system errors of the current 0 boot

    journalctl  --boot=-1 --priority=4

    will give you all warnings 4 of the previous -1 boot.

  • For more info:

    man journalctl

:+1:

1 Like
3

Thank you for updating the tutorial Fabby, much clearer!

Using DuckDuckGo to search for “file bug kwin_x11” pulled lots of results from various kde forums, and then after I adjusted the search for “kde forums” I found a hit that instructed someone not to post bugs in the forums, but rather to post at https://bugs.kde.org/
Screenshot_20210720_092508

I did a search in the KDE (I’m assuming) bugzilla for “kwin_x11” to confirm… lots of entries there… so I suspect I found the right place.

Will we generally find a bug tracker system to post our bugs too, or are there some upstreams that may accept bug reports in forums?

4

Most have a specialised bug tracking site…

5

okay thank you, looks like I’m creating an account so I can post my bug report there.

6

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.