search

pop-os / pop

A project for managing all Pop!_OS sources
https://system76.com/pop
2.43k stars 84 forks source link

Syslog bloating with log messages (gnome-shell stage views actor & AMDGPU modelines) #3166

Open AdivonSlav opened 10 months ago

AdivonSlav commented 10 months ago

Distribution (run cat /etc/os-release): Pop!_OS 22.04 LTS

Related Application and/or Package Version (run apt policy $PACKAGE NAME): gnome-shell 42.5

Issue/Bug Description: There are two very frequent messages happening in the syslog. The first one seems to be related whenever auto-tiling is enabled and windows are being resized/moved. Gnome-shell keeps spitting out the following log messages in var/log/syslog. 

Oct 26 18:09:01 adi-popos gnome-shell[3527]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x56139d028320] is on because it needs an allocation.
Oct 26 18:09:01 adi-popos gnome-shell[3527]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5613a0b9dad0] is on because it needs an allocation.
Oct 26 18:09:01 adi-popos gnome-shell[3527]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x56139d5e26b0] is on because it needs an allocation.
Oct 26 18:09:01 adi-popos gnome-shell[3527]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x56139d028320] is on because it needs an allocation.
Oct 26 18:09:01 adi-popos gnome-shell[3527]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5613a0b9dad0] is on because it needs an allocation.
Oct 26 18:09:01 adi-popos gnome-shell[3527]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x56139d5e26b0] is on because it needs an allocation.
Oct 26 18:09:01 adi-popos gnome-shell[3527]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x56139d1eab20] is on because it needs an allocation.
Oct 26 18:09:01 adi-popos gnome-shell[3527]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x56139ecca350] is on because it needs an allocation.

Also, far more frequent are messages like this coming from the amdgpu driver (I'm guessing?):

Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): EDID vendor "DEL", prod id 41087
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Using hsync ranges from config file
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Using vrefresh ranges from config file
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Printing DDC gathered Modelines:
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
Oct 26 18:06:43 adi-popos /usr/libexec/gdm-x-session[3381]: (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)

It is so frequent that the syslog, at this point in time, has grown to 10GB in size. Especially the messages coming from gdm-x-session number around 40k lines in the past 10 days.

Steps to reproduce (if you know): For the gnome-shell logs, simply turn on tiling and resize a window. The logs should appear As for the gdm-x-session amdgpu logs, I've no idea what causes them.

Expected behavior: Not so so many logs being written

Other Notes: I am not sure if this is intended behaviour or whether Pop is the right place to file it, but I thought I'd point it out just for a clarification if there is any

manu-git-code commented 8 months ago

I'm on 22.04, 42.5 Gnome and AMD card as well and I use auto-tiling all the time. If I journalctl -f my terminal is flooded with those gnome messages. Inside syslog I can also see the same AMD messages OP mentioned. I can't really say that I feel anything wrong with the pc, just this massive bloat in the logging system.