Re: dpkg-reconfigure of xserver-xorg creates problem for users!
On Wed, May 16, 2007 at 01:55:35 +0000, Bruce M. Ward wrote:
> Thanks to those who responded. Unfortunately, on this machine I'm restricted to using web-mail so can't continue the thread ...
>
> Michael - problem user is in same groups (and more) as new user.
Which groups are those? Maybe the problematic user does something during
X startup which the new user cannot do.
> Here follows the output Florian asked for:
>
> egrep '^\((EE|WW)\)' /var/log/Xorg.0.log
>
> (WW) The directory "/usr/X11R6/lib/X11/fonts/misc" does not exist.
[ snip: more font warnings ]
> (WW) (1600x1200,E70-9) mode clock 175.5MHz exceeds DDC maximum 110MHz
[ snip: more mode clock warnings ]
> (EE) AIGLX: Screen 0 is not DRI capable
The warnings should not keep the X server from starting. The last error
is to be expected with the vesa driver and not critical AFAIK.
> cat .xsession-errors
>
> /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
> /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "student"
> /etc/gdm/Xsession: Beginning session setup...
> The application 'x-session-manager' lost its connection to the display :0.0;
> most likely the X server was shut down or you killed/destroyed
> the application.
> Xsession: X session started for student at Wed May 16 13:20:53 NZST 2007
That looks like it is really the X server that crashes and not a user
process. I think Micheal was on the right track when asking about the
detailed group memberships of the two users.
> lspci -i egrep 'vga|video|display|graphic'
>
> 01:00.0 VGA compatible controller: VIA Technologies, Inc. Unknown device 3230 (rev 11)
>
> (which is why we use the vesa driver)
Yes, it looks like the Chrome 9 support might still take a while:
http://wiki.openchrome.org/tikiwiki/tiki-index.php?page=HardwareCaveats
> awk '/Section "Device"/,/EndSection/' /etc/X11/xorg.conf
>
> Section "Device"
> Identifier "Generic Video Card"
> Driver "vesa"
> BusID "PCI:1:0:0"
> EndSection
No obvious problem here. Grasping for straws, you could try if disabling
"ShadowFB" and/or "ModeSetClearScreen" makes a difference (see "man
vesa").
> Here is the end portion of the Xorg log file:
>
> (II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD) xkb_keycodes { include "xfree86+aliases(qwerty)" };
> xkb_types { include "complete" };
> xkb_compatibility { include "complete" };
> xkb_symbols { include "pc(pc105)+us" };
> xkb_geometry { include "pc(pc104)" };
> (II) Configured Mouse: ps2EnableDataReporting: succeeded
> (II) VESA(0): VBESetVBEMode failed...Tried again without customized values.
> Backtrace:
> 0: /usr/bin/X11/X(xf86SigHandler+0x84) [0x80c4354]
> 1: [0xb7fc8420]
> 2: /usr/lib/xorg/modules/libfb.so(fbCopyNtoN+0x226) [0xb7b893e6]
> 3: /usr/lib/xorg/modules/libfb.so(fbCopyRegion+0x8f) [0xb7b8827f]
> 4: /usr/lib/xorg/modules/libfb.so(fbDoCopy+0x498) [0xb7b888e8]
> 5: /usr/lib/xorg/modules/libfb.so(fbCopyArea+0x78) [0xb7b88ab8]
Unfortunately this goes beyond my knowledge of X.
[...]
> Fatal server error:
> Caught signal 11. Server aborting
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: