bismuth icon indicating copy to clipboard operation
bismuth copied to clipboard

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

Open razimantv opened this issue 1 year ago • 0 comments

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 avatar Nov 24 '23 13:11 razimantv