Journal flooded with gdm-x messages

Ask Fedora
, ,
1

The journal is being flooded with the following messages:

Jun 12 06:01:31 bob.localdomain /usr/libexec/gdm-x-session[25817]: (--) NVIDIA(GPU-0):
Jun 12 06:01:42 bob.localdomain /usr/libexec/gdm-x-session[25817]: (--) NVIDIA(GPU-0): Acer S232HL (DFP-1): connected
Jun 12 06:01:42 bob.localdomain /usr/libexec/gdm-x-session[25817]: (--) NVIDIA(GPU-0): Acer S232HL (DFP-1): Internal TMDS
Jun 12 06:01:42 bob.localdomain /usr/libexec/gdm-x-session[25817]: (--) NVIDIA(GPU-0): Acer S232HL (DFP-1): 600.0 MHz maximum pixel clock

I am running Fedora 42, fully updated, and nvidia version 575.57.08-1.fc42.x86_64.

Is there anything that can be done to stop this?

1 Like
2

Gnome always spams the journal, maybe switch to another DM and DE if you don’t like it.

3

why flooding? WIth an X11 session gdm will log the output of the X11 server ( compare with /var/log/Xorg.0.log ) at login.

1 Like
4

This isn’t a constructive answer Leigh. Let’s please keep to helping the user with their specific query—negative remarks about tools are not useful, and we’re not being excellent to everyone here.

5

edit /etc/systemd/journald.conf

and change

#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg

to

MaxLevelStore=crit
MaxLevelSyslog=crit
MaxLevelKMsg=crit
MaxLevelConsole=crit
#MaxLevelWall=emerg

Then run

sudo systemctl restart systemd-journald.service
2 Likes
6

I’ve seen my display do a similar spam of display connects on i915 Intel a while back, but I’m not sure on specifics (might have been modesetting vs intel DDX or color/icc/GNOME’s color daemon).

I’d try using open NVIDIA GSP; I recall that doing something different with my display in logs vs regular proprietary drivers.

If you do a reinstall, I’d check logs frequently while setting up and up to NVIDIA’s driver install to see if it starts happening out of nowhere; you might be able to narrow it down to a setting or package install/update.

7

Don’t make this about nvidia, it has nothing to do with gnome spamming the log with basic xorg messages.

8

I went looking to see if others had similar issues, and found this:

It does provide a workaround/fix but they’re not using journalctl from the looks of it. Perhaps the documentation will have some hints. I’m not running X11 here on this machine, unfortunately, so I can’t quite check how gdm-x-session calls X on my machine either, but perhaps there’s a way to tweak that on Fedora. It’ll require some digging.