Debian Bug report logs - #692814
"X crash with gdm3 on boot and with kdm on first logout"

version graph

Package: xserver-xorg; Maintainer for xserver-xorg is Debian X Strike Force <debian-x@lists.debian.org>; Source for xserver-xorg is src:xorg.

Reported by: Praveen A <pravi.a@gmail.com>

Date: Fri, 9 Nov 2012 11:03:02 UTC

Severity: important

Found in version xorg/1:7.7+1

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Fri, 09 Nov 2012 11:03:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen A <pravi.a@gmail.com>:
New Bug report received and forwarded. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Fri, 09 Nov 2012 11:03:04 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Praveen A <pravi.a@gmail.com>
To: submit@bugs.debian.org
Subject: gdm3 is not staring normally
Date: Fri, 9 Nov 2012 16:30:26 +0530
[Message part 1 (text/plain, inline)]
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.
[:0.log.error (application/octet-stream, attachment)]
[:0.log (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Fri, 09 Nov 2012 15:15:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Simon McVittie <smcv@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Fri, 09 Nov 2012 15:15:03 GMT) Full text and rfc822 format available.

Message #10 received at 692814@bugs.debian.org (full text, mbox):

From: Simon McVittie <smcv@debian.org>
To: Praveen A <pravi.a@gmail.com>, 692814@bugs.debian.org, debian-x@lists.debian.org
Subject: Re: Bug#692814: gdm3 is not staring normally
Date: Fri, 09 Nov 2012 15:11:08 +0000
On 09/11/12 11:00, Praveen A wrote:
> 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.

This doesn't necessarily look like a gdm bug to me: it's a crash in the
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



Information forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Fri, 09 Nov 2012 20:48:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen A <pravi.a@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Fri, 09 Nov 2012 20:48:03 GMT) Full text and rfc822 format available.

Message #15 received at 692814@bugs.debian.org (full text, mbox):

From: Praveen A <pravi.a@gmail.com>
To: Simon McVittie <smcv@debian.org>
Cc: 692814@bugs.debian.org, debian-x@lists.debian.org
Subject: Re: Bug#692814: gdm3 is not staring normally
Date: Sat, 10 Nov 2012 02:15:41 +0530
[Message part 1 (text/plain, inline)]
2012/11/9 Simon McVittie <smcv@debian.org>:
> On 09/11/12 11:00, Praveen A wrote:
>> 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.
>
> This doesn't necessarily look like a gdm bug to me: it's a crash in the
> 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

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).

--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
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.
[xserver-xorg.template (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Fri, 09 Nov 2012 21:12:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen A <pravi.a@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Fri, 09 Nov 2012 21:12:05 GMT) Full text and rfc822 format available.

Message #20 received at 692814@bugs.debian.org (full text, mbox):

From: Praveen A <pravi.a@gmail.com>
To: Simon McVittie <smcv@debian.org>
Cc: 692814@bugs.debian.org, debian-x@lists.debian.org
Subject: Re: Bug#692814: gdm3 is not staring normally
Date: Sat, 10 Nov 2012 02:38:36 +0530
2012/11/10 Praveen A <pravi.a@gmail.com>:
> 2012/11/9 Simon McVittie <smcv@debian.org>:
>> On 09/11/12 11:00, Praveen A wrote:
>>> 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.
>>
>> This doesn't necessarily look like a gdm bug to me: it's a crash in the
>> 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
>
> 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).

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.

--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
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.



Information forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Sun, 11 Nov 2012 15:36:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Julien Cristau <jcristau@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Sun, 11 Nov 2012 15:36:05 GMT) Full text and rfc822 format available.

Message #25 received at 692814@bugs.debian.org (full text, mbox):

From: Julien Cristau <jcristau@debian.org>
To: Praveen A <pravi.a@gmail.com>
Cc: Simon McVittie <smcv@debian.org>, 692814@bugs.debian.org, debian-x@lists.debian.org
Subject: Re: Bug#692814: gdm3 is not staring normally
Date: Sun, 11 Nov 2012 16:33:57 +0100
[Message part 1 (text/plain, inline)]
On Sat, Nov 10, 2012 at 02:15:41 +0530, Praveen A wrote:

> 2012/11/9 Simon McVittie <smcv@debian.org>:
> > On 09/11/12 11:00, Praveen A wrote:
> >> 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.
> >
> > This doesn't necessarily look like a gdm bug to me: it's a crash in the
> > 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
> 
> 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).
> 
Please get us the X log showing the error, the one in your message seems
fine.

Cheers,
Julien
[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Tue, 13 Nov 2012 05:24:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen A <pravi.a@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Tue, 13 Nov 2012 05:24:03 GMT) Full text and rfc822 format available.

Message #30 received at 692814@bugs.debian.org (full text, mbox):

From: Praveen A <pravi.a@gmail.com>
To: Julien Cristau <jcristau@debian.org>
Cc: Simon McVittie <smcv@debian.org>, 692814@bugs.debian.org, debian-x@lists.debian.org
Subject: Re: Bug#692814: gdm3 is not staring normally
Date: Tue, 13 Nov 2012 10:50:36 +0530
[Message part 1 (text/plain, inline)]
2012/11/11 Julien Cristau <jcristau@debian.org>:
> Please get us the X log showing the error, the one in your message seems
> fine.

Log attached.

--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
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.
[Xorg.0.log (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Wed, 14 Nov 2012 15:57:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen A <pravi.a@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Wed, 14 Nov 2012 15:57:07 GMT) Full text and rfc822 format available.

Message #35 received at 692814@bugs.debian.org (full text, mbox):

From: Praveen A <pravi.a@gmail.com>
To: Julien Cristau <jcristau@debian.org>
Cc: Simon McVittie <smcv@debian.org>, 692814@bugs.debian.org, debian-x@lists.debian.org
Subject: Re: Bug#692814: gdm3 is not staring normally
Date: Wed, 14 Nov 2012 21:23:05 +0530
[Message part 1 (text/plain, inline)]
2012/11/13 Praveen A <pravi.a@gmail.com>:
> 2012/11/11 Julien Cristau <jcristau@debian.org>:
>> Please get us the X log showing the error, the one in your message seems
>> fine.
>
> Log attached.

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

--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
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.
[Xorg.0.log (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Sun, 25 Nov 2012 08:51:10 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen A <pravi.a@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Sun, 25 Nov 2012 08:51:10 GMT) Full text and rfc822 format available.

Message #40 received at 692814@bugs.debian.org (full text, mbox):

From: Praveen A <pravi.a@gmail.com>
To: Julien Cristau <jcristau@debian.org>
Cc: Simon McVittie <smcv@debian.org>, 692814@bugs.debian.org, debian-x@lists.debian.org
Subject: Re: Bug#692814: gdm3 is not staring normally
Date: Sun, 25 Nov 2012 14:20:47 +0530
[Message part 1 (text/plain, inline)]
2012/11/14 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.

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.

--
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
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.
[Xorg.0.log (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, francipvb@hotmail.com, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Thu, 20 Dec 2012 02:09:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Francisco Del Roio <francipvb@hotmail.com>:
Extra info received and forwarded to list. Copy sent to francipvb@hotmail.com, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Thu, 20 Dec 2012 02:09:04 GMT) Full text and rfc822 format available.

Message #45 received at 692814@bugs.debian.org (full text, mbox):

From: Francisco Del Roio <francipvb@hotmail.com>
To: Debian Bug Tracking System <692814@bugs.debian.org>
Subject: Re: gdm3 is not staring normally
Date: Wed, 19 Dec 2012 23:07:28 +0000
[Message part 1 (text/plain, inline)]
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.
-- System Information:
Debian Release: wheezy/sid
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gdm3 depends on:
ii  accountsservice                             0.6.21-7
ii  adduser                                     3.113+nmu3
ii  dconf-gsettings-backend                     0.12.1-3
ii  dconf-tools                                 0.12.1-3
ii  debconf [debconf-2.0]                       1.5.46
ii  dpkg                                        1.16.9
ii  gir1.2-glib-2.0                             1.32.1-1
ii  gnome-session-bin                           3.6.0-1
ii  gnome-session-fallback [x-session-manager]  3.6.0-1
ii  gnome-settings-daemon                       3.4.2+git20120925.a4c817-2
ii  gnome-terminal [x-terminal-emulator]        3.4.1.1-2
ii  gsettings-desktop-schemas                   3.6.0-1
ii  libaccountsservice0                         0.6.21-7
ii  libatk1.0-0                                 2.6.0-1
ii  libaudit0                                   1:1.7.18-1.1
ii  libc6                                       2.13-37
ii  libcairo-gobject2                           1.12.6-1
ii  libcairo2                                   1.12.6-1
ii  libcanberra-gtk3-0                          0.28-6
ii  libcanberra0                                0.28-6
ii  libfontconfig1                              2.9.0-7
ii  libgdk-pixbuf2.0-0                          2.26.4-2
ii  libglib2.0-0                                2.34.3-1
ii  libglib2.0-bin                              2.34.3-1
ii  libgtk-3-0                                  3.6.1-1
ii  libpam-modules                              1.1.3-7.1
ii  libpam-runtime                              1.1.3-7.1
ii  libpam0g                                    1.1.3-7.1
ii  libpango1.0-0                               1.30.1-1
ii  librsvg2-common                             2.36.1-1
ii  libselinux1                                 2.1.9-5
ii  libupower-glib1                             0.9.17-1
ii  libwrap0                                    7.6.q-24
ii  libx11-6                                    2:1.5.0-1
ii  libxau6                                     1:1.0.7-1
ii  libxdmcp6                                   1:1.1.1-1
ii  libxrandr2                                  2:1.3.2-2
ii  lsb-base                                    4.1+Debian8
ii  metacity [x-window-manager]                 1:2.34.3-3
ii  policykit-1-gnome                           0.105-2
ii  upower                                      0.9.17-1
ii  x11-common                                  1:7.7+1
ii  x11-xserver-utils                           7.7~3

Versions of packages gdm3 recommends:
ii  at-spi2-core               2.5.3-2
ii  desktop-base               7.0.3
ii  gnome-icon-theme           3.4.0-2
ii  gnome-icon-theme-symbolic  3.4.0-2
ii  x11-xkb-utils              7.7~1
ii  xserver-xephyr             2:1.12.4-4
ii  xserver-xorg               1:7.7+1
ii  zenity                     3.4.0-2

Versions of packages gdm3 suggests:
ii  gnome-orca            3.4.2-2
pn  gnome-shell           <none>
pn  gok                   <none>
ii  libpam-gnome-keyring  3.4.1-5

-- debconf information:
* shared/default-x-display-manager: gdm3
  gdm3/daemon_name: /usr/sbin/gdm3
[:0.log (text/plain, attachment)]
[Xorg.0.log (text/plain, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>:
Bug#692814; Package gdm3. (Wed, 16 Jan 2013 07:30:06 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen A <pravi.a@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>. (Wed, 16 Jan 2013 07:30:06 GMT) Full text and rfc822 format available.

Message #50 received at 692814@bugs.debian.org (full text, mbox):

From: Praveen A <pravi.a@gmail.com>
To: 692814@bugs.debian.org
Subject: Attaching today's log
Date: Wed, 16 Jan 2013 12:56:37 +0530
[Message part 1 (text/plain, inline)]
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.

-- 
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
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.
[Xorg.0.log.16jan (application/octet-stream, attachment)]

Bug reassigned from package 'gdm3' to 'xserver-xorg'. Request was from Praveen A <praveen@debian.org> to control@bugs.debian.org. (Wed, 16 Jan 2013 07:36:05 GMT) Full text and rfc822 format available.

No longer marked as found in versions gdm3/3.6.1-1 and gdm3/3.6.1-2. Request was from Praveen A <praveen@debian.org> to control@bugs.debian.org. (Wed, 16 Jan 2013 07:36:05 GMT) Full text and rfc822 format available.

Changed Bug title to '"X crash with gdm3 on boot and with kdm on first logout"' from 'gdm3 is not staring normally' Request was from Praveen A <praveen@debian.org> to control@bugs.debian.org. (Wed, 16 Jan 2013 07:51:09 GMT) Full text and rfc822 format available.

Marked as found in versions xorg/1:7.7+1. Request was from Praveen A <praveen@debian.org> to control@bugs.debian.org. (Wed, 16 Jan 2013 07:51:10 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian X Strike Force <debian-x@lists.debian.org>:
Bug#692814; Package xserver-xorg. (Wed, 16 Jan 2013 08:33:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to sandeep shedmake <sandeep.shedmake@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <debian-x@lists.debian.org>. (Wed, 16 Jan 2013 08:33:03 GMT) Full text and rfc822 format available.

Message #63 received at 692814@bugs.debian.org (full text, mbox):

From: sandeep shedmake <sandeep.shedmake@gmail.com>
To: 692814@bugs.debian.org
Subject: backtrace
Date: Wed, 16 Jan 2013 14:01:34 +0530
[Message part 1 (text/plain, inline)]
backtrace @praveen_box
[Message part 2 (text/html, inline)]
[deb_692814_bktrace.txt (text/plain, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian X Strike Force <debian-x@lists.debian.org>:
Bug#692814; Package xserver-xorg. (Mon, 21 Jan 2013 11:00:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen A <pravi.a@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <debian-x@lists.debian.org>. (Mon, 21 Jan 2013 11:00:04 GMT) Full text and rfc822 format available.

Message #68 received at 692814@bugs.debian.org (full text, mbox):

From: Praveen A <pravi.a@gmail.com>
To: 692814@bugs.debian.org
Subject: systemd starts gdm3 correctly
Date: Mon, 21 Jan 2013 16:27:13 +0530
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.

-- 
പ്രവീണ്‍ അരിമ്പ്രത്തൊടിയില്‍
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.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian X Strike Force <debian-x@lists.debian.org>:
Bug#692814; Package xserver-xorg. (Thu, 24 Jan 2013 17:06:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Diazepan Medina <spanishbizarro3@yahoo.com>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <debian-x@lists.debian.org>. (Thu, 24 Jan 2013 17:06:03 GMT) Full text and rfc822 format available.

Message #73 received at 692814@bugs.debian.org (full text, mbox):

From: Diazepan Medina <spanishbizarro3@yahoo.com>
To: "692814@bugs.debian.org" <692814@bugs.debian.org>
Subject: not happening to me on kdm
Date: Thu, 24 Jan 2013 09:02:39 -0800 (PST)
[Message part 1 (text/plain, inline)]
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
[Message part 2 (text/html, inline)]

Severity set to 'important' from 'critical' Request was from Julien Cristau <jcristau@debian.org> to control@bugs.debian.org. (Sat, 26 Jan 2013 17:48:06 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian X Strike Force <debian-x@lists.debian.org>:
Bug#692814; Package xserver-xorg. (Sat, 11 May 2013 09:06:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Luca Bruno <lethalman88@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <debian-x@lists.debian.org>. (Sat, 11 May 2013 09:06:04 GMT) Full text and rfc822 format available.

Message #80 received at 692814@bugs.debian.org (full text, mbox):

From: Luca Bruno <lethalman88@gmail.com>
To: 692814@bugs.debian.org
Subject: Re: Bug#692814: gdm3 is not staring normally
Date: Sat, 11 May 2013 11:02:23 +0200
[Message part 1 (text/plain, inline)]
Hi, I'm having the same issue. I'm attaching both :1.log from /var/log/gdm3
and Xorg.1.log .

-- 
www.debian.org - The Universal Operating System
[Message part 2 (text/html, inline)]
[Xorg.1.log (application/octet-stream, attachment)]
[:1.log (application/octet-stream, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian X Strike Force <debian-x@lists.debian.org>:
Bug#692814; Package xserver-xorg. (Wed, 13 Nov 2013 05:27:10 GMT) Full text and rfc822 format available.

Acknowledgement sent to Praveen Arimbrathodiyil <praveen@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian X Strike Force <debian-x@lists.debian.org>. (Wed, 13 Nov 2013 05:27:10 GMT) Full text and rfc822 format available.

Message #85 received at 692814@bugs.debian.org (full text, mbox):

From: Praveen Arimbrathodiyil <praveen@debian.org>
To: N: <692814@bugs.debian.org>, control@bugs.debian.org
Subject: this is fixed in current version of X
Date: Wed, 13 Nov 2013 10:52:21 +0530
notfound: 1:7.7+4



Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sun Apr 20 19:29:49 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.