New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warnings or non important messages handled by journald #3927

Closed
donob4n opened this Issue May 24, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@donob4n

donob4n commented May 24, 2018

Qubes OS version:

Qubes 4

Affected component(s):

journald / hardisk usage


Steps to reproduce the behavior:

Hi,

I noticed tons of warnings from Vinagre,
(vinagre:17442): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node box owner ViewAutoDrawer)
https://bugzilla.redhat.com/show_bug.cgi?id=1404688

After three days uptime (which plenty hours of sleep state) I have near 1GB on /var/log. I am trying to open vinagre from a desktop shortcut and discard this warnings, maybe an script calling "vinagre &> /dev/null" but I think some default alternative would be nice.

In my opinion standard user apps should not write warnings or messages to journald which is supposed to "system messages".

At least it would be nice to have an option on 'qvm-run' for change this behaviour (--no-log?).

Expected behavior:

Journal should handle only system relevant messages and maybe some important application.

Actual behavior:

It logs tons of unimportant messages and warnings.

General notes:


Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 25, 2018

Member

Possibly notourbug, but I'll leave that determination up to @marmarek.

Member

andrewdavidwong commented May 25, 2018

Possibly notourbug, but I'll leave that determination up to @marmarek.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 25, 2018

Member

Yes, that's not the right place for such bug report.
The idea with a wrapper script redirecting stderr to /dev/null should work.

Member

marmarek commented May 25, 2018

Yes, that's not the right place for such bug report.
The idea with a wrapper script redirecting stderr to /dev/null should work.

@marmarek marmarek closed this May 25, 2018

@andrewdavidwong andrewdavidwong added notourbug and removed bug labels May 25, 2018

@donob4n

This comment has been minimized.

Show comment
Hide comment
@donob4n

donob4n May 25, 2018

Ok. After thinking about this maybe the useful thing would be a centralized way for see all logs from the system (log files and journalds).

donob4n commented May 25, 2018

Ok. After thinking about this maybe the useful thing would be a centralized way for see all logs from the system (log files and journalds).

@marmarek

This comment has been minimized.

Show comment
Hide comment
Member

marmarek commented May 25, 2018

#830 ?

@donob4n

This comment has been minimized.

Show comment
Hide comment
@donob4n

donob4n May 25, 2018

Yes, I was thinking about it.

donob4n commented May 25, 2018

Yes, I was thinking about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment