Skip to content
This repository has been archived by the owner on Jun 16, 2024. It is now read-only.

[FEATURE]: Is there a way to avoid bismuth from hogging the journal #497

Open
razimantv opened this issue Nov 24, 2023 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@razimantv
Copy link

Summary

If I check journalctl, it is full of debug information from bismuth

kwin_x11[155020]: org.kde.bismuth: onCurrentSurfaceChanged,[object Object]
kwin_x11[155020]: org.kde.bismuth: arrange
kwin_x11[155020]: org.kde.bismuth: arrangeScreen/finished,[object Object]
kwin_x11[155020]: org.kde.bismuth: onCurrentSurfaceChanged,[object Object]
kwin_x11[155020]: org.kde.bismuth: arrange
kwin_x11[155020]: org.kde.bismuth: arrangeScreen/finished,[object Object]
kwin_x11[155020]: org.kde.bismuth: onCurrentSurfaceChanged,[object Object]
kwin_x11[155020]: org.kde.bismuth: arrange
kwin_x11[155020]: org.kde.bismuth: arrangeScreen/finished,[object Object]
kwin_x11[155020]: org.kde.bismuth: onCurrentSurfaceChanged,[object Object]
kwin_x11[155020]: org.kde.bismuth: arrange
kwin_x11[155020]: org.kde.bismuth: arrangeScreen/finished,[object Object]
kwin_x11[155020]: org.kde.bismuth: onCurrentSurfaceChanged,[object Object]

This does not seem to be important (warning/error) level information, and I don't know how to suppress these.

A clear and concise description of what you want to happen

I would like there to be an option to log only critical information

A clear and concise description of any alternative solutions or features you've considered.

No response

Additional info

  • OS: arch
  • KDE: plasma 5.27.9
  • bismuth: 3.1.4-5 (from AUR)
@razimantv razimantv added the enhancement New feature or request label Nov 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant