Re: root can startx, user can't

• To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
• Subject: Re: root can startx, user can't
• From: Rahul Sundaram <rahulsundaram@xxxxxxxxx>
• Date: Tue, 16 Nov 2004 09:06:24 +0530
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=NBwzAFDoN9Hj51DEiEHszLJ0MSpYRw8X54x5pspQCTBlbKPsNZ3IcCMVhmXEy7QDLHBKyP5KNPbKrrmXJBM7uWHAFgbDhcqibQItSNqEEm6ihdBMe2rEAjbxleyuWCXUd2E592W35zAQubY33YdcZ7J5/sZ8/c6vuSiOY+6AYj8=
• In-reply-to: <[email protected]>
• References: <[email protected]>
• Reply-to: Rahul Sundaram <rahulsundaram@xxxxxxxxx>, For users of Fedora Core releases <fedora-list@xxxxxxxxxx>

Hi


> 
> "*** glibc detected *** corrupted double-linked list: 0x08a9ebd0***
> /etc/X11/xinit/xinitrc-common: line 45:  4690 Aborted             xmodmap
> "$sysmodmap"


read the release notes for fc3

http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/os/RELEASE-NOTES-en.html

it mentions about glibc adding some internal checks. change the
environment variable as mentioned there and report it in
bugzilla.redhat.com against xorg. it would be useful to mention that
this bug seems to be trigged by nvidia driver though it is not
supported by redhat directly

regards
Rahul Sundaram

• Follow-Ups:
  • Re: root can startx, user can't
    • From: Etanisla Lopez-Ortiz

• References:
  • root can startx, user can't
    • From: Etanisla Lopez-Ortiz

• Prev by Date: Re: Fedora Core 3 - setting refresh rate for monitor
• Next by Date: Re: Yup, it's definitely fedora's fault, not my hardware.
• Previous by thread: root can startx, user can't
• Next by thread: Re: root can startx, user can't
• Index(es):
  • Date
  • Thread