[CLE266]Since upgrade from jaunty to karmic, one of two thin clients' login broken (AIGLX problem).
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-openchrome (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Since upgrade from jaunty (ubuntu 9.04) to karmic (ubuntu 9.10), one of my two thin clients using ltsp no longer permits logins, even though the thin client boots fine and serves up the login screen. It looks like a display driver error or authentication error. The machine works fine with karmic when directly running live-CD (via usb-stick; it is a diskless mini-itx via based thin client). It worked fine under jaunty.
Once I enter the user name and then password, the wait icon appears, but after approx 2/3s time the display reverts back to the login screen. Login on the other thin client hardware using same credentials works fine.
ProblemType: Bug
Architecture: amd64
Date: Sun Nov 15 00:19:17 2009
DistroRelease: Ubuntu 9.10
Package: ltsp-server 5.1.90-0ubuntu3
PackageArchitec
ProcEnviron:
LANGUAGE=
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ltsp
Uname: Linux 2.6.31-14-generic x86_64
Jon Coldewey (coldewey) wrote : | #1 |
- Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
- XsessionErrors.txt Edit (10.6 KiB, text/plain; charset="utf-8")
Jon Coldewey (coldewey) wrote : | #2 |
affects: | ltsp (Ubuntu) → xserver-xorg-video-ati (Ubuntu) |
Tormod Volden (tormodvolden) wrote : | #3 |
Please attach your Xorg.0.log and dmesg output, so we can verify if this is a duplicate or not.
Changed in xserver-xorg-video-ati (Ubuntu): | |
status: | New → Incomplete |
Jon Coldewey (coldewey) wrote : | #4 |
OK, sorry, but I may need some help in obtaining the requested logs: on jaunty I had the thin clients set up to send their logs to the server in specified client subdirectories, using syslog-ng. Karmic uses rsyslog by default, and I haven't yet figured out how to open this up for external logging. Jon
Tormod Volden (tormodvolden) wrote : | #5 |
I am not so familiar with the LTSP setup, but can you log in as a local user on a text console? Then you can use scp to copy the files to another computer. Note that the X server does not use rsyslog anyway.
Tormod Volden (tormodvolden) wrote : | #6 |
Jon Coldewey (coldewey) wrote : Re: [Bug 482875] Re: Since upgrade from jaunty to karmic, one of two thin clients' login broken. | #7 |
Thanks, I will set something up and obtain the logs. It may take some time,
because I only have intermittent access (I can only boot into the karmic
system when this does not disturb regular operation. I re-instated jaunty on
another partition to maintain regular operation).
Jon
2009/11/17 Tormod Volden <email address hidden>
> I am not so familiar with the LTSP setup, but can you log in as a local
> user on a text console? Then you can use scp to copy the files to
> another computer. Note that the X server does not use rsyslog anyway.
>
> --
>
Tormod Volden (tormodvolden) wrote : Re: Since upgrade from jaunty to karmic, one of two thin clients' login broken. | #8 |
If you can attach the Xorg.0.log and dmesg output from booting the Karmic live CD usb stick, it would help also. And try to run glxinfo on it.
Jon Coldewey (coldewey) wrote : | #9 |
glxinfo on client hardware when booting from live-CD-usb:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_
GLX_
GLX_
GLX_
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
GLX_
GLX_
GLX_
GLX_
GLX_
GLX_
GLX_
GLX version: 1.2
GLX extensions:
GLX_
GLX_
GLX_
GLX_
GLX_
OpenGL vendor string: VIA Technology
OpenGL renderer string: Mesa DRI CastleRock (CLE266) 20060710 x86/MMX/SSE
OpenGL version string: 1.2 Mesa 7.6
OpenGL extensions:
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
GL_
24 GLX Visuals
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
-------
0x21 24...
Jon Coldewey (coldewey) wrote : | #10 |
dmesg on client hardware when booting from live-CD-usb:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 (Ubuntu 2.6.31-
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000003bff0000 (usable)
[ 0.000000] BIOS-e820: 000000003bff0000 - 000000003bff3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000003bff3000 - 000000003c000000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.2 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x3bff0 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask FC0000000 write-back
[ 0.000000] 1 base 03C000000 mask FFC000000 uncachable
[ 0.000000] 2 base 0C0000000 mask FF0000000 write-combining
[ 0.000000] 3 base 0D0000000 mask FFC000000 write-combining
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009fc00 (usable)
[ 0.000000] modified: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000003bff0000 (usable)
[ 0.000000] modified: 000000003bff0000 - 000000003bff3000 (ACPI NVS)
[ 0.000000] modified: 000000003bff3000 - 000000003c000000 (ACPI data)
[ 0.000000] modified: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] modified: 00000000ffff0000 - 0000000100000000 (reser...
Jon Coldewey (coldewey) wrote : | #11 |
Xorg.7.log from client hardware when booting from live-CD-usb:
X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686
Kernel command line: initrd=/ubninit file=/cdrom/
Build Date: 26 October 2009 05:15:02PM
xorg-server 2:1.6.4-2ubuntu4 (buildd@)
Before reporting problems, check http://
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/
(II) Loader magic: 0x3bc0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0:1:0:0) 1106:3122:1019:1b44 VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics rev 3, Mem @ 0xd0000000/
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default openchrome Device 0"
Driver "openchrome"
EndSection
Section "Screen"
Identifier "Builtin Default openchrome Screen 0"
Device "Builtin Default openchrome Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default openchrome Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default openchrome Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default openchrome Device 0"
(==) No monitor specified for screen "Builtin Default openchrome Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/f...
Jon Coldewey (coldewey) wrote : | #12 |
dmesg from client after ltsp netboot:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 (Ubuntu 2.6.31-
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000003bff0000 (usable)
[ 0.000000] BIOS-e820: 000000003bff0000 - 000000003bff3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000003bff3000 - 000000003c000000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.2 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x3bff0 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask FC0000000 write-back
[ 0.000000] 1 base 03C000000 mask FFC000000 uncachable
[ 0.000000] 2 base 0C0000000 mask FF0000000 write-combining
[ 0.000000] 3 base 0D0000000 mask FFC000000 write-combining
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009fc00 (usable)
[ 0.000000] modified: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000003bff0000 (usable)
[ 0.000000] modified: 000000003bff0000 - 000000003bff3000 (ACPI NVS)
[ 0.000000] modified: 000000003bff3000 - 000000003c000000 (ACPI data)
[ 0.000000] modified: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] modified: 00000000ffff0000 - 0000000100000000 (reserved)
[ 0.000000...
Jon Coldewey (coldewey) wrote : | #13 |
Xorg.7.log from client after ltsp netboot.. (XSERVER not specified):
X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux saturn 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686
Kernel command line: ro initrd=initrd.img quiet splash BOOT_IMAGE=vmlinuz
Build Date: 26 October 2009 05:15:02PM
xorg-server 2:1.6.4-2ubuntu4 (buildd@)
Before reporting problems, check http://
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/
(II) Loader magic: 0x3bc0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0:1:0:0) 1106:3122:1019:1b44 VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics rev 3, Mem @ 0xd0000000/
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default openchrome Device 0"
Driver "openchrome"
EndSection
Section "Screen"
Identifier "Builtin Default openchrome Screen 0"
Device "Builtin Default openchrome Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default openchrome Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default openchrome Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default openchrome Device 0"
(==) No monitor specified for screen "Builtin Default openchrome Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/
E...
Jon Coldewey (coldewey) wrote : | #14 |
Xorg.7.log from client after ltsp netboot (XSERVER specified as openchrome):
X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux saturn 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686
Kernel command line: ro initrd=initrd.img quiet splash BOOT_IMAGE=vmlinuz
Build Date: 26 October 2009 05:15:02PM
xorg-server 2:1.6.4-2ubuntu4 (buildd@)
Before reporting problems, check http://
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/
(++) Using config file: "/var/run/
(==) No Layout section. Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) | |-->Monitor "<default monitor>"
(==) No device specified for screen "Default Screen Section".
Using the first device section listed.
(**) | |-->Device "Device0"
(==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/
Entry deleted from font path.
(WW) The directory "/usr/share/
Entry deleted from font path.
(WW) The directory "/var/lib/
Entry deleted from font path.
(==) FontPath set to:
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
built-ins
(==) ModulePath set to "/usr/lib/
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0x3bc0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0:1:0:0) 1106:3122:1019:1b44 VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics rev 3, Mem @ 0xd0000000/
(WW) Open ACPI failed (/var/run/
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
Module class: ...
Jon Coldewey (coldewey) wrote : | #15 |
By-the-way: specifying XSERVER as vesa leaves all screens black.
Interestingly, using the specification of XSERVER = openchrome, I had a very brief glimpse of the user desktop from the server, before I was thrown back to the login screen. While I cannot sucessfully log into gnome desktop from the ltsp terminal, I can login to xterm and lauch X applications such as firefox, etc from there!
Jon
Jon Coldewey (coldewey) wrote : | #16 |
various .xsession-errors from _host_ after attempted logins on ltsp terminal:
example 1:
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_GB.
Start IM through /etc/X11/
GNOME_KEYRING_
SSH_AUTH_
(gnome-
(gnome-
Checking for Xgl: not present.
xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log
Detected PCI ID for VGA:
Checking for texture_
present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Checking screen 1Comparing resolution (1366x768) to maximum 3D texture size (4096): Passed.
Checking for Software Rasterizer: Not present.
Checking for nVidia: not present.
Checking for FBConfig: present.
running under gnome seesion, checking for gnomecompat
Checking for Xgl: not present.
(polkit-
(polkit-
Starting gtk-window-
WARNING: Application calling GLX 1.3 function "glXCreatePixmap" when GLX 1.3 is not supported! This is an application bug!
(nautilus:3796): Eel-CRITICAL **: eel_preferences
Announce the service on avahi
Starting ICA
** Message: Reading of RFKILL events failed
** Message: killswitches state 3
** (gnome-panel:3795): DEBUG: Adding applet 0.
** (gnome-panel:3795): DEBUG: Initialized Panel Applet Signaler.
** (gnome-panel:3795): DEBUG: Adding applet 1.
** (gnome-panel:3795): DEBUG: Adding applet 2.
** Message: killswitches state 3
** (nautilus:3796): WARNING **: No marshaller for signature of signal 'UploadFinished'
** (nautilus:3796): WARNING **: No marshaller for signature of signal 'DownloadFinished'
** (nautilus:3796): WARNING **: No marshaller for signature of signal 'ShareCreateError'
** (gnome-panel:3795): DEBUG: Adding applet 3.
** (gnome-panel:3795): DEBUG: Adding applet 4.
/usr/bin/
** (gnome-panel:3795): DEBUG: Adding applet 5.
** (gnome-panel:3795): DEBUG: Adding applet 6.
Initializing nautilus-gdu extension
I/O warning : failed to load external entity "/home/
** (gnome-panel:3795): DEBUG: Adding applet 7.
Established under name 'italc jon'
WARNING: Application calling GLX 1.3 function "glXDestroyPixmap" when GLX 1.3 is not supported! This is an application bug!
PORT=5900
** (gnome-panel:3795): DEBUG: Adding applet 8.
(gnome-panel:3795): Gdk-WARNING **: /build/
** (gnome-panel:3795): DEBUG: Adding applet 9.
(na...
Tormod Volden (tormodvolden) wrote : | #17 |
Thanks. For the future, please attach the logs instead of pasting them into the comments.
You are using the -openchrome driver (with the "via" 3D driver) so it is certainly not a radeon issue here.
I noticed this in the LTSP X log, but I do not know if it causes any harm:
[config/dbus] couldn't take over org.x.config: org.freedesktop
The xsession-errors are difficult to read, but I wonder if this:
Trying again with indirect rendering:
Checking for texture_
means glxinfo is bombing out when tried with indirect rendering? Please try "glxinfo -i" on the live CD.
affects: | xserver-xorg-video-ati (Ubuntu) → xorg (Ubuntu) |
Tormod Volden (tormodvolden) wrote : | #18 |
Instead of the live CD, you can of course use the xterm which you mention in comment 15.
Jon Coldewey (coldewey) wrote : | #19 |
glxinfo and glxinfo -i don't work in the xterm ltsp login session. I get an error:
"name of display 192.168.0.110:7.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major Opcode of failed request: 138 (DRI2)
Minor Opcode of failed request: 1 (DRI2Connect)
Serial number of failed request: 19
..."
glxinfo -i within an Xsession on the live-CD system is interesting in that it immediately kicks me out of the session to a logon screen, and corrupts the video on all the VTs. That behaviour is identical to what happens, when the netbooted ltsp client attempts to login from the ldm login screen into the server X session. Then also, the client side virtual terminals get a corrupted screen.
Jon
Jon Coldewey (coldewey) wrote : | #20 |
PS: I get the X Error BadRequest also in an xterm under jaunty, so that seems to be a sane response:
jon@sun:~$ glxinfo -i
name of display: 192.168.0.110:7.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 138 (DRI2)
Minor opcode of failed request: 1 ()
Serial number of failed request: 19
Current serial number in output stream: 19
Jon
Tormod Volden (tormodvolden) wrote : | #21 |
(To correct myself, this is using the "unichrome" 3D driver)
There should be no DRI2 support on these drivers/cards, so I guess a DRI2 request should fail, unless it is a "is-there-DRI2" probe request. Anyway, glxinfo -i should not fail like that.
Just to make sure this is still an issue in latest upstream versions, can you please try the openchrome driver from https:/
Jon Coldewey (coldewey) wrote : | #22 |
Tormod, do I need to install this updated driver in the ltsp chroot (client), on the server (host), or both?
Although, I guess it shouldn't do any harm installing them in both, as the server doesn't have any openchrome hardware.
Jon
Tormod Volden (tormodvolden) wrote : | #23 |
In the LTSP chroot. The graphics driver (the X server) is running entirely on the LTSP client. Only the X clients (applications and window manager) are running on the LTSP server, and send drawing requests to the X server (and receive keyboard/mouse events).
Jon Coldewey (coldewey) wrote : | #24 |
I have now installed the upstream openchrome driver in the chroot and updated the image. There is no change in the bahaviour of the affected thin client.
Jon
Changed in xorg (Ubuntu): | |
status: | Incomplete → Confirmed |
Bartosz Kosiorek (gang65) wrote : | #25 |
Attach your /var/log/Xorg.0.log file.
If you can from after reproducing this issue.
Jon Coldewey (coldewey) wrote : | #26 |
- Xorg.7.log -- from ltsp client, post-login Edit (51.1 KiB, text/plain)
Bartosz, I have already (unfortunately pasted into the comments, instead of attached), please see thread above. It is "Xorg.7.log" because it originates from the ltsp client. I will attach it properly for reference. Jon
Jon Coldewey (coldewey) wrote : | #27 |
- Xorg.7.log -- using openchrome driver from jaunty Edit (53.3 KiB, text/plain)
I'm not sure this is an issue with the openchrome driver. I copied the openchrome driver from jaunty ltsp to the karmic ltsp, well expecting it wouldn't work at all, because it was compiled for a different kernel. But the system boots up and shows the same fault symptoms as with the current and upstream openchrome video drivers, Xorg.7.log attached.
Jon
Jon Coldewey (coldewey) wrote : | #28 |
.. then again, the terminal that _does_ work, uses the vesa driver!
affects: | xorg (Ubuntu) → xserver-xorg-video-openchrome (Ubuntu) |
Bartosz Kosiorek (gang65) wrote : Re: [CLE266]Since upgrade from jaunty to karmic, one of two thin clients' login broken. | #29 |
Hello.
Try to run Karmic with kernel from Jaunty (2.6.28).
Try also disable DRI by adding editing xorg.conf file:
Section "Module"
...
Disable "dri"
...
EndSection
summary: |
- Since upgrade from jaunty to karmic, one of two thin clients' login - broken. + [CLE266]Since upgrade from jaunty to karmic, one of two thin clients' + login broken. |
Jon Coldewey (coldewey) wrote : | #30 |
I created an xorg.conf file (there is no xorg.conf by default) in /opt/ltsp/
Jon
Bartosz Kosiorek (gang65) wrote : | #31 |
Hi.
Try to enable DRI and disable AIGLX.
You can disable AIGLX and the compositing extension by amending your /etc/X11/xorg.conf like this:
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
Changed in xserver-xorg-video-openchrome (Ubuntu): | |
importance: | Undecided → High |
Jon Coldewey (coldewey) wrote : | #32 |
Bartosz,
That works as well.. I have removed the section from xorg.conf, that disabled DRI, and instead switched off AIGLX and disabled the compositing extension, as proposed.
Jon
summary: |
[CLE266]Since upgrade from jaunty to karmic, one of two thin clients' - login broken. + login broken (AIGLX problem). |
Bartosz Kosiorek (gang65) wrote : | #33 |
Add the to the Section "Device" following lines:
Option "XAANoOffscreen
Next, find the Section "ServerLayout" for your graphics card, and add the following:
Option "AIGLX" "true"
Try also enable compositing extension.
Changed in openchrome: | |
status: | Unknown → New |
Bartosz Kosiorek (gang65) wrote : | #34 |
Can you check the output of ~/.xsession-errors for anything interesting (with DRI and AIGLX enabled)?
Jon Coldewey (coldewey) wrote : | #35 |
OK.. wee problem related to my ignorance in configuring xorg.conf from scratch: at least under LTSP, xorg.conf is generated on the fly when the thin client boots up. I have created a custom xorg.conf for the various parameters outlined in this thread, but this does not include a "ServerLayout" section for the graphics card. How do I ensure the right naming convention for my card, so that we are sure it is actually read?
Jon
Bartosz Kosiorek (gang65) wrote : | #36 |
Sorry.
My mistake.
There is no ServerLayout.
Enable AIGLX and add to the Section "Device" following lines:
Option "XAANoOffscreen
Dolganov Victor (victor-dolganov) wrote : | #37 |
I have the same problem with openchrome on one karmic client and with kde 4.3 on LTSP server. If KDE 3.5 on LTSP server it works fine. On other ltsp client with openchrome it works with both KDE 4.3 and KDE 3.5.
Dolganov Victor (victor-dolganov) wrote : | #38 |
Option "XAANoOffscreen
tags: | added: karmic |
tags: | added: jaunty |
gcc (chris+ubuntu-qwirx) wrote : | #39 |
I found the same problem with an Aleutia E2 (VIA Eden CX700/VX700, openchrome), lucid, LTSP thin client.
It appears to be caused by this bug: https:/
Note that it usually, but not always, fails to log in from ldm on the LTSP client. The session crashes after about 3 seconds of spinning wheel wait cursor, and I get kicked back to the login screen.
There is a workaround that you could try in that bug report: force gnome to use metacity instead of compiz as the window manager.
Changed in xserver-xorg-video-openchrome (Ubuntu): | |
status: | Confirmed → Invalid |
no longer affects: | openchrome |
It appears this is a duplicate of bug: 463369, see:
"https:/ /bugs.launchpad .net/ubuntu/ +source/ compiz/ +bug/463369"
Sorry for the unnecessary report/post.
Jon