#692814 "X crash with gdm3 on boot and with kdm on first logout"

Package:
xserver-xorg
Source:
xorg
Description:
X.Org X server
Submitter:
Praveen A
Date:
2013-11-13 05:27:10 UTC
Severity:
important
#692814#5
Date:
2012-11-09 11:00:26 UTC
From:
To:
package: gdm3
severity: critical
version: 3.6.1-1

In /var/log/gdm3/:0.log I can see this error message (complete log
attached :0.log.error)

DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [9]
param: 4, val: 32653
Xorg: ../../intel/intel_bufmgr_gem.c:2783: drm_intel_bufmgr_gem_init:
Assertion `0' failed.

But when I go to single user mode (using grub "recovery mode" menu)
and start manually /etc/init.d/gdm3 it start successfully. Once I exit
from single user mode, I can get the gdm3 screen and login. Attaching
the log of gdm3 after it started successfully (:0.log).

Every time I boot, I have to use the same work around and it is not
intuitive either.

Let me know if you need any other log files.

Thanks
Praveen
--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
You have to keep reminding your government that you don't get your
rights from them; you give them permission to rule, only so long as
they follow the rules: laws and constitution.

#692814#10
Date:
2012-11-09 15:11:08 UTC
From:
To:
...
Xorg server started by gdm, possibly to do with libdrm-intel1 or the
i915 driver in the kernel (or maybe X, or the X Intel driver).

Please send the information that would have been gathered if you'd
reported this as an X bug, which you can get with this command:

    reportbug --template xserver-xorg

Do you get this error with gdm3 3.4 from unstable, or only with gdm3 3.6
from experimental?

X maintainers: any ideas?

    S

#692814#15
Date:
2012-11-09 20:45:41 UTC
From:
To:
2012/11/9 Simon McVittie <smcv@debian.org>:

attaching the reportbug template.  It started appearing after I
updated gdm3 to the version in experimental. I will try to switch back
to 3.4 version, but I may be able to do it only in one or two days
(currently on a mobile internet plan, but I will try now).

#692814#20
Date:
2012-11-09 21:08:36 UTC
From:
To:
2012/11/10 Praveen A <pravi.a@gmail.com>:

It looks like an X issue as I was able to reproduce the issue with gdm
3.4 (I was just worried I may have to pull in lots of dependencies). I
just have to enter recovery mode, then just exit it (earlier I was
starting gdm3 before I exit from recovery mode). It could be something
related to order or services started too.

#692814#25
Date:
2012-11-11 15:33:57 UTC
From:
To:
Please get us the X log showing the error, the one in your message seems
fine.

Cheers,
Julien

#692814#30
Date:
2012-11-13 05:20:36 UTC
From:
To:
2012/11/11 Julien Cristau <jcristau@debian.org>:

Log attached.

#692814#35
Date:
2012-11-14 15:53:05 UTC
From:
To:
2012/11/13 Praveen A <pravi.a@gmail.com>:

Also kdm seemed to be able start X normally. Attaching X log with kdm.
I have switched to kdm for now as default.

#692814#40
Date:
2012-11-25 08:50:47 UTC
From:
To:
2012/11/14 Praveen A <pravi.a@gmail.com>:

I found out there is a problem with kdm too, but only when I logout. X
crashes (can't switch to any VT to see what went wrong) after I logout
from the session.

Attaching the X crash log. When I tried a second time, I was dropped
into a VT, where I collected /var/log/Xorg.0.log. Also startx worked
without any problem. I think it is the way display managers launch X
or it could be a library version mis-match.

#692814#45
Date:
2012-12-19 23:07:28 UTC
From:
To:
Package: gdm3
Version: 3.6.1-2
Followup-For: Bug #692814

Hi.

I ave the same problem, but when I switch to the VTTY7 I can ear the speech incoming from orca, and I can start a
gnome session, and I can work normally, but the X graphics output cann't be seen in the display.
In the display I can see text, but I cann't read it because the X server takes the keyboard.

I attach the gdm3 and the x log to you.

Regards.

#692814#50
Date:
2013-01-16 07:26:37 UTC
From:
To:
After switching to kdm, initial login works, but when I logout X
crashes. I did ssh into my machine and copied the log. But there seems
not much info other than a line "Backtrace:" at the end. Is there
another way I can get more info? Let me try and install dbg package
for Xorg.

#692814#63
Date:
2013-01-16 08:31:34 UTC
From:
To:
backtrace @praveen_box
#692814#68
Date:
2013-01-21 10:57:13 UTC
From:
To:
After switching to systemd, I'm able to start gdm3 during boot. So it
could be the way sysvinit is trying to start X server that is causing
problems.

#692814#73
Date:
2013-01-24 17:02:39 UTC
From:
To:
I logged out and logged in back in kdm and nothing happened.

Here's the backtrace

gonzalo@gonzalo:~$ sudo gdb --pid=3343
[sudo] password for gonzalo:
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Attaching to process 3343
Reading symbols from /usr/bin/kdm...(no debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libX11.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libX11.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libXau.so.6...(no debugging symbols found)...done.
Loaded
 symbols for /usr/lib/x86_64-linux-gnu/libXau.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libXdmcp.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
Reading symbols from /lib/x86_64-linux-gnu/libpam.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libpam.so.0
Reading symbols from /usr/lib/x86_64-linux-gnu/libck-connector.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libck-connector.so.0
Reading symbols from /lib/x86_64-linux-gnu/libdbus-1.so.3...(no debugging symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libdbus-1.so.3
Reading symbols from /lib/x86_64-linux-gnu/librt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/librt.so.1
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging symbols found)...done.
Loaded
 symbols for /lib/x86_64-linux-gnu/libc.so.6
Reading symbols from /usr/lib/x86_64-linux-gnu/libxcb.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/libxcb.so.1
Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/x86_64-linux-gnu/libdl.so.2
Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...(no debugging symbols found)...done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Loaded symbols for /lib/x86_64-linux-gnu/libpthread.so.0
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
0x00007f30f9da5553 in select () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) c
Continuing.

I use sysvinit 2.88dsf-37, kdm 4:4.8.4-5 and xserver-xorg 1:7.7+1

#692814#80
Date:
2013-05-11 09:02:23 UTC
From:
To:
Hi, I'm having the same issue. I'm attaching both :1.log from /var/log/gdm3
and Xorg.1.log .

#692814#85
Date:
2013-11-13 05:22:21 UTC
From:
To:
notfound: 1:7.7+4