Bug#692814: gdm3 is not staring normally
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
Bug#692814: gdm3 is not staring normally
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 dpkg1.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 libcanberra00.28-6 ii libfontconfig1 2.9.0-7 ii libgdk-pixbuf2.0-0 2.26.4-2 ii libglib2.0-02.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 libpam0g1.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 libwrap07.6.q-24 ii libx11-62: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-base4.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-orca3.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 X.Org X Server 1.12.4 Release Date: 2012-08-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 i686 Debian Current Operating System: Linux itec7-0204 3.2.0-4-686-pae #1 SMP Debian 3.2.32-1 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID=0d9fded6-7940-4a64-8c6c-446fdfd7d247 ro resume=UUID=95274e47-fa26-431e-9adc-88179159e230 quiet splash Build Date: 29 November 2012 08:52:43PM xorg-server 2:1.12.4-4 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.26.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Dec 19 22:39:55 2012 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen
Bug#692814: gdm3 is not staring normally
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 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 Description: Binary data
Bug#692814: gdm3 is not staring normally
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, only so long as they follow the rules: laws and constitution. Xorg.0.log Description: Binary data
Bug#692814: gdm3 is not staring normally
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 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 Description: Digital signature
Bug#692814: gdm3 is not staring normally
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692814: gdm3 is not staring normally
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: -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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
