After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 670694 - Only start X with maximum verbosity if debug is enabled
Only start X with maximum verbosity if debug is enabled
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-23 15:54 UTC by Vincent Untz
Modified: 2012-02-24 07:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
server: Only start Xorg with maximum verbosity if debug is enabled (2.07 KB, patch)
2012-02-23 15:55 UTC, Vincent Untz
committed Details | Review

Description Vincent Untz 2012-02-23 15:54:32 UTC
Forwarding https://bugzilla.novell.com/show_bug.cgi?id=748283

I am using the radeon driver on a Radon HD5450 card, under Gnome 3.2. File
/var/log/Xorg.0.log gets filled with the following two debug messages over and
over again:

(II) RADEON(0): radeon_dri2_flip_event_handler:981 fevent[0x17082c0] width 1280
pitch 5120 (/4 1280)
(II) RADEON(0): radeon_dri2_schedule_flip:619 fevent[0x27c7b80]

As these messages do not appear to be reporting any error or even have any
informative value for the end user, I qualify them as debug messages. Or is
there anything bad about these messages?

I get about 3650 such messages per day, for a total of 680 kB. You may consider
this a cosmetic issue, but I still would like to see it fixed, for two reasons:

* Valuable messages are very hard to spot in the log file because it is flooded
by these debug messages.
* I have /var/log on a SSD. Such drives do not like repeated writes. I do not
want to see the lifetime of my drive shorten by useless log messages.
Comment 1 Vincent Untz 2012-02-23 15:55:00 UTC
Created attachment 208285 [details] [review]
server: Only start Xorg with maximum verbosity if debug is enabled

Only start Xorg with maximum verbosity if gdm itself was started with
debugging enabled. Making Xorg overly verbose by default fills up the
log file with driver debugging messages, hiding the important error or
warning messages.

https://bugzilla.gnome.org/show_bug.cgi?id=670694
https://bugzilla.novell.com/show_bug.cgi?id=748283
https://bugzilla.redhat.com/show_bug.cgi?id=785507
Comment 2 Ray Strode [halfline] 2012-02-23 23:27:43 UTC
Comment on attachment 208285 [details] [review]
server: Only start Xorg with maximum verbosity if debug is enabled

Thanks, i've been meaing to write this patch for a couple weeks now actually.  Please commit!
Comment 3 Vincent Untz 2012-02-24 07:07:48 UTC
Comment on attachment 208285 [details] [review]
server: Only start Xorg with maximum verbosity if debug is enabled

Pushed, thanks.