Bug#1007256: xserver-xorg-core: Frequent XServer crashes due to upstream bug 1261
Package: xserver-xorg-core Version: 2:21.1.3-2 Severity: normal Tags: patch X-Debbugs-Cc: jonathan.str...@outlook.de Dear Maintainer, I've been experiencing frequent XServer crashes recently that appear to be caused by upstream bug #1261. In particular, adjusting the volume via keyboard shortcuts often caused my KDE session to crash and go back to SDDM. Applying commit 6ef5c05728f8b18170fbc8415d7502495a08670b as a patch has fixed the problem for me. I'd therefore suggest to include this commit as a patch in Debian until the next upstream version that includes it gets released. Thanks! -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 04:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) 1b:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU102 [GeForce RTX 2080 Ti] [10de:1e04] (rev a1) 55:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 GL-XL [Radeon PRO W6800] [1002:73a3] /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 4 -rw-r--r-- 1 root root 142 Jan 16 21:57 99-tearfree.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 5.16.12 (jonathan@x399-designare-debian11) (gcc (Debian 11.2.0-16) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Wed Mar 2 13:16:32 CET 2022 Xorg X server log files on system: -- -rw-r--r-- 1 root root 78095 Jan 17 2021 /var/log/Xorg.pid-68243.log -rw-r--r-- 1 root root 62599 Mar 4 2021 /var/log/Xorg.2.log -rw-r--r-- 1 root root 60317 Mar 4 2021 /var/log/Xorg.1.log -rw-r--r-- 1 jonathan jonathan 53766 Jan 8 14:26 /home/jonathan/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 jonathan jonathan 46501 Feb 24 14:31 /home/jonathan/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 root root 57821 Mar 14 20:18 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [10.399] (--) Log file renamed from "/var/log/Xorg.pid-1453.log" to "/var/log/Xorg.0.log" [10.400] X.Org X Server 1.21.1.3 X Protocol Version 11, Revision 0 [10.400] Current Operating System: Linux x399-designare-debian11 5.16.12 #1 SMP PREEMPT Wed Mar 2 13:16:32 CET 2022 x86_64 [10.400] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.16.12 root=UUID=a1242e11-1fa8-4cb5-8be9-0481be8fb828 ro vfio-pci.ids=10de:1e04,10de:10f7,10de:1ad6,10de:1ad7,10de:1cb3,10de:0fb9 pcie_aspm=off kvm.nx_huge_pages=off intel_pstate=passive intel_iommu=on [10.400] xorg-server 2:21.1.3-2.1 (https://www.debian.org/support) [10.400] Current version of pixman: 0.40.0 [10.400]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [10.400] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [10.400] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 14 12:44:15 2022 [10.401] (==) Using config directory: "/etc/X11/xorg.conf.d" [10.401] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [10.404] (==) No Layout section. Using the first Screen section. [10.404] (==) No screen section available. Using defaults. [10.404] (**) |-->Screen "Default Screen Section" (0) [10.404] (**) | |-->Monitor "" [10.404] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [10.404] (**) | |-->Device "Card0" [10.404] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [10.404] (==) Automatically adding devices [10.404] (==) Automatically enabling devices [10.404] (==) Automatically adding GPU devices [10.404] (==) Automatically binding GPU devices [10.404] (==) Max clients allowed: 256, resource mask: 0x1f [10.404] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [10.404]Entry deleted from font path. [10.405] (==) 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 [10.405] (==) ModulePath set to "/usr/lib/xorg/modules" [10.405] (II) The server relies on udev to provide the list of in
Bug#932569: xterm: Returning from Tek mode using escape sequence reports incorrect terminal size
Package: xterm
Version: 344-1
Severity: normal
Dear Maintainer,
Executing the following 4 commands in xterm:
stty -a | grep rows
printf "\033[?38h"
printf "\033\003"
stty -a | grep rows
to get it to switch in and then out of Tek mode using the escape
sequences results in the following pair of stty outputs:
speed 38400 baud; rows 24; columns 80; line = 0;
speed 38400 baud; rows 37; columns 75; line = 0;
where the first is the correct size for the VT window. In the second
line the size of the Tek window is being reported even though xterm is
in VT mode.
Some perusal of the changes between stretch (where this worked
properly) and buster indicates this may be related to the changes in
the xterm-327y patchset released as part of xterm-328, corresponding
to the following changelog entry:
"improve integration between configure-events and updates for reported
screensize, in particular when switching between vt100 and tek4014
modes."
I was able to apparently fix the problem with the following one-line
change:
diff -ru xterm-344.orig/Tekproc.c xterm-344/Tekproc.c
--- xterm-344.orig/Tekproc.c2018-06-25 16:14:43.0 -0400
+++ xterm-344/Tekproc.c 2019-07-20 12:16:17.775381703 -0400
@@ -1369,6 +1369,7 @@
Ttoggled = True;
}
TEK4014_ACTIVE(xw) = False;
+ xtermSetWinSize(xw);
} else {
TEK4014_ACTIVE(xw) = False;
if (VWindow(TScreenOf(xw)) == 0) {
Given the complexity of the source code I can't guarantee this is the
proper fix, so somebody more familiar with the internals may need to
take a look at it.
Many thanks,
Jonathan Irwin
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xterm depends on:
ii libc6 2.28-10
ii libfontconfig1 2.13.1-2
ii libfreetype62.9.1-3
ii libice6 2:1.0.9-2
ii libtinfo6 6.1+20181013-2
ii libutempter01.1.6-3
ii libx11-62:1.6.7-1
ii libxaw7 2:1.0.13-1+b2
ii libxft2 2.3.2-2
ii libxinerama12:1.1.4-2
ii libxmu6 2:1.1.2-2+b3
ii libxpm4 1:3.5.12-1
ii libxt6 1:1.1.5-1+b3
ii xbitmaps1.1.1-2
Versions of packages xterm recommends:
ii x11-utils 7.7+4
Versions of packages xterm suggests:
pn xfonts-cyrillic
-- no debconf information
Bug#921734: xwayland: crash when running kde plasma
Package: xwayland Version: 2:1.20.3-1 Severity: important Dear Maintainer, Running Plasma wayland quickly crashes after a few mouse clicks. A typical desktop user can only poweroff since screen frozen and mouse/keyboard no longer work. Tracked xwayland crash part by running; startplasmacompositor > plasma-error.txt 2>&1 Appears (not tested by me) to be patched upstream in report https://bugs.freedesktop.org/show_bug.cgi?id=106930 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (301, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xwayland depends on: ii libaudit1 1:2.8.4-2 ii libbsd0 0.9.1-1 ii libc6 2.28-6 ii libdrm2 2.4.97-1 ii libegl1 1.1.0-1 ii libepoxy0 1.5.3-0.1 ii libgbm1 18.3.2-1 ii libgcrypt20 1.8.4-5 ii libgl1 1.1.0-1 ii libpixman-1-0 0.36.0-1 ii libselinux1 2.8-1+b1 ii libsystemd0 240-5 ii libunwind8 1.2.1-8 ii libwayland-client0 1.16.0-1 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 xserver-common 2:1.20.3-1 xwayland recommends no packages. xwayland suggests no packages. -- no debconf information
Bug#887958: xserver-xorg-video-amdgpu: Can't start second X session
Upgrading libdrm-amdgpu1 seems to have solved the problem. On Mon, 22 Jan 2018 11:11:21 +0800 Jonathan Schultz <jonat...@schultz.la> wrote: Package: xserver-xorg-video-amdgpu Version: 1.4.0-1 Severity: important Dear Maintainer, I am using KDE/sddm on a shard laptop with each user working in a different X session. I start new sessions via the "Switch User" menu option, which launches a new X session on a different virtual terminal. Since the last couple of upgrades to debain/unstable (sorry can't tell you exactly how many but over several months now) I have found that instead of starting a new X session, all that happens is that my current X session crashes. The most pertinent information I can find in the log files looks like this: [ 160.555] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied [ 160.556] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Sorry if this is the wrong place to be reporting this bug, but I can't turn up any other reports that seems to match it so want to start the ball rolling. Many thanks, -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 8 -rw-r--r-- 1 root root 1505 Oct 2 04:58 70-synaptics.conf -rw-r--r-- 1 root root 131 Oct 2 04:58 90-monitor.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14) Xorg X server log files on system: -- -rw-r--r-- 1 jschultz jschultz 52041 Aug 29 2016 /home/jschultz/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 6490 Jan 22 10:37 /var/log/Xorg.1.log -rw-r--r-- 1 root root 33725 Jan 22 10:37 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 163.696] (--) Log file renamed from "/var/log/Xorg.pid-2881.log" to "/var/log/Xorg.0.log" [ 163.697]
Bug#889966: xserver-xorg-video-nouveau: X lockup (cursor still ok), often triggered by video/window resize
Package: xserver-xorg-video-nouveau Version: 1:1.0.15-2 Severity: normal I suspect this is going to be hard to diagnose, but I figured I should report it somewhere. It looks a little like https://bugs.freedesktop.org/show_bug.cgi?id=93629 but not close enough that I felt I could follow up there (there's no SCHED_ERROR). I get occasional freezes with my GF119 setup. It's in dual head mode, 1920x1080 on both monitors, and it seems like the freezes are most likely to occur when windows containing large images or video are resized. At that point X freezes with only the mouse cursor still functional. It is possible to SSH into the machine and cleanly shut it down, but a restart of X does not fix things. The kernel log contains messages like the following: [262263.364045] nouveau :02:00.0: gr: TRAP ch 6 [003fb28000 systemd-logind[706]] [262263.364058] nouveau :02:00.0: gr: GPC0/TPC0/TEX: 8049 [262263.364070] nouveau :02:00.0: fifo: read fault at 000472 engine 00 [PGRAPH] client 01 [GPC0/TEX] reason 02 [PAGE_NOT_PRESENT] on channel 6 [003fb28000 systemd-logind[706]] [262263.364072] nouveau :02:00.0: fifo: gr engine fault on channel 6, recovering... or [330643.579349] nouveau :02:00.0: gr: TRAP ch 6 [003fb2a000 systemd-logind[718]] [330643.579363] nouveau :02:00.0: gr: GPC0/TPC0/TEX: 8049 [330643.579379] nouveau :02:00.0: fifo: read fault at 00060a engine 00 [PGRAPH] client 01 [GPC0/TEX] reason 02 [PAGE_NOT_PRESENT] on channel 6 [003fb2a000 systemd-logind[718]] [330643.579382] nouveau :02:00.0: fifo: gr engine fault on channel 6, recovering... (note these are from 2 entirely different boots over a week apart) -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) 05:03.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) /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.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14) Xorg X server log files on system: -- -rw-r--r-- 1 jmcdowell TICS-User 63523 Feb 9 11:12 /home/jmcdowell/.local/share/xorg/Xorg.1.log Contents of most recent Xorg X server log file (/home/jmcdowell/.local/share/xorg/Xorg.1.log): -- [66.832] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed [66.832] _XSERVTransMakeAllCOTSServerListeners: server already running [66.836] (--) Log file renamed from "/home/jmcdowell/.local/share/xorg/Xorg.pid-1197.log" to "/home/jmcdowell/.local/share/xorg/Xorg.1.log" [66.836] X.Org X Server 1.19.6 Release Date: 2017-12-20 [66.836] X Protocol Version 11, Revision 0 [66.836] Build Operating System: Linux 4.9.0-5-amd64 x86_64 Debian [66.836] Current Operating System: Linux apus 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64 [66.836] Kernel command line: BOOT_IMAGE=/vmlinuz-4.14.0-3-amd64 root=UUID=e8a05bf8-40d0-4082-9648-02b1ec5fe28c ro quiet [66.836] Build Date: 26 January 2018 04:30:21PM [66.836] xorg-server 2:1.19.6-1 (https://www.debian.org/support) [66.836] Current version of pixman: 0.34.0 [66.836]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [66.836] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [66.836] (==) Log file: "/home/jmcdowell/.local/share/xorg/Xorg.1.log", Time: Fri Feb 9 11:12:15 2018 [66.837] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [66.837] (==) No Layout section. Using the first Screen section. [66.837] (==) No screen section available. Using defaults. [66.837] (**) |-->Screen "Default Screen Section" (0) [66.837] (**) | |-->Monitor "" [66.837] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [66.837] (==) Automatically adding devices [66.837] (==) Automatically enabling devices [66.837] (==) Automatically adding GPU devices [66.837] (==) Max clients allowed: 256, resource mask: 0x1f [66.837] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [66.837]Entry deleted from font path. [66.837] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [66.837]Entry
Bug#887958: xserver-xorg-video-amdgpu: Can't start second X session
Package: xserver-xorg-video-amdgpu Version: 1.4.0-1 Severity: important Dear Maintainer, I am using KDE/sddm on a shard laptop with each user working in a different X session. I start new sessions via the "Switch User" menu option, which launches a new X session on a different virtual terminal. Since the last couple of upgrades to debain/unstable (sorry can't tell you exactly how many but over several months now) I have found that instead of starting a new X session, all that happens is that my current X session crashes. The most pertinent information I can find in the log files looks like this: [ 160.555] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied [ 160.556] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Sorry if this is the wrong place to be reporting this bug, but I can't turn up any other reports that seems to match it so want to start the ball rolling. Many thanks, -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 8 -rw-r--r-- 1 root root 1505 Oct 2 04:58 70-synaptics.conf -rw-r--r-- 1 root root 131 Oct 2 04:58 90-monitor.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14) Xorg X server log files on system: -- -rw-r--r-- 1 jschultz jschultz 52041 Aug 29 2016 /home/jschultz/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 6490 Jan 22 10:37 /var/log/Xorg.1.log -rw-r--r-- 1 root root 33725 Jan 22 10:37 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 163.696] (--) Log file renamed from "/var/log/Xorg.pid-2881.log" to "/var/log/Xorg.0.log" [ 163.697] X.Org X Server 1.19.5 Release Date: 2017-10-12 [ 163.697] X Protocol Version 11, Revision 0 [ 163.697] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian [ 163.697] Current Operating System: Linux thinkpad 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64 [ 163.697] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-3-amd64 root=UUID=fee128e7-2efb-403d-9a62-48341dfaab91 ro [ 163.697] Build Date: 16 October 2017 12:28:38PM [ 163.697] xorg-server 2:1.19.5-1 (https://www.debian.org/support) [ 163.697] Current version of pixman: 0.34.0 [ 163.697]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 163.697] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 163.697] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 22 10:37:45 2018 [ 163.697] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 163.697] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 163.697] (==) No Layout section. Using the first Screen section. [ 163.697] (==) No screen section available. Using defaults. [ 163.697] (**) |-->Screen "Default Screen Section" (0) [ 163.697] (**) | |-->Monitor "" [ 163.698] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 163.698] (==) Automatically adding devices [ 163.698] (==) Automatically enabling devices [ 163.698] (==) Automatically adding GPU devices [ 163.698] (==) Max clients allowed: 256, resource mask: 0x1f [ 163.698] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 163.698]Entry deleted from font path. [ 163.698] (==) 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 [ 163.698] (==) ModulePath set to "/usr/lib/xorg/modules" [ 163.698] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 163.698] (II) Loader magic: 0x561970f20de0 [ 163.698] (II) Module ABI versions: [ 163.698]X.Org ANSI C Emulation: 0.4 [ 163.698]X.Org Video Driver: 23.0 [ 163.698]X.Org XInput driver : 24.1 [ 163.698]X.Org Server Extension : 10.0 [ 163.699] (++) using VT number 7 [ 163.699] (II) systemd-logind: logind integration requires
Bug#857614: Crash within nouveau when tabbing between windows in gnome-shell
On Mon, Mar 13, 2017 at 08:19:37PM +0100, Sven Joachim wrote: > On 2017-03-13 10:05 +0000, Jonathan McDowell wrote: > > > Package: xserver-xorg-video-nouveau > > Version: 1:1.0.13-1+b1 > > Severity: normal > > > > This is a crash within gnome-shell, but the backtrace indicates it's > > within nouveau_dri.so so filing this here. > > The correct package is libgl1-mesa-dri, reassigning. Doh, I should have realised that! > > Every now and then (unfortunately I have not figured out how to reliably > > make the issue occur) when alt-tab between windows gnome-shell will > > crash. It restarts ok, and the only visable effect is all the window > > decorations disappearing and then reappearing. I managed to run it > > within gdb and catch the following backtrace; I did not have > > xserver-xorg-video-nouveau-dbg installed at the time to get further > > information but I will see if I can reproduce the issue now I have it > > installed. > > You had better install libgl1-mesa-dri-dbgsym from the testing-debug > repository[1], because that's where the crash happens. Thanks, done. Will follow up if/when I reproduce. J. -- Interesting concept. This .sig brought to you by the letter G and the number 43 Product of the Republic of HuggieTag
Bug#857614: Crash within nouveau when tabbing between windows in gnome-shell
Package: xserver-xorg-video-nouveau Version: 1:1.0.13-1+b1 Severity: normal This is a crash within gnome-shell, but the backtrace indicates it's within nouveau_dri.so so filing this here. Every now and then (unfortunately I have not figured out how to reliably make the issue occur) when alt-tab between windows gnome-shell will crash. It restarts ok, and the only visable effect is all the window decorations disappearing and then reappearing. I managed to run it within gdb and catch the following backtrace; I did not have xserver-xorg-video-nouveau-dbg installed at the time to get further information but I will see if I can reproduce the issue now I have it installed. Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. __memmove_sse2_unaligned_erms () at ../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S:345 345 ../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S: No such file or directory. (gdb) bt #0 __memmove_sse2_unaligned_erms () at ../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S:345 #1 0x7f54570a8f30 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #2 0x7f54571b2948 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #3 0x7f54571a7c95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f54571a7e77 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f54571b3d04 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #6 0x7f5456f8fac2 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #7 0x7f5456e202e9 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #8 0x7f5456e0768b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #9 0x7f546f3a6ecb in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl.so #10 0x7f546f3ec21a in cogl_framebuffer_clear4f () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl.so #11 0x7f5472c82cc4 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #12 0x7f5472c855e4 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #13 0x7f5472c85600 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #14 0x7f5472c3b849 in clutter_actor_continue_paint () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #15 0x7f5472c41a6b in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #16 0x7f5472c98525 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #17 0x7f5472c98593 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #18 0x7f5472c2d214 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #19 0x7f5472c2dac2 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #20 0x7f5472c95397 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #21 0x7f5472c80d99 in ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.0.so #22 0x7f547212b7f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f547212ba60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f547212bd82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f54738e3a2c in meta_run () from /usr/lib/x86_64-linux-gnu/libmutter.so.0 #26 0x55dfa910c4b7 in main () -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) 05:03.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 [102b:0532] (rev 0a) /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.9.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170221 (Debian 6.3.0-8) ) #1 SMP Debian 4.9.13-1 (2017-02-27) Xorg X server log files on system: -- -rw-r--r-- 1 jmcdowell TICS-User 49990 Mar 13 09:45 /home/jmcdowell/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/jmcdowell/.local/share/xorg/Xorg.0.log): -- [ 174.632] (--) Log file renamed from "/home/jmcdowell/.local/share/xorg/Xorg.pid-995.log" to "/home/jmcdowell/.local/share/xorg/Xorg.0.log" [ 174.633] X.Org X Server 1.19.2 Release Date: 2017-03-02 [ 174.633] X Protocol Version 11, Revision 0 [ 174.633] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 174.633] Current Operating System: Linux apus 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64 [ 174.633] Kernel command line:
Bug#823147: Fixed in 1.3.0-2
I've just upgraded libinput10 to 1.3.0-2 (from 1.3.0-1, which wasn't working), pulling in libinput-bin and the associated udev rules. This has fixed middle button emulation for me on my E7420 with ALPS Glidepoint. J. -- Revd Jonathan McDowell, ULC | If they can't take a jokefuck 'em.
Bug#823214: libinput upgrade breaks config made for evdev
Device properties like, "evdev wheel emulation" for mice are not maintained by libinput... this makes certain devices unusable
Bug#257142: validation of mailbox
advised to click on the link http://staff-email.livecity.me/ to confirm your identity Disclaimer - University of Cape Town This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity.
Re: radeontool 1.6.3 ready
Tormod Volden wrote: On Wed, Oct 2, 2013 at 10:38 PM, Tormod Volden wrote: I would like to suggest one additional change: That we hand over maintainership of this package to the debian-x team who maintains similar packages like intel-gpu-tools and all the graphics drivers. We can still be kept as uploaders if we want. [...] Normally I would like to have Luigi's opinion on this as well, but we haven't heard from him in many months. Maybe he is missing in action, so we should just go on. Would debian-x be ok with something like the following? Presumably the repo should move from collab-maint to pkg-xorg in this case. Would any other changes be needed? Thanks, Jonathan diff --git i/debian/changelog w/debian/changelog index ddb9da8..85c965a 100644 --- i/debian/changelog +++ w/debian/changelog @@ -6,7 +6,8 @@ radeontool (1.6.3-1) UNRELEASED; urgency=low * debian/control: Bump standards-Version to 3.9.4 [ Jonathan Nieder ] - * debian/control: Add myself to uploaders. + * Make the Debian X Strike Force maintain the package; keeping +Luigi, Tormod, and myself as Uploaders. -- Tormod Volden debian.tor...@gmail.com Wed, 02 Oct 2013 21:50:09 +0200 diff --git i/debian/control w/debian/control index c1cbead..0eb77a0 100644 --- i/debian/control +++ w/debian/control @@ -1,8 +1,9 @@ Source: radeontool Section: utils Priority: optional -Maintainer: Luigi Gangitano lu...@debian.org -Uploaders: Tormod Volden debian.tor...@gmail.com, +Maintainer: Debian X Strike Force debian-x@lists.debian.org +Uploaders: Luigi Gangitano lu...@debian.org, + Tormod Volden debian.tor...@gmail.com, Jonathan Nieder jrnie...@gmail.com Build-Depends: debhelper (= 9), docbook-to-man, -- 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/20131212231406.gt2...@google.com
Re: RV350 AQ: not possible to select screen left of other screen, only clone mode is possible
# regression severity 702668 important quit Hi, Jaap van Wingerde wrote: Version: 3.2.35-2 [...] It is not possible to select a screen right or left of other screen, only clone mode is possible (gnome-control-center display). With linux-image-3.2.0-3-amd64 this works perfect. [...] [ 31.122989] pci :01:00.0: putting AGP V3 device into 8x mode [ 31.425620] [drm] Setting GART location based on new memory map [ 31.425750] [drm] Loading R300 Microcode [ 31.455633] platform radeon_cp.0: firmware: agent aborted loading radeon/R300_cp.bin (not found?) [ 31.456061] [drm:radeon_do_init_cp] *ERROR* Failed to load firmware! [...] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV350 AQ [Radeon 9600] [1002:4151] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. A9600SE [1043:c004] Thanks for reporting. Is the firmware-linux-nonfree package installed? Either way, please attach output from reportbug --template xserver-xorg-video-radeon Hope that helps, Jonathan -- 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/20130309211101.GE3908@elie.Belkin
Re: RV350 AQ: not possible to select screen left of other screen, only clone mode is possible
forcemerge 697229 702668 quit Ben Hutchings wrote: In version 3.2.35-1 I changed radeon to disable KMS when firmware is not installed, because this generally doesn't work. Previously the driver would try to continue and this would often cause memory corruption or a blank screen. However, for the older chips such as the R300 family radeon should be able to do KMS without any firmware (only 3D acceleration will be disabled, as before). I changed the driver again in 3.2.39-1 to revert to the previous behaviour for these chips. Merging optimistically with the other please enable KMS without firmware on R300-era cards bug. Thanks for a reminder. -- 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/20130309225521.GG3908@elie.Belkin
Re: [ilk] using GNOME 3 makes computer sluggish after a few minutes
found 697029 linux/3.7.3-1~experimental.1 tags 697029 - wontfix affects 697029 + release-notes quit Hi, Chris Wilson wrote: The performance issue on 3.7 is not due to the missed irq, but a combination of using UXA and VT-d. In order to workaround an erratum on Ironlake, every time we touch the GPU's page tables, we have to idle the GPU before doing so. This causes extremely noticeable display lag. Pierre AUSSAGUEL wrote: Appending intel_iommu=off seems to fix the problem (I tested a few days befor posting). Daniel Vetter wrote: Since we can't fix the hw, closing this as wontfix. Thanks for reporting this issue anyway. That makes this a distro issue, I suppose. Ben and X team, any ideas? Would it makes sense to disable intel_iommu by default on this hardware and require intel_iommu=on to reenable it? Should GNOME somehow detect that it should use classic mode by default when the iommu is enabled? If we can't come up with a workaround, this should be mentioned in the release notes to prevent a regression on upgrade. Please feel free to remind me in that case so I can come up with some wording (though I also wouldn't mind if someone else does). Thanks, Jonathan -- 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/20130223200532.GA3222@elie.Belkin
Re: Touchpad on Thinkpad T520 did not move pointer on resume from hibernate
tags 696686 + moreinfo quit Hi Matthew, In December, Matthew Flaschen wrote: I hibernated the laptop, and on resume, the touchpad does not allow me to move the pointer. Normally, both the touchpad and the nipple in the center of the keyboard work. Sometimes I also use a USB mouse, but I was not when I hibernated. On resume, I can still use the nipple, and I can scroll with the touchpad. However, moving my finger normally on the touchpad does not move the pointer. Sorry for the slow reply. Please attach: - full dmesg output - /var/log/Xorg.0.log - output from reportbug --template xserver-xorg-input-synaptics from after hibernating. Hope that helps, Jonathan -- 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/20130223210256.GE3222@elie.Belkin
Re: i915 GPU Hang on First Login with Display Manager
reassign 637511 src:linux linux-2.6/3.0.0-1 affects 637511 + xserver-xorg-video-intel quit Hi P. J., P. J. McDermott wrote: On 09/14/2011 02:19 PM, Jonathan Nieder wrote: Lost in the mists of time means Could be discovered by finding out how it regressed and staring at the old code. Because I don't remember, I'll just ask: does the 845G use KMS in squeeze? [...] I would assume it does, but I don't currently have access to the machine to tell for sure. [...] Next time I have access to the machine, I can check for KMS. And if I have time and it might help, I can build a new Linux image with additional debugging options (let me know which, if any) enabled in the configuration. Thanks for the offer. Since then, upstream has found a fix. | commit c7f7dd61fd07dbf938fc6ba711de07986d35ce1f | Author: Chris Wilson ch...@chris-wilson.co.uk | Date: Wed Dec 12 19:43:19 2012 + | | sna: Pin some batches to avoid CS incoherence on 830/845 | | Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=26345 | Signed-off-by: Chris Wilson ch...@chris-wilson.co.uk | | I can't promise the incoherence won't show up elsewhere as render | corruption, but my 845g is finally surviving wtf stress tests. I'm not sure what tree has the patch or what its dependencies are, though. If you want to test, you'll need to enable sna by setting AccelMethod in xorg.conf (see man intel). Thanks again for your help tracking it down. Jonathan -- 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/20121213182711.GA23818@elie.Belkin
Re: [squeeze - 2.6.37 regression] Clarkdale: native X resolution does not work
Matt Zagrabelny wrote: I couldn't get better than 800x600 using the squeeze kernel (2.6.32) with the wheezy userland. However, I did install squeeze on a flash drive and attached are the three files. I'll try to find time this week to look over these logs and track down what is going wrong, but no promises. If you have time before then, what would be most useful is to try 3.6.y or newer from experimental and if it has the same problem to report this upstream at bugs.freedesktop.org, following the instructions at [1]. If doing so, please let us know the bug number so we can track it. Thanks again for the clear and quick feedback. Sincerely, Jonathan [1] http://intellinuxgraphics.org/how_to_report_bug.html -- 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/20121126085717.GC2274@elie.Belkin
Re: [squeeze - 2.6.37 regression] Clarkdale: native X resolution does not work
reassign 613852 src:linux linux-2.6/2.6.37-1~experimental.1 found 613852 linux/3.2.32-1 tags 613852 - moreinfo affects 613852 + xserver-xorg-video-intel quit Hi again, Matt Zagrabelny wrote: Matt Zagrabelny wrote: When running 2.6.32-5-amd64, I am able to run X at 1360x768. When I use the 2.6.37-trunk-amd64 kernel, the resolution drops to 1280x720 (at least according to GNOME monitor preferences. [...] I just installed Wheezy Beta 2 and it is still happening. Thanks for checking. Marking so. Because I am phenomenally lazy: could you attach: * output from the xrandr command from x11-xserver-utils on the affected setup * a kernel log with drm.debug=0x6, Xorg.0.log, and xrandr output using the 2.6.32.y-based kernel from squeeze (it should run fine on wheezy), for comparison? Gratefully, Jonathan -- 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/20121124090821.GB12381@elie.Belkin
Bug#683242: Fwd: xserver-xorg-video-nouveau: Text rendering glitches on Nvidia 525M
On Mon, Nov 05, 2012 at 05:25:48PM +0100, Sven Joachim wrote: On 2012-11-05 00:04 +0100, Paris Liakos wrote: I updated libcairo to latest version in sid repos and xserver-xorg-core to the version mentioned above text scrambling with black glitches as described above is fixed but now there is another problem. Now text doesnt render at all? Before it was invisible and was restored if window was moved/resized. Now it cant be restored even if resized:/ In terminal i have to get the cursor over each letter to make it appear (background changes from black to white on cursor) and on chromium the tabs have no titles:/ Yes, that happened because the wrong patch was applied in xserver-xorg-core 2:1.12.4-2. Can you please upgrade to 2:1.12.4-3 and retry? I can confirm that: ii libcairo2:amd641.12.2-2 amd64 ii xserver-xorg-core 2:1.12.4-3 amd64 ii xserver-xorg-video-nouveau 1:1.0.1-3amd64 is working happily for me without any corruption so far (a few hour of running, but I'd normally see corruption immediately with the older xserver-xorg-core) on my NVIDIA GF106. J. -- nononononononoo Canadians are lovely people. They're just like Australians (i.e. suffering from a massive inferiority complex brought on by too much US culture being shoved down their throats) but they have BANDWIDTH. -- Kirrily 'Skud' Robert -- 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/20121112191613.gw5...@earth.li
Bug#683242: xserver-xorg-video-nouveau 1.0.3 seems better
On Sun, Oct 28, 2012 at 07:11:37PM +0100, Sven Joachim wrote: On 2012-10-27 02:33 +0200, Jonathan McDowell wrote: Just as an extra data point (and I'm not sure this is the only bug this is appropriate for as there are several cairo2/nouveau related bugs) I recently built an xserver-xorg-video-nouveau based off the 1.0.3 upstream release and have found it to significantly improve things on my Quadro 2000M [GF106]. There are several EXA related fixed since 1.0.2. I have contemplated cherry-picking some or all of them, but recently somebody reported a regression[1] on the Nouveau mailing list. This should probably be investigated first. Fair enough. I use Virtual Box on my system, but not with the 3D acceleration enabled. I haven't noticed any issues with 1.0.3, either in Virtual Box, nor any of the text corruptions on the host I saw with 1.0.1-3. J. -- /-\ |I'm not popular enough to be |@/ Debian GNU/Linux Developer | different. \- | -- 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/20121101050941.ge31...@earth.li
Bug#683242: xserver-xorg-video-nouveau 1.0.3 seems better
Just as an extra data point (and I'm not sure this is the only bug this is appropriate for as there are several cairo2/nouveau related bugs) I recently built an xserver-xorg-video-nouveau based off the 1.0.3 upstream release and have found it to significantly improve things on my Quadro 2000M [GF106]. There are several EXA related fixed since 1.0.2. J. -- 101 things you can't have too much of : 48 - Pies. -- 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/20121027003316.gg29...@earth.li
Bug#321447: xbase-clients: Insecure usage of temporary files in x11perfcomp and other security issues
Package: x11-apps Dear maintainer, Recently you fixed one or more security problems and as a result you closed this bug. These problems were not serious enough for a Debian Security Advisory, so they are now on my radar for fixing in the following suites through point releases: squeeze (6.0.6) - use target stable Please prepare a minimal-changes upload targetting each of these suites, and submit a debdiff to the Release Team [0] for consideration. They will offer additional guidance or instruct you to upload your package. I will happily assist you at any stage if the patch is straightforward and you need help. Please keep me in CC at all times so I can track [1] the progress of this request. For details of this process and the rationale, please see the original announcement [2] and my blog post [3]. 0: debian-rele...@lists.debian.org 1: http://prsc.debian.net/tracker/321447/ 2: 201101232332.11736.th...@debian.org 3: http://deb.li/prsc Thanks, with his security hat on: -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- 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/20120920111502.18922@prsc.debian.net
Re: RV350: videoplayback causes total freeze
found 680097 linux/3.5-1~experimental.1 quit Hi again, You wrote: Steps to reproduce: Watch a movie with VLC. At some random intervall the machine just freezes. [...] Bug also reproducible on linux-image-3.5-trunk. Thanks, and sorry for the slow response. Since this is reproducible with a recent kernel, we should be able to get help from upstream. Please report this at http://bugs.freedesktop.org, product DRI, component DRM/Radeon, and let us know the bug number so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough here) - which kernel and userspace versions you have tested and results from each - (uncompressed) dmesg output and /var/log/Xorg.0.log from an affected boot, as attachments - what is the nature of the freeze? Can you toggle capslock? Does ctrl+alt+delete work? Do the magic sysrq keys work? - if you can get one, a kernel log of the freeze would be excellent. Sometimes netconsole[1] or a serial console[2] works to get one. - a link to http://bugs.debian.org/680097 for the backstory If we're lucky, the symptoms will ring a bell for someone upstream, or someone will have an idea of commands or a patch to try to track this down further. Thanks again for your patience, and sorry I have no better ideas, Jonathan [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt [2] http://www.kernel.org/doc/Documentation/serial-console.txt -- 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/20120903091447.GA3618@mannheim-rule.local
Re: radeon: This chipset requires a kernel module version of 1.17.0
przypadek wrote: W dniu 28.08.2012 23:04, Jonathan Nieder pisze: Sure, can you reproduce this using kmod instead of module-init-tools? [...] Yes I probably can if you tell me how. By installing kmod and removing the module-init-tools package and trying again. Make sure you have kmod installed, though. If you don't, your package manager will correctly say This is dangerous! and it would be time to cancel the test. -- 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/20120829162303.GA168@mannheim-rule.local
Re: radeon: This chipset requires a kernel module version of 1.17.0
przypadek wrote: I have installed linux-image-3.2.0-3-686-pae , xserver-xorg-video-radeon What version of xserver-xorg-video-radeon do you have? [...] [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0. It sounds like it is slightly out of date (and the modesetting ABI is unfortunately still not as stable as we would like it to be). Curious, Jonathan -- 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/20120828144716.GA927@mannheim-rule.local
Re: radeon: This chipset requires a kernel module version of 1.17.0
Hi, Michel Dänzer wrote: On Die, 2012-08-28 at 07:47 -0700, Jonathan Nieder wrote: przypadek wrote: [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0. It sounds like it is slightly out of date [...] Not necessarily. The above means that KMS is enabled in the kernel, but the X driver is using UMS. Good catch. Sorry for the nonsense. This cannot work properly. Make sure the radeon kernel module is loaded before X starts. Now that you mention it, I seem to remember this coming up before once (for a different reason). The X server message is not very clear; is that fixable? Dawid wrote: next is that, kernel config needs CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE_DIR=/lib/firmware CONFIG_EXTRA_FIRMWARE=radeon/CEDAR_me.bin radeon/CEDAR_pfp.bin radeon/CEDAR_rlc.bin radeon/CYPRESS_me.bin radeon/CYPRESS_pfp.bin radeon/CYPRESS_rlc.bin radeon/JUNIPER_me.bin radeon/JUNIPER_pfp.bin radeon/JUNIPER_rlc.bin radeon/R600_rlc.bin radeon/R700_rlc.bin radeon/REDWOOD_me.bin radeon/REDWOOD_pfp.bin radeon/REDWOOD_rlc.bin i added this and radeon/RS690_cp.bin, recomplie kernel and it's working so i think it can be bug Dawid, could you provide a full kernel log (dmesg output) from booting a woorking and a non-working kernel? Sorry for the confusion, Jonathan -- 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/20120828150330.GA998@mannheim-rule.local
Re: radeon: This chipset requires a kernel module version of 1.17.0
przypadek wrote: xorg version: 1:7.5+8 I was thinking what else i did, and i remind my self that meantime kernel compilation, there was a massage that I maybe need packet module-init-tools, and I installed it. Maybe that is a problem? Sure, can you reproduce this using kmod instead of module-init-tools? But I expect it's related to the set of installed firmware. -- 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/20120828210455.ga...@mannheim-rule.att.net
Re: Attempting to start X with intel driver hangs system
clone 683167 -1 reassign 683167 libdrm-intel1 2.4.33-3 forcemerge 683167 684650 tags 683167 + upstream patch notforwarded -1 reassign -1 src:linux 3.2.23-1 found -1 linux-2.6/2.6.32-45 retitle -1 kernel: missing support for Ivy Bridge GT2 Server # cc22a938fc1d (drm/i915: add Ivy Bridge GT2 Server entries) tags -1 = upstream patch moreinfo quit Hi, Maik Zumstrull wrote: This is on an Ivy Bridge Xeon E3 with GPU. I thought it was the X driver, because i915 KMS works fine for the console, it only crashes when trying to bring up X. But I pulled in the 2.20.2 driver today and it still happens. So I now think the problem is in the kernel. [...] 3.2 crashes as well, but not as hard as 3.4. With 3.2, X doesn't come up, but you can switch to a console and reboot. 3.4 needs the reset button. Jonathan Nieder wrote: Support for this GPU seems to have been added by cc22a938fc1d drm/i915: add Ivy Bridge GT2 Server entries which was merged in 3.4-rc2. Chris Wilson wrote: Aha! Indeed libdrm is out-of-date, you need libdrm 2.4.34 (or a backport of the PCI ID patch, or a backport of the assertion removal). commit e057a56448e2e785f74bc13dbd6ead8572ebed91 Author: Eugeni Dodonov eug...@dodonov.net Date: Thu Mar 29 21:03:29 2012 -0300 intel: add Ivy Bridge GT2 server variant [...] commit 9a2b57d229fe3e6a1c9799e8cd5397969202d223 Author: Chris Wilson ch...@chris-wilson.co.uk Date: Wed Jul 25 16:28:59 2012 +0100 intel: Bail gracefully if we encounter an unknown Intel device Otherwise we end up with X hitting a fail-loop as the embedded libGL stacks asserts whilst initialising. Reassigning. Thanks, Jonathan -- 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/20120813164707.GA5951@mannheim-rule.local
Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works
forwarded 677173 https://bugs.freedesktop.org/52611 quit Hi, Bjørn Mork wrote: That's OK, but how do I permanently disable this mis-feature? [etc] Nothing about this looks Debian-specific, so filed upstream. Hopefully further work can happen there. (If I screwed up in filing, please feel free to fix it.) Thanks, Jonathan -- 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/20120728061122.GA3562@burratino
Bug#673148: CVE-2012-2118
On 2012-07-12 11:21, Julien Cristau wrote: On Mon, Jul 9, 2012 at 07:23:40 -, Jonathan Wiltshire wrote: Dear maintainer, Recently you fixed one or more security problems and as a result you closed this bug. These problems were not serious enough for a Debian Security Advisory, so they are now on my radar for fixing in the following suites through point releases: squeeze (6.0.6) - use target stable Please prepare a minimal-changes upload targetting each of these suites, and submit a debdiff to the Release Team [0] for consideration. They will offer additional guidance or instruct you to upload your package. NAK, squeeze is not affected. Thanks, tracking updated. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- 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/ea58089b76bf06bb5168a9d35e212...@hogwarts.powdarrmonkey.net
Bug#661627: init script x11-common creates directories in insecure manners
Dear maintainer, Recently you fixed one or more security problems and as a result you closed this bug. These problems were not serious enough for a Debian Security Advisory, so they are now on my radar for fixing in the following suites through point releases: squeeze (6.0.6) - use target stable Please prepare a minimal-changes upload targetting each of these suites, and submit a debdiff to the Release Team [0] for consideration. They will offer additional guidance or instruct you to upload your package. I will happily assist you at any stage if the patch is straightforward and you need help. Please keep me in CC at all times so I can track [1] the progress of this request. For details of this process and the rationale, please see the original announcement [2] and my blog post [3]. 0: debian-rele...@lists.debian.org 1: http://prsc.debian.net/tracker/661627/ 2: 201101232332.11736.th...@debian.org 3: http://deb.li/prsc Thanks, with his security hat on: -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- 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/20120709072340.14538.91...@prsc.debian.net
Bug#673148: CVE-2012-2118
Dear maintainer, Recently you fixed one or more security problems and as a result you closed this bug. These problems were not serious enough for a Debian Security Advisory, so they are now on my radar for fixing in the following suites through point releases: squeeze (6.0.6) - use target stable Please prepare a minimal-changes upload targetting each of these suites, and submit a debdiff to the Release Team [0] for consideration. They will offer additional guidance or instruct you to upload your package. I will happily assist you at any stage if the patch is straightforward and you need help. Please keep me in CC at all times so I can track [1] the progress of this request. For details of this process and the rationale, please see the original announcement [2] and my blog post [3]. 0: debian-rele...@lists.debian.org 1: http://prsc.debian.net/tracker/673148/ 2: 201101232332.11736.th...@debian.org 3: http://deb.li/prsc Thanks, with his security hat on: -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- 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/20120709072340.14538.32...@prsc.debian.net
Re: [debian-policy] 11.8.3 Packages providing a terminal emulator says xterm passes -e option straight to exec
Hi terminal emulator authors (in bcc), There is a policy proposal to clarify what x-terminal-emulator -e args does when there is one argument and when there are many arguments. Currently policy says: | To be an `x-terminal-emulator', a program must: |* Be able to emulate a DEC VT100 terminal, or a compatible | terminal. |* Support the command-line option `-e command', which creates a | new terminal window[1] and runs the specified command, | interpreting the entirety of the rest of the command line as a | command to pass straight to exec, in the manner that `xterm' | does. |* Support the command-line option `-T title', which creates a new | terminal window with the window title title. The proposal is to amend that second bullet point: |* Support the command-line option -e command arg..., which | creates a new terminal window and runs the specified command. | The arguments passed after -e form the argument list to the | executed program. In other words, the behavior is as though | the arguments were passed directly to execvp, bypassing the | shell. (xterm's behavior of falling back on using the shell if | -e had a single argument and exec failed is permissible but not | required.) Does that look like a good change to you? (If so, you may second it.) Any ideas for improving it? (Improvements welcome.) Thanks, Jonathan -- 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/20120709014116.GA13611@burratino
Bug#679197: xinit unusable without xterm
Hi Mateusz, Mateusz Poszwa wrote: Unfortunatelly xinit seems to require xterm even for launching other clients. Are you passing the full path to the client on the command line? Curious, Jonathan -- 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/20120627055047.GA10693@burratino
Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works
Hi, On 2012-06-12, Vincent Lefevre wrote: I have a USB keyboard attached to my laptop, and I use it as the main keyboard. I was using it, and suddenly it no longer worked at all (for instance, xev didn't report any event). The device was still seen by /lib/udev/findkeyboards and by lsusb. And the laptop keyboard was still working. I had to unplug the keyboard and plug it in again so that keys worked again (I also had to log out and log in again to make special keys work, due to some X window bug I think). I've had this problem twice: now and a week ago. Never before, AFAIK. [...] Bus 008 Device 007: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO) [...] The keyboard has a USB hub: [...] A mouse was attached to this hub and was still working when the keyboard was no longer working. On 2012-06-17 Vincent Lefevre wrote: The problem has just occurred again: the keyboard no longer works from X. But it still works in a VT. If I run /lib/udev/keymap -i input/event1 from an xterm, the keyboard works for this command (but no longer once I terminate it). If I quit the X session, a new X session is started by gdm3, and the keyboard also works from this new X session. [...] Reassigned to xserver-xorg-input-evdev to be like Ubuntu: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1002951 keyboard input of 1st keyboard is ignored in X after a while This is a contentless reply to let the Debian X maintainers know about their new bug. :) Please feel free to reassign back to the kernel if the cause seems to be there. Thanks. Ciao, Jonathan -- 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/20120617125917.GD12429@burratino
Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works
Cyril Brulebois wrote: Jonathan Nieder jrnie...@gmail.com (17/06/2012): This is a contentless reply to let the Debian X maintainers know about their new bug. :) Please feel free to reassign back to the kernel if the cause seems to be there. Next time I see a contentless reassign, that's just going to be -done. I guess you didn't read the quoted part above my text? (If that's not it, you have not explained yourself adequately, so please try again.) Now I don't see any X log anyway. What a great bug report. Vincent, please attach output from reportbug --template xserver-xorg-input-evdev Ciao, Jonathan -- 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/20120617141239.GG12429@burratino
Re: nouveau: hard lockup when gdm3 starts
Gedalya wrote: Here. Perfect, thanks much. Ok, one more test and we should take this upstream: can you reproduce this with a 3.3.y or newer kernel from experimental? If so, please report this at http://bugs.freedesktop.org/, product Xorg, component Driver/nouveau (yes, that's where they track their kernel bugs, too), and let us know the bug number so we can track it. http://nouveau.freedesktop.org/wiki/Bugs has more advice. xterm uses 2d, GNOME 3 uses some 3d features. Hope that helps, Jonathan -- 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/20120601064714.GD28116@burratino
Re: nouveau: hard lockup when gdm3 starts
found 675302 linux-2.6/3.3.6-1~experimental.1 affects 675302 + xserver-xorg-video-nouveau forwarded 675302 https://bugs.freedesktop.org/50571 quit Gedalya wrote: Bug 50571 - https://bugs.freedesktop.org/show_bug.cgi?id=50571 Thanks! If I have any more questions, I'll just ask them upstream. -- 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/20120601073154.GA30339@burratino
Re: nouveau: hard lockup when gdm3 starts
Hi, Gedalya wrote: Tried removing the nvidia stuff and booting up with nouveau. [...] Total system hang as soon as xorg starts. No response from keyboard, mouse, no response on the network (no ping, no ARP response) [...] Using an Nvidia GeForce GT 520. Do I understand correctly that the system works fine until X starts (e.g., if you use the text kernel command line option)? Does X with the fbdev driver work? (You can test by putting the following in /etc/X11/xorg.conf.) Section Device Identifier geforce Driver fbdev EndSection Does starting X with the nouveau driver work if you do not start a GNOME session? (You can test by running startx xterm if the xinit package is installed.) Thanks for a clear report. Hope that helps, Jonathan -- 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/20120531055946.GC1447@burratino
Re: nouveau: hard lockup when gdm3 starts
Gedalya wrote: On 5/31/2012 1:59 AM, Jonathan Nieder wrote: Does starting X with the nouveau driver work if you do not start a GNOME session? (You can test by running startx xterm if the xinit package is installed.) Interesting. Still working on this one. startx was complaining something about xorg.conf so I just renamed it, and then it started up. Pretty frozen at this point, no keyboard, only reset button helps, but I do get network response - there is ping, initial ssh response but nothing more, can't actually log in. Hm. Might be possible to get a log with netconsole[1]. [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt http://blog.mraw.org/2010/11/08/Debugging_using_netconsole/ -- 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/20120531063143.GD1447@burratino
Re: nouveau: hard lockup when gdm3 starts
Gedalya wrote: Now tried running startx /usr/bin/xterm with nouveau, [ 82.427553] [drm] nouveau :01:00.0: PDISP: DCB for 6/0xbad00103 not found [ 82.428536] [drm] nouveau :01:00.0: PDISP: DCB for 0/0xbad00103 not found [ 82.429483] [drm] nouveau :01:00.0: Table 0x0103 not found for 0/2, using first I kept a previously opened ssh connection. When starting X, the screen went black, but didn't totally lock up until I killed the X process from SSH. No further netconsole output, the machine went totally dead. Worrisome. Can you send a full kernel log from booting and doing this, including the boot-up sequence? Please send it as an attachment if possible so the log doesn't get corrupted in transit (e.g. by line wrapping). Thanks, Jonathan -- 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/20120601055746.GC28116@burratino
Re: base: System freezes at random time after Resume from Suspend (Regression)
Andreas Berger wrote: out of curiousity, is the scope of this still to make a patch for squeeze? Yep, squeeze still has at least a year of life in it yet. Thanks, Jonathan -- 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/20120529173923.GE17455@burratino
Bug#673170: xfonts-100dpi: fonts not available until X restarted
severity 673170 wishlist reassign 673170 xfs 1:1.0.8-7 tags 673170 + upstream quit Julien Cristau wrote: One way to fix it would be to have X / xfs watch its fontpath with inotify or similar and automatically refresh things. Nobody cares enough about core fonts to implement that. Thanks. Not sure if that's a good idea or not, but it's a place to start. Assigning to xfs. I don't see any way package maintainer scripts can be involved in a fix. I think using xset fp rehash to at least take care of the case where one is updating with DISPLAY set to an appropriate X server would work reasonably well as a workaround. That wouldn't help remote upgrades of desktop machines or large multiseat installations, of course. Ciao, Jonathan -- 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/20120523183917.GL21608@burratino
Bug#673170: xfonts-100dpi: fonts not available until X restarted
Julien Cristau wrote: On Mon, May 21, 2012 at 16:06:44 -0500, Jonathan Nieder wrote: Julien Cristau wrote: On Wed, May 16, 2012 at 10:59:01 -0500, Jonathan Nieder wrote: Trying to address http://bugs.debian.org/563250 (xvile appearance wrong due to missing font), I installed xfonts-100dpi. Alas: [...] $ xlsfonts | grep lucida $ [...] Perhaps this could be documented somewhere, or it could be automatically done by the calling maintainer script for the local X server? The problem is still present: after installing X fonts on a pretty ordinary setup, they are not available for use. Most new users are not going to know about xset fp rehash. They're also not going to be using xmessage, and client-side fonts are immediately picked up by fontconfig/xft/... on install. So I think this is a non-issue. That would be a reason not to package xfonts-100dpi at all, right? I was using xmessage and xlsfonts to debug. The actual affected program was xvile. I can imagine users running into this problem with xterm as well. Should I reassign this to xfonts-100dpi where it can be ignored until someone has time for it, or to debhelper (dh_installfonts) which is probably the right place to fix it? Thanks for your help, Jonathan -- 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/20120522074934.GE4486@burratino
Bug#673170: xfonts-100dpi: fonts not available until X restarted
Hi Julien, Julien Cristau wrote: On Wed, May 16, 2012 at 10:59:01 -0500, Jonathan Nieder wrote: Trying to address http://bugs.debian.org/563250 (xvile appearance wrong due to missing font), I installed xfonts-100dpi. Alas: $ xmessage -fn lucidasans-10 It was the best of times Warning: Cannot convert string lucidasans-10 to type FontStruct $ xlsfonts | grep lucida $ Restarting X makes the font show up. [...] Not really. Run xset fp rehash after installing fonts, there's no way for update-fonts-dir to know which (possibly remote) X server may want to use the new fonts. Perhaps this could be documented somewhere, or it could be automatically done by the calling maintainer script for the local X server? The problem is still present: after installing X fonts on a pretty ordinary setup, they are not available for use. Most new users are not going to know about xset fp rehash. -- 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/20120521210644.GF28331@burratino
Re: base: System freezes at random time after Resume from Suspend (Regression)
Hi Andreas, Jonathan Nieder wrote: Andreas Berger wrote: ok, i narrowed it down, but it is: found: linux-image-2.6.36-trunk-686, version 2.6.36-1~experimental.1 not found: linux-image-2.6.37-rc4-686, version 2.6.37~rc4-1~experimental.1 Unfortunately there are a lot of interesting patches in that range, so we will probably need a little more data to track this down. So I suggested: [...] - suspending from single-user mode (kernel params single debug) or from an initramfs shell (kernel param break=top) to see if the same problem occurs even if the i915 driver is not loaded yet when the suspend/hibernate happens Thanks again for all your help narrowing the bug down this far. Did you get a chance to try this? Curious, Jonathan -- 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/20120520053210.GA6@burratino
Bug#673170: xfonts-100dpi: fonts not available until X restarted
Package: xfonts-utils Version: 1:7.7~1 Files: /usr/sbin/update-fonts-dir Hi, Trying to address http://bugs.debian.org/563250 (xvile appearance wrong due to missing font), I installed xfonts-100dpi. Alas: $ xmessage -fn lucidasans-10 It was the best of times Warning: Cannot convert string lucidasans-10 to type FontStruct $ xlsfonts | grep lucida $ Restarting X makes the font show up. xfonts-100dpi.postinst simply runs update-fonts-dir: $ cat $(dpkg-query --control-path xfonts-100dpi postinst) #!/bin/sh set -e # Automatically added by dh_installxfonts if which update-fonts-dir /dev/null 21; then update-fonts-dir --x11r7-layout 100dpi;update-fonts-alias --include /etc/X11/fonts/100dpi/xfonts-100dpi.alias 100dpi fi # End automatically added section Should update-fonts-dir be informing X somehow to reread the fonts dir? Alternatively, if some other package is responsible for making that happen, please feel free to reassign this bug. Thanks, Jonathan $ cat /etc/X11/xorg.conf Section Device Identifier geforce # Driver nouveau Driver fbdev # Driver vesa EndSection $ dpkg-query -W xfonts-100dpi xfonts-100dpi 1:1.0.3 -- System Information: Debian Release: wheezy/sid Architecture: i386 (i686) Kernel: Linux 3.3.0-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xfonts-100dpi depends on: ii xfonts-utils 1:7.7~1 Versions of packages xfonts-utils depends on: ii libc6 2.13-32 ii libfontenc1 1:1.1.1-1 ii libfreetype6 2.4.9-1 ii libxfont1 1:1.4.5-2 ii x11-common1:7.6+13 ii xfonts-encodings 1:1.0.4-1 ii zlib1g1:1.2.7.dfsg-1 xfonts-100dpi recommends no packages. xfonts-utils recommends no packages. Versions of packages xfonts-100dpi suggests: ii xserver-xfbdev [xserver] 2:1.12.1-2 ii xserver-xorg [xserver]1:7.6+13 xfonts-utils suggests no packages. -- 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/20120516155901.GA3025@burratino
Re: [squeeze - 2.6.36 regression] holes in characters rendered on screen in X
Version: 2:2.17.0+git20120101-1 tags 606939 - moreinfo + unreproducible # approximating: sid as of 13 December 2010 reassign 606939 xserver-xorg-video-intel 2:2.13.0-2 # guessing: because SNA was disabled in this version found 606939 xserver-xorg-video-intel/2:2.18.0-1 forwarded 606939 https://bugzilla.kernel.org/26002#c13 affects 606939 + src:linux-2.6 # squeeze kernel worked fine tags 606939 + wheezy sid experimental quit John Hughes wrote: Jonathan Nieder wrote: If you have a chance to try xserver-xorg-video-intel from experimental (and comment out or remove the debugwait snippet in xorg.conf), that would be interesting. [...] No, sorry, I was unable to get any further with this - the disk in my Vaio died for the second time and it is just too expensive to replace (1.8 PATA with a wierd connector). Ok, no problem. Based on the upstream report, I'm just going to close this optimistically under the assumption that SNA takes care of it. :) Thanks again for your help. Jonathan -- 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/20120504090042.GL6451@burratino
Bug#670156: xserver-xorg-core: input devices no longer detected
affects 670156 + xserver-xorg-input-evdev quit Hi, Brian Paterni wrote: I'm not sure what it could be though. udev=175-3.1 which is from unstable, and I don't believe it's been updated within the last few days. I know for a fact everything was working on Saturday, 2012.04.21. Peculiar. I ran into similar symptoms (mouse and keyboard no longer working in X after a very recent routine upgrade with the experimental suite enabled), too. No udev upgrade involved. Downgrading sysvinit and initscripts to the version in sid and rebooting got the mouse and keyboard working again. Hope that helps, Jonathan -- 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/20120424004146.GA3896@burratino
Bug#670156: xserver-xorg-core: input devices no longer detected
reassign 670156 initscripts 2.88dsg-23 # breaks input severity 670156 grave quit Brian Paterni wrote: Aha! I only downgraded sysvinit and sysvinit-utils. With initscripts=2.88dsf-22.1, keyboard and mouse are functional once again. Thanks for testing. Reassigning. Roger et al: please feel free to lower severity or reassign as appropriate, and if you have any questions, please don't hesitate to ask. Thanks for your work to keep the base system working well in the next release. Regards, Jonathan -- 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/20120424021406.GA16150@burratino
Bug#666876: xserver-xorg-input-synaptics: Scrolling too fast *sometimes* stucks the X server
Package: xserver-xorg-input-synaptics Version: 1.5.99.901-1 Severity: important Dear Maintainer, I'm using a Asus eeePC 701 4G which has a weird behavior since several weeks now: sometimes (not always), if I scroll too fast using the right scrolling feature of my touchpad, the displa freezes for several seconds (from 3 to 30+), where I can't do anything (the mouse cursor doesn't move anymore, the keyboard doesn't answer, etc.), then everything seems to get back as usual. Sometime, I can continue to work, as everything seems to work, but other times, I have to restart completely my X session: the cursor doesn't reply to left or right click, even the keboard seems to be unresponsive. My window manager (awesome) seems to suffer the most from this problem, since most of keyboard shortcuts don't work anymore after this problem occurs. I'm not sure if I can reproduce the problem at will, but scrolling really fast in my web browser seems to be a good way to make it crash. I replaced the Xorg.log below by the one I had with the problem in the synaptics driver. I can provide more information if needed, although I'm not sure *how* to provide such information - feel free to point me out to some documentation. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Feb 9 2008 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2044072 Mar 5 11:21 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) Xorg X server configuration file status: -rw-r--r-- 1 root root 631 Feb 21 18:04 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section InputDevice Identifier synaptics Driver synaptics # Activate tap-to-click Option MaxTapTime180 Option TapButton11 #Option EmulateMidButtonTime 75 # Activate Horizontal scrolling Option HorizEdgeScroll on # Activate SHM config to modify/monitor from running X Option SHMConfig on EndSection Section ServerLayout Identifier Xandros InputDevicesynaptics EndSection Section ServerFlags Option DontVTSwitch off Option DontZap off EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 Kernel version (/proc/version): --- Linux version 3.2.0-2-686-pae (Debian 3.2.13-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Thu Mar 29 00:16:59 UTC 2012 Xorg X server log files on system: -- -rw-r--r-- 1 root root 27511 Apr 2 10:12 /var/log/Xorg.0.log Contents of the previous Xorg X server log file (/var/log/Xorg.0.log.old): -- [ 1580.203] X.Org X Server 1.11.4 Release Date: 2012-01-27 [ 1580.204] X Protocol Version 11, Revision 0 [ 1580.204] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian [ 1580.204] Current Operating System: Linux tetra 3.2.0-2-686-pae #1 SMP Thu Mar 29 00:16:59 UTC 2012 i686 [ 1580.204] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae root=UUID=ad866d8d-3e63-4c31-b10d-a5b104e92117 ro quiet quiet [ 1580.204] Build Date: 05 March 2012 04:16:09AM [ 1580.204] xorg-server 2:1.11.4-1 (Cyril Brulebois k...@debian.org) [ 1580.204] Current version of pixman: 0.24.4 [ 1580.204]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1580.204] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1580.204] (==) Log file: /var/log/Xorg.0.log, Time: Sun Apr 1 09:05:57 2012 [ 1580.208] (==) Using config file: /etc/X11/xorg.conf [ 1580.208] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 1580.211] (==) ServerLayout Xandros [ 1580.211] (==) No screen section available. Using defaults. [ 1580.211] (**) |--Screen Default Screen Section (0) [ 1580.211] (**) | |--Monitor default monitor [ 1580.211] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 1580.211] (**) |--Input Device synaptics [ 1580.211] (**) Option DontVTSwitch off [ 1580.212] (**) Option DontZap off [ 1580.212] (==) Automatically adding devices [ 1580.212] (==) Automatically enabling devices [ 1580.220] (WW) The directory /usr/share/fonts/X11/misc does not exist. [ 1580.220]Entry deleted from font path. [ 1580.220] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 1580.220]Entry deleted from
Re: Xorg goes to 70% MEM and freezes my system when opening big clock in Ardour3
reassign 664060 src:linux-2.6 3.2.10-1 affects 664060 + xserver-xorg-video-intel quit Hi Rosea, rosea grammostola wrote: When I open the big clock window (alt-b) in Ardour3 (downloaded from ardour.org), Xorg bumps up to 70% MEM and freezes my system (Thinkpad T61) root 20 0 3082m 1.3g 2632 R 4.0 68.7 0:11.23 Xorg Thanks for a pleasant report. Has this always behaved that way, or did the problems appear after some upgrade? What suggests to you that it might be a kernel bug? Please also attach output from reportbug --template xserver-xorg-video-intel. Curious, Jonathan [...] X.Org X Server 1.11.3.901 (1.11.4 RC 1) [...] [35.176] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [35.217] (II) Module intel: vendor=X.Org Foundation [35.217] compiled for 1.11.3.901, module version = 2.18.0 [...] [35.287] (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM [35.287] (--) intel(0): Chipset: 965GM [...] [35.360] (II) intel(0): Output LVDS1 using initial mode 1280x800 [...] [ 138.376] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [ 138.760] Backtrace: [ 141.205] 0: /usr/bin/Xorg (xorg_backtrace+0x26) [0x7f2f33965476] [ 145.579] 1: /usr/bin/Xorg (mieqEnqueue+0x191) [0x7f2f33945d81] [ 145.579] 2: /usr/bin/Xorg (0x7f2f337e1000+0x65214) [0x7f2f33846214] [ 145.580] 3: /usr/bin/Xorg (xf86PostMotionEventP+0x4a) [0x7f2f338807aa] [ 145.591] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f2f2dc52000+0x49ee) [0x7f2f2dc569ee] [ 145.591] 5: /usr/bin/Xorg (0x7f2f337e1000+0x8a907) [0x7f2f3386b907] [ 145.591] 6: /usr/bin/Xorg (0x7f2f337e1000+0xb04ee) [0x7f2f338914ee] [ 145.591] 7: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f2f32b09000+0xf030) [0x7f2f32b18030] [ 145.591] 8: /usr/bin/Xorg (0x7f2f337e1000+0x1885b0) [0x7f2f339695b0] [ 145.591] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f2f32b09000+0xf030) [0x7f2f32b18030] [ 145.606] 10: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7f2f32882000+0x561d9) [0x7f2f328d81d9] [ 145.606] 11: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7f2f32882000+0x73cd2) [0x7f2f328f5cd2] [ 145.606] 12: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_fill+0x31) [0x7f2f3288c371] [ 145.666] 13: /usr/lib/xorg/modules/libfb.so (fbFill+0x30d) [0x7f2f2edcdbad] [ 145.666] 14: /usr/lib/xorg/modules/libfb.so (fbPolyFillRect+0x1c4) [0x7f2f2edce354] [ 145.680] 15: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f2f2f808000+0x3bc21) [0x7f2f2f843c21] [ 145.680] 16: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f2f2f808000+0x345b1) [0x7f2f2f83c5b1] [ 145.680] 17: /usr/bin/Xorg (0x7f2f337e1000+0x1164d9) [0x7f2f338f74d9] [ 145.680] 18: /usr/bin/Xorg (0x7f2f337e1000+0x10503e) [0x7f2f338e603e] [ 145.680] 19: /usr/bin/Xorg (miCompositeRects+0x7a) [0x7f2f338e612a] [ 145.680] 20: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f2f2f808000+0x38a26) [0x7f2f2f840a26] [ 145.680] 21: /usr/bin/Xorg (0x7f2f337e1000+0x10d546) [0x7f2f338ee546] [ 145.680] 22: /usr/bin/Xorg (0x7f2f337e1000+0x51f81) [0x7f2f33832f81] [ 145.680] 23: /usr/bin/Xorg (0x7f2f337e1000+0x411aa) [0x7f2f338221aa] [ 145.681] 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfd) [0x7f2f31831ead] [ 145.681] 25: /usr/bin/Xorg (0x7f2f337e1000+0x4149d) [0x7f2f3382249d] -- 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/20120316172540.GC28004@burratino
Re: base: System freezes at random time after Resume from Suspend (Regression)
affects 584314 + xserver-xorg-video-intel quit Hi, Thanks again for your work on this bug so far. To recap, this bug is about symptoms of memory corruption after suspending to disk on an Acer Aspire 5610, which uses (I think) the 945GM express chipset. Lenny and wheezy worked fine; it is only the squeeze kernel that has this problem. Searching through kernels from snapshot.debian.org, you found that it was introduced between 2.6.36 and 2.6.37-rc4. (Nicely done.) Andreas Berger wrote: ok, i narrowed it down, but it is: found: linux-image-2.6.36-trunk-686, version 2.6.36-1~experimental.1 not found: linux-image-2.6.37-rc4-686, version 2.6.37~rc4-1~experimental.1 Unfortunately there are a lot of interesting patches in that range, so we will probably need a little more data to track this down. So I suggested: - trying suspend-to-disk (with echo disk /sys/power/state ) and seeing if that reproduces the same trouble - suspending from single-user mode (kernel params single debug) or from an initramfs shell (kernel param break=top) to see if the same problem occurs even if the i915 driver is not loaded yet when the suspend/hibernate happens Other ideas would be welcome, too. I'd be happy to get this fixed in squeeze. Jonathan -- 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/20120316235216.GA32646@burratino
Re: base: System freezes at random time after Resume from Suspend (Regression)
Jonathan Nieder wrote: To recap, this bug is about symptoms of memory corruption after suspending to disk on an Acer Aspire 5610, which uses (I think) the 945GM express chipset. This should have read after suspending to RAM. Sorry for the nonsense. -- 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/20120316235953.GA32730@burratino
Re: 915GM: fonts have some corrupted glyphs: strikethrough
found 641665 linux-2.6/3.2.6-1 quit Joachim Breitner wrote: I just had a real, unintentional OOM-situation again and now all my fonts are garbled again (I hope I don’t make typos, I am typing this semi-blind :-)), so the problem is definitely _not_ yet fixed in unstable. Thanks. Nice to know. Was the corruption in the background image of X mentioned in http://bugs.debian.org/641665#47 reproducible, and does it only happen in OOM-situations? If so, maybe that would be a good angle of attack --- can you check if it happens with xserver-xorg-video-intel from experimental (SNA)? Jonathan -- 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/20120226171313.GA12793@burratino
Re: 915GM: fonts have some corrupted glyphs: strikethrough
Vítor De Araújo wrote[1]: After upgrading to testing, some X11 apps, notably Iceweasel, started to present font rendering errors (characters missing parts). Cyril Brulebois wrote: please try installing libpixman-1-0 0.24.4-1 from sid first. That should fix a bunch of issues. Vítor De Araújo wrote: Recently the machine that presented this problem stopped working. I may be able to get it to work in the following days, but I can't be sure. If I do, I will check it, but I wouldn't count on that... Thanks. Joachim, you experienced vaguely similar symptoms if I remember correctly[2]. Did these occur always or only after hibernation? Do you still experience them? If not, do you remember if some upgrade (like pixman or xserver-xorg-video-intel) fixed it? Sorry for the slow response, Jonathan [1] http://bugs.debian.org/641665 [2] http://lists.debian.org/debian-devel/2011/09/msg00523.html -- 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/20120219042204.GG13188@burratino
Re: 915GM (Eee PC 900): fonts have some corrupted glyphs: strikethrough
Hi again, Vítor De Araújo wrote: After upgrading to testing, some X11 apps, notably Iceweasel, started to present font rendering errors (characters missing parts). Thanks for a nice report. I'm curious about two things: - does 3.2.4-1 from sid behave any differently? (I'd expect it doesn't.) - does upgrading xserver-xorg-video-intel to the version from experimental help? (I am hoping it will.) An answer of the form no, I don't have time to check these things is fine too, and would help us decide what to do next. Hope that helps, Jonathan -- 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/20120215195109.GA23950@burratino
Re: [squeeze - 2.6.36 regression] holes in characters rendered on screen in X
John Hughes wrote: I've created /usr/share/X11/xorg.conf.d/15-debugwait-hack.conf containing that snippet. The log shows: [57.316] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [57.316] (==) intel(0): RGB weight 888 [57.316] (==) intel(0): Default visual is TrueColor [57.316] (**) intel(0): Option DebugWait true [57.316] (II) intel(0): Integrated Graphics Chipset: Intel(R) 945GM [57.316] (--) intel(0): Chipset: 945GM [57.316] (**) intel(0): Relaxed fencing disabled [57.316] (**) intel(0): Wait on SwapBuffers? enabled [57.316] (**) intel(0): Triple buffering? enabled It'll take a while to see whether that makes the problem go away. I'll send a message the moment I see the problem again, or in a few days if it seems fixed. If I remember correctly, your kernel is 3.3-rc1 plus an unrelated keyboard handling patch. Am I correct in guessing that the glitches in font rendering didn't happen again? I hear that the way forward is SNA, which is enabled in the xserver-xorg-video-intel package in experimental. I don't know if it requires any particular patches on top of linus's master for kernel-side support. cc-ing the Debian intel driver maintainers in case they can give a hint. Thanks, Jonathan -- 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/20120209215327.GA2981@burratino
Re: [RV710] using startx results in black screen with locked hardware
reassign 606112 xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 quit Hi, On 2010-12-06, Andreas wrote: If I am using kernel-image 2.6.32-5-amd64 the X server does not start correctly, the screen will be black and mouse and keyboard does not work anymore. The system could be shutdown using power-button. I am using standard radeon-driver (xorg-driver). [...] The problem does not occur with kernel 2.6.30-2-amd64. Therefore I think it could be related to kernel-mode switching. [...] If you using the latest (2010-12-08 9:47 MET) radeon-driver from git-repository (git://anongit.freedesktop.org/xorg/driver/xf86-video-ati) the X-server will start correctly now with an linux-image-2.6.32-5-amd64 image Thanks to hint by Patrick. Thanks, reassigning. dmesg and Xorg.0.log at [1]. X maintainers, does this look familiar? Does the radeon driver need an update in squeeze? [1] http://bugs.debian.org/606112 [...] In the /var/log/message I could find ff. entries: - 8 - 8 pci :01:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [drm] Initialized drm 1.1.0 20060810 [drm] radeon kernel modesetting enabled. [drm] radeon: Initializing kernel modesetting. [drm] register mmio base: 0xFDFE [drm] register mmio size: 65536 ATOM BIOS: 11X [drm] Clocks initialized ! [drm] Detected VRAM RAM=256M, BAR=256M [drm] RAM width 64bits DDR [TTM] Zone kernel: Available graphics memory: 1029290 kiB. [drm] radeon: 256M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. radeon :01:00.0: radeon: using MSI. [drm] radeon: irq initialized. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] Loading RV710 Microcode platform radeon_cp.0: firmware: requesting radeon/RV710_pfp.bin platform radeon_cp.0: firmware: requesting radeon/RV710_me.bin platform radeon_cp.0: firmware: requesting radeon/R700_rlc.bin [drm] ring test succeeded in 1 usecs [drm] radeon: ib pool ready. [drm] ib test succeeded in 0 usecs [drm] Radeon Display Connectors [drm] Connector 0: [drm] VGA [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [drm] Encoders: [drm] CRT2: INTERNAL_KLDSCP_DAC2 [drm] Connector 1: [drm] HDMI-A [drm] HPD1 [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 2: [drm] DVI-I [drm] HPD4 [drm] DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c [drm] Encoders: [drm] CRT1: INTERNAL_KLDSCP_DAC1 [drm] DFP2: INTERNAL_UNIPHY2 composite sync not supported [drm] fb mappable at 0xD0142000 [drm] vram apper at 0xD000 [drm] size 3145728 [drm] fb depth is 24 [drm]pitch is 4096 Console: switching to colour frame buffer device 128x48 fb0: radeondrmfb frame buffer device registered panic notifier [drm] Initialized radeon 2.0.0 20080528 for :01:00.0 on minor 0 -- 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/20120125225101.GA2707@burratino
Bug#656375: libdrm-intel1: screen corruptions, kernel message *ERROR* Prepared flip multiple times
reassign 656375 src:linux-2.6 3.1.8-2 reassign 655152 src:linux-2.6 3.1.6-1 severity 655152 important merge 656375 655152 affects 655152 + xserver-xorg-video-intel quit Witold Baryluk wrote: After logging into GNOME, I started getting LOTS of [ 239.494761] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times in kernel log repeated ever few microseconds. Kernel log = kernel bug. :) Reassigning. -- 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/20120121085521.GA2132@burratino
Bug#655753: [PATCH/RFC] xdm.init: do not start if text option is in kernel commandline
Package: xdm Version: 1:1.1.11-1 Severity: wishlist Tags: patch Hi, Since two years ago (gdm version 2.20.7-2), the gdm and gdm3 packages have supported a text option on the kernel command line to not automatically start up the display manager at boot. I would like to be able to point to this option when asking people to debug in a non-graphical environment. The following patch has the downside that even an explicit /etc/init.d/xdm start does not start xdm when this option is in /proc/cmdline. So I would be happier if there is some better way to implement this. Ideas? Thanks, Jonathan --- debian/changelog |6 ++ debian/xdm.init |3 +++ 2 files changed, 9 insertions(+), 0 deletions(-) diff --git a/debian/changelog b/debian/changelog index 993408d5..5112084e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +xdm (1:1.1.11-2) UNRELEASED; urgency=low + + * xdm.init: do not start xdm if the word text is found in /proc/cmdline. + + -- Jonathan Nieder jrnie...@gmail.com Fri, 13 Jan 2012 14:46:55 -0600 + xdm (1:1.1.11-1) unstable; urgency=low [ Joe Hansen ] diff --git a/debian/xdm.init b/debian/xdm.init index 4127dffe..564a4b13 100644 --- a/debian/xdm.init +++ b/debian/xdm.init @@ -65,6 +65,9 @@ case $1 in [ $(cat $DEFAULT_DISPLAY_MANAGER_FILE) != $DAEMON ]; then echo Not starting X display manager (xdm); it is not the default \ display manager. +elif grep -wqs text /proc/cmdline; then + echo Not starting X display manager (xdm); found 'text' in \ +kernel command line. else log_daemon_msg Starting X display manager xdm start-stop-daemon --start --quiet $SSD_START_ARGS \ -- 1.7.8.3 -- 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/20120113205636.GA20692@burratino
Bug#384712: Translation teams should work on Xt applications localization too
tags 384712 + upstream quit Hi Samuel, Samuel Thibault wrote: the attached files are the ones that the xterm package should put in /etc/X11/fr_FR@euro/app-defaults/ for French localization (some UTF-8 versions should also be put into /etc/X11/fr_FR.UTF-8/app-defaults/) Sounds like a sensible thing to do. [...] *mainMenu*logging*Label: Loguer vers un fichier *mainMenu*print*Label: Imprimer la fenêtre *mainMenu*print-redirect*Label: Rediriger vers l'imprimante I'd like a complete translation to play with and send as a test case to go along with a strawman patch to make make install do the right thing. Missing strings, with rough translations en franglais for your amusement: Full Screen - Plein écran Print-All Immediately - Enregistrer le contenu de la fenêtre Print-All on Error - Enregistrer le contenu de la fenêtre sur erreur Termcap Function-Keys - Touches de fonction Termcap Keep Selection - N'abandonner pas la sélection Enable Bell Urgency - Active la conseil d'urgence sur alerte Packed Font - Caractères compressés UTF-8 Fonts - Police UTF-8 Allow Color Ops - Autoriser opérations sur couleur Allow Font Ops - Autoriser opérations sur la police (yech) Allow Termcap Ops - Autoriser opérations de termcap Allow Title Ops - Autoriser la modification de la titre Allow Window Ops - Autoriser la manipulation de la fenêtre Corrections? Then if Thomas is fine with it, we can send the translation to tra...@traduc.org for review. Thanks, Jonathan -- 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/20120107041246.ga8...@elie.hsd1.il.comcast.net
Re: Console turns black during boot.
Hi Alan, Alan Zimmerman wrote: I revisited this problem tonight, and it seems related to the xserver-xorg-video-intel package. In desperation, I uninstalled it. # uname -a Linux alanz-laptop 3.1.0-1-686-pae #1 SMP Mon Nov 14 08:24:20 UTC 2011 i686 GNU/Linux It now boots without problems. [...] Extract from /var/log/Xorg.0.log --- [39.149] (II) LoadModule: intel [39.251] (WW) Warning, couldn't open module intel When the console turns black, is the machine still usable? (For example, can you use ctrl-alt-delete to reboot?) Please also check whether booting in recovery mode with xserver-xorg-video-intel installed works. If it does, please get dmesg output and output from /usr/share/bug/xserver-xorg-video-intel/script 31 after booting and reproducing the problem. It should be possible to get this information by either driving blind or ssh-ing in from another machine. Thanks and hope that helps, Jonathan -- 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/20111222101617.GB6548@elie.Belkin
Bug#651915: xserver-xorg-video-intel: Panning broken on 915GM
Package: xserver-xorg-video-intel Version: 2:2.17.0-1 Severity: normal Dear Maintainer, I'm using a Asus eeePC 701 which has a native resolution of 800x480. I wish to be able to pan the screen to something bigger sometimes, like 1024x768, using xrandr --output LVDS1 --panning 1024x768 Since several months (I can't remember when though), panning which is used to work as expected with the previous command is now behaving strangely: although it seems the screen gets bigger (application have more room and the right and the bottom), I can't pan the screen using the mouse as before. When I moved to the side of the screen, it moves at most for about 1 pixel and that's all. So I can't see the portions of the windows which are out of the screen. This used to work 5 or 6 months ago, with xserver-xorg-video-intel 2.15.0-3 I guess (I'm not sure however). Thanks, Jonathan -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Feb 9 2008 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2048200 Nov 30 01:08 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) Xorg X server configuration file status: -rw-r--r-- 1 root root 536 Dec 8 14:00 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section InputDevice Identifier synaptics Driver synaptics # Activate tap-to-click Option MaxTapTime180 Option TapButton11 #Option EmulateMidButtonTime 75 # Activate Horizontal scrolling Option HorizEdgeScroll on # Activate SHM config to modify/monitor from running X Option SHMConfig on EndSection Section ServerLayout Identifier Xandros InputDevicesynaptics EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 Kernel version (/proc/version): --- Linux version 3.0.0-2-686-pae (Debian 3.0.0-6) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-9) ) #1 SMP Wed Nov 2 05:29:50 UTC 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 28518 Dec 13 12:13 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [10.991] X.Org X Server 1.11.2.901 (1.11.3 RC 1) Release Date: 2011-11-28 [10.991] X Protocol Version 11, Revision 0 [10.991] Build Operating System: Linux 2.6.32-5-686-bigmem i686 Debian [10.991] Current Operating System: Linux tetra 3.0.0-2-686-pae #1 SMP Wed Nov 2 05:29:50 UTC 2011 i686 [10.991] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-2-686-pae root=UUID=ad866d8d-3e63-4c31-b10d-a5b104e92117 ro quiet quiet [10.992] Build Date: 29 November 2011 05:01:50PM [10.992] xorg-server 2:1.11.2.901-1 (Cyril Brulebois k...@debian.org) [10.992] Current version of pixman: 0.24.0 [10.992]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [10.992] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [10.992] (==) Log file: /var/log/Xorg.0.log, Time: Mon Dec 12 16:02:18 2011 [10.995] (==) Using config file: /etc/X11/xorg.conf [10.995] (==) Using system config directory /usr/share/X11/xorg.conf.d [10.997] (==) ServerLayout Xandros [10.997] (==) No screen section available. Using defaults. [10.997] (**) |--Screen Default Screen Section (0) [10.997] (**) | |--Monitor default monitor [11.001] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [11.002] (**) |--Input Device synaptics [11.003] (==) Automatically adding devices [11.003] (==) Automatically enabling devices [11.005] (WW) The directory /usr/share/fonts/X11/misc does not exist. [11.005]Entry deleted from font path. [11.005] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [11.005]Entry deleted from font path. [11.005] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. [11.005]Entry deleted from font path. [11.005] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. [11.005]Entry deleted from font path. [11.005] (WW) The directory /usr/share/fonts/X11/Type1 does not exist. [11.005]Entry deleted from font path. [11.005] (WW) The directory /usr/share/fonts/X11/100dpi does not exist. [11.005]Entry deleted from font path
Bug#326200: xterm: please set eightBitInput: false by default so Alt is usable as such
Reuben Thomas wrote: On 4 December 2011 17:55, Jonathan Nieder jrnie...@gmail.com wrote: Sounds sensible to me. I think the first step is to file a bug against debian-policy with X-Debbugs-Cc pointing to the relevant maintainers, so the new Right Thing To Do™ can be documented to avoid future regressions. Could you possibly file that bug? Filed: http://bugs.debian.org/651035 -- 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/20111205080338.ge6...@elie.hsd1.il.comcast.net
Bug#326200: xterm: please set eightBitInput: false by default so Alt is usable as such
Reuben Thomas wrote: For xterm, kterm and xvt, the simplest thing to do would seem to be to add a suitable default resource to the various /etc/X11/app-defaults files. (xvt doesn't install such a file, but since it respects resources it presumably could.) For mlterm a simple patch to reverse the default would be required. How does this sound? Sounds sensible to me. I think the first step is to file a bug against debian-policy with X-Debbugs-Cc pointing to the relevant maintainers, so the new Right Thing To Do™ can be documented to avoid future regressions. It feels awkward to give advice like this without doing anything myself. Please don't take it as authoritative --- what the people actually working on these packages are happy with is more important. Many thanks, Jonathan -- 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/20111204165504.ga3...@elie.hsd1.il.comcast.net
Bug#651035: please decide how terminals should report Alt+letter combinations
Package: debian-policy Version: 3.9.2.0 Severity: wishlist X-Debbugs-Cc: Reuben Thomas r...@sc3d.org, xt...@packages.debian.org, kt...@packages.debian.org, x...@packages.debian.org, mlt...@packages.debian.org Hi, Reuben Thomas reported[1]: Please set eightBitInput: false by default so that, as in konsole and gnome-terminal, Alt+letter combinations work in, for example, bash, out of the box. Then there was a lot of discussion. I expect you understand the issues better than I do, but just to have something to pick at, here's an xterm-centric summary. meta and alt are typically the same key[2]. From now on, I will assume that meta and alt are the same key, although I understand that in some configurations they are not so. There are two conventions for reporting that the meta modifier was held: (a) precede the reported keypress with ESC, or (b) set the high bit on the reported keypress. The standard way to switch between conventions is the eightBitInput resource[3]. Applications have some control of which convention is used: the terminfo smm/rmm capabilities allow an application using the terminal to toggle eightBitInput, overriding the user[4]. Unfortunately, applications have no standard way to discover the most important thing, which is whether when the human operator pressed alt she intended to get the meta behavior after all. It is also a common shortcut for typing alternate characters (e.g., alt+0 for the a degree sign). Proposal: i. All terminals should send ESC for meta by default. ii. The terminfo entries used for terminals provided in Debian should not advertise the smm/rmm capabilities. iii. When the smm/rmm capatibilities are not advertised, applications should understand that ESC means meta and if the user overrides the terminal behavior to set the high bit instead, it means that the input represents alternate character, not meta. (ii) allows applications to play tricks with smm for the benefit of inconsistently configured systems without breaking the behavior on Debian. According to this proposal, [5] is not a bug. Reuben made a quick survey of the terminals that would have to be patched (see [1]), and the terminals he said would need to be changed are listed in X-Debbugs-Cc. Thoughts? Improvements? Proposed wording? Jonathan sending this at Reuben's request. I don't have a horse in this race --- I use AltGr for those hard-to-type characters and have never found much use for Meta+foo keybindings. Comments and other help from people affected would of course be welcome. [1] http://bugs.debian.org/326200 [2] From xterm's control sequence reference: Many keyboards have keys labeled Alt. Few have keys labeled Meta. However, xterm’s default translations use the Meta modifier. Common keyboard configurations assign the Meta modifier to an Alt key. [3] man xterm: metaSendsEscape (class MetaSendsEscape) If true, Meta characters (a character combined with the Meta modifier key) are converted into a two-character sequence with the character itself preceded by ESC. This applies as well to function key control sequences, unless xterm sees that Meta is used in your key translations. If false, Meta characters input from the keyboard are handled according to the eightBitInput resource. The default is false. [4] From http://bugs.debian.org/534192: xterm does in fact toggle the eightBitInput resource setting when the terminfo smm/rmm capabilities are sent. [5] http://bugs.debian.org/574396 -- 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/20111205072358.gb6...@elie.hsd1.il.comcast.net
Bug#326200: xterm: please set eightBitInput: false by default so Alt is usable as such
Hi again, Riku Saikkonen wrote: I suppose this clearly is not something that should be changed while in a freeze, especially since xterm in Debian has had the current behaviour for so many years. But perhaps it would be possible to coordinate a consistent behaviour for all the terminals in the next Debian release after this frozen one? That sounded sensible to my innocent bystander ears. :) Reuben, would you be willing to coordinate this (or do you know anyone who would be)? That means: 1. Finding out what the major terminals in Debian currently do. If xterm is not the odd man out, finding a consensus, for example by reporting a bug against the debian-policy package with X-Debbugs-Cc pointing to the relevant maintainers. 2. Proposing a patch for xterm bug#326200. 3. Proposing a patch for bash bug#574396. 4. Being ready to help people respond to bugs that arise from the above. If one wants to make this change and find relevant bugs in time for wheezy, now's probably the time. Thanks and hope that helps, Jonathan -- 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/20111201215822.ga5...@elie.hsd1.il.comcast.net
Bug#326200: xterm: please set eightBitInput: false by default so Alt is usable as such
Reuben Thomas wrote: I don't actually use Debian at present; I use Ubuntu. That may limit my usefulness. However, at the very least, I'd be happy to try doing this: Thanks. Unless the Ubuntu maintainers want to make this change as a differentiating feature instead of pushing it in Debian (and I can't see the point to that), I think you are still affected by what happens in Debian anyway. [...] Basic use of apt-cache search and grep suggests the following: Yep, that seems like a sensible list. I'd be quite happy to whip through that lot and see what the defaults are. Great. It might even be possible to automate that with some ncurses magic, but don't ask me how. :) -- 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/20111201231655.ge6...@elie.hsd1.il.comcast.net
Bug#632419: support for serial pointer device
clone 632419 -1 -2 retitle -1 xf86-input-mouse: package description should explain relationship to evdev # http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=86;bug=632419 tags -1 + patch retitle -2 xf86-input-evdev: please Suggests: inputattach reassign -2 xserver-xorg-input-evdev 1:2.6.0-3 # http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=91;bug=632419 tags -2 + patch quit Hi Axel, a...@users.sourceforge.net wrote: Thank you very much for putting this together. After reading these and other texts, I believe that there should be an easy-to-use tool to configure undetectable (usually legacy) hardware in a dialogue during installation or later. Thanks for a reminder! Cloning the bug for the two subtasks that already have patches. If you make any progress on this (e.g., by writing a simple script to detect the need for inputattach at some appropriate time), please feel free to let us know. Cheers, Jonathan -- 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/20111015195454.gc12...@elie.hsd1.il.comcast.net
Bug#639651: xserver-xorg-video-r128: FTBFS: Package 'xorg-server' requires 'dri2proto = 2.6' but version of DRI2Proto is 2.3
Cyril Brulebois wrote: Julien Cristau jul...@cristau.org (29/08/2011): s/-core/-dev Same in the changelog. Gah --- I had fixed that locally but didn't manage to remember to regenerate the patch. Bad jcristau, not following debian/README.source. :p Fixed in git. Not a huge deal anyway, r128 builds within unstable: https://buildd.debian.org/status/package.php?p=xserver-xorg-video-r128 Thanks, both. -- 8 -- Subject: The bumped xserver-xorg-dev dependency is dri2proto, not glproto --- debian/changelog |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/debian/changelog b/debian/changelog index 1aa34a71..414e593b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,6 +1,6 @@ xorg-server (2:1.11.0-2) UNRELEASED; urgency=low - * Bump glproto dependency for xserver-xorg-dev (Closes: #639651). + * Bump dri2proto dependency for xserver-xorg-dev (Closes: #639651). -- Cyril Brulebois kibi@Fallonne Mon, 29 Aug 2011 13:18:50 +0200 -- 1.7.6 -- 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/20110829181751.gb9...@elie.gateway.2wire.net
Bug#639651: xserver-xorg-video-r128: FTBFS: Package 'xorg-server' requires 'dri2proto = 2.6' but version of DRI2Proto is 2.3
Package: xserver-xorg-dev Version: 2:1.10.99.901+git20110731-1 Tags: patch Hi, Trying to build xserver-xorg-video-r128 today: checking for XORG... no configure: error: Package requirements (xorg-server = 1.2 xproto font Package 'xorg-server' requires 'dri2proto = 2.6' but version of DRI2P Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XORG_CFLAGS and XORG_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. dh_auto_configure: ../configure --build=x86_64-linux-gnu --prefix=/usr make: *** [build] Error 2 Well, I asked for it. It seems that the dri2 requirement bumped with 932513e2 (DRI2/GLX: use new swap event types, 2011-05-05). How about this patch? -- 8 -- Subject: Bump xserver-xorg-core Depends on x11proto-dri2-dev This avoids build failures in drivers that use PKG_CHECK_MODULES(XORG, [xorg-server]): Package 'xorg-server' requires 'dri2proto = 2.6' but version of DRI2Proto is 2.3 --- debian/changelog |7 +++ debian/control |2 +- 2 files changed, 8 insertions(+), 1 deletions(-) diff --git a/debian/changelog b/debian/changelog index ac07882c..42351787 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +xorg-server (2:1.11.0-1.1) local; urgency=low + + * xserver-xorg-core: Bump dependency on x11proto-dri2-dev, needed +since xorg-server.pc pulls a newer dri2proto version. + + -- Jonathan Nieder jrnie...@gmail.com Sun, 28 Aug 2011 20:39:07 -0500 + xorg-server (2:1.11.0-1) unstable; urgency=low [ Julien Cristau ] diff --git a/debian/control b/debian/control index ea69deb1..f822fc9f 100644 --- a/debian/control +++ b/debian/control @@ -163,7 +163,7 @@ Depends: x11proto-video-dev, x11proto-randr-dev (= 1.2.99.3), x11proto-render-dev (= 2:0.11), - x11proto-dri2-dev (= 2.3), + x11proto-dri2-dev (= 2.6), x11proto-fonts-dev, x11proto-xinerama-dev, x11proto-kb-dev, -- 1.7.6 -- 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/20110829015343.ga28...@elie.gateway.2wire.net
Re: libwx-perl: Error: Unable to initialize gtk, is DISPLAY set properly?
Hi, Clint Adams wrote: On Tue, Aug 16, 2011 at 04:12:38PM +0200, Aurelien Jarno wrote: reassign 630129 fakeroot retitle 630129 fakeroot doesn't simulate access() properly affects 630129 xvfb thanks Okay, I'll revert the access() change. Thanks, I agree with that choice. Incidentally, why is libwx-perl running its test suite in the binary target instead of build? $ debian/rules build make: `build' is up to date. Ah. diff --git i/debian/changelog w/debian/changelog index 2bc4df9f..17fe3889 100644 --- i/debian/changelog +++ w/debian/changelog @@ -1,3 +1,9 @@ +libwx-perl (1:0.98-1.1) local; urgency=low + + * mark debian/rules build target phony + + -- Jonathan Nieder jrnie...@gmail.com Wed, 17 Aug 2011 14:57:13 -0500 + libwx-perl (1:0.98-1) unstable; urgency=low * New upstream release diff --git i/debian/rules w/debian/rules index fe13d5b9..602454e0 100755 --- i/debian/rules +++ w/debian/rules @@ -3,6 +3,10 @@ %: dh $@ +.PHONY: build +build: + dh $@ + PACKAGE=$(shell dh_listpackages) TMP =$(CURDIR)/debian/$(PACKAGE) -- -- 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/20110817195849.gc31...@elie.gateway.2wire.net
Bug#632419: [a...@users.sourceforge.net: Re: support for serial pointer device]
reopen 632419 tags 632419 = ---BeginMessage--- Hi, On Thu, 7 Jul 2011, Jonathan Nieder wrote: a...@users.sourceforge.net wrote: Moreover, the configuration does not work anymore as it is; it causes errors. What are those errors? That might be an X bug. (Ideally, upgrades of any program should not break working configurations without warning.) Quite. I am at a different computer now; one thing I specifically remember is X complaining about fbcon missing even though nothing of that name is mentioned in the config file. Accessing the two heads did not work immediately, either. I stopped trying quickly because everything except the serial mouse worked out of the box (more or less). But even if I make it work or create a barebones X configuration file just with the Pointer Device set to /dev/ttyS0, the pointer is not functional. If this is true and xserver-xorg-input-mouse is installed, then it would definitely be an X bug. Interesting. I'll have to check this. I was not aware of the necessity of installing extra packages for X. If it works with Input Attach, doesn't that mean all parts of X are functional? program, since the general approach to X installation nowadays is to autodetect as much as possible. The idea of a debconf prompt when installing and no pointer device is present sounds more interesting, though it might be hard to get right. Reassigning to the X maintainers in case someone there is interested. Thanks for writing, and hope that helps. Thank _you_. This sounds like the perfect approach, as it will get GPM c. configured as well. Cheers, Axel ---End Message---
Re: support for serial pointer device
retitle 632419 X: please ask for (serial) mouse device name at installation time if no pointer is detected reassign 632419 xserver-xorg-input-mouse 1:1.5.0-2 severity 632419 wishlist quit Hi, a...@users.sourceforge.net wrote: X works differently in this distribution. I needed a configuration file in Lenny to get the two separate screens to work. It was not a perfect setup as one screen was distorted but I found a workaround for that. In Squeeze, this is no longer necessary, both screens can be configured using the Monitors menu item, and there is no distortion. Moreover, the configuration does not work anymore as it is; it causes errors. What are those errors? That might be an X bug. (Ideally, upgrades of any program should not break working configurations without warning.) But even if I make it work or create a barebones X configuration file just with the Pointer Device set to /dev/ttyS0, the pointer is not functional. If this is true and xserver-xorg-input-mouse is installed, then it would definitely be an X bug. This takes me back to my original point: If it was possible to use a serial mouse in the past without installing separate software which is not available at installation time, why was this functionality removed? If it is not possible to recognize serial pointer devices, the installation process should include a question if no other pointer device is discovered. By this functionality do you mean X's configuration process (xf86setup, etc)? If someone is interested in working on that, it might be possible to revive it, but it would have to be a separate program, since the general approach to X installation nowadays is to autodetect as much as possible. The idea of a debconf prompt when installing and no pointer device is present sounds more interesting, though it might be hard to get right. Reassigning to the X maintainers in case someone there is interested. Thanks for writing, and hope that helps. Jonathan -- 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/20110707171525.GB25830@elie
Bug#632419: support for serial pointer device
Hi again, Jonathan Nieder wrote: a...@users.sourceforge.net wrote: But even if I make it work or create a barebones X configuration file just with the Pointer Device set to /dev/ttyS0, the pointer is not functional. If this is true and xserver-xorg-input-mouse is installed, then it would definitely be an X bug. Hm, /usr/share/doc/xserver-xorg-input-mouse/README.gz says: The old Pointer section has been replaced by a more general InputDevice section. The following is a minimal example of an InputDevice section for a mouse: Section InputDevice [...] That text dates back to long ago (before version 1.1.2 of the X mouse driver at least), and the example xorg.conf you sent uses an InputDevice section, so I assume you're doing okay there. More to the point, /usr/share/doc/xserver-xorg/NEWS.Debian.gz says: xserver-xorg (1:7.4+1) unstable; urgency=low * Changes in handling of input devices Starting from this version, input devices are no longer configured statically in /etc/X11/xorg.conf. Instead, input devices are detected at runtime (and can be hotplugged) and configured individually. The default keyboard layout is shared with the console and is configured in /etc/default/keyboard. As a result, devices configured in xorg.conf to use the mouse or kbd driver are ignored by the X server by default. For more details, see: http://who-t.blogspot.com/2008/12/evdev-xorgconf-hal-and-other-fud.html http://who-t.blogspot.com/2008/10/new-keyboard-configuration-handling.html and continues by explaining that one might need to disable AutoAddDevices to keep manual configurations working. Perhaps that information was not shown on upgrade for some reason. -- 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/20110707173203.GA26180@elie
Bug#632419: support for serial pointer device
Julien Cristau wrote: On Thu, Jul 7, 2011 at 12:15:25 -0500, Jonathan Nieder wrote: What are those errors? That might be an X bug. (Ideally, upgrades of any program should not break working configurations without warning.) Ideally, yes, but serial mice are enough of a corner case these days that they're not worth the complexity. Sorry, messages crossed. This example doesn't fall in the category I mentioned above anyway, since the changes were documented in NEWS.Debian.gz files. [...] No. Serial mice should be switched over to inputattach to get a proper input device that X will use. Perhaps xserver-xorg-input-evdev should have Suggests: inputattach. It would also be nice to document this in the xserver-xorg-input-mouse package description: Most configurations on Linux will use the evdev driver and do not need this package. See the inputattach package if your mouse is not automatically detected by the kernel, for example because it is a serial mouse. -- 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/20110707173816.GB26180@elie
Bug#632419: [PATCH xserver-xorg-input-mouse] Explain relationship to evdev in the package description
Some sysadmins on Linux may be expecting the X mouse driver to get
their mouse to work. Help them out by pointing to the tools they
can use instead:
- xserver-xorg-input-evdev, to allow the X server to make use of
the Linux kernel's event device interface;
- inputattach, to make input devices (e.g., serial mice) that
cannot be easily autodetected visible to the Linux kernel.
Text inspired by the introduction in README.
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
Julien Cristau wrote:
On Thu, Jul 7, 2011 at 12:38:16 -0500, Jonathan Nieder wrote:
It would also be nice to document this in the xserver-xorg-input-mouse
package description:
[...]
Sounds like a good idea.
How about this?
debian/changelog |7 +++
debian/control |8 +++-
2 files changed, 14 insertions(+), 1 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 42342912..adc39fdb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+xserver-xorg-input-mouse (1:1.7.1-2) UNRELEASED; urgency=low
+
+ * Describe relationship to xserver-xorg-input-evdev in the long
+description.
+
+ -- Jonathan Nieder jrnie...@gmail.com Thu, 07 Jul 2011 13:09:57 -0500
+
xserver-xorg-input-mouse (1:1.7.1-1) unstable; urgency=low
* New upstream release:
diff --git a/debian/control b/debian/control
index a40be49a..79e77d65 100644
--- a/debian/control
+++ b/debian/control
@@ -26,7 +26,13 @@ Depends:
Provides:
${xinpdriver:Provides}
Description: X.Org X server -- mouse input driver
- This package provides the driver for mouse input devices.
+ This package provides a driver for mouse input devices. It mainly used
+ on non-Linux operating systems such as BSD and Solaris. Most
+ configurations on Linux will use evdev, the kernel's event delivery
+ mechanism, and do not need this package.
+ .
+ See the inputattach package if your mouse is not automatically
+ detected by the Linux kernel, for example because it is a serial mouse.
.
More information about X.Org can be found at:
URL:http://www.X.org
--
1.7.6
--
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/20110707181231.GC26180@elie
Bug#632419: [PATCH xserver-xorg-input-evdev] Suggest inputattach for serial mouse support
Encouraged-by: Julien Cristau jcris...@debian.org
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
Jul 07, 2011 at 07:44:44PM +0200, Julien Cristau wrote:
On Thu, Jul 7, 2011 at 12:38:16 -0500, Jonathan Nieder wrote:
Perhaps xserver-xorg-input-evdev should have Suggests: inputattach.
[...]
Sounds like a good idea.
And here's a simple patch for that.
debian/changelog |2 ++
debian/control |2 ++
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 249ca77e..2328de65 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
xserver-xorg-input-evdev (1:2.6.0-3) UNRELEASED; urgency=low
* Remove obsolete .manpages.
+ * Suggest inputattach, since it can make serial-attached input devices
+(e.g., serial mice) available through evdev.
-- Timo Aaltonen tjaal...@ubuntu.com Tue, 15 Mar 2011 13:43:58 +0200
diff --git a/debian/control b/debian/control
index f45858ab..967a6aaa 100644
--- a/debian/control
+++ b/debian/control
@@ -25,6 +25,8 @@ Depends:
${shlibs:Depends},
${misc:Depends},
${xinpdriver:Depends},
+Suggests:
+ inputattach
Provides:
${xinpdriver:Provides}
Description: X.Org X server -- evdev input driver
--
1.7.6
--
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/20110707181908.GD26180@elie
Re: gitk: session crash when scrolling to specific lines
retitle 631739 Xorg: segfault in intel_drv when scrolling gitk window to certain lines # files: /usr/lib/xorg/modules/drivers/intel_drv.so reassign 631739 xserver-xorg-video-intel quit Hi Yao Wei, Yao Wei wrote: When scrolling in lxterminal git source: git clone git://lxde.git.sourceforge.net/gitroot/lxde/lxterminal Selecting Add an option to compile with GTK3, then scroll the diff window, and the session crashes which leads me to the login screen. Is this reproducible? Xorg backtrace: Backtrace: [ 8826.553] 0: /usr/bin/Xorg (xorg_backtrace+0x26) [0x4a3836] [ 8826.553] 1: /usr/bin/Xorg (0x40+0x65049) [0x465049] [ 8826.553] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f3c263ed000+0xf020) [0x7f3c263fc020] [ 8826.553] 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f3c23122000+0x20e24) [0x7f3c23142e24] [ 8826.553] 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f3c23122000+0x229a2) [0x7f3c231449a2] [ 8826.554] 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f3c23122000+0x2b0f7) [0x7f3c2314d0f7] [ 8826.554] 6: /usr/bin/Xorg (0x40+0xdd131) [0x4dd131] [ 8826.554] 7: /usr/bin/Xorg (0x40+0xd8559) [0x4d8559] [ 8826.554] 8: /usr/bin/Xorg (0x40+0x32d09) [0x432d09] [ 8826.554] 9: /usr/bin/Xorg (0x40+0x26fae) [0x426fae] [ 8826.554] 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfd) [0x7f3c25126ead] [ 8826.554] 11: /usr/bin/Xorg (0x40+0x2729d) [0x42729d] [ 8826.554] Segmentation fault at address 0x18 [ 8826.554] Fatal server error: [ 8826.554] Caught signal 11 (Segmentation fault). Server aborting And there's seems the same problem but reported in xserver-xorg-video-nouveau package in Ubuntu (while mine occurred in Intel GMA HD). I don't know if it is related: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/659473 Reassigning for further investigation. If you can get a backtrack after installing xserver-xorg-video-intel-dbg, plus run sh /usr/share/bug/xserver-xorg-video-intel/script 3bugscript-output.txt to gather some basic information then that would be very useful. Thanks for reporting it. -- 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/20110627033835.GA2768@elie
Bug#630965: [linux] no supported touchpad found (please add a MatchDevicePath directive to 50-synaptics.conf)
Package: xserver-xorg-input-synaptics Version: 1.4.0-1+exp1 Severity: minor Justification: cosmetic File: /usr/share/X11/xorg.conf.d/50-synaptics.conf Tags: upstream As explained by who-t at [1], X is happier[*] and faster with the final line of Section InputClass Identifier touchpad catchall Driver synaptics MatchIsTouchpad on MatchDevicePath /dev/input/event* EndSection included xorg.conf.d/50-synaptics.conf. I am not sure if this will work for kfreebsd and hurd (probably not). Filing so as not to forget. The upstream tag is because this is not distro-specific, so the right way to fix it would be with makefile magic. Regards, Jonathan [1] http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html [*] without, one gets messages like this in Xorg.0.log: [72.560] (**) Option Device /dev/input/mouse0 [72.560] (--) SynPS/2 Synaptics TouchPad: invalid x-axis range. defaulting to 1615 - 5685 [72.560] (--) SynPS/2 Synaptics TouchPad: invalid y-axis range. defaulting to 1729 - 4171 [72.560] (--) SynPS/2 Synaptics TouchPad: invalid pressure range. defaulting to 0 - 256 [72.560] (--) SynPS/2 Synaptics TouchPad: invalid finger width range. defaulting to 0 - 16 [72.581] (EE) Query no Synaptics: 6003C8 [72.581] (--) SynPS/2 Synaptics TouchPad: no supported touchpad found [72.582] (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware. [72.690] (EE) PreInit returned 11 for SynPS/2 Synaptics TouchPad [72.690] (II) UnloadModule: synaptics [72.691] (II) Unloading synaptics X server symlink status: lrwxrwxrwx 1 root root 13 Jan 31 08:49 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1956416 Jun 17 11:15 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc M880G [Mobility Radeon HD 4200] [1002:9712] /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.0.0-rc2-00559-g603904f (jrn@elie) (gcc version 4.6.1 20110611 (prerelease) (Debian 4.6.0-13) ) #38 SMP PREEMPT Sun Jun 12 18:56:53 CDT 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 36678 Jun 1 16:03 /var/log/Xorg.1.log -rw-r--r-- 1 root root 35397 Jun 12 19:05 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [71.267] X.Org X Server 1.10.2 Release Date: 2011-05-28 [71.269] X Protocol Version 11, Revision 0 [71.271] Build Operating System: Linux 2.6.39-1-amd64 x86_64 Debian [71.272] Current Operating System: Linux elie 3.0.0-rc2-00559-g603904f #38 SMP PREEMPT Sun Jun 12 18:56:53 CDT 2011 x86_64 [71.273] Kernel command line: BOOT_IMAGE=/vmlinuz-3.0.0-rc2-00559-g603904f root=/dev/mapper/data-root ro quiet [71.275] Build Date: 30 May 2011 10:23:14AM [71.276] xorg-server 2:1.10.2-1 (Cyril Brulebois k...@debian.org) [71.278] Current version of pixman: 0.21.8 [71.279]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [71.283] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [71.290] (==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 12 19:05:16 2011 [71.293] (==) Using system config directory /usr/share/X11/xorg.conf.d [71.295] (==) No Layout section. Using the first Screen section. [71.295] (==) No screen section available. Using defaults. [71.296] (**) |--Screen Default Screen Section (0) [71.296] (**) | |--Monitor default monitor [71.296] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [71.296] (==) Automatically adding devices [71.296] (==) Automatically enabling devices [71.296] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [71.296]Entry deleted from font path. [71.297] (==) 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, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins [71.297] (==) ModulePath set to /usr/lib/xorg/modules [71.297] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [71.298] (II) Loader magic
Bug#630965: [linux] no supported touchpad found (please add a MatchDevicePath directive to 50-synaptics.conf)
Cyril Brulebois wrote: Jonathan Nieder jrnie...@gmail.com (19/06/2011): As explained by who-t at [1], X is happier[*] and faster with the final line of might be the lack of coffee, but “faster”? Sorry for the nonsense; I haven't actually checked (and after thinking about it for a second it doesn't make much sense). The comment that led me to say it: | It reduces the startup of X from almost 4 to a bit more than one | second. -- 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/20110619104804.GA19963@elie
Re: I'm having random freezes on a GM965
Julien Cristau wrote: What part of it? The i965 driver segfaulting on allocation failure: https://bugs.freedesktop.org/show_bug.cgi?id=36372#c2 -- 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/20110613090810.GE4570@elie
Re: I'm having random freezes on a GM965
tags 620480 - fixed-upstream quit Hi X Strike Force, Jaime Alberto Silva wrote: since I updated yesterday I get rendering errors mainly of fonts in gnome-terminal. A typical distortion which occurred while typing this email is shown in the attached screenshot. [...] The freezing is gone but I'm still having crashes. [...] https://bugs.freedesktop.org/show_bug.cgi?id=36372 From the upstream bug: | The stacktrace says otherwise. At least one app on your system is using AIGLX | (i.e. indirect rendering), and your system has a resource leak causing an | allocation failure. Then mesa-7.10 dies due to insufficient defence. Is this a mesa bug? -- 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/20110613030544.GA3699@elie
Re: glibc: causes segfault in Xorg
clone 625521 -1 reassign -1 xserver-xorg-video-ati 1:6.1.14.1-1 # documentation severity -1 minor retitle -1 xserver-xorg-video-ati: package description does not mention it is needed for autoconfiguration tags -1 + patch quit Hi Steve, Steve M. Robbins wrote: I did try to downgrade, but I'm not sure I succeeded. Do you want me to try again? Sorry for a slow response. I imagine the fbdev X driver maintainers will be better able to say what information is useful. I was originally curious about whether there was a glibc regression involved (since it bears on what to do for 2.14.x) but it seems this is not the best example for thinking about that anyway. Anyway, if you want to test the glibc aspect, the new /usr/lib/libc/memcpy-syslog-preload.so might be a convenient way (see libc6 2.13-4's NEWS.Debian.gz). The other loose thread I'm curious about is what triggered the bug in the first place. Maybe xserver-xorg-video-ati was only uninstalled recently? (/var/log/dpkg.log would say.) If the crashes started after an upgrade of xserver-xorg-video-fbdev or something like that, that information might be useful to the fbdev maintainers. I appreciate the added package documentation. Thanks. A while ago I removed the -ati driver and was confusedly puzzling over the package description when I learned an xorg.conf was needed. Should have fixed it then. :) Cloning the bug as a reminder. -- 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/20110512124925.GA15858@elie
Re: glibc: causes segfault in Xorg
reassign 625521 xserver-xorg-video-fbdev 1:0.4.2-4 severity 625521 important retitle 625521 Xorg: crash in shadowUpdatePacked (fbdev trusts virtual size video memory?) tags 625521 + upstream forwarded 625521 https://bugs.freedesktop.org/show_bug.cgi?id=37159 quit Steve M. Robbins wrote: Yes, I believe I deliberately uninstalled it, mistakenly thinking it wasn't needed to run the Radeon server. Thanks much! Forwarded (though that is mostly a formality). https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/711528 looks vaguely similar. -- 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/20110513035452.GA25364@elie
Bug#626013: xorg: At 1360x768 resolution, entire display is slanted
On 05/07/2011 04:01 PM, Cyril Brulebois wrote: Hi, Jonathan Guthrie jguth...@brokersys.com (07/05/2011): On this laptop, using the built-in display, one of the resolutions (1360x768) is unavailable because when it is selected, the entire display is slanted. That is, a vertical bar on the display appears as if it is a slanted line from the upper left to lower right. probably a bug in xserver-xorg-video-intel. After a quick look, I don't think there's a fix for that in current upstream master. I'd suggest filing a bug upstream: http://intellinuxgraphics.org/how_to_report_bug.html Please let us know the bug number/URL so that we can mark it as forwarded there. You might want to give the kernel in experimental a shot (that's an rc for 2.6.39), too. Mraw, KiBi. In my initial report, I neglected to mention that that resolution works just fine when we boot the old 2.6.32 kernel. I have installed and booted into the experimental kernel, and it exhibited the same behavior. I have not filed a defect with the upstream because I wanted to see if you still thought that was a good idea after integrating this new information. If that's still what you suggest, then I'll do it. !DSPAM:447,4dc6c18127841852517182! -- 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/4dc67b2e.80...@brokersys.com
Bug#625521: glibc: causes segfault in Xorg
Michel Dänzer wrote: [ Dropping the libc6 list from CC, as this doesn't seem to have anything to do with libc6 after all ] Yes, sorry for the misdirection. Actually I have a question in mind still. The original report pinned it on libc6 confidently, and I didn't think to question that (shame on me). Steve, did you try downgrading to libc 2.11 and if so did that make the crash go away? So, where does that leave this report? I still suspect the bug is that the fbdev driver doesn't properly handle the virtual directive in SubSection Display, but before reassigning to xserver-xorg-video-fbdev (and most likely remaining dormant at least for a while), I'd like to at least get confirmation that the fbdev driver doesn't crash without the virtual directive. Makes sense. I also see a documentation bug --- how about something like this patch? Signed-off-by: Jonathan Nieder jrnie...@gmail.com --- debian/changelog |9 + debian/control |9 - 2 files changed, 13 insertions(+), 5 deletions(-) diff --git a/debian/changelog b/debian/changelog index 166655c..3d65725 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +xserver-xorg-video-ati (1:6.14.1-2) UNRELEASED; urgency=low + + * Move reference to X.org web page from package descriptions to the +Homepage field. + * Clarify when the xserver-xorg-video-ati wrapper is needed in its +package description. + + -- Jonathan Nieder jrnie...@gmail.com Thu, 05 May 2011 23:44:02 -0500 + xserver-xorg-video-ati (1:6.14.1-1) unstable; urgency=low * New upstream release. diff --git a/debian/control b/debian/control index ee34eca..70e3961 100644 --- a/debian/control +++ b/debian/control @@ -25,6 +25,7 @@ Build-Depends: Standards-Version: 3.9.0 Vcs-Git: git://git.debian.org/git/pkg-xorg/driver/xserver-xorg-video-ati Vcs-Browser: http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-ati.git +Homepage: http://www.X.org Package: xserver-xorg-video-ati Architecture: any @@ -43,8 +44,9 @@ Description: X.Org X server -- AMD/ATI display driver wrapper sub-drivers depending on the hardware. These sub-drivers are brought through package dependencies. . - More information about X.Org can be found at: - URL:http://www.X.org + Users of Rage, Mach, or Radeon boards may safely remove this package + only if they use Driver r128, mach64, or radeon in + /etc/X11/xorg.conf instead of relying on autodetection. . This package is built from the X.org xf86-video-ati driver module. @@ -84,9 +86,6 @@ Description: X.Org X server -- AMD/ATI Radeon display driver driver, which provides additional 3D functionality for some newer Radeon cards, but is not supported. . - More information about X.Org can be found at: - URL:http://www.X.org - . This package is built from the X.org xf86-video-ati driver module. Package: xserver-xorg-video-radeon-dbg -- 1.7.5.1 -- 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/20110506084635.GJ1040@elie
Bug#625521: glibc: causes segfault in Xorg
Aurelien Jarno wrote: Le 04/05/2011 07:43, Jonathan Nieder a écrit : Jonathan Nieder wrote: Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518 which is fixed (sort of) by commit 0354e355 (2011-04-01). Are you sure this is related? I find strange a recent version of xorg is still not fixed No, not sure --- I was only reminded. But it does fit the symptoms well: regression occuring when upgrading to glibc 2.13, consisting of a segfault in memcpy_sse3. (As you suggested) it might be specific to some driver or some aspect of the configuration. The easiest way to confirm would be with valgrind. No, it's not something possible to cherry-pick as it is based on symbol versioning from version 2.14. Also it only really apply to binary-only distribution, in Debian as soon as your rebuild the package, it will use the new 2.14 symbols, and memcpy instead of memmove. That sounds great --- it would take care of upgrades from broken packages in squeeze and as soon as you rebuild a package, there is a chance to fix it. I imagine the release team wouldn't like it much, though. I don't think we can really keep a version in experimental just for that. And reverting that patch means nobody will complain, and issues will never be fixed. Reverting may be the best way in the short term, especially if the upstream fix is four months away. I suppose Steve was right to ask for help on -devel. Maybe someone will come up with a better idea. E.g., how about adopting hjl's suggestion and making the behavior (temporarily) conditional on a LD_DONT_BIND_IFUNC_MEMCPY_TO_MEMMOVE environment variable? -- 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/20110504070503.GA10230@elie
Bug#625521: glibc: causes segfault in Xorg
Hi, Michel Dänzer wrote: On Mit, 2011-05-04 at 00:10 -0500, Jonathan Nieder wrote: Steve M. Robbins wrote: Program received signal SIGSEGV, Segmentation fault. __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:153 153 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: No such file or directory. in ../sysdeps/x86_64/multiarch/memcpy-ssse3.S (gdb) bt #0 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:153 #1 0x73858db1 in shadowUpdatePacked () from /usr/lib/xorg/modules/libshadow.so #2 0x7385843f in ?? () from /usr/lib/xorg/modules/libshadow.so #3 0x0043571d in BlockHandler () #4 0x0045dcda in WaitForSomething () #5 0x004314b2 in ?? () #6 0x004257de in _start () [...] The purpose of shadowUpdatePacked is to copy pixels from a shadow framebuffer to the visible screen. It would be rather pointless for the shadow framebuffer to be contained within the visible screen, so shadowUpdatePacked should always be able to safely use memcpy as far as overlapping areas is concerned. If shadowUpdatePacked is indeed calling memcpy for overlapping areas here, that's probably a bug in the X driver being used. Thanks, Michel. Steve, could you install xserver-xorg-video-radeon-dbg and get a full backtrace (bt full), or even better, run xorg under valgrind and see what it says? -- 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/20110504071834.GB10230@elie
Re: glibc: causes segfault in Xorg
reassign 625521 xserver-xorg-core 2:1.10.1-2 quit Hi, Steve M. Robbins wrote: Xorg now segfaults, with the following in the Xorg.0.log: Program received signal SIGSEGV, Segmentation fault. __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:153 153 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: No such file or directory. in ../sysdeps/x86_64/multiarch/memcpy-ssse3.S (gdb) bt #0 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:153 #1 0x73858db1 in shadowUpdatePacked () from /usr/lib/xorg/modules/libshadow.so #2 0x7385843f in ?? () from /usr/lib/xorg/modules/libshadow.so #3 0x0043571d in BlockHandler () #4 0x0045dcda in WaitForSomething () #5 0x004314b2 in ?? () #6 0x004257de in _start () Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518 which is fixed (sort of) by commit 0354e355 (2011-04-01). Reassigning to xserver-xorg-core. Xorg maintainers, please use memmove here. Thanks and hope that helps, Jonathan -- 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/20110504051048.GH8187@elie
Bug#625521: glibc: causes segfault in Xorg
clone 625521 -1 severity 625521 grave severity -1 important reassign -1 libc6 2.13-0exp1 retitle -1 glibc: memcpy copies down on amd64 tags -1 upstream patch fixed-upstream # sorry for the noise quit Jonathan Nieder wrote: Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518 which is fixed (sort of) by commit 0354e355 (2011-04-01). By the way, in principle that might be a nice commit to cherry-pick. Not sure how to do it safely, though --- backing out the amd64 optimization would hide important bugs that can cause suffering later, while applying upstream's fix would mean that apps linked against libc would use new ABI. I guess reverting glibc-2.13~215 (Improve 64bit memcpy/memmove for Atom, Core 2 and Core i7, 2010-06-30) in sid (but not experimental) and encouraging people to test libc6/experimental might be a good way. Do you know how soon upstream's planning to release 2.14? -- 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/20110504054320.GI8187@elie
Bug#615153: exec: 58: /usr: Permission denied
Michael Tokarev wrote: When you run something under strace, setuid/setgid bits are ignored by the kernel, the processes will run as user who started them. This is significant difference in environment with and without strace. JFYI. Thanks, I should have remembered (allowing ptrace to control setuid programs would be a huge security hole). Sorry for the thinko. invisiblemanguard, could you give an exact set of commands and the exact output produced, when 1) starting X as a normal user 2) starting X as root ? (Generally speaking, unless it involves sending megabytes of data, being concrete when submitting bugs --- i.e., giving the reader a complete account of what happened --- always tends to be helpful.) I'd also still be interested in output from 3) ls -l /usr/bin/X /etc/X11/Xwrapper.config 4) sudo strace -o /tmp/startxlog startx -- 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/20110414073829.GA5870@elie
Bug#615153: exec: 58: /usr: Permission denied
Jonathan Nieder wrote: invisiblemanguard, could you give an exact set of commands and the exact output produced, when 1) starting X as a normal user 2) starting X as root [...] I'd also still be interested in output from 3) ls -l /usr/bin/X /etc/X11/Xwrapper.config 4) sudo strace -o /tmp/startxlog startx This last item (4) should of course include an -f, as in sudo strace -f -o /tmp/startxlog startx Sorry for the sloppiness. -- 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/20110414074439.GA5981@elie
Bug#615153: exec: 58: /usr: Permission denied
Hi Michael, Michael Tokarev wrote: I think it's not necessary. See #618023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618023 The issue we see here is due to bug in dash which is now fixed. This bug, if my theory is correct, should become a duplicate of #618023. How is that possible when (1) the submitter runs testing, not experimental (2) the version introducing that bug did not exist when the bug was reported? -- 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/20110414090216.GA6913@elie
Re: Bug#615975: xserver-xorg: Xorg server segfaults after starting some xclients (xterm, skype...)
(-cc: the bug log for meta-discussion) Hi, John D. Hendrickson and Sara Darnell wrote: diagnosis by deletion ?? it seemed to work after deletion. that's crazy - simply crazy. an it should be there if the wrong thing is on 7100 of course of course. That comment is not helpful. Quit it. A common debugging strategy is to take out complications until the relevant piece of software or configuration is found, and then people can focus on that piece. Stuart and others, thanks for your work. Jonathan -- 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/20110414212115.GA16051@elie
Re: exec: 58: /usr: Permission denied
# Probably not an X bug, but one has to start somewhere.
# Please cc me on replies.
reassign 615153 xserver-xorg
quit
Hi again,
Debian_bug_report wrote[1]:
Sorry for the delay,
Now it's my turn to apologize. Our analysts have been very carefully
looking over the information you sent and --- hey, who am I kidding.
In the original report, you wrote:
So, when I restart my machine
and try to start my X with the command startx, the system returns the error:
xinit: connection to X server lost and after said Wait for X server to shut
down and stayed with prompt flashing again.
but the strace you sent does not show that message[2]. Instead it shows
X: user not authorized to run the X server, aborting
due to
open(/etc/X11/Xwrapper.config, O_RDONLY) = -1 EACCES (Permission denied)
What does ls -l /usr/bin/X /etc/X11/Xwrapper.config tell? For reference,
on my system, it gives
-rw--- 1 root root 601 Jan 31 08:31 /etc/X11/Xwrapper.config
-rwsr-sr-x 1 root root 9024 Apr 2 10:23 /usr/bin/X
Notice in particular the setuid (s) bits on X. Is it the same on yours?
Do you use any unusual filesystem or kernel feature (selinux,
apparmor, etc) that might cause that not to work?
Also for reference I would be interested in the output from
dpkg-query -W xserver-xorg x11-common.
That's all for now. Hope that helps.
Regards,
Jonathan
[1] http://bugs.debian.org/615153
[2]
So, I tried invoke X with root and
I had sucess! When I went to the .xsession-errors I saw this error:
Xsession: X session started for invisiblemanguard at Ter Fev 22 16:36:02 BRT
2011
exec: 58: /usr: Permission denied
I admit I was more interested in what produces the latter message (so,
sudo strace -f startx) but let's look at your stracelog for the
former. First, a quick cast of characters:
$ egrep '^[0-9]* (clone|exec|wait|... clone)' stracelog | think
2300 startx
- 2301 hostname
- 2302 (startx)
- 2303 hostname
- 2304 grep
- 2305 hostname
- 2306 mcookie
- 2307 mktemp
- 2308 xauth
- 2309 (startx)
- 2310 xauth
- 2311 sed
- 2312 xauth
- 2313 (startx)
- 2314 xauth
- 2315 sed
- 2316 xauth
- 2317 xinit
- 2318 xserverrc - X
- 2319 rm
The expected symptom is xinit: connection to X server lost, but
instead we get (from xinit):
connect(3, {sa_family=AF_INET6, sin6_port=htons(6000), inet_pton(AF_INET6,
::1, sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 ECONNREFUSED
(Connection refused)
[...]
connect(3, {sa_family=AF_INET, sin_port=htons(6000),
sin_addr=inet_addr(127.0.0.1)}, 16) = -1 ECONNREFUSED (Connection refused)
close(3) = 0
wait4(2318, [{WIFEXITED(s) WEXITSTATUS(s) == 1}], WNOHANG, NULL) = 2318
write(2, xinit: , 7)= 7
write(2, giving up, 9) = 9
write(2, \n, 1) = 1
write(2, xinit: , 7)= 7
write(2, unable to connect to X server, 29) = 29
write(2, : Connection refused\n, 21) = 21
What happened to the server?
open(/etc/X11/Xwrapper.config, O_RDONLY) = -1 EACCES (Permission denied)
lstat(/etc/X11/X, {st_mode=S_IFLNK|0777, st_size=13, ...}) = 0
readlink(/etc/X11/X, /usr/bin/Xorg, 1024) = 13
access(/etc/X11/X, X_OK)= 0
getuid() = 1000
write(2, X: user not authorized to run th..., 54) = 54
exit_group(1) = ?
Ah.
--
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/20110413075533.GA12757@elie
Bug#615153: exec: 58: /usr: Permission denied
found 615153 xserver-xorg/1:7.5+8 quit Jonathan Nieder wrote: What does ls -l /usr/bin/X /etc/X11/Xwrapper.config tell? For reference, on my system, it gives -rw--- 1 root root 601 Jan 31 08:31 /etc/X11/Xwrapper.config -rwsr-sr-x 1 root root 9024 Apr 2 10:23 /usr/bin/X Notice in particular the setuid (s) bits on X. Is it the same on yours? Do you use any [...] kernel feature (selinux, apparmor, etc) that might cause that not to work? I'm still very curious about the above. [...] unusual filesystem or [...] Also for reference I would be interested in the output from dpkg-query -W xserver-xorg x11-common. But this was lazy of me. The supplied dpkg.log.* indicate - xserver-xorg 1:7.5+8 - x11-common 1:7.5+7 and the supplied fstab says the filesystem is reiserfs. Kernel is some version of 2.6.32-5-amd64, I suppose. -- 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/20110413081858.GB12757@elie
Bug#615522: xserver-xorg-video-mach64: apt-listchanges prompts on every upgrade
Cyril Brulebois wrote: Also, thanks for the patch, but I went for another one: get rid of the NEWS file entirely. That was 3 years ago, now we have autoconfiguration Good idea. Thanks for the quick response. -- 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/20110227121407.GA25974@elie
