Bug 759737
| Summary: | gnome-session debugging in messages file | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | udo <udovdh> |
| Component: | gnome-session | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dadreggors, dkovalsk, edgar.hoch, jmccann, rstrode |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-15 00:21:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
udo
2011-12-03 14:23:26 UTC
I see this too. Gnome-session is incredibly verbose, gnome-session itself is responsible for about 5% of all lines in /var/log/messages. Please make the debugging output tunable, or turn it off. gnome-session-3.2.1-2.fc16.x86_64 Any updates? Anyone? do you have Enable=true in the [debug] section of /etc/gdm/custom.conf ? oh i see what's happening i think.. gdm runs gnome-session with --debug, and gnome-session outputs to syslog in that case. No 'Enable=true' here. External Bug ID| |GNOME Desktop 672801 That external bug id does not really promise progress. So what will Redhat do about this? Either developers trust their users and more so trust their products and make debug configurable or force that debug stuff onto us, which is not so nice - whatever the excuse. Sorry I'm not groking comment 7 at all. Can you reiterate? We (users) do not need debug. We (users) do not expect nor want bugs. We (users) can (if needed) enable debug. Developers should trust their products and their users so that debug can be off (as it should be) and can be turned on when needed. The comments in the external bug ID do not show any understanding of that perspective. They appear to reason from the developer perspective only. Because of the simple nature of the problem we cannot wait for upstream. What will redhat do instead of wait for upstream? "Because of the simple nature of the problem we cannot wait for upstream." <-- what does this mean? (i'm not trying to be obtuse, by the way, I just really don't understand your perspective) We do not like our logs full. We like our logs close to empty. So just make the debugging an option, give us a choice. English is not my first language, so please excuse my French. Just get rid of the spamming in the logfile (and logfiles in general). Same issue here in Fedora 17, no fix yet? While this is not news to Ray Stroder, it may be news for the others here... The upstream patch to fix this issues is in according to the external bug tracker at Gnomes bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=672801 Sorry, that is Ray Strode (not Stroder). gdm-3.2.1.1-10.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gdm-3.2.1.1-10.fc16 gdm-3.4.1-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/gdm-3.4.1-3.fc17 Thanks Ray! Package gdm-3.4.1-3.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gdm-3.4.1-3.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-9175/gdm-3.4.1-3.fc17 then log in and leave karma (feedback). Works for me, I added Karma at the link above. gdm-3.4.1-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. gdm-3.2.1.1-10.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |