Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I've tried setting up /etc/gdm/custom.conf as follows, but it still seems to ignore the debug setting. Note that for this cut-n-paste I removed the blank lines.# GDM configuration storage
[daemon]
[security]
DisallowTCP=true
[xdmcp]
[greeter]
[chooser]
[debug]
Enable=false

I've looked for other configuration files that might be overriding the custom.conf file, but haven't been able to find one. I used the gconf tools to try and find any configuration settings that way, but with no luck on the debug setting.

It isn't a fatal problem, but it is very annoying. Until the upgrade to F16 and Gnome3 I never got these messages. Although I've switched to xfce4 as a result of Gnome3 being a different kind of pain than just the messages, I still keep some vestiges of Gnome on the system for certain programs so completely removing it isn't an option.

After looking through the source for gdm-3.2.1.1, I found that gdm-greeter-session.c is hardcoded to start gnome-session in debug mode. The specific command it uses is "/gnome-session -f --debug". Compiling it myself, I get the debug stuff to shut off, although I've got lots of other issues in trying to get the configuration parameters correct...

Is it possible that this program was distributed with debugging forced on by accident?

I hit this same debug message issue when I did a clean install to Fedora 17. It happened beginning with the very first boot after the OS was installed.

The solution to clearing it? I removed NetworkManager as a package. Since I don't need NetworkManager on a desktop machine I figured I'd get rid of it. The side effect was that the Gnome debug messages went away once NetworkManage was removed. I didn't even have to change anything in Gnome (I'm using XFCE by the way), and didn't need to remove any other Gnome packages to clear this.

It is annoying that even with F17 the debug messages were still there. They tend to fill the log in a spot where I'm trying find other issues.

No, the debug is not part of the grub configuration. It was GNOME specific, and seemed to only happen when the Gnome GDM was used. It happened to me on two machines with clean installs, and on both removing NetworkManager solved the problem for me. I've also switched to using SLIM, in part because it is simpler, and from a security point of view it prompts for an id, instead of telling you an id and just prompting for a password like GDM started doing a little while back.