** Tags added: valid-xorg-conf
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Right, the sync-lines aren't written anymore, so closing as fixed.
** Changed in: xorg (Ubuntu)
Status: Incomplete = Fix Released
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of
If the sync lines aren't written to the xorg.conf file anymore with
Hardy, I don't believe that anyone will encounter the problem. However
the problem still exists in Gutsy, and I haven't tested Hardy yet.
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
What is the status of this bug? It has become a bit confusing to follow.
The vesa crash is due to wrong settings in the default xorg.conf. That's
fixed in hardy since those values are not written (although vesa could
still fail). Other issues should be on separate bugs.
** Changed in: xorg
I don't know the value of xineramascreen. I'll have to single step the
code, as the value is optimized out at the point where the program
segfaults.
But xscreens is a pointer to a XineramaScreenInfo structure, and the
pointer value is NULL, so screen[0].x_org is also invalid.
--
gdm greeter
Hmm... I just took a more through look at the code, and it seems that
the code where gdm crashes should only be executed if XineramaIsActive
returns true. So as far as I can tell, one of three things causes the
problem:
1) XineramaIsActive falsely returns TRUE, even though no Xinerama support is
** Changed in: xorg (Ubuntu)
Assignee: Tormod Volden (tormodvolden) = (unassigned)
Status: Incomplete = Confirmed
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs,
Has anything changed with the new nv 2.1.5 driver?
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Can you please also attach gdm.conf? I don't get why startx worked while
gdm didn't.
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) = Tormod Volden (tormodvolden)
Status: New = Incomplete
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
Ok. I'll test with the nv driver later, as I don't want to restart my X
currently.
The gdm.conf, as stated previously, is the one that is installed per
default. I've made no changes. Should I attach it anyways?
Since the greeter segfaults, it should be possible to obtain a core-
dump, and from
Sorry, I misread I doesn't work with the config files that are
installed by default as if you had to modify them. Funny enough I got
it right the last time :)
(from https://wiki.ubuntu.com/DebuggingXorg)
If you can't find any core files after a crash, look also in /var/crash, where
apport (the
Allright. I could not get it to produce a core file I could find (even
when setting core_pattern to /tmp/core).
However I inserted some raise(SIGSTOP) at strategic points in the file,
and then attached gdb to the process before it crashed. This is the
output from gdb (running in the daemon
What is the value of xineramascreen? I have on idea of the inner workings of
gdm :) but vesa does not do xinerama.
Is xscreens[0].x_org ok?
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of
Thanks for trying out the live cd. It picks the wrong driver, but I
don't know why. Can you try this:
sudo discover --disable-all --enabled=pci --format=%S\t%D\n video
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification
BTW, the greeter should not segfault because of a wrong sync line. I
would suggest keeping this bug for the crash - it should be allowed to
change the driver in xorg.conf without adjusting the monitor sync
ranges. And open a new bug on the installer picking the wrong driver for
your card.
--
gdm
This is the output from running the above command, on a gutsy updated 3
hours ago:
$ sudo discover --disable-all --enable=pci --format=%S\t%D\n video
XFree86 nv
XFree86 nv
XFree86 nv
I searched for the installer picking the wrong driver for my card, and
that has already been reported in:
Ok. Attached is the xorg.conf I have obtained using the break=bottom
method, using a tribe5 kubuntu installer. As you can see, it tries to
use the nv driver. Also it have detected the display size to be
1920x1920 instead of the correct 1920x1200. However the refresh rates
seem to be correct.
**
You can switch to a virtual console with ctrl-alt-F2 and log in and copy
the xorg.conf. Then modify it to work and restart X.
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs,
Unfortunately CTRL+ALT+F2 does not work. However I think that the laptop
is still alive, as it requests a DHCP lease, when a network cable is
connected, after X have started. Is it possible to have the LiveCD start
up the SSH-server, or display a console on an USB Serial converter?
--
gdm
Boot with break=bottom on the kernel line. Then copy /root/etc/X11/xorg.conf to
/root/etc/X11/xorg.conf.nonsafe
You can now edit the file with: chroot /root nano /etc/X11/xorg.conf
When you're done exit the break shell and it will continue booting.
--
gdm greeter crashes when X is using vesa
Ok. I finally got time to test kubuntu tribe 5. It will not bring up a
working X, when booting ordinarily. However the safe graphics mode, will
bring up working X. However in this case, the refresh settings are:
HorizSync 30-70
VertRefresh 50-160
I.e. the ones that
Nope. The autodetection causes the nv driver to be used, and my graphics
card is too new to work with that driver.
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Did the installer choose nv by itself the first time, or have you
selected nv at some point?
From your log I found the PCI ID 10de:040c which I can not find in
discover-data. It's not in src/nv_driver.c either. It clearly should not
select the nv driver.
--
gdm greeter crashes when X is using
To be honest, I can't remember. I believe that I had working X, with the
wrong screen resolution after the installation, but I might have changed
the driver to vesa before that. I don't remember.
I know that I have manually selected the nv-driver by editing
/etc/X11/xorg.conf, at some point.
dpkg-reconfigure xserver-xorg keeps a setting in the debconf database
xserver-xorg/config/device/driver to remember which driver has been
detected or chosen. You can look at the /var/cache/debconf/config.dat
file, but I wouldn't recommend to modify it manually. If you run dpkg-
reconfigure without
Do you mean just booting the livecd, or re-installing from the livecd?
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Just booting from it.
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I forgot to mention it in the bug report, but the X server is actually
working as it should, if I start it using startx on the command line.
** Attachment added: Xorg.0.log when trying to start gdm
http://launchpadlibrarian.net/9211254/Xorg.0.log
--
gdm greeter crashes when X is using vesa
Can you please attach /etc/gdm/gdm.conf ? Did you ever change it, or gdm
.conf-custom?
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I doesn't work with the config files that are installed by default. Do
you still want a copy?
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Do you still want a copy?
No, that is not needed I think.
** Changed in: xorg (Ubuntu)
Assignee: Tormod Volden = (unassigned)
Status: Incomplete = New
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification
Ok. I figure the problem out. I got an xorg.conf file from another user
with a T61p, who didn't have any problems using kdm, and if I use his
refresh settings, both gdm and kdm works again.
I changed the refresh settings from:
Horizsync 30-70
Vertrefresh 50-160
to:
Funny that it worked when you launched X with startx.
Is autodetection working, will dpkg-reconfigure -phigh xserver-xorg make it
work again? (Maybe backup your xorg.conf first)
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug
** Attachment added: Output from running gdm -nodaemon and with debug enabled
http://launchpadlibrarian.net/9206997/gdm.log
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs,
looks like an xorg issue
** Changed in: xorg (Ubuntu)
Sourcepackagename: gdm = xorg
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Can you please attach /var/log/Xorg.0.log (from using the vesa driver)?
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) = Tormod Volden
Status: New = Incomplete
--
gdm greeter crashes when X is using vesa driver
https://bugs.launchpad.net/bugs/138718
You received this bug
36 matches
Mail list logo
