Bug#692814: gdm3 is not staring normally

[Praveen A]

2012/11/10 Praveen A <pravi.a at gmail.com>:
> 2012/11/9 Simon McVittie <smcv at 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.