Bug#981368: xserver-xorg-video-intel: Xserver becomes unresponsive with some worloads. maybe related to video rendering
Control: reassign -1 linux Control: found -1 5.10.0-2 Control: affects -1 xserver-xorg-video-intel Control: fixed -1 5.10.19-1 Control: close -1 5.10.19-1 On Tue, 23 Feb 2021 22:36:02 +0100 joerg.mechnich wrote: > Looks like this was actually a bug in the i915 module: > > https://gitlab.freedesktop.org/drm/intel/-/issues/2905 > > There is a linked issue #2923 > "deadlock in intel_atomic_cleanup_work (kernel 5.10.5)" > that seems to fit the descriptions in this thread here. > > After upgrading to a custom 5.10.17 kernel, I don't seem to experience > the same issue anymore while still using the intel Xorg driver. > > I agree that this report could be closed now. Hi, Since this seems to be a kernel bug, I am resssigning this bug report to linux kernel and marking it as affecting xserver-xorg-video-intel. Since linux 5.10.19 is already in sid I am marking this bug report as fixed with that upload. Trying to do everything with this message, not sure if it will work well. > Cheers and thanks for keeping the intel driver alive, still performs > significantly better on my particular system than the modesetting driver! +1 Regards, -- Agustin
Bug#943893: glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
On Thu, Oct 31, 2019 at 05:24:52PM +0100, Michel Dänzer wrote: > On 2019-10-31 3:11 p.m., Agustin Martin Domingo wrote: > > Package: xserver-xorg-core > > Version: 2:1.20.4-1 > > Severity: important > > > > Dear Maintainer, > > > > X session crashes randomly, losing unsaved information. > > > > Xorg.0.log (attached below) shows that a segfault is aborting the server. > > > > Error starts with > > > > glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage > > > > Browsing for that error I found > > > > [Bug 110500 - X-Server crashes - GL error: GL_OUT_OF_MEMORY in > > glTexSubImage ] > > https://bugs.freedesktop.org/show_bug.cgi?id=110500 > > > > with a similar backtrace. > > > > Very similar backtraces (but for /usr/bin/Xwayland instead of > > /usr/lib/xorg/modules/libglamoregl.so) are reported in > > > > [Sometimes my Ubuntu Log me out and close all applications] > > https://gitlab.freedesktop.org/xorg/xserver/issues/833. > > > > and > > > > [https://gitlab.freedesktop.org/xorg/xserver/issues/647] > > https://gitlab.freedesktop.org/xorg/xserver/issues/647 > > > > This last one seems already fixed upstream, and there is a suggestion that > > Xwayland 1.20.5 contains the fix. Since I see libglamoregl.so in my > > backtrace I am setting xserver-xorg-core as affected package. Please > > reassign if aprppriate. > > The root cause seems to be a memory leak in the nouveau drivers. While > glamor can be made more robust against not being able to allocate/update > OpenGL textures, at some point it won't be able to continue if no memory > can be allocated, so it's better to address the leak. Thanks for the info. Seems that this has already been reported against the nouveau driver, [Xorg crashes randomly because of memory leak] https://bugs.freedesktop.org/show_bug.cgi?id=110714 Bad news in that bug report are that 1.20.5 is reported not helping. Regards, -- Agustin
Bug#943893: glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
Package: xserver-xorg-core Version: 2:1.20.4-1 Severity: important Dear Maintainer, X session crashes randomly, losing unsaved information. Xorg.0.log (attached below) shows that a segfault is aborting the server. Error starts with glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage Browsing for that error I found [Bug 110500 - X-Server crashes - GL error: GL_OUT_OF_MEMORY in glTexSubImage ] https://bugs.freedesktop.org/show_bug.cgi?id=110500 with a similar backtrace. Very similar backtraces (but for /usr/bin/Xwayland instead of /usr/lib/xorg/modules/libglamoregl.so) are reported in [Sometimes my Ubuntu Log me out and close all applications] https://gitlab.freedesktop.org/xorg/xserver/issues/833. and [https://gitlab.freedesktop.org/xorg/xserver/issues/647] https://gitlab.freedesktop.org/xorg/xserver/issues/647 This last one seems already fixed upstream, and there is a suggestion that Xwayland 1.20.5 contains the fix. Since I see libglamoregl.so in my backtrace I am setting xserver-xorg-core as affected package. Please reassign if aprppriate. Thanks for your work in xorg. Regards, -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jan 11 2010 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Mar 5 2019 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 0 KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), LANGUAGE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration 1.193 ii libaudit1 1:2.8.5-2 ii libbsd0 0.10.0-1 ii libc6 2.29-2 ii libdbus-1-3 1.12.16-2 ii libdrm2 2.4.99-1 ii libegl1 1.1.0-1+b1 ii libegl1-mesa19.2.1-1 ii libepoxy0 1.5.3-0.1 ii libgbm1 19.2.1-1 ii libgcrypt20 1.8.5-3 ii libgl1 1.1.0-1+b1 ii libpciaccess0 0.14-1 ii libpixman-1-0 0.36.0-1 ii libselinux1 2.9-2+b2 ii libsystemd0 242-7 ii libudev1242-7 ii libunwind8 1.2.1-9 ii libxau6 1:1.0.8-1+b2 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.3-1 ii libxshmfence1 1.3-1 ii udev242-7 ii xserver-common 2:1.20.4-1 Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 19.2.1-1 ii libpam-systemd 242-7 Versions of packages xserver-xorg-core suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- no debconf information Xorg.0.log.old Description: application/trash
Bug#900550: xserver-xorg-core: X server segfaults for xfce4+nouveau after 2:1.19.6-1 -> 2:1.20.0-2 upgrade
Control: tags -1 +patch Control: affects -1 xfce4-session On Fri, Jun 01, 2018 at 12:00:37PM +0200, Michel Dänzer wrote: > On 2018-06-01 10:10 AM, Agustin Martin Domingo wrote: > > Package: xserver-xorg-core > > Version: 2:1.20.0-2 > > Severity: important > > > > Dear Maintainer, > > > > After 2:1.19.6-1 -> 2:1.20.0-2 xfce4-session+nouveau segfaults on startup > > and cannot start sesion. Trying to start it manually with startxfce4 > > fails giving > > they suggests that it may be the real cause, with a a fatal interaction > > between the "compositor" option of xfwm4 and xorg-server-1.20.0. It is also > > noted that this may be a problem not only with the nouveau driver, but also > > with radeon driver, both with xfce4. > > It would happen with anything using EXA. > > https://patchwork.freedesktop.org/patch/226573/ fixes it. Patch tested, problem gone with xfce4 composer enabled. Thanks. -- Agustin
Bug#900550: xserver-xorg-core: X server segfaults for xfce4+nouveau after 2:1.19.6-1 -> 2:1.20.0-2 upgrade
Package: xserver-xorg-core Version: 2:1.20.0-2 Severity: important Dear Maintainer, After 2:1.19.6-1 -> 2:1.20.0-2 xfce4-session+nouveau segfaults on startup and cannot start sesion. Trying to start it manually with startxfce4 fails giving (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x555e574106fd] (EE) 1: /usr/lib/xorg/Xorg (0x555e5725d000+0x1b73b9) [0x555e574143b9] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fc78ff7+0x11f50) [0x7fc78ff81f50] (EE) 3: /usr/lib/xorg/Xorg (miRenderColorToPixel+0xe) [0x555e57384a9e] (EE) 4: /usr/lib/xorg/modules/libexa.so (0x7fc78c9e+0xf12b) [0x7fc78c9ef12b] (EE) 5: /usr/lib/xorg/Xorg (0x555e5725d000+0x13a786) [0x555e57397786] (EE) 6: /usr/lib/xorg/Xorg (0x555e5725d000+0x12eaec) [0x555e5738baec] (EE) 7: /usr/lib/xorg/Xorg (0x555e5725d000+0x5b008) [0x555e572b8008] (EE) 8: /usr/lib/xorg/Xorg (0x555e5725d000+0x5f008) [0x555e572bc008] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7fc78fbd1a87] (EE) 10: /usr/lib/xorg/Xorg (_start+0x2a) [0x555e572a5d0a] (EE) (EE) Segmentation fault at address 0x8 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.2.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. No problem with icewm and probably other windows managers. I have googled a bit about this problem and found a recent message in debian-user about this very same problem, [upgrade to X 1.20.0 broken] https://lists.debian.org/debian-user/2018/05/msg01008.html Problem has been confirmed by some people in that thread and it is suggested to be triggered by the Xfce compositor https://lists.debian.org/debian-user/2018/05/msg01035.html As a matter of fact, if I disable the compositor, problem goes away. I am filing this bug report against xserver-xorg-core because in other reference about this problem in slackware, https://www.linuxquestions.org/questions/slackware-14/slackware-current-xorg-server-1-20-0-with-xf86-video-nouveau-segfaults-4175629581/ they suggests that it may be the real cause, with a a fatal interaction between the "compositor" option of xfwm4 and xorg-server-1.20.0. It is also noted that this may be a problem not only with the nouveau driver, but also with radeon driver, both with xfce4. In slackware they rebuild xfce4 with --disable-compositor as a workaround, but in that thread they point to an old xorg-server 2009 commit as dealing with this, not sure if that still applies. Note: This bug report is sent from icewm, not xfce4. Regards, -- Agustin -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jan 11 2010 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 May 24 18:23 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27) udev information: - P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME="Power Button" E: PHYS="LNXPWRBN/button/input0" E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=26651401 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3 N: input/event3 E: BACKSPACE=guess E: DEVNAME=/dev/input/event3 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: LIBINPUT_DEVICE_GROUP=19/0/1:LNXPWRBN/button E: MAJOR=13 E: MINOR=67 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=28869196 E: XKBLAYOUT=es E: XKBMODEL=pc105 E: XKBOPTIONS=lv3:ralt_switch,terminate:ctrl_alt_bksp P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 E: EV=3 E: ID_FOR_SEAT=input-acpi-PNP0C0C_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-PNP0C0C:00 E: ID_PATH_TAG=acpi-PNP0C0C_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME="Power
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Tue, Oct 04, 2016 at 11:43:07AM +0200, Agustin Martin wrote: > On Wed, Sep 07, 2016 at 12:08:15PM +0200, Agustin Martin wrote: > > On Wed, Jan 27, 2016 at 03:51:22PM +0100, Agustin Martin wrote: > > > On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote: > > > > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote: > > > > > > > > > Package: xserver-xorg-core > > > > > Version: 2:1.17.3-2 > > > > > Severity: normal > > > > > > > > > > Dear Maintainers, > > > > > > > > > > I am having a strange problem apparently starting with 2:1.17.2-3. > > > > > > > > > > I often have a display-manager controlled X session for one user and > > > > > open > > > > > another X session in a free tty for a different user with startx. > > > > > > > > > > This has been working for a long time. However, after a recent testing > > > > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > > > > > (failure happened before in a sid box, but there were more upgrades to > > > > > look when trying to locate which change might be responsible). > > > > > > > > > > When I have a display-mamager controlled X session and, without > > > > > leaving the > > > > > session, switch to a free tty, login as another user and start an X > > > > > session > > > > > with startx original X session gets killed and I am sent to DM > > > > > greeter. > > > > > > > > > Please provide the log from both X processes. > > > > > > Hi, thanks for quick reply. > > > > > > Please find them attached. > > > > Hi, > > > > Just to add some additional info. This problem is happening not only with > > the xserver-xorg-video-nouveau driver, but also if I remove it leaving the > > fbdev > > or vesa drivers. Hi, some funny info about this problem, I am using a sysvinit box and it is currently suffering from https://bugs.debian.org/844785 [systemd-shim not fully compatible with systemd 232] and similar bugs against lightdm #770885 lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out and nonfunctional #804165 lightdm: Options reboot,suspend,hibernate are all greyed out The funny thing is that as soon as this systemd-shim bug reappeared my original problem reported in this bug #812791 report become no longer present when using "sysvinit"+"buggy systemd-shim". I have booted with systemd to see what happens and my original problem reappeared, cannot switch. So, this may be related to interaction with policykit or friends, but apart from that guess I am clueless. Regards, -- Agustin
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Tue, Oct 04, 2016 at 11:43:07AM +0200, Agustin Martin wrote: > Package: xserver-xorg-core > Version: 2:1.17.3-2 > Severity: normal > > Dear Maintainers, > > I am having a strange problem apparently starting with 2:1.17.2-3. > > I often have a display-manager controlled X session for one user and open > another X session in a free tty for a different user with startx. > > This has been working for a long time. However, after a recent testing > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > (failure happened before in a sid box, but there were more upgrades to > look when trying to locate which change might be responsible). > > When I have a display-mamager controlled X session and, without leaving the > session, switch to a free tty, login as another user and start an X session > with startx original X session gets killed and I am sent to DM greeter. Hi, I could also reproduce this problem in a i5 laptop with integrated intel card, so this seems not related to a particular issue with Nvidia cards. xserver-xorg-legacy is installed and Xwrapper.config contains allowed_users=console needs_root_rights=yes Xorg.log files showing the failure are attached, both with none of fbdev+vesa+intel xorg drivers installed and with all of them (intel seems not used). Regards, Additional information follows: Versions of used packages: -- xserver-xorg: 1:7.7+16 xserver-xorg-core: 2:1.18.4-2 xserver-xorg-legacy: 2:1.18.4-2 xserver-xorg-video-fbdev: 1:0.4.4-1+b4 xserver-xorg-video-intel: 2:2.99.917+git20160706-1 xserver-xorg-video-vesa: 1:2.3.4-1+b1 (see some auto-retrieved versions at the end of the message) X server symlink status: lrwxrwxrwx 1 root root 13 Sep 25 2013 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Sep 6 15:09 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.8-1 (2016-10-19) DRM Information from dmesg: --- [2.053999] Linux agpgart interface v0.103 [ 42.962476] [drm] Initialized drm 1.1.0 20060810 [ 43.582387] [drm] Memory usable by graphics device = 2048M [ 43.582391] [drm] Replacing VGA console driver [ 43.588324] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 43.588327] [drm] Driver supports precise vblank timestamp query. [ 43.880196] fbcon: inteldrmfb (fb0) is primary device [ 44.919349] [drm] Initialized i915 1.6.0 20160425 for :00:02.0 on minor 0 [ 44.924531] i915 :00:02.0: fb0: inteldrmfb frame buffer device -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration1.152 ii libaudit1 1:2.6.7-1 ii libc6 2.24-3 ii libdbus-1-3 1.10.12-1 ii libdrm2 2.4.71-1 ii libegl1-mesa 12.0.3-1 ii libepoxy0 1.3.1-1 ii libgbm1 12.0.3-1 ii libgcrypt20 1.7.3-2 ii libgl1-mesa-glx [libgl1] 12.0.3-1 ii libpciaccess0 0.13.4-1 ii libpixman-1-0 0.34.0-1 ii libselinux1 2.5-3 ii libsystemd0 231-9 ii libudev1 231-9 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1.1 ii libxfont1 1:1.5.2-1 ii libxshmfence1 1.2-1 ii udev 231-9 ii xserver-common2:1.18.4-2 Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 12.0.3-1 ii libpam-systemd 231-9 Versions of packages xserver-xorg-core suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- Agustin [67.291] X.Org X Server 1.18.4 Release Date: 2016-07-19 [67.291] X Protocol Version 11, Revision 0 [67.291] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [67.291] Current Operating System: Linux lenovo-testing 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19) x86_64 [67.291] Kernel command line: BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/debian-testing ro quiet [67.291] Build Date: 06 September
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Wed, Sep 07, 2016 at 12:08:15PM +0200, Agustin Martin wrote: > On Wed, Jan 27, 2016 at 03:51:22PM +0100, Agustin Martin wrote: > > On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote: > > > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote: > > > > > > > Package: xserver-xorg-core > > > > Version: 2:1.17.3-2 > > > > Severity: normal > > > > > > > > Dear Maintainers, > > > > > > > > I am having a strange problem apparently starting with 2:1.17.2-3. > > > > > > > > I often have a display-manager controlled X session for one user and > > > > open > > > > another X session in a free tty for a different user with startx. > > > > > > > > This has been working for a long time. However, after a recent testing > > > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > > > > (failure happened before in a sid box, but there were more upgrades to > > > > look when trying to locate which change might be responsible). > > > > > > > > When I have a display-mamager controlled X session and, without leaving > > > > the > > > > session, switch to a free tty, login as another user and start an X > > > > session > > > > with startx original X session gets killed and I am sent to DM greeter. > > > > > > > Please provide the log from both X processes. > > > > Hi, thanks for quick reply. > > > > Please find them attached. > > Hi, > > Just to add some additional info. This problem is happening not only with > the xserver-xorg-video-nouveau driver, but also if I remove it leaving the > fbdev > or vesa drivers. Forgot to mention that this also happens without any of those (nouveau, vesa, fbdev) drivers installed, log attached Regards, -- Agustin [86.097] X.Org X Server 1.18.4 Release Date: 2016-07-19 [86.097] X Protocol Version 11, Revision 0 [86.097] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [86.097] Current Operating System: Linux mala-sid 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 (2016-08-28) x86_64 [86.097] Kernel command line: BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/debian-sid ro quiet [86.097] Build Date: 06 September 2016 01:32:44PM [86.097] xorg-server 2:1.18.4-2 (https://www.debian.org/support) [86.097] Current version of pixman: 0.33.6 [86.097]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [86.097] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [86.097] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 9 10:36:00 2016 [86.113] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [86.236] (==) No Layout section. Using the first Screen section. [86.236] (==) No screen section available. Using defaults. [86.236] (**) |-->Screen "Default Screen Section" (0) [86.236] (**) | |-->Monitor "" [86.258] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [86.258] (==) Automatically adding devices [86.258] (==) Automatically enabling devices [86.258] (==) Automatically adding GPU devices [86.258] (==) Max clients allowed: 256, resource mask: 0x1f [86.403] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [86.403]Entry deleted from font path. [86.465] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [86.466] (==) ModulePath set to "/usr/lib/xorg/modules" [86.466] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [86.488] (II) Loader magic: 0x558d0b61fdc0 [86.488] (II) Module ABI versions: [86.488]X.Org ANSI C Emulation: 0.4 [86.488]X.Org Video Driver: 20.0 [86.488]X.Org XInput driver : 22.1 [86.488]X.Org Server Extension : 9.0 [86.489] (++) using VT number 7 [86.489] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [86.490] (II) xfree86: Adding drm device (/dev/dri/card0) [86.492] (--) PCI:*(0:1:0:0) 10de:104a:1043:8460 rev 161, Mem @ 0xfd00
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Wed, Jan 27, 2016 at 03:51:22PM +0100, Agustin Martin wrote: > On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote: > > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote: > > > > > Package: xserver-xorg-core > > > Version: 2:1.17.3-2 > > > Severity: normal > > > > > > Dear Maintainers, > > > > > > I am having a strange problem apparently starting with 2:1.17.2-3. > > > > > > I often have a display-manager controlled X session for one user and open > > > another X session in a free tty for a different user with startx. > > > > > > This has been working for a long time. However, after a recent testing > > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > > > (failure happened before in a sid box, but there were more upgrades to > > > look when trying to locate which change might be responsible). > > > > > > When I have a display-mamager controlled X session and, without leaving > > > the > > > session, switch to a free tty, login as another user and start an X > > > session > > > with startx original X session gets killed and I am sent to DM greeter. > > > > > Please provide the log from both X processes. > > Hi, thanks for quick reply. > > Please find them attached. Hi, Just to add some additional info. This problem is happening not only with the xserver-xorg-video-nouveau driver, but also if I remove it leaving the fbdev or vesa drivers. This does not always happen in first switch, sometimes more switches are needed, seems some sort of race condition. Attached logs for both failures. /etc/X11/Xwrapper.config contains "needs_root_rights=yes" and xserver-xorg-legacy is installed. Versions: xserver-xorg-video-fbdev: 1:0.4.4-1+b4 xserver-xorg-video-vesa: 1:2.3.4-1+b1 Regards, -- Agustin [86.058] X.Org X Server 1.18.4 Release Date: 2016-07-19 [86.058] X Protocol Version 11, Revision 0 [86.058] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [86.058] Current Operating System: Linux mala-sid 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 (2016-08-28) x86_64 [86.058] Kernel command line: BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/debian-sid ro quiet [86.058] Build Date: 20 July 2016 05:14:41AM [86.058] xorg-server 2:1.18.4-1 (http://www.debian.org/support) [86.058] Current version of pixman: 0.33.6 [86.058]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [86.058] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [86.058] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 5 18:04:52 2016 [86.102] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [86.184] (==) No Layout section. Using the first Screen section. [86.184] (==) No screen section available. Using defaults. [86.184] (**) |-->Screen "Default Screen Section" (0) [86.184] (**) | |-->Monitor "" [86.199] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [86.199] (==) Automatically adding devices [86.199] (==) Automatically enabling devices [86.199] (==) Automatically adding GPU devices [86.199] (==) Max clients allowed: 256, resource mask: 0x1f [86.340] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [86.340]Entry deleted from font path. [86.469] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [86.469] (==) ModulePath set to "/usr/lib/xorg/modules" [86.469] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [86.493] (II) Loader magic: 0x56340226cdc0 [86.493] (II) Module ABI versions: [86.493]X.Org ANSI C Emulation: 0.4 [86.493]X.Org Video Driver: 20.0 [86.493]X.Org XInput driver : 22.1 [86.493]X.Org Server Extension : 9.0 [86.494] (++) using VT number 7 [86.494] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [86.494] (II) xfree86: Adding drm device (/dev/dri/card0) [86.497] (--) PCI:*(0:1:0:0) 10de:104a:1043:8460 rev 161, Mem @ 0xfd00/16777216, 0xf000/134217728, 0xf800/33554432, I
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote: > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote: > > > Package: xserver-xorg-core > > Version: 2:1.17.3-2 > > Severity: normal > > > > Dear Maintainers, > > > > I am having a strange problem apparently starting with 2:1.17.2-3. > > > > I often have a display-manager controlled X session for one user and open > > another X session in a free tty for a different user with startx. > > > > This has been working for a long time. However, after a recent testing > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail > > (failure happened before in a sid box, but there were more upgrades to > > look when trying to locate which change might be responsible). > > > > When I have a display-mamager controlled X session and, without leaving the > > session, switch to a free tty, login as another user and start an X session > > with startx original X session gets killed and I am sent to DM greeter. > > > Please provide the log from both X processes. Hi, thanks for quick reply. Please find them attached. DM (wdm in this case) is started at display 0, startx from tty is started at display 1 Xorg.1.log: Log for display 1, session started with startx -- :1 Xorg.0.log: Log for display 0 when user session has already been wrongly killed and DM greeter shown again. Xorg.0.log.old: Hopefully log for killed session at display 0. Did not notice before, but there is some possibly interesting info in it. - Unable to get master: Invalid argument - NOUVEAU(0): failed to set mode: Permission denied - Fatal server error: EnterVT failed for screen 0 - Error dropping master: -22(Invalid argument) ... xserver-xorg-legacy is installed for this test. Hope this helps, -- Agustin [ 1410.663] X.Org X Server 1.17.3 Release Date: 2015-10-26 [ 1410.663] X Protocol Version 11, Revision 0 [ 1410.663] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 1410.663] Current Operating System: Linux uguindo 4.3.0-1-amd64 #1 SMP Debian 4.3.3-7 (2016-01-19) x86_64 [ 1410.663] Kernel command line: BOOT_IMAGE=/vmlinuz-4.3.0-1-amd64 root=/dev/mapper/debian-testing ro quiet [ 1410.663] Build Date: 27 October 2015 11:41:02PM [ 1410.663] xorg-server 2:1.17.3-2 (http://www.debian.org/support) [ 1410.663] Current version of pixman: 0.33.6 [ 1410.663]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1410.663] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1410.663] (==) Log file: "/var/log/Xorg.1.log", Time: Wed Jan 27 15:28:33 2016 [ 1410.663] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1410.664] (==) No Layout section. Using the first Screen section. [ 1410.664] (==) No screen section available. Using defaults. [ 1410.664] (**) |-->Screen "Default Screen Section" (0) [ 1410.664] (**) | |-->Monitor "" [ 1410.664] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 1410.664] (==) Automatically adding devices [ 1410.664] (==) Automatically enabling devices [ 1410.664] (==) Automatically adding GPU devices [ 1410.664] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 1410.664]Entry deleted from font path. [ 1410.664] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 1410.664] (==) ModulePath set to "/usr/lib/xorg/modules" [ 1410.664] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 1410.664] (II) Loader magic: 0x55c456ea7de0 [ 1410.664] (II) Module ABI versions: [ 1410.664]X.Org ANSI C Emulation: 0.4 [ 1410.664]X.Org Video Driver: 19.0 [ 1410.664]X.Org XInput driver : 21.0 [ 1410.664]X.Org Server Extension : 9.0 [ 1410.667] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_34 [ 1410.667] (II) xfree86: Adding drm device (/dev/dri/card0) [ 1410.668] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0 [ 1410.669] (--) PCI:*(0:1:0:0) 10de:104a:1043:8460 rev 161, Mem @ 0xfd00/16777216, 0xf000/134217728, 0xf800/33554432, I/O @ 0xe000/128, BIOS @ 0x/524288 [ 1410.669] (II) LoadModul
Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty
Package: xserver-xorg-core Version: 2:1.17.3-2 Severity: normal Dear Maintainers, I am having a strange problem apparently starting with 2:1.17.2-3. I often have a display-manager controlled X session for one user and open another X session in a free tty for a different user with startx. This has been working for a long time. However, after a recent testing upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail (failure happened before in a sid box, but there were more upgrades to look when trying to locate which change might be responsible). When I have a display-mamager controlled X session and, without leaving the session, switch to a free tty, login as another user and start an X session with startx original X session gets killed and I am sent to DM greeter. With 2:1.17.2-3 I was not even allowed to re-open a DM controlled session even if I close first the startx created X session. Seems that this is no longer happening and I can now re-enter but after some session switch original new DM controlled session gets killed. Tried with xdm, wdm and lightdm as DM and xfce4, icewm and openbox as sessions opened from the DM. With xfce4 session killing is faster, but it is killed anyway with the other. Tried with xserver-xorg-legacy and /etc/X11/Xwrapper.config containing needs_root_rights=yes allowed_users=console No luck, problem persists. No problem if I create different X sessions with startx from different ttys. If I downgrade xserver-xorg stuff to versions in wheezy/stable, problem seems to disappear. Also, note that I am using sysvinit in this box. No apparent errors in usual log files. auth.log just shows it as a normal logout. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jun 4 2009 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Oct 28 00:43 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160114 (Debian 5.3.1-6) ) #1 SMP Debian 4.3.3-7 (2016-01-19) DRM Information from dmesg: --- [0.00] AGP: No AGP bridge found [0.00] AGP: Checking aperture... [0.00] AGP: No AGP bridge found [0.00] AGP: Node 0: aperture [bus addr 0x-0x01ff] (32MB) [0.00] AGP: Your BIOS doesn't leave an aperture memory hole [0.00] AGP: Please enable the IOMMU option in the BIOS setup [0.00] AGP: This costs you 64MB of RAM [0.00] AGP: Mapping aperture over RAM [mem 0xd000-0xd3ff] (65536KB) [1.155897] PCI-DMA: Disabling AGP. [1.155979] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture [1.182742] Linux agpgart interface v0.103 [ 23.916063] [drm] Initialized drm 1.1.0 20060810 [ 24.620545] nouveau :01:00.0: DRM: VRAM: 2048 MiB [ 24.620549] nouveau :01:00.0: DRM: GART: 1048576 MiB [ 24.620555] nouveau :01:00.0: DRM: TMDS table version 2.0 [ 24.620559] nouveau :01:00.0: DRM: DCB version 4.0 [ 24.620564] nouveau :01:00.0: DRM: DCB outp 00: 02000300 [ 24.620570] nouveau :01:00.0: DRM: DCB outp 01: 01000302 00020030 [ 24.620574] nouveau :01:00.0: DRM: DCB outp 02: 02011362 00020010 [ 24.620578] nouveau :01:00.0: DRM: DCB outp 03: 04022310 [ 24.620582] nouveau :01:00.0: DRM: DCB conn 00: 1030 [ 24.620585] nouveau :01:00.0: DRM: DCB conn 01: 2161 [ 24.620589] nouveau :01:00.0: DRM: DCB conn 02: 0200 [ 24.622677] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 24.622680] [drm] Driver supports precise vblank timestamp query. [ 24.677537] nouveau :01:00.0: DRM: MM: using COPY0 for buffer copies [ 24.899601] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x6, bo 8800da058400 [ 24.992886] [drm] Initialized nouveau 1.3.0 20120801 for :01:00.0 on minor 0 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (200, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration1.134 ii libaudit1 1:2.4.5-1 ii libc6 2.21-6 ii libdbus-1-3 1.10.6-1 ii libdrm2 2.4.66-2 ii libegl1-mesa 11.1.1-2 ii libepoxy0
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
2015-05-10 12:48 GMT+02:00 Agustin Martin agmar...@debian.org: 2015-05-05 19:43 GMT+02:00 Martin-Éric Racine martin-eric.rac...@iki.fi: 2015-05-05 19:38 GMT+03:00 Agustin Martin agmar...@debian.org: On Mon, May 04, 2015 at 12:49:52PM +0200, Agustin Martin wrote: Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. [...] http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=b7387454bda64a16350fabee4d81bec3b8de8fa2 applied, but I then noticed that it is already in jessie's kernel. Martin-Éric, has jessie's kernel fixed the problem in your box? Agustin, There's two NVDIA boxes involved (IIRC, I filed separate bugs reports). Neither box works with the Nouveau X.org driver in Jessie. In both cases, I've had to remove xserver-xorg-video-nouveau and let Xserver use the generic modeline driver. Hi, Just to add that this freeze no longer appears with jessie's kernel if I pass nouveau.noaccel=1 as a kernel boot parameter (as suggested in #776838) or if I put options nouveau noaccel=1 in my /etc/modprobe.d/local-video.conf. No intense graphics use is done in this box, so I did not notice a performance loss. Hi all, I have been searching the web to try finding more info about this problem. Seems that there are some reports about similar problems in different forums (added some info below for those curious) and that it appeared somewhere between kernel 3.6 and 3.7. I have tried unsuccessfully a couple of the proposed patches, no luck. The good news are that I have also tried sid kernel removing the nouveau noaccel=1 from boot cmdline, and I am no longer having this problem for a couple of days with that sid kernel (cross fingers), I have even re-enabled use hardware acceleration if possible in firefox and things are still working well. Summarizing, in this jessie box: linux-image-3.2.0-4-amd64 (3.2.65-1+deb7u2): No problem found linux-image-3.16.0-4-amd64 (3.16.7-ckt11-1): Problem is present linux-image-4.0.0-2-amd64 (4.0.7-1): No problem found, did not try with testing 4.0.5-1 So, at least in my box, problem seems not to be a problem with xserver-xorg-video-nouveau but with the nouveau module in kernel. For those curious, other possibly related references I found in my web searches * https://bugzilla.redhat.com/show_bug.cgi?id=901816 Bug 901816 - artifacts/freezeups in graphical mode with nouveau and GeForce 6150SE * https://bugs.freedesktop.org/show_bug.cgi?id=61321 Bug 61321 - [regression][NV4c] System hang while loading gdm on 3.7 kernel (works on 3.6) * https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bug 87361 - [NV4C] GPU lock-up after booting to desktop in Fedora 20 21 (Nvidia Geforce 6100 IGP) * https://bugzilla.redhat.com/show_bug.cgi?id=679619 Bug 679619 - Nouveau freeze when try to start X. nvidia Geforce Go 6150 * https://forums.gentoo.org/viewtopic-t-952224-start-0.html Kernel 3.7.9 crashes (nouveau?) * https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1181902 Nouveau driver glitch on Ubuntu 13.04 will cause system to freeze under certain conditions, Bug #1181902 * http://www.linuxquestions.org/questions/slackware-14/firefox-nouveau-on-fresh-current-install-freezes-system-4175455844/ Firefox + nouveau on fresh -current install freezes system * https://bugzilla.kernel.org/show_bug.cgi?id=50091 Bug 50091 - [BISECTED]GeForce 6150SE: system hangs on X-server start with garbled screen * http://ubuntuforums.org/showthread.php?t=2181430 Nouveau crash and freeze on install of 13.10 * https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1217585 #1217585, System hangs after some time with nouveau and GT240 * https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bug 87361 - [NV4C] GPU lock-up after booting to desktop in Fedora 20 21 (Nvidia Geforce 6100 IGP) * https://bbs.archlinux.org/viewtopic.php?id=156690 Upgrade to linux-3.7.3: freeze on some actions in X (nouveau driver) * https://bugs.freedesktop.org/show_bug.cgi?id=89842 Bug 89842 - Nvidia nouveau drivers hangs all gnome when opening the new legacy tray (and many other situations) * https://bugs.freedesktop.org/show_bug.cgi?id=90276 Bug 90276 - [NVE4] read fault error, bisected * https://bugs.freedesktop.org/show_bug.cgi?id=90453 Bug 90453 - [NVE4] Desktop freezes
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
2015-05-05 19:43 GMT+02:00 Martin-Éric Racine martin-eric.rac...@iki.fi: 2015-05-05 19:38 GMT+03:00 Agustin Martin agmar...@debian.org: On Mon, May 04, 2015 at 12:49:52PM +0200, Agustin Martin wrote: Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. [...] http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=b7387454bda64a16350fabee4d81bec3b8de8fa2 applied, but I then noticed that it is already in jessie's kernel. drm/nv4c/mc: disable msi commit 4761703bd04bbdf56396d264903cc5a1fdcb3c01 upstream. Martin-Éric, has jessie's kernel fixed the problem in your box? Agustin, There's two NVDIA boxes involved (IIRC, I filed separate bugs reports). Neither box works with the Nouveau X.org driver in Jessie. In both cases, I've had to remove xserver-xorg-video-nouveau and let Xserver use the generic modeline driver. Hi, Just to add that this freeze no longer appears with jessie's kernel if I pass nouveau.noaccel=1 as a kernel boot parameter (as suggested in #776838) or if I put options nouveau noaccel=1 in my /etc/modprobe.d/local-video.conf. No intense graphics use is done in this box, so I did not notice a performance loss. -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cahmxk7jnno0us76jxoymvo7mgbgg5boaruwwsyy8+w4_lv+...@mail.gmail.com
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
On Mon, May 04, 2015 at 12:49:52PM +0200, Agustin Martin wrote: Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. Noticed that something similar has been reported in http://bugs.debian.org/758460 for a GeForce 6150LE. Not merging both bug reports in case they are different issues for different chip variants, but cc'ing. Following advice there I tried with kernel boot parameter nouveau.config=NvMSI=0 in the command line and with options nouveau NvMSI=0 in a /etc/modprobe.d/local-video.conf file (also built a new initramfs in case this is needed), problem is still here, no luck. Hi, I was thinking about building a kernel with patch mentioned in http://bugs.debian.org/758460 http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=b7387454bda64a16350fabee4d81bec3b8de8fa2 applied, but I then noticed that it is already in jessie's kernel. Searching kernel changelogs, I found this in https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.4 commit 715f7c8214c7822833af757109022006c3f01d6a Author: Ilia Mirkin imir...@alum.mit.edu Date: Tue Dec 16 13:55:38 2014 -0500 drm/nv4c/mc: disable msi commit 4761703bd04bbdf56396d264903cc5a1fdcb3c01 upstream. Several users have, over time, reported issues with MSI on these IGPs. They're old, rarely available, and MSI doesn't provide such huge advantages on them. Just disable. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74492 Fixes: fa8c9ac72fe (drm/nv4c/mc: nv4x igp's have a different msi rearm register) Signed-off-by: Ilia Mirkin imir...@alum.mit.edu Signed-off-by: Ben Skeggs bske...@redhat.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org also in https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.30 (LTS?) Now it is clear why setting NvMSI=0 did not make any difference in the box with the GeForce 6150SE where I hit the bug (Did not try with noaccel). Martin-Éric, has jessie's kernel fixed the problem in your box? -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150505163815.ga5...@agmartin.aq.upm.es
Bug#758460: xserver-xorg-video-nouveau: Crash and freeze with GeForce 6150SE.
Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Followup-For: Bug #783805 Dear Maintainer, 1) I've just switched to Jessie and now my system is very unstable (barely usable). That was not the case at all with Wheezy. I guess it's related to the nouveau driver, but maybe some cryptic kernel issue are involved too ? Just for the record, I gave a try to Jessie in the beginning of 2013 (so testing at that time), but went back to Wheezy, for the same reason : way too frequent crashes. 2) ctrl+alt+F1 doesn't work to take control again. 3) It's difficult to accurately trigger (at user level) which typical action entails a crash, it's somewhat fuzzy. 4) I skimmed through the bug lists but I can't figure out whether or not the same *exact* bug has always been reported. Forgive me, if so. And it's my first bug report. 5) I used the reportbug tool, but why some critical section doesn't figure and reportbug removes it, like this one (extract of dmesg) : dmesg:[ 68.627296] nouveau E[PBUS][:00:0d.0] MMIO write of x00820001 FAULT at 0x00b000 Hi, Just to confirm a similar problem in a GeForce 6150SE graphics engine, 00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) Similar messages in syslog, [ 711.849697] nouveau E[PBUS][:00:0d.0] MMIO write of 0x00870001 FAULT at 0x00b010 and random freeze. Last seen thing is some sort of zig-zag random pattern apparently with colors used at that time. Nothing but hard reboot helps once the system is frozen, not even Magic SysRq. No relevant info seems to appear in syslog. An important info is that this does not happen if I reboot with old 3.2.04-amd64 (3.2.65-1+deb7u2) wheezy kernel. So this seems to be a problem with the nouveau kernel module. Noticed that something similar has been reported in http://bugs.debian.org/758460 for a GeForce 6150LE. Not merging both bug reports in case they are different issues for different chip variants, but cc'ing. Following advice there I tried with kernel boot parameter nouveau.config=NvMSI=0 in the command line and with options nouveau NvMSI=0 in a /etc/modprobe.d/local-video.conf file (also built a new initramfs in case this is needed), problem is still here, no luck. I am still blindly trying to find a reproducibility pattern, Seems that when mozilla is used and closed, if I try to open it again inmediately failure often happens. Just have to do one of this quick iceweasel start and stop cycles to hit the problem with a very high probability (funny, this seems not to happen with chromium). I do not have daily access to the affected box (and it is not one of my boxes), but let me know if I can try to provide more info. By the way, gdm3 is not used there, just lightdm, and init is sysvinit. Regards, X server symlink status: lrwxrwxrwx 1 root root 13 Mar 11 2014 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 01:35 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:0d.0 VGA compatible controller [0300]: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150504104952.ga27...@agmartin.aq.upm.es
Bug#759005: xdm: Missing xdm.service, can't use with systemd
On Sat, Aug 23, 2014 at 09:30:24PM +0200, Sven Joachim wrote: On 2014-08-23 19:52 +0200, Kan-Ru Chen (陳侃如) wrote: Package: xdm Version: 1:1.1.11-1 Severity: important The xdm upstream ships a xdm.service file however it is not include in the xdm debian package. It would probably make sense to ship it, but care must be taken not to enable the service unless xdm is the default display manager. Hi, Please have a look at the info I provided for wdm in #761642. Main reference is https://titanpad.com/s-gsprintchangelog section = default display manager selection = Since xdm is not as complex as gdm, I think that lightdm may also be used as a reference. For implementation details, see https://bugs.debian.org/733220 where, among other things, it is proposed to use something like ExecStartPre=/bin/sh -c '[ ! -f /etc/X11/default-display-manager -o $(cat /etc/X11/default-display-manager 2/dev/null) = /usr/sbin/lightdm ]' Note that other things mentioned there are needed. While we are with errors just warn you about slim's bug https://bugs.debian.org/748668 which I'd expect to also affect xdm. slim.service enables the service unconditionally regardless of being default display manager or not. If xdm is the default slim will hijack that status. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140917102915.ga6...@agmartin.aq.upm.es
Bug#626331: xserver-xorg-core: Crashes server when loading background color from 'icewmbg' and 'pcmanfm --desktop'
On Mon, May 23, 2011 at 12:31:17PM +0200, Cyril Brulebois wrote:
severity 626331 important
thanks
Hi all,
Agustin Martin agmar...@debian.org (20/05/2011):
Haven't posted it to xorg-devel yet.
diff -ru xorg-server-1.10.1/dix/window.c
xorg-server-1.10.1-new/dix/window.c
--- xorg-server-1.10.1/dix/window.c 2011-02-25 04:27:25.0
+0100
+++ xorg-server-1.10.1-new/dix/window.c 2011-05-15 15:15:03.912919996
+0200
@@ -474,6 +474,7 @@
pWin-background.pixel = pScreen-whitePixel;
backFlag |= CWBackPixmap;
} else {
+ pWin-backgroundState = BackgroundPixel;
if (whiteRoot)
pWin-background.pixel = pScreen-whitePixel;
else
@@ -972,6 +973,7 @@
else if (party_like_its_1989)
MakeRootTile(pWin);
else {
+ pWin-backgroundState = BackgroundPixel;
if (whiteRoot)
pWin-background.pixel = pScreen-whitePixel;
else
done now:
http://lists.x.org/archives/xorg-devel/2011-May/022281.html
I suggested it for the 1.10 stable branch:
http://lists.x.org/archives/xorg-devel/2011-May/022455.html
Hopefully will be in the next upload.
Hi, Cyril
Looking at 2:1.10.2.902-1 changelog.
xorg-server (2:1.10.2.902-1) unstable; urgency=low
* New upstream release (1.10.3 rc2):
- DIX: Set backgroundState correctly for root window (Closes: #632134).
* Drop 20-workaround-36986.diff, fixed upstream.
* Bump Standards-Version to 3.9.2 (no changes).
This should also fix merged bug reports #626331, #626655, #626774. At
least I can no longer find this problem with icewm-session and icewmbg.
Not yet closing these bug reports in case some of the other submiters still
find problems,
Thanks for fixing this.
Regards,
--
Agustin
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110713104750.ga3...@agmartin.aq.upm.es
Bug#626774: xserver-xorg-core: Crashes server when loading background color from 'icewmbg' and 'pcmanfm --desktop'
On Tue, May 17, 2011 at 07:18:44PM +0200, Marko Macek wrote:
On 05/17/2011 03:23 PM, Agustin Martin wrote:
For the records, it crashes the X server, leaving a message in Xorg log,
[ 855.821]
Backtrace:
[ 855.821] 0: /usr/bin/X (xorg_backtrace+0x37) [0x80ed307]
[ 855.821] 1: /usr/bin/X (0x8048000+0x6356a) [0x80ab56a]
[ 855.821] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb77ba40c]
[ 855.822] 3: /usr/bin/X (0x8048000+0xbf6d2) [0x81076d2]
[ 855.822] 4: /usr/bin/X (ChangeWindowAttributes+0xcdc) [0x80a06bc]
[ 855.822] 5: /usr/bin/X (0x8048000+0x26f7e) [0x806ef7e]
[ 855.822] 6: /usr/bin/X (0x8048000+0x2d527) [0x8075527]
[ 855.822] 7: /usr/bin/X (0x8048000+0x205ac) [0x80685ac]
[ 855.822] 8: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6)
[0xb74b6e46]
[ 855.822] 9: /usr/bin/X (0x8048000+0x208c1) [0x80688c1]
[ 855.823] Segmentation fault at address 0x10
[ 855.823]
Fatal server error:
[ 855.823] Caught signal 11 (Segmentation fault). Server aborting
[ 855.823]
But note that this is not the original problem in this bug report.
This one rather seems a problem either in icewm or in xserver-xorg-core. I
have some other things to do now, but hope to have time to go to #626331 and
clone a specific bug for the icewm part. Since I am not sure if xorg or icewm
is to blame, I will reassign to both simultaneously, so both teams can look
at the problem
I posted this patch for review at:
https://bugzilla.redhat.com/show_bug.cgi?id=684556 (probably wrong bug)
Haven't posted it to xorg-devel yet.
diff -ru xorg-server-1.10.1/dix/window.c xorg-server-1.10.1-new/dix/window.c
--- xorg-server-1.10.1/dix/window.c 2011-02-25 04:27:25.0 +0100
+++ xorg-server-1.10.1-new/dix/window.c 2011-05-15 15:15:03.912919996
+0200
@@ -474,6 +474,7 @@
pWin-background.pixel = pScreen-whitePixel;
backFlag |= CWBackPixmap;
} else {
+ pWin-backgroundState = BackgroundPixel;
if (whiteRoot)
pWin-background.pixel = pScreen-whitePixel;
else
@@ -972,6 +973,7 @@
else if (party_like_its_1989)
MakeRootTile(pWin);
else {
+ pWin-backgroundState = BackgroundPixel;
if (whiteRoot)
pWin-background.pixel = pScreen-whitePixel;
else
Hi, Marko,
Noticed that you also posted the proposed fix to icewmbg related bug report,
http://sourceforge.net/tracker/?func=detailatid=100031aid=3289566group_id=31
I am sending a copy of your reply to
http://bugs.debian.org/626774 [crash on loading background image]
which may be related to the same problem (ancient xv sources seems to use
XSetWindowBackgroundPixmap), and to
http://bugs.debian.org/626331 [gnome-settings-daemon doesn't allow to log
into IceWM, LXDE.]
and cc'ing submitters in case they want to add something.
By the way, Just noticed a mail from Sergio Cipolla to #626331 reporting
that for both 'icewmbg' and 'pcmanfm --desktop' seems that using a
background image instead of a background colour also prevents the X
session from crashing.
Regards,
--
Agustin
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110520163453.ga3...@agmartin.aq.upm.es
Bug#612681: x11-common: treat empty session names silently as default session
On Mon, May 16, 2011 at 10:21:14PM +0200, Marko Macek wrote: On 05/16/2011 03:51 PM, Agustin Martin wrote: These are the .xsession-error messages for the failing icewm-session invocation from wdm (lines with AMD-WARNING are the extra info I requested) Xsession: X session started for testuser at Mon May 16 15:26:28 CEST 2011 Xsession: AMD-WARNING: Running /etc/X11/wdm/Xsession with arguments icewm-session Xsession: AMD-WARNING: Passing session as argument icewm-session /home/testuser/.Xresources:1:24: warning: missing terminating ' character /home/testuser/.Xresources:13:28: warning: missing terminating ' character Xsession: AMD-WARNING: starting /usr/bin/ssh-agent /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session icewm-session icewm-session: using /home/testuser/.icewm for private configuration files IceWM: using /home/testuser/.icewm for private configuration files icewmtray: using /home/testuser/.icewm for private configuration files icewmbg: using /home/testuser/.icewm for private configuration files XIO: fatal IO error 104 (Connection reset by peer) on X server :0 after 205 requests (205 known processed) with 2 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 after 110 requests (105 known processed) with 0 events remaining. XIO: fatal IO error 104 (Connection reset by peer) on X server :0 after 122 requests (122 known processed) with 0 events remaining. Invalid MIT-MAGIC-COOKIE-1 keyicewmbg: Can't open display: :0. X must be running and $DISPLAY set. Does the X server crash here? Any messages in Xorg log? I found a bug in X in Fedora that fails like this, might be the same. In my case seems that icewmbg is the one to blame, but still have to check before cloning #626331 and reassigning. Possible upstream bug report: http://sourceforge.net/tracker/?func=detailatid=100031aid=3289566group_id=31 Possible Ubuntu launchpad bug report: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/757610 If I have time today, I will try to reproduce the problem once again, but now looking more carefully at Xorg log. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110517111308.ga20...@agmartin.aq.upm.es
Bug#612681: x11-common: treat empty session names silently as default session
On Tue, May 17, 2011 at 01:13:09PM +0200, Agustin Martin wrote: On Mon, May 16, 2011 at 10:21:14PM +0200, Marko Macek wrote: On 05/16/2011 03:51 PM, Agustin Martin wrote: These are the .xsession-error messages for the failing icewm-session invocation from wdm (lines with AMD-WARNING are the extra info I requested) Xsession: X session started for testuser at Mon May 16 15:26:28 CEST 2011 Xsession: AMD-WARNING: Running /etc/X11/wdm/Xsession with arguments icewm-session Xsession: AMD-WARNING: Passing session as argument icewm-session /home/testuser/.Xresources:1:24: warning: missing terminating ' character /home/testuser/.Xresources:13:28: warning: missing terminating ' character Xsession: AMD-WARNING: starting /usr/bin/ssh-agent /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session icewm-session icewm-session: using /home/testuser/.icewm for private configuration files IceWM: using /home/testuser/.icewm for private configuration files icewmtray: using /home/testuser/.icewm for private configuration files icewmbg: using /home/testuser/.icewm for private configuration files XIO: fatal IO error 104 (Connection reset by peer) on X server :0 after 205 requests (205 known processed) with 2 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 after 110 requests (105 known processed) with 0 events remaining. XIO: fatal IO error 104 (Connection reset by peer) on X server :0 after 122 requests (122 known processed) with 0 events remaining. Invalid MIT-MAGIC-COOKIE-1 keyicewmbg: Can't open display: :0. X must be running and $DISPLAY set. Does the X server crash here? Any messages in Xorg log? I found a bug in X in Fedora that fails like this, might be the same. If I have time today, I will try to reproduce the problem once again, but now looking more carefully at Xorg log. For the records, it crashes the X server, leaving a message in Xorg log, [ 855.821] Backtrace: [ 855.821] 0: /usr/bin/X (xorg_backtrace+0x37) [0x80ed307] [ 855.821] 1: /usr/bin/X (0x8048000+0x6356a) [0x80ab56a] [ 855.821] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb77ba40c] [ 855.822] 3: /usr/bin/X (0x8048000+0xbf6d2) [0x81076d2] [ 855.822] 4: /usr/bin/X (ChangeWindowAttributes+0xcdc) [0x80a06bc] [ 855.822] 5: /usr/bin/X (0x8048000+0x26f7e) [0x806ef7e] [ 855.822] 6: /usr/bin/X (0x8048000+0x2d527) [0x8075527] [ 855.822] 7: /usr/bin/X (0x8048000+0x205ac) [0x80685ac] [ 855.822] 8: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb74b6e46] [ 855.822] 9: /usr/bin/X (0x8048000+0x208c1) [0x80688c1] [ 855.823] Segmentation fault at address 0x10 [ 855.823] Fatal server error: [ 855.823] Caught signal 11 (Segmentation fault). Server aborting [ 855.823] But note that this is not the original problem in this bug report. This one rather seems a problem either in icewm or in xserver-xorg-core. I have some other things to do now, but hope to have time to go to #626331 and clone a specific bug for the icewm part. Since I am not sure if xorg or icewm is to blame, I will reassign to both simultaneously, so both teams can look at the problem Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110517132342.ga8...@agmartin.aq.upm.es
Re: Bug#626331: gnome-settings-daemon: Update
On Mon, May 16, 2011 at 06:02:21PM -0300, S??rgio Cipolla wrote:
Package: gnome-settings-daemon
Version: 2.30.2-3
Followup-For: Bug #626331
Simply putting it, running 'pcmanfm --desktop' or 'icewmbg' crashes the
session.
I haven't tried with feh because I don't have it installed here.
It's valid to remember that this issue happens only with sessions ruled by
display managers (at least wdm, slim and gdm3 with gnome-settings-daemon).
Hi, Sergio and (cc'ed) Debian X maintainers.
That is right. Since I use 'icewmbg' only to set a solid color as
background, I have put a dirty alternative personal 'icewmbg' at
/usr/local/bin,
# --- 8 --- /usr/local/bin/icewmbg -
#!/bin/sh
ICEWM_PREFERENCES=${HOME}/.icewm/preferences
echo Warning: Running alternative /usr/local/bin/icewmbg
if [ -r $ICEWM_PREFERENCES ]; then
COLOR=$(grep ^DesktopBackgroundColor= $ICEWM_PREFERENCES)
COLOR=${COLOR#DesktopBackgroundColor=}
COLOR=$(eval echo $COLOR)
fi
if [ -n $COLOR ]; then
xsetroot -solid $COLOR
fi
# --- 8
and with it, problem seems to disappear.
This seems to have been reported upstream for icewm and also to Ubuntu
launchpad.
Possible upstream bug report:
http://sourceforge.net/tracker/?func=detailatid=100031aid=3289566group_id=31
Possible Ubuntu launchpad bug report:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/757610
I do not think gnome-settings-daemon is causing this bug report, just
triggering it, because it calls either 'pcmanfm --desktop' or 'icewmbg'.
I am more inclined to reassign this bug report to 'xserver-xorg-core', since
is the common link between 'pcmanfm --desktop' and 'icewmbg' that has been
upgraded just prior to the problem.
Also, this bug report may have the same origin as
http://bugs.debian.org/626774 (crash on loading background image)
because of the look of both Xorg errors (see below for mine).
I am cc'ing Debian X maintainers to know what they think.
More aditional information from my side:
These are the .xsession-error messages for the failing icewm-session
invocation from wdm (lines with AMD-WARNING are extra info I requested).
Related info for failed login in IceWM from gnome is given by Sergio Cipolla
in message http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626331#5
---
Xsession: X session started for testuser at Mon May 16 15:26:28 CEST 2011
Xsession: AMD-WARNING: Running /etc/X11/wdm/Xsession with arguments
icewm-session
Xsession: AMD-WARNING: Passing session as argument icewm-session
/home/testuser/.Xresources:1:24: warning: missing terminating ' character
/home/testuser/.Xresources:13:28: warning: missing terminating ' character
Xsession: AMD-WARNING: starting /usr/bin/ssh-agent
/usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session
icewm-session
icewm-session: using /home/testuser/.icewm for private configuration files
IceWM: using /home/testuser/.icewm for private configuration files
icewmtray: using /home/testuser/.icewm for private configuration files
icewmbg: using /home/testuser/.icewm for private configuration files
XIO: fatal IO error 104 (Connection reset by peer) on X server :0
after 205 requests (205 known processed) with 2 events remaining.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0
after 110 requests (105 known processed) with 0 events remaining.
XIO: fatal IO error 104 (Connection reset by peer) on X server :0
after 122 requests (122 known processed) with 0 events remaining.
Invalid MIT-MAGIC-COOKIE-1 keyicewmbg: Can't open display: :0. X must be
running and $DISPLAY set.
---
and details about the Xorg failure in Xorg log file (same as I gave in
unrelated #612681). Note that this looks not very different from that reported
in #626774 (crash on loading background image),
[ 855.821]
Backtrace:
[ 855.821] 0: /usr/bin/X (xorg_backtrace+0x37) [0x80ed307]
[ 855.821] 1: /usr/bin/X (0x8048000+0x6356a) [0x80ab56a]
[ 855.821] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb77ba40c]
[ 855.822] 3: /usr/bin/X (0x8048000+0xbf6d2) [0x81076d2]
[ 855.822] 4: /usr/bin/X (ChangeWindowAttributes+0xcdc) [0x80a06bc]
[ 855.822] 5: /usr/bin/X (0x8048000+0x26f7e) [0x806ef7e]
[ 855.822] 6: /usr/bin/X (0x8048000+0x2d527) [0x8075527]
[ 855.822] 7: /usr/bin/X (0x8048000+0x205ac) [0x80685ac]
[ 855.822] 8: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6)
[0xb74b6e46]
[ 855.822] 9: /usr/bin/X (0x8048000+0x208c1) [0x80688c1]
[ 855.823] Segmentation fault at address 0x10
[ 855.823]
Fatal server error:
[ 855.823] Caught signal 11 (Segmentation fault). Server aborting
[ 855.823]
with
processor: AMD Athlon XP 2800+
VGA controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01)
using radeon server.
--
Agustin
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Bug#612681: x11-common: treat empty session names silently as default session
On Wed, Feb 09, 2011 at 11:30:47PM +0100, Malte S. Stretz wrote: Package: x11-common Version: 1:7.5+6ubuntu3 Severity: wishlist Tags: patch When I upgraded to KDE 4.6.0 recently, some weird bug in kdm (I guess, haven't had the time to research further) started Xsession with an empty first argument. This resulted in the message 'Xsession: unable to launch X session --- not found; falling back to default session.' My suggestion is to interpret an empty first argument (which will of course never work as a session manager) the same as no arguments and just silently fall back to the default session. The rationale is that the user who is confronted with such a behaviour can't really do anything about it. The original bug was reported on launchpad at https://launchpad.net/bugs/710144 but I forwarded it here since this is an unmodified file from Debian. For the records, I am having the same problem with slim and wdm, only in sid (at least, until today's testing upgrade, which I still did not test) For both, selecting an explicitly available session temporarily helps, but I'd prefer something like in your proposed patches. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110516113701.ga18...@agmartin.aq.upm.es
Bug#612681: x11-common: treat empty session names silently as default session
On Mon, May 16, 2011 at 01:37:01PM +0200, Agustin Martin wrote: On Wed, Feb 09, 2011 at 11:30:47PM +0100, Malte S. Stretz wrote: Package: x11-common Version: 1:7.5+6ubuntu3 Severity: wishlist Tags: patch When I upgraded to KDE 4.6.0 recently, some weird bug in kdm (I guess, haven't had the time to research further) started Xsession with an empty first argument. This resulted in the message 'Xsession: unable to launch X session --- not found; falling back to default session.' My suggestion is to interpret an empty first argument (which will of course never work as a session manager) the same as no arguments and just silently fall back to the default session. The rationale is that the user who is confronted with such a behaviour can't really do anything about it. The original bug was reported on launchpad at https://launchpad.net/bugs/710144 but I forwarded it here since this is an unmodified file from Debian. For the records, I am having the same problem with slim and wdm, only in sid (at least, until today's testing upgrade, which I still did not test) For both, selecting an explicitly available session temporarily helps, but I'd prefer something like in your proposed patches. Trying with my just upgraded testing and my problem started to appear. I added some lines to get debugging info displayed, and now I think mine is not the same problem as yours. While I indeed saw the message you mention when using slim (and thus, I think something like your patch should be included), seems that my real problem is that icewm-session is behaving badly. In this box, after looking at the extra info, when using default, seems that correct selection is done (icewm-session in my case). However, is that specific selection which fails, even if I explicitly select it. Selecting plain icewm does work. These are the .xsession-error messages for the failing icewm-session invocation from wdm (lines with AMD-WARNING are the extra info I requested) Xsession: X session started for testuser at Mon May 16 15:26:28 CEST 2011 Xsession: AMD-WARNING: Running /etc/X11/wdm/Xsession with arguments icewm-session Xsession: AMD-WARNING: Passing session as argument icewm-session /home/testuser/.Xresources:1:24: warning: missing terminating ' character /home/testuser/.Xresources:13:28: warning: missing terminating ' character Xsession: AMD-WARNING: starting /usr/bin/ssh-agent /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session icewm-session icewm-session: using /home/testuser/.icewm for private configuration files IceWM: using /home/testuser/.icewm for private configuration files icewmtray: using /home/testuser/.icewm for private configuration files icewmbg: using /home/testuser/.icewm for private configuration files XIO: fatal IO error 104 (Connection reset by peer) on X server :0 after 205 requests (205 known processed) with 2 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 after 110 requests (105 known processed) with 0 events remaining. XIO: fatal IO error 104 (Connection reset by peer) on X server :0 after 122 requests (122 known processed) with 0 events remaining. Invalid MIT-MAGIC-COOKIE-1 keyicewmbg: Can't open display: :0. X must be running and $DISPLAY set. and these are for the sucessful icewm start from wdm. Xsession: X session started for testuser at Mon May 16 15:26:45 CEST 2011 Xsession: AMD-WARNING: Running /etc/X11/wdm/Xsession with arguments icewm Xsession: AMD-WARNING: Passing session as argument icewm /home/testuser/.Xresources:1:24: warning: missing terminating ' character /home/testuser/.Xresources:13:28: warning: missing terminating ' character Xsession: AMD-WARNING: starting /usr/bin/ssh-agent /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session icewm IceWM: using /home/testuser/.icewm for private configuration files IceWM: MappingNotify Will look a bit more at this in case I can get some info and file a bug report with it against icewm. This seems completely unrelated to your original bug report. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110516135100.ga6...@agmartin.aq.upm.es
Bug#612681: x11-common: treat empty session names silently as default session
On Mon, May 16, 2011 at 03:51:01PM +0200, Agustin Martin wrote: Will look a bit more at this in case I can get some info and file a bug report with it against icewm. This seems completely unrelated to your original bug report. For the records, the problem I found seems closer to http://bugs.debian.org/626331 (gnome-settings-daemon doesn't allow to log into IceWM, LXDE.) with the difference that I do not have gnome-settings-daemon installed. I will send a followup there. One of the packages updated today in my testing box was xserver-xorg-core, mentioned as a possibility in that bug report, and looking at the date it entered sid, is about the time I started noticing problems. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110516145504.ga4...@agmartin.aq.upm.es
Bug#564324: xserver-xorg-input-evdev: Xorg SEGFAULT with evdev module
On Wed, Jan 13, 2010 at 04:05:26PM +, Julien Cristau wrote: On Wed, Jan 13, 2010 at 16:19:25 +0100, Agustin Martin wrote: Finally found the reason for this problem, kernel evdev module was not loaded. I have worked around this by explicitly adding evdev to /etc/modules in my sid box. However, until last weekend/this week, it was automagically loaded, with no need for explicit inclusion into /etc/modules. What has changed in this time to trigger the problem? It's autoloaded just fine here, and apparently for everyone else, without touching /etc/modules. No clue. I finally found what I think is causing evdev not be loaded, and that is related to my system being non-standard, so I will fix that locally. I do not know which exact xserver-xorg change made that happens, but I do not think that is very relevant now. More details follow in case I am not the only one setting this kind of non-standard systems. In my system I have different partitions for different dists (sid, ...) and all the boot+kernel+modules stuff is at a different place. Each dist partition has proper symlinks, and special code is added to /etc/init.d to make sure partition containing /lib/modules is mounted just before /etc/init.d/module-init-tools is run and unmounted afterwards, before /etc/init.d/checkfs is run, so /etc/modules is honoured. Things are mounted again later according to /etc/fstab. The problem in my system is that with the above setup udev init scripts are run way before /lib/modules is mounted and so evdev module is not loaded by udev because is not found. I have to see what is the best workaround for this in my system. Having evdev in /etc/modules seems simpler, but I have to investigate other possibilities, like mounting before /etc/init.d/udev is run. Sorry for the noise and thanks a lot for the feedback. Cheers, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564324: xserver-xorg-input-evdev: Xorg SEGFAULT with evdev module
On Mon, Jan 11, 2010 at 01:44:46PM +, Julien Cristau wrote: On Mon, Jan 11, 2010 at 14:22:10 +0100, Agustin Martin wrote: ... (**) ABBHOME USB Keyboard: always reports core events (**) ABBHOME USB Keyboard: Device: /dev/input/mouse1 (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device (II) UnloadModule: evdev ... Not sure if this is the same problem, but wdm gets stalled here with new xorg and a possible reason is also shown above. No possibility of using any key. I noticed that as above, evdev module is unloaded after similar problems with my mouse here. I could only go out from there by pressing the reboot button. The above is a red herring, it doesn't have anything to do with whatever bug you're seeing. Finally found the reason for this problem, kernel evdev module was not loaded. I have worked around this by explicitly adding evdev to /etc/modules in my sid box. However, until last weekend/this week, it was automagically loaded, with no need for explicit inclusion into /etc/modules. What has changed in this time to trigger the problem? Cheers, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564324: xserver-xorg-input-evdev: Xorg SEGFAULT with evdev module
On Sat, Jan 09, 2010 at 10:42:58AM +0100, Marcin Kucharczyk wrote: Package: xserver-xorg-input-evdev Version: 1:2.3.2-2 Severity: important ... (**) ABBHOME USB Keyboard: always reports core events (**) ABBHOME USB Keyboard: Device: /dev/input/mouse1 (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device (II) UnloadModule: evdev ... Not sure if this is the same problem, but wdm gets stalled here with new xorg and a possible reason is also shown above. No possibility of using any key. I noticed that as above, evdev module is unloaded after similar problems with my mouse here. I could only go out from there by pressing the reboot button. VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564324: xserver-xorg-input-evdev: Xorg SEGFAULT with evdev module
On Mon, Jan 11, 2010 at 01:44:46PM +, Julien Cristau wrote: On Mon, Jan 11, 2010 at 14:22:10 +0100, Agustin Martin wrote: ... (**) ABBHOME USB Keyboard: always reports core events (**) ABBHOME USB Keyboard: Device: /dev/input/mouse1 (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device (II) UnloadModule: evdev ... Not sure if this is the same problem, but wdm gets stalled here with new xorg and a possible reason is also shown above. No possibility of using any key. I noticed that as above, evdev module is unloaded after similar problems with my mouse here. I could only go out from there by pressing the reboot button. The above is a red herring, it doesn't have anything to do with whatever bug you're seeing. Thanks for the info That was one of the last things in my Xorg.0.log for failing sid ... (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/mouse0) (II) LoadModule: evdev (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so (II) Module evdev: vendor=X.Org Foundation compiled for 1.7.3.902, module version = 2.3.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (**) ImPS/2 Generic Wheel Mouse: always reports core events (**) ImPS/2 Generic Wheel Mouse: Device: /dev/input/mouse0 (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device (II) UnloadModule: evdev (EE) PreInit returned NULL for ImPS/2 Generic Wheel Mouse ... - In a testing box, that is - ... (II) config/hal: Adding input device AT Translated Set 2 keyboard (II) LoadModule: evdev (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so (II) Module evdev: vendor=X.Org Foundation compiled for 1.6.3, module version = 2.2.5 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 ... (II) config/hal: Adding input device ImPS/2 Generic Wheel Mouse (**) ImPS/2 Generic Wheel Mouse: always reports core events (**) ImPS/2 Generic Wheel Mouse: Device: /dev/input/event4 (II) ImPS/2 Generic Wheel Mouse: Found 3 mouse buttons (II) ImPS/2 Generic Wheel Mouse: Found x and y relative axes (II) ImPS/2 Generic Wheel Mouse: Found scroll wheel(s) (II) ImPS/2 Generic Wheel Mouse: Configuring as mouse (**) ImPS/2 Generic Wheel Mouse: YAxisMapping: buttons 4 and 5 (**) ImPS/2 Generic Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device ImPS/2 Generic Wheel Mouse (type: MOUSE) (**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1 (**) ImPS/2 Generic Wheel Mouse: (accel) filter chain progression: 2.00 (**) ImPS/2 Generic Wheel Mouse: (accel) filter stage 0: 20.00 ms (**) ImPS/2 Generic Wheel Mouse: (accel) set acceleration profile 0 (II) ImPS/2 Generic Wheel Mouse: initialized for relative axes. ... - So, seems that despite having xserver-xorg-input-evdev and xserver-xorg-input-kbd, keyboard is not loaded in X in my sid box (note that evdev is loaded late with mouse and not before with keyboard as for testing). I will try to find more info about this before filing a new bug report, fortunately I can use magic SysRq to leave X11 raw mode. Keyboard works outside of X. Also tried with xdm instead of wdm, but no luck. Cheers, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [buildd-tools-devel] Bug#549407: ivtools 1.2.6-1 FTBFS on sparc and powerpc
clone 549407 -1 reassign -1 xutils-dev retitle -1 imake: Must not unconditionally mangle pre-defined symbols in paths. thanks On Tue, Dec 08, 2009 at 03:01:12PM +, Roger Leigh wrote: Thanks for identifying the cause of the problem! So, to state the problem clearly: Imake is substituting the $(ARCH) part of the path to something else. Such as 'i386' being swapped for something else entirely, thus resulting in an invalid path. Exactly. This is particularly obscure, since not all arch names have the associated symbol defined, e.g., I could not reproduce this with amd64, and there were no problems with other autobuilders using new sbuild, but there were with i386, sparc and powerpc. This is, IMO, completely broken on the part of Imake. Agreed I'm reluctant to alter sbuild to accommodate such bad behaviour. For one thing, it can substitute /any part/ of the path, so there's no guarantee it won't randomly break on the XX random part or any other path component for any given build. The fix just makes the arch mismatch because underscore makes the two parts a single token, but that is not to say it will /never/ match. I accept that it solves the immediate issue, but it doesn't correct the fundamental underlying defect in imake. What's worse is that the random path might actually be /valid/, in which case it might scribble junk into, or delete files from, a directory other than the build directory. Unlikely, but possible, so a potential security problem on the buildd. Agreed also, but note that there is the same potential problem with the current setup. IIRC, few packages still use imake, so this is not at all a generalized problem. The only action I'd currently expect to be considered from the sbuild side is documenting this misbehavior. I agree that this is an imake misbehavior, so I am cloning this bug report and reassigning the clone to xutils-dev. I am keeping current RC severity, xutils-dev maintainers, please readjust at your will. Is this possible to fix in ivtools using the -u option to undefine things as suggested in the FAQ? Given the package-specific nature of the problem, I feel this would be a more appropriate place for a fix. Yes, that is the scheduled fix. Unfortunately, the buildd-tools mailing list stripped the patch, this is the relevant part, +# Make sure this symbol is disabled when imake is invoked. +MAKE += SPECIAL_IMAKEFLAGS=-U$(ARCH) + and changed make-$(MAKE). In practice, this should only affect the Makefile and Makefiles targets. However, I did not check carefully if there is other indirect imake invocation, so doing things this way does not hurt. I expect to upload a fixed ivtools NMU today. Cheers, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524096: xserver-xorg-core: no mouse and keyboard after upgrade to 1.6.0
On Tue, Apr 14, 2009 at 10:21:39PM +0200, Brice Goglin wrote: Tino Keitel wrote: Thank you for the quick reply. My fault was to use a kernel without evdev support. I recompiled the kernel with CONFIG_INPUT_EVDEV enabled, and everything worked as expected, without the need for AllowEmptyInput settings. Oh, it reminds me of my first try at input-hotplug a couple months ago :) Closing the bug then. I'd appreciate if the need of a kernel with CONFIG_INPUT_EVDEV enabled is put more clearly in the xserver-xorg NEWS file. This has been driving me crazy for a couple of days. I was looking at the xserver-xorg bugs, but unfortunately missed this one (my fault) and only noticed it after looking at the debian-x list. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#463076: xserver-xorg-video-ati: machine freezes when X is stopped or second X started
On Wed, Mar 05, 2008 at 09:25:17AM +0100, Bram Senders wrote: On Tue, 2008-02-26 at 23:49 +, Roger Leigh wrote: Hi folks, Just another datapoint for this bug. My Mac Mini has a :00:10.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) (prog-if 00 [VGA controller]) and I was also bitten by this bug. My system locked hard if I tried to kill X or shutdown the system (which causes kdm to stop X). It also locked if I tried to switch to a VT with C-A-Fn. Further investigation showed that this worked perfectly if I booted the system with video=radeonfb:[EMAIL PROTECTED] on the command-line. I can now switch VTs at will, as well as start and stop X, shut down the system, etc. without problems. However, booting with video=ofonly results in all the problems mentioned above. Is this the same for the other people suffering from this bug? Yes, I can confirm this. The only difference is that I have to boot with a lower resolution (1024x768), otherwise my monitor stays blank (even though it is capable of displaying higher resolutions). I can now switch VTs as well... this has never been possible for me before (after X had started, all VTs always weren't capable of being displayed anymore). So thank you Roger, for this hint! My Mac Mini has more functionality now ;-) Just adding that after setting my xorg to use framebuffer in /etc/xorg.conf (through the debconf prompt) I can no longer reproduce the problem, --- $ diff -u xorg.conf.20080505151844 xorg.conf --- xorg.conf.200805051518442008-05-05 15:18:44.0 +0200 +++ xorg.conf 2008-05-05 15:18:44.0 +0200 @@ -29,6 +29,7 @@ Section Device Identifier Configured Video Device + Option UseFBDev true EndSection Section Monitor --- Unfortunately, this seems to not fix http://bugs.debian.org/472703 #472703: wdm: Sometimes I cannot login, Enter doesn't work Although I already cc'ed the X strike force about this, I would like to explicitly make you aware of that bug report, since the two persons that have experienced it are using ATI radeon. I think that #472703 did propagate to testing right after xserver-xorg-video-ati reached it. -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463076: xserver-xorg-video-ati: machine freezes when X is stopped or second X started
On Thu, May 08, 2008 at 08:29:33AM -0400, Alex Deucher wrote: Just adding that after setting my xorg to use framebuffer in /etc/xorg.conf (through the debconf prompt) I can no longer reproduce the problem, --- $ diff -u xorg.conf.20080505151844 xorg.conf --- xorg.conf.200805051518442008-05-05 15:18:44.0 +0200 +++ xorg.conf 2008-05-05 15:18:44.0 +0200 @@ -29,6 +29,7 @@ Section Device Identifier Configured Video Device + Option UseFBDev true What version of the driver are you using? This option no longer exists on 6.7.19x and newer versions of the ati driver. Hmmm, xserver-xorg-video-ati Version: 1:6.8.0-1 So the option above should do nothing. Indeed, looking at the Xorg log, -- (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message. (WW) RADEON(0): Option UseFBDev is not used (--) RandR disabled -- After removing the option I have tried unsuccessfully to reproduce the problem (Note that it previously appeared here randomly, not in a sistematically reproducible way). So, I have to admit that I have no idea about what helped (or even if the problem will eventually come back), just noticed that I could not reproduce it with the newly arrived to testing xserver-xorg-video-ati, and that line was the only difference once xorg.conf is regenerated. Sorry for the noise, -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wdm: Sometimes I cannot login, Enter doesn't work
On Tue, Mar 25, 2008 at 10:28:13PM +0100, Ladislav Dobias wrote: sometimes I cannot log in using Wdm, I can write only Login name but I cannot get to a password field - Enter doesn't work. As a workaround, I must to Zap (Ctrl-Alt-Backspace) and try again. And after few times - 4x for example, it works. What a magic! I use WindowMaker, if this info helps. I can paste some messages from syslog if they make sense: Mar 25 21:01:21 edc wdm: /etc/X11/wdm/Xresources_0: line 1: /etc/X11/wdm/Xresources_0: Permission denied Mar 25 21:01:21 edc wdm: /etc/X11/wdm/Xresources_0: line 2: syntax error near unexpected token `newline' Mar 25 21:01:21 edc wdm: /etc/X11/wdm/Xresources_0: line 2: `!' Mar 25 21:01:21 edc wdm: Cannot open config file. Using builtin defaults I would like to add that I didn't touch anything in /etc/X11/wdm... I can reproduce this problem. I found this a while ago in sid and this week it seems to have propagated to testing. I am suspicious that it might be related to the new xserver-xorg-video-ati 1:6.8.0-1 package that has been for a while in sid and just propagated to testing (cc'ing the X Strike force so they are aware of this), since I had some other problem with it, or some other similar thing. Is your card an ATI Radeon? -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463076: xserver-xorg-video-ati: machine freezes when X is stopped or second X started
On Tue, Jan 29, 2008 at 05:34:04PM +0100, Bram Senders wrote: On Tue, 2008-01-29 at 09:57 -0500, Alex Deucher wrote: On Jan 29, 2008 6:15 AM, Bram Senders [EMAIL PROTECTED] wrote: However, I now have the problem that the machine freezes when the X server is stopped... Just a hard freeze when I try to logout, or shutdown the machine, or restart gdm; anything that kills the X server causes the entire machine to lock up. My Xorg.0.log contains no information about stopping X. Do any of the following device options help? Option DRI False Option BusType PCI Option AGPMode 4 Trying either of the three options doesn't help; the same hard freeze occurs on logout. Option AGPMode 8 My X log states that 8 is not a supported value for AGPMode (even though I read on Wikipedia that the Radeon 9200 should support 8x AGP), so this doesn't help either, alas. I am also having random freezes when opening a second display, doing some work on it, and closing the display. Not fully reproducible, seems that just opening and closing did not (yet) trigger the problem. Only once my main display got frozen. Cannot even switch to other display when this happens. Just wanted to add that I can recover control with the Magic SysRq+k, that allows me switch to other display and resume work in it. After sysrq+k and before switching display looks frozen, but allows me switching. Some rubbish appears in the old display after switching back. So at least here, seems to not be a full machine lock up, I am sending this mail after that. VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev01) xserver-xorg-video-ati 1:6.8.0-1 (I think this happened with .197 too) The problem does not appear with testing (1:6.6.3-2) Hope this helps, -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368298: trying to overwrite `/usr/X11R6/bin', which is also in package ivtools-dev
On Sun, May 21, 2006 at 05:19:24PM -0700, Steve Langasek wrote: clone 368298 -1 reopen -1 reassign -1 ivtools-dev thanks On Sun, May 21, 2006 at 11:29:03AM +0200, Julien Danjou wrote: Package: x11-common Version: 1:7.0.18 Severity: grave ... dpkg: error processing /var/cache/apt/archives/x11-common_1%3a7.0.19_i386.deb (--unpack): trying to overwrite `/usr/X11R6/bin', which is also in package ivtools-dev Well, the x11-common side of this has now been fixed, which just leaves ivtools-dev now uninstallable. Cloning reassigning. I think this problem, along with some other RC bugs, is fixed by Christoph Berg NMU for ivtools, waiting in NEW queue for 3 weeks. See last message in http://bugs.debian.org/346695 for NMU notification. -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
