[KM400]Haven't been able to execute normal gnome login since 10.04 installation; screen blanks then returns to login screen

[Stuart Hall]

Binary package hint: xorg

After a fresh 10.04 installation which seemed to go perfectly, I now can't execute a normal gnome login, but can using safe mode gnome and xterm. When attempting a normal login there is a short wait after the login screen disappears, then the screen goes blank for a few seconds before returning to the login screen.

The following lines from syslog are what make me think this is a bug;

Jun 4 13:15:34 saltcreek acpid: client connected from 2495[0:0]
Jun 4 13:15:34 saltcreek acpid: 1 client rule loaded
Jun 4 13:15:34 saltcreek kernel: [ 1388.249939] agpgart-via 0000:00:00.0: AGP 3.5 bridge
Jun 4 13:15:34 saltcreek kernel: [ 1388.249969] agpgart-via 0000:00:00.0: bridge is in legacy mode, falling back to 2.x
Jun 4 13:15:34 saltcreek kernel: [ 1388.249977] agpgart-via 0000:00:00.0: putting AGP V2 device into 4x mode
Jun 4 13:15:34 saltcreek kernel: [ 1388.250033] pci 0000:01:00.0: putting AGP V2 device into 4x mode
Jun 4 13:15:36 saltcreek gdm-simple-greeter[2530]: Gtk-WARNING: /build/buildd/gtk+2.0-2.20.0/gtk/gtkwidget.c:5636: widget not within a GtkWindow
Jun 4 13:15:39 saltcreek gdm-session-worker[2532]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jun 4 13:15:49 saltcreek kernel: [ 1403.715360] Xorg[2495]: segfault at 0 ip 080a6712 sp bf99bd2c error 4 in Xorg[8048000+19f000]
Jun 4 13:15:50 saltcreek acpid: client 2495[0:0] has disconnected

Ubuntu release:
~$ lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04

My system:
~$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
01:00.0 VGA compatible controller: VIA Technologies, Inc. KM400/KN400/P4M800 [S3 UniChrome] (rev 01)

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Fri Jun 4 13:36:30 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=9a26cb71-8670-4c6c-9a21-20f8f5f804b4 ro quiet splash
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
dmi.bios.date: 09/23/2004
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: 7VM400AM-RZ
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd09/23/2004:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn7VM400AM-RZ:rvrx.x:cvn:ct3:cvr:
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

[Bartosz Kosiorek (gang65)]

Try to disable AIGLX by adding option to /etc/X11/xorg.conf file.

[Stuart Hall (stuart-vicnet)]

Hi,

There was no existing xorg.conf file in /etc/X11, so I
created one with the following content;

Section
"ServerFlags"
    Option "AIGLX"
"off"
EndSection

After rebooting, I was
successfully automatically logged in (which was the option I chose in my
third attempt to install).  The last bit of the syslog after the
reboot is now

Jun 26 16:09:51 saltcreek kernel: [
16.256256] [drm] Initialized via 2.11.1 20070202 for 0000:01:00.0 on minor
0
Jun 26 16:09:51 saltcreek kernel: [   16.258993]
agpgart-via 0000:00:00.0: AGP 3.5 bridge
Jun 26 16:09:51 saltcreek
kernel: [   16.259022] agpgart-via 0000:00:00.0: bridge is in
legacy mode, falling back to 2.x
Jun 26 16:09:51 saltcreek kernel:
[   16.259031] agpgart-via 0000:00:00.0: putting AGP V2 device
into 4x mode
Jun 26 16:09:51 saltcreek kernel: [
16.259087] pci 0000:01:00.0: putting AGP V2 device into 4x mode
Jun
26 16:09:52 saltcreek /usr/sbin/hplj1020: foo2zjs: HP LaserJet 1020
firmware already loaded into /dev/usb/lp0
Jun 26 16:09:52 saltcreek
/usr/sbin/hplj1020: foo2zjs: HP LaserJet 1020 firmware already loaded into
/dev/usblp0
Jun 26 16:10:59 saltcreek kernel: [
83.897278] usb 1-1: usbfs: interface 0 claimed by usblp while 'usb' sets
config #1
Jun 26 16:11:45 saltcreek kernel: [  130.325832]
usblp0: removed

Since the problem occurred after 5th last line
and before the firmware load, I'd say this is a successful workaround.

Thank you.

Cheers,

Stuart Hall

> Try to disable AIGLX by adding option to /etc/X11/xorg.conf
file.
>
> ** Summary changed:
>
> -
Haven't been able to execute normal gnome login since 10.04
>
installation; screen blanks then returns to login screen
> +
[KM400]Haven't been able to execute normal gnome login since 10.04
> installation; screen blanks then returns to login screen
>

> ** Changed in: xserver-xorg-video-openchrome (Ubuntu)
>
   Importance: Undecided => High
>
> ** Changed in:
xserver-xorg-video-openchrome (Ubuntu)
> Importance: High =>
Medium
>
> --
> [KM400]Haven't been able to
execute normal gnome login since 10.04
> installation; screen
blanks then returns to login screen
>
https://bugs.launchpad.net/bugs/589520
> You received this bug
notification because you are a direct subscriber
> of the bug.
>
> Status in
“xserver-xorg-video-openchrome” package in
Ubuntu: Confirmed
>
> Bug description:
> Binary
package hint: xorg
>
> After a fresh 10.04 installation
which seemed to go perfectly, I now can't
> execute a normal gnome
login, but can using safe mode gnome and xterm.
> When attempting
a normal login there is a short wait after the login
> screen
disappears, then the screen goes blank for a few seconds before
>
returning to the login screen.
>
> The following lines
from syslog are what make me think this is a bug;
>
> Jun
 4 13:15:34 saltcreek acpid: client connected from 2495[0:0]
