Bug#692814: gdm3 is not staring normally

2013-05-11 Thread Luca Bruno
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 Xorg.1.log Description: Binary data :1.log Description: Binary data

Re: Bug#692814: gdm3 is not staring normally

2012-11-14 Thread Praveen A
2012/11/13 Praveen A prav...@gmail.com: 2012/11/11 Julien Cristau jcris...@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

Re: Bug#692814: gdm3 is not staring normally

2012-11-12 Thread Praveen A
2012/11/11 Julien Cristau jcris...@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,

Re: Bug#692814: gdm3 is not staring normally

2012-11-11 Thread Julien Cristau
On Sat, Nov 10, 2012 at 02:15:41 +0530, Praveen A wrote: 2012/11/9 Simon McVittie s...@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

Re: Bug#692814: gdm3 is not staring normally

2012-11-09 Thread Simon McVittie
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:

Re: Bug#692814: gdm3 is not staring normally

2012-11-09 Thread Praveen A
2012/11/10 Praveen A prav...@gmail.com: 2012/11/9 Simon McVittie s...@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: