Miles_Prower
May 1st, 2009, 02:36 AM
I upgraded to ubuntu 9.04 recently, and when I logged in, I got an error about no screen being available. After a bit, I got the machine to boot to a GUI by reverting to default x settings. This, it turned out, disables the proprietary nvidia drivers I'd been using. I noticed that desktop effects had been disabled and wanted to spiff up the new notifications, so I tried reinstalling the hardware drivers from system>administration>hardware drivers. It kept failing without an error message, so I installed the nvidia-glx-173 and linux-restricted-modules packages, then ran nvidia-xconfig, followed by pkill x. This restarted the x server and brought me the same error message: ...something about no screen being available, or a screen being available, but not having usable settings". I know that's subpar error reporting, so if someone could tell me where to look, I'd be happy to dig up some error logs. I don't know where X keeps them, though. Would my .xsession-errors help? Here, see it:
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root privileges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
GNOME_KEYRING_SOCKET=/tmp/keyring-1tDemt/socket
SSH_AUTH_SOCK=/tmp/keyring-1tDemt/socket.ssh
Window manager warning: Failed to read saved session file /home/taels/.config/metacity/sessions/108fdd0f4a2189550d124114057610069600000050950022.m s: Failed to open file '/home/taels/.config/metacity/sessions/108fdd0f4a2189550d124114057610069600000050950022.m s': No such file or directory
Initializing trackerd...
Tracker-Message: Checking XDG_DATA_HOME is writable and exists
Tracker-Message: XDG_DATA_HOME is '(null)'
Tracker-Message: XDG_DATA_HOME set to '/home/taels/.local/share'
Tracker-Message: Path is OK
Tracker-Message: Setting IO priority
Tracker-Message: Setting up monitor for changes to config file:'/home/taels/.config/tracker/tracker.cfg'
Failure: Module initalization failed
Tracker-Message: Loading defaults into GKeyFile...
Tracker-Message: Legacy config option 'IndexEvolutionEmails' found
Tracker-Message: This option has been replaced by 'DisabledModules'
Tracker-Message: Option 'DisabledModules' removed 'evolution'
Tracker-Message: Legacy config option 'IndexThunderbirdEmails' found
Tracker-Message: This option is no longer supported and has no effect
Tracker-Message: Legacy config option 'SkipMountPoints' found
Tracker-Message: Option 'IndexMountedDirectories' set to true
Tracker-Message: Setting up stopword list for language code:'en'
** (gnome-panel:5269): DEBUG: Adding applet 0.
** (gnome-panel:5269): DEBUG: Initialized Panel Applet Signaler.
Tracker-Message: Setting up stemmer for language code:'en'
Tracker-Message: Checking directory exists:'/home/taels/.local/share/tracker/data'
Tracker-Message: Checking directory exists:'/home/taels/.cache/tracker'
Tracker-Message: Registering DBus service...
Name:'org.freedesktop.Tracker'
Starting log:
File:'/home/taels/.local/share/tracker/trackerd.log'
** (gnome-panel:5269): DEBUG: Adding applet 1.
** (gnome-panel:5269): DEBUG: Adding applet 2.
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: old state indicates that this was not a disconnect 0
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (gnome-panel:5269): DEBUG: Adding applet 3.
** (gnome-panel:5269): DEBUG: Adding applet 4.
** (gnome-panel:5269): DEBUG: Adding applet 5.
** (gnome-panel:5269): DEBUG: Adding applet 6.
** (gnome-panel:5269): DEBUG: Adding applet 7.
** (gnome-panel:5269): DEBUG: Adding applet 8.
** (gnome-panel:5269): DEBUG: Adding applet 9.
** (gnome-panel:5269): DEBUG: Adding applet 10.
** (nautilus:5270): WARNING **: Unable to add monitor: Not supported
** (gnome-panel:5269): DEBUG: Adding applet 11.
** (gnome-panel:5269): DEBUG: Adding applet 12.
** (gnome-panel:5269): DEBUG: Adding applet 13.
** (gnome-panel:5269): DEBUG: Adding applet 14.
** (gnome-panel:5269): DEBUG: Adding applet 15.
** (gnome-panel:5269): DEBUG: Adding applet 16.
(gnome-panel:5269): libglade-WARNING **: Unexpected element <requires-version> inside <glade-interface>.
** (gnome-panel:5269): DEBUG: Adding applet 17.
** (gnome-panel:5269): DEBUG: Adding applet 18.
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: foo_client_state_changed_cb
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: foo_client_state_changed_cb
evolution-alarm-notify-Message: Setting timeout for 81791 1241222400 1241140609
evolution-alarm-notify-Message: Fri May 1 19:00:00 2009
evolution-alarm-notify-Message: Thu Apr 30 20:16:49 2009
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a000c7 (Mozilla Fi)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a000c7 (Restart X )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a000c7 (Restart X )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a000c7 (Restart X )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (update-notifier:5298): DEBUG: /usr/lib/update-notifier/apt-check returned 0 (security: 0)
** (update-notifier:5298): DEBUG: crashreport_check
I'm not sure quite what happened, but the proprietary nvidia drivers were working before I upgraded to jaunty. Is there a config file or error log I can look at somewhere?
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root privileges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
GNOME_KEYRING_SOCKET=/tmp/keyring-1tDemt/socket
SSH_AUTH_SOCK=/tmp/keyring-1tDemt/socket.ssh
Window manager warning: Failed to read saved session file /home/taels/.config/metacity/sessions/108fdd0f4a2189550d124114057610069600000050950022.m s: Failed to open file '/home/taels/.config/metacity/sessions/108fdd0f4a2189550d124114057610069600000050950022.m s': No such file or directory
Initializing trackerd...
Tracker-Message: Checking XDG_DATA_HOME is writable and exists
Tracker-Message: XDG_DATA_HOME is '(null)'
Tracker-Message: XDG_DATA_HOME set to '/home/taels/.local/share'
Tracker-Message: Path is OK
Tracker-Message: Setting IO priority
Tracker-Message: Setting up monitor for changes to config file:'/home/taels/.config/tracker/tracker.cfg'
Failure: Module initalization failed
Tracker-Message: Loading defaults into GKeyFile...
Tracker-Message: Legacy config option 'IndexEvolutionEmails' found
Tracker-Message: This option has been replaced by 'DisabledModules'
Tracker-Message: Option 'DisabledModules' removed 'evolution'
Tracker-Message: Legacy config option 'IndexThunderbirdEmails' found
Tracker-Message: This option is no longer supported and has no effect
Tracker-Message: Legacy config option 'SkipMountPoints' found
Tracker-Message: Option 'IndexMountedDirectories' set to true
Tracker-Message: Setting up stopword list for language code:'en'
** (gnome-panel:5269): DEBUG: Adding applet 0.
** (gnome-panel:5269): DEBUG: Initialized Panel Applet Signaler.
Tracker-Message: Setting up stemmer for language code:'en'
Tracker-Message: Checking directory exists:'/home/taels/.local/share/tracker/data'
Tracker-Message: Checking directory exists:'/home/taels/.cache/tracker'
Tracker-Message: Registering DBus service...
Name:'org.freedesktop.Tracker'
Starting log:
File:'/home/taels/.local/share/tracker/trackerd.log'
** (gnome-panel:5269): DEBUG: Adding applet 1.
** (gnome-panel:5269): DEBUG: Adding applet 2.
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: old state indicates that this was not a disconnect 0
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (gnome-panel:5269): DEBUG: Adding applet 3.
** (gnome-panel:5269): DEBUG: Adding applet 4.
** (gnome-panel:5269): DEBUG: Adding applet 5.
** (gnome-panel:5269): DEBUG: Adding applet 6.
** (gnome-panel:5269): DEBUG: Adding applet 7.
** (gnome-panel:5269): DEBUG: Adding applet 8.
** (gnome-panel:5269): DEBUG: Adding applet 9.
** (gnome-panel:5269): DEBUG: Adding applet 10.
** (nautilus:5270): WARNING **: Unable to add monitor: Not supported
** (gnome-panel:5269): DEBUG: Adding applet 11.
** (gnome-panel:5269): DEBUG: Adding applet 12.
** (gnome-panel:5269): DEBUG: Adding applet 13.
** (gnome-panel:5269): DEBUG: Adding applet 14.
** (gnome-panel:5269): DEBUG: Adding applet 15.
** (gnome-panel:5269): DEBUG: Adding applet 16.
(gnome-panel:5269): libglade-WARNING **: Unexpected element <requires-version> inside <glade-interface>.
** (gnome-panel:5269): DEBUG: Adding applet 17.
** (gnome-panel:5269): DEBUG: Adding applet 18.
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: foo_client_state_changed_cb
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: applet_common_device_state_changed
** (nm-applet:5287): DEBUG: foo_client_state_changed_cb
evolution-alarm-notify-Message: Setting timeout for 81791 1241222400 1241140609
evolution-alarm-notify-Message: Fri May 1 19:00:00 2009
evolution-alarm-notify-Message: Thu Apr 30 20:16:49 2009
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a000c7 (Mozilla Fi)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a000c7 (Restart X )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a000c7 (Restart X )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a000c7 (Restart X )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (update-notifier:5298): DEBUG: /usr/lib/update-notifier/apt-check returned 0 (security: 0)
** (update-notifier:5298): DEBUG: crashreport_check
I'm not sure quite what happened, but the proprietary nvidia drivers were working before I upgraded to jaunty. Is there a config file or error log I can look at somewhere?