> Jun
 4 13:15:34 saltcreek acpid: 1 client rule loaded
> Jun 4
13:15:34 saltcreek kernel: [ 1388.249939] agpgart-via 0000:00:00.0:
> AGP 3.5 bridge
> Jun 4 13:15:34 saltcreek kernel: [
1388.249969] agpgart-via 0000:00:00.0:
> bridge is in legacy mode,
falling back to 2.x
> Jun 4 13:15:34 saltcreek kernel: [
1388.249977] agpgart-via...

[Felicia (sisternotes)]

I hope I am not hijacking this bug. I am using my sonś laptop, which I set up with a fresh install of 10.04. It is also set up to automatically log him in since I do not use it very often. He is away so I am using it and can not log in - the username/password combo is correct (I have check cap lock too). If I try to do an update, which requires authentication and enter his password (he has not changed it), the update will not work. If I esc out of the auto login screen and manual log into his account with his password (or my own account) I get an authentication failure message.

I cannot make any changes under System>>Administration>>Users and Groups because none of the user/password combinations will work. I have no idea when this authentication issue started, because I was able to login when I first did the switch to 10.04 back in May. Please help!

Side note: I did a fresh install of 10.04 on my daughterś laptop and regrettable chose the option to secure the hard drive (this step then gives a long pass code that must be saved upon first booting after installation). The result is I cannot set up automatic login - though I guess that would have defeated securing the computer anyway. Once I figured out the problem, I went back to requiring passwords to login and all is well...Iḿ glad there were two users or I would not have been able to login as well...there should be a warning with the installation for this security feature. I do not recall if I had made the same choice when setting up my sonś computer, but since his auto login works, I suspect I did not.

[Felicia (sisternotes)]

I fixed my authentication failure issue. It seems my issue may not be associated with this particular bug report.
--I had to boot into recovery mode
--select the drop into root user option (on the bottom of the list)
--enter passwd username (put the user's login name in place of "username")
--enter a new password, hit enter
--re-enter the password
--type exit
--according to the instructions that I was following, I should have next selected the "return to normal boot" option. However, for some reason I ended up stuck in command mode. I eventually shut down "shutdown now" and restarted the laptop. All is well again.

I think that the problem may have started with a power outage. I remember having a similar login problem when I accidentally pulled the laptop's power cord out. At that time I was a new ubuntu user and did a fresh install. Ever since I've been especially careful with the cord (I have no battery power).

[Antony Jones (wrh)]

This is also affecting my Dell Mini 1010 - the one with the horrendous gma500/poulsbo chipset.

The suggested workaround doesn't work, moving .compiz, .gnome2 or .config or .dbus out of the way does not help, but I can log in under failsafe gnome without issue.

Completely stumped.

I am seeing the exact same in my /var/log/syslog/ as the bug author sees in the original bug report, i.e. this part:

Jun 4 13:15:36 saltcreek gdm-simple-greeter[2530]: Gtk-WARNING: /build/buildd/gtk+2.0-2.20.0/gtk/gtkwidget.c:5636: widget not within a GtkWindow
Jun 4 13:15:39 saltcreek gdm-session-worker[2532]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

Could this be a GTK bug? It's a real blocker as I really can't afford to reinstall right now, and I can only assume I'm not the only one.

[Antony Jones (wrh)]

Okay, just fixed mine with this:

/etc/X11/xorg.conf
Section "ServerFlags"
    Option "AIGLX" "off"
EndSection

[Lucazade (lucazade)]

VGA compatible controller: VIA Technologies, Inc. KM400/KN400/P4M800 [S3 UniChrome] (rev 01)
not an Intel gma500 gfx

[Roman (romanoza)]

same problem, start when 10.04 was installed, now upgreded to 10.10b (logged in from recovery), problem was not solved and now trying to boor up with recovery, kernel panic

[Jose Bernardo (bernardo-bandos)]

Roman, please check if your issue is bug #612467

[Roman (romanoza)]

Sorry, can't tell you.
And I'm on 10.10 now

[macbuntu (macbeth)]

I had the same issue with 10.04 as well as 10.10 Beta.

This fixed the problem for both;

There was no existing xorg.conf file in /etc/X11, so I created one with the following content;

Section
"ServerFlags"
    Option "AIGLX"
"off"
EndSection

This is my hardware; http://paste.ubuntu.com/507411/

[Anibal Avelar (aavelar)]

I had a similar problem, I always got this messages after some time:

Jul 26 12:50:11 server1 gdm-simple-greeter[1266]: Gtk-WARNING: /build/buildd/gtk+2.0-2.19.6/gtk/gtkwidget.c:5634: widget not within a GtkWindow

Jul 26 12:50:18 server1 gdm-session-worker[1268]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

But I didn't have another idea about was happen. The error ocurred overall using Firefox or Thunderbird, my session always close

But works for me this option in /etc/X11/xorg.conf

Section "Module"
          ....
         #Load "record"
         Disable "record"
         ....
EndSection

I need to "explicit" disable this module. Then the problem disappear for ever :P

I know the module is loaded by default then if you don't have the option doesn't mean the module is not used, you need disable explicitly.

Regards.