Bug#884466: mesa: firefox, thunderbird, chromium don't start with mesa 17.3.0-1
Package: libglx-mesa0 Followup-For: Bug #884466 This works for me with [AMD/ATI] Baffin [Radeon RX 460] (rev cf) I can open chromium and firefox just fine. -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 'testing'), (171, 'unstable'), (151, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.14.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libglx-mesa0:amd64 depends on: ii libc62.24-11+deb9u1 ii libdrm2 2.4.89-1 ii libexpat12.2.0-2+deb9u1 ii libgl1-mesa-dri 17.3.1-1 ii libglapi-mesa17.3.1-1 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb-dri2-01.12-1 ii libxcb-dri3-01.12-1 ii libxcb-glx0 1.12-1 ii libxcb-present0 1.12-1 ii libxcb-sync1 1.12-1 ii libxcb-xfixes0 1.12-1 ii libxcb1 1.12-1 ii libxdamage1 1:1.1.4-2+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxshmfence11.2-1+b2 ii libxxf86vm1 1:1.1.4-1+b2 ii zlib1g 1:1.2.8.dfsg-5 libglx-mesa0:amd64 recommends no packages. libglx-mesa0:amd64 suggests no packages. -- no debconf information
Bug#810914: /usr/bin/Xorg: cannot start X server
Package: xserver-xorg-core Version: 2:1.17.3-2 Severity: normal File: /usr/bin/Xorg Hello, after recent upgrade I cannot start X server from the console (as root). X server starts normally when systemd spawns the display manager on boot. However, starting the X server by hand or resterting the display manager from console fails. I have no idea what to check here. Thanks Michal -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Oct 3 2014 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 274 Oct 28 00:32 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RS200M [Radeon IGP 330M/340M/345M/350M] [1002:4337] /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.3.0-1-686 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04) Xorg X server log files on system: -- -rw-r--r-- 1 root root 21424 Jan 13 17:45 /var/log/Xorg.1.log -rw-r--r-- 1 root root 21424 Jan 13 17:46 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 213.334] X.Org X Server 1.17.3 Release Date: 2015-10-26 [ 213.356] X Protocol Version 11, Revision 0 [ 213.364] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [ 213.372] Current Operating System: Linux nc4000 4.3.0-1-686 #1 SMP Debian 4.3.3-5 (2016-01-04) i686 [ 213.373] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-686 root=UUID=fde9fa62-0a08-4a39-b63c-610fb20cf7c1 ro quiet splash [ 213.386] Build Date: 27 October 2015 11:29:29PM [ 213.394] xorg-server 2:1.17.3-2 (http://www.debian.org/support) [ 213.401] Current version of pixman: 0.33.4 [ 213.414]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 213.415] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 213.444] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 13 17:46:35 2016 [ 213.452] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 213.452] (==) No Layout section. Using the first Screen section. [ 213.452] (==) No screen section available. Using defaults. [ 213.452] (**) |-->Screen "Default Screen Section" (0) [ 213.452] (**) | |-->Monitor "" [ 213.453] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 213.453] (==) Automatically adding devices [ 213.453] (==) Automatically enabling devices [ 213.453] (==) Automatically adding GPU devices [ 213.453] (WW) The directory "/usr/share/fonts/X11/misc" does not exist. [ 213.453]Entry deleted from font path. [ 213.453] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 213.453]Entry deleted from font path. [ 213.453] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 213.453]Entry deleted from font path. [ 213.453] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 213.453]Entry deleted from font path. [ 213.453] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 213.453]Entry deleted from font path. [ 213.453] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 213.453]Entry deleted from font path. [ 213.453] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 213.453]Entry deleted from font path. [ 213.453] (==) FontPath set to: built-ins [ 213.453] (==) ModulePath set to "/usr/lib/xorg/modules" [ 213.453] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 213.453] (II) Loader magic: 0x8026b700 [ 213.453] (II) Module ABI versions: [ 213.453]X.Org ANSI C Emulation: 0.4 [ 213.453]X.Org Video Driver: 19.0 [ 213.453]X.Org XInput driver : 21.0 [ 213.453]X.Org Server Extension : 9.0 [ 213.466] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31 [ 213.469] (II) xfree86: Adding drm device (/dev/dri/card0) [ 213.471] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0 [ 213.473] (--) PCI:*(0:1:5:0) 1002:4337:0e11:005a rev 0, Mem @ 0x9800/134217728, 0x9000/65536, I/O @ 0x2000/256, BIOS @ 0x/131072 [ 213.473] (II) LoadModule: "glx" [ 213.474] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 213.477] (II) Module glx: vendor="X.Org Foundation
Bug#656719: Please provide xvmc and vdpau Gallium3D video acceleration drivers (libg3dvl-mesa package)
Source: mesa
Followup-For: Bug #656719
Hello,
Sending the debdiff updated for mesa 10.
Both mesa 9.2.2 and mesa 10 work for vdpau playback on Cedar (radeon).
Thanks
Michal
-- System Information:
Debian Release: 7.3
APT prefers stable
APT policy: (990, 'stable'), (171, 'unstable'), (151, 'experimental'), (121,
'precise-updates'), (121, 'precise-security'), (121, 'precise'), (101,
'stable'), (101, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11-trunk-amd64 (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/dash
diff -u mesa-10.0.1/debian/changelog mesa-10.0.1/debian/changelog
--- mesa-10.0.1/debian/changelog
+++ mesa-10.0.1/debian/changelog
@@ -1,3 +1,13 @@
+mesa (10.0.1-1.1) experimental; urgency=low
+
+ [ Mikhail Kshevetskiy ]
+
+ * debian: Add libxvmc1-gallium-drivers and libvdpau1-gallium-drivers
+packages to provide xvmc and vdpau video acceleration for nouveau,
+radeon and softpipe drivers.
+
+ -- Mikhail Kshevetskiy Sun, 09 Jun 2013 02:14:05 +0400
+
mesa (10.0.1-1) experimental; urgency=low
* New upstream release.
diff -u mesa-10.0.1/debian/control mesa-10.0.1/debian/control
--- mesa-10.0.1/debian/control
+++ mesa-10.0.1/debian/control
@@ -33,6 +33,8 @@
llvm-3.3-dev (>= 1:3.3-4) [amd64 i386 kfreebsd-amd64 kfreebsd-i386 armhf],
libelf-dev [amd64 i386 kfreebsd-amd64 kfreebsd-i386 armhf],
libwayland-dev (>= 1.0.2) [linux-any],
+ libxvmc-dev,
+ libvdpau-dev,
Vcs-Git: git://git.debian.org/git/pkg-xorg/lib/mesa
Vcs-Browser: http://git.debian.org/?p=pkg-xorg/lib/mesa.git
Homepage: http://mesa3d.sourceforge.net/
@@ -784,2 +786,76 @@
+Package: libvdpau1-gallium-drivers
+Section: libs
+Priority: optional
+Architecture: linux-any
+Depends:
+ ${shlibs:Depends},
+ ${misc:Depends},
+ firmware-linux-nonfree
+Recommends: libgl1-mesa-dri, libxvmc-mesa-drivers
+Multi-Arch: same
+Description: VDPAU Gallium3D video acceleration drivers
+ This package provide vdpau gallium drivers to accelerate video decoding
+ on r300/r600/radeonsi (AMD Radeon chips), nouveau (NVidia chips) and
+ softpipe.
+ .
+ Features:
+ r300: MPEG1, MPEG2
+ r600/radeonsi: MPEG1, MPEG2, H264, VC1, MPEG4 (see note)
+ nouveau: ???
+ softpipe: ???
+ .
+ Recent MPlayer versions use the provided library automatically. But you
+ can manually use it using for example the following command line.
+ .
+ .mplayer -vo vdpau -vc ffmpeg12vdpau example.mpeg2
+ .
+ Note: you'll need UVD support in your kernel to get H264/VC1/MPEG4
+ video decoding on AMD Radeon chips (linux >= 3.10 and latest
+ radeon firmware files required).
+ .
+ Beware that this is work in progress and might not work as expected.
+
+Package: libvdpau1-gallium-drivers-dbg
+Section: debug
+Priority: extra
+Architecture: linux-any
+Depends:
+ libvdpau1-gallium-drivers (= ${binary:Version}),
+ ${misc:Depends}
+Multi-Arch: same
+Description: debugging symbols for VDPAU Gallium3D video acceleration drivers
+ This package contains the debugging symbols for the VDPAU gallium drivers.
+
+Package: libxvmc1-gallium-drivers
+Section: libs
+Priority: optional
+Architecture: linux-any
+Depends:
+ libxvmc1,
+ ${shlibs:Depends},
+ ${misc:Depends},
+Recommends: libgl1-mesa-dri, libvdpau1-gallium-drivers
+Multi-Arch: same
+Description: XvMC Gallium3D video acceleration drivers
+ This package provide accelerated XvMC gallium drivers for
+ r300/r600/radeonsi (AMD Radeon chips), nouveau (NVidia chips) and
+ softpipe.
+ .
+ You have to edit `/etc/X11/XvMCConfig` and list your hardware specific
+ library in there, for example `libXvMCr600.so.1`.
+ .
+ Beware that this is work in progress and might not work as expected.
+
+Package: libxvmc1-gallium-drivers-dbg
+Section: debug
+Priority: extra
+Architecture: linux-any
+Depends:
+ libxvmc1-gallium-drivers (= ${binary:Version}),
+ ${misc:Depends}
+Multi-Arch: same
+Description: debugging symbols for XvMC Gallium3D video acceleration drivers
+ This package contains the debugging symbols for the XvMCV gallium libraries.
+
# vim: tw=0
diff -u mesa-10.0.1/debian/rules mesa-10.0.1/debian/rules
--- mesa-10.0.1/debian/rules
+++ mesa-10.0.1/debian/rules
@@ -115,7 +115,6 @@
--enable-shared-glapi \
--enable-texture-float \
--enable-xa \
- --disable-xvmc --disable-vdpau \
$(confflags_DIRECT_RENDERING) \
$(confflags_EGL) \
$(confflags_GALLIUM) \
@@ -130,22 +129,25 @@
--enable-xlib-glx \
--disable-egl \
--disable-shared-glapi \
+ --disable-gallium-g3dvl \
$(buildflags)
confflags-swx11-static = \
--disable-dri \
--disable-egl \
--with-gallium-drivers= \
+ --disable-shared-glapi \
+ --disable-gallium-g3dvl \
--enable-xlib-glx \
--enable-static \
--disable-egl \
- --disable-shared-glapi \
$(buildflags)
confflags-swx11-i386-i686 = \
--disable-dri \
--disable-egl \
--with-gallium-drivers= \
+ --disable-gallium-g3dvl \
--enable-xlib-glx \
--disable-egl \
Bug#561185: /usr/share/X11/xkb/symbols/ctrl: Re: xkb-data: support custom layouts
Package: xkb-data Version: 2.5.1-3 Followup-For: Bug #561185 Hello, so how are custom layouts supposed to work? It looks to me like you need to modify the rules file when adding a layout but that file is not conffile and is not extensible. Or is extending that file just undocumented? I have a weird keyboard for which I want to remap a few keys. Presumably I could make an udev rule that matches the keyboard and amends /etc/default/keyboard. But what do I amend? I want layout and options as specified by the user so the only part I can possibly replace is model. But without rules model is totally meaningless. You can use symbol file references in layout directly perhaps but options need rules too. Thanks Michal -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- debsums errors found: debsums: changed file /usr/share/X11/xkb/rules/evdev (from xkb-data package) debsums: changed file /usr/share/X11/xkb/symbols/altwin (from xkb-data package) debsums: changed file /usr/share/X11/xkb/symbols/ctrl (from xkb-data 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/20130812133701.10174.49230.report...@optiplex960.ruk.cuni.cz
Bug#719494: /usr/share/X11/xkb/symbols/ctrl: cannot remap left control key when using ctrl:nocaps option
Package: xkb-data
Version: 2.5.1-3
Severity: normal
File: /usr/share/X11/xkb/symbols/ctrl
Hello,
I was trying to swap left control and window key and I kept getting both
control and mod4 modifier on left control.
It turns out that ctrl:nocaps unconditionally maps control to left
control. This is useless because the pc keymap already does that mapping
in a more reasonable way and the nocaps mapping conflicts with possible
latter mappings of the left control key.
Please fix the ctrl file.
Thanks
Michal
--- symbols/ctrl~ 2013-08-12 14:17:15.0 +0200
+++ symbols/ctrl2013-08-12 15:12:30.0 +0200
@@ -2,7 +2,7 @@
partial modifier_keys
xkb_symbols "nocaps" {
replace key { [ Control_L, Control_L ] };
-modifier_map Control { , };
+modifier_map Control { };
};
// replace left control with Meta
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (500,
'testing'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'),
(150, 'precise-security'), (150, 'precise')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/share/X11/xkb/rules/evdev (from xkb-data package)
debsums: changed file /usr/share/X11/xkb/symbols/altwin (from xkb-data package)
debsums: changed file /usr/share/X11/xkb/symbols/ctrl (from xkb-data 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/20130812134336.10463.71029.report...@optiplex960.ruk.cuni.cz
Bug#700015: libx11-6: crashes on systems using Mali graphics
On 4 March 2013 14:24, Сергей И. Королев wrote: > I think we can have libMali different version or target. My target > Samsung Exynos and version R3P2. Yes, I am running r3p0 which is the version available for A10 at this time. Still r3p2 diff is useful at least for users of that version. Thanks Michal -- 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/caomqcttyvz2ubtwhsqwg_z4br9qkalexq6dvk0pppc1zkw5...@mail.gmail.com
Bug#700015: libx11-6: crashes on systems using Mali graphics
Hello, On 4 March 2013 13:46, Сергей И. Королев wrote: > good news! i make quick and dirty hacks and this work system wide. That's cool but not exactly easily reproducible. Could you prehaps attach a bsdiff? Thanks Michal -- 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/caomqctredmtz8q3a2jaufpm0tsbafbaxsrhfb72x3dkhxxs...@mail.gmail.com
Bug#700015: libx11-6: crashes on systems using Mali graphics
On 4 March 2013 09:17, Сергей И. Королев wrote: > in my instalation gnome-shell, empathy, evolution, emerillon and some > other application affected to this bug. i think about system way > workaround. how about patch libMali.so to call XInitThreads in init > after library loaded? > That's presumably possible but you will have to binary-patch the library. There is no source. Also it's good idea to try the workaround with gdb to make sure you really have the same problem. Thanks Michal -- 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/CAOMqctQwQQzGjxNfYWQoPN=stpyhhhca0pzqmn0r7xodgo8...@mail.gmail.com
Bug#700015: libx11-6: crashes on systems using Mali graphics
Hello I moved gnome-shell to /usr/local/bin and use this script instead: #!/bin/sh gdb -ex 'break main' -ex 'r' -ex 'call XInitThreads()' -ex 'c' -ex 'bt full' -ex 'quit' --args /usr/local/bin/gnome-shell.distrib "$@" HTH Michal -- 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/caomqctqyhw+bn73ds-e_dg8u5y7md75h934dqvp4_-mhz+m...@mail.gmail.com
Bug#700015: libx11-6: crashes on systems using Mali graphics
On 8 February 2013 11:20, Julien Cristau wrote: > On Fri, Feb 8, 2013 at 11:17:11 +0100, Michal Suchanek wrote: >> >> The GLES library is not in position to call XInitThreads because it's >> passed a X11 window id which was obtained by the application by a Xlib >> call already. >> >> gnome-shell is not interested in threading so does not call XInitThreads. >> > Sounds like you're screwed then. > > Cheers, > Julien Actually, the GLES library tries to initialize the X threading after the fact which leads to the uninitialized mutex. Since the mutex allocation does nothing when threading is not initialized there are no mutexes in objects created before. This is probably a bug in the library. Breakpoint 2, XInitThreads () at ../../src/locking.c:573 573 ../../src/locking.c: No such file or directory. (gdb) bt full #0 XInitThreads () at ../../src/locking.c:573 No locals. #1 0xb6455f5e in __egl_platform_initialize () from /usr/lib/arm-linux-gnueabihf/libEGL.so.1 No symbol table info available. #2 0xb645143a in __egl_main_open_mali () from /usr/lib/arm-linux-gnueabihf/libEGL.so.1 No symbol table info available. #3 0xb6450440 in _egl_initialize () from /usr/lib/arm-linux-gnueabihf/libEGL.so.1 No symbol table info available. #4 0xb6450be8 in eglInitialize () from /usr/lib/arm-linux-gnueabihf/libEGL.so.1 No symbol table info available. #5 0xb64f6a9e in ?? () from /usr/lib/arm-linux-gnueabihf/libcogl.so.9 No symbol table info available. #6 0xb64f6a9e in ?? () from /usr/lib/arm-linux-gnueabihf/libcogl.so.9 No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) So yes, you are screwed. Given the X and GLES interfaces it's not possible for threading libraries to work unless applications go out of their way to be compatible and call XInitThreads on their own. Thanks Michal -- 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/caomqctspojniksrcdkwst6dmxd_pobhesw3usr+kz8tvezw...@mail.gmail.com
Bug#700015: libx11-6: crashes on systems using Mali graphics
Package: libx11-6 Version: 2:1.5.0-1 Followup-For: Bug #700015 Hello, it seems this problem is fixed by calling XInitThreads(). This is probably very platfrom specific problem, however. Drivers for this platform not available in Debian. Starting program: /usr/bin/gnome-shell [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". Breakpoint 1, 0x9704 in main () (gdb) XInitThreads() Undefined command: "XInitThreads". Try "help". (gdb) call XInitThreads() $1 = 1 (gdb) c Continuing. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 3.4.24+ (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages libx11-6 depends on: ii libc6 2.13-37 ii libx11-data2:1.5.0-1 ii libxcb11.8.1-2 ii multiarch-support 2.13-37 libx11-6 recommends no packages. libx11-6 suggests no packages. -- no debconf information -- 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/20130207143708.11755.15816.report...@a10.burning-in.hell
Bug#699084: /usr/bin/Xorg: X crash in FreeGlyphSet
On 27 January 2013 13:19, Cyril Brulebois wrote: > Michal Suchanek (27/01/2013): >> Package: xserver-xorg-core >> Version: 2:1.12.4-4 >> Severity: normal >> File: /usr/bin/Xorg >> >> Hello, >> >> the X server crashed in FreeGlyphSset. >> >> Not sure if the bug is in the glyph handling or in resource handling in >> general. This happened first time after long time of running X server. I >> was viewing some Chinese pages in a web browser at the moment so it >> might cause more stress to glyph handling. > > As you know, a full backtrace would be helpful. Sorry, this is not exactly frequent crash. I don't think I will be able to collect a better backtrace. Thanks Michal -- 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/CAOMqctQZtcKp0fwoNmM=0ijbLq1zPO-g0q=w2-tfksesjbj...@mail.gmail.com
Bug#698682: /usr/bin/xwd: -screen is always in effect - cannot capture content of obscured window
Package: x11-apps Version: 7.7~2 Severity: normal File: /usr/bin/xwd Hello, capturing with -id and without setting -screen should supposedly give content of window regardless of other windows drawn on top of it. However, xwd behaves as if -screen was given and captures whatever is currently on the screen in the area where the window would be. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (171, 'unstable'), (151, 'experimental'), (121, 'precise-updates'), (121, 'precise-security'), (121, 'precise'), (101, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (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/dash Versions of packages x11-apps depends on: ii cpp 4:4.7.2-1 ii libc62.16-0experimental1 ii libpng12-0 1.2.49-1 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.5.0-1 ii libxaw7 2:1.0.10-2 ii libxcursor1 1:1.1.13-1 ii libxext6 2:1.3.1-2 ii libxft2 2.3.1-1 ii libxkbfile1 1:1.0.8-1 ii libxmu6 2:1.1.1-1 ii libxmuu1 2:1.1.1-1 ii libxrender1 1:0.9.7-1 ii libxt6 1:1.1.3-1 Versions of packages x11-apps recommends: ii xbitmaps 1.1.1-1 Versions of packages x11-apps suggests: ii mesa-utils 8.0.1-2+b3 -- Configuration Files: /etc/X11/app-defaults/XCalc changed [not included] -- no debconf information -- 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/20130122101502.532.6703.reportbug@iscsi
Bug#681781: dummy: Please include sample xorg.conf
Excerpts from Samuel Thibault's message of Mon Jan 07 15:21:44 +0100 2013: > Michal Suchanek, le Mon 07 Jan 2013 15:13:27 +0100, a écrit : > > Excerpts from Samuel Thibault's message of Mon Jan 07 15:01:28 +0100 2013: > > > Michal Suchanek, le Mon 07 Jan 2013 14:38:13 +0100, a écrit : > > > > Excerpts from Samuel Thibault's message of Mon Jan 07 14:24:24 +0100 > > > > 2013: > > > > > Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit : > > > > > > Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 > > > > > > +0100 2013: > > > > > > > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit : > > > > > > > > How are these devices not configured? > > > > > > > > > > > > > > Err, aren't you taking this thread for another one? See the > > > > > > > subject, > > > > > > > this is about providing a sample xorg.conf. I'm here saying there > > > > > > > is no need for input sections, since they are already > > > > > > > automatically > > > > > > > configured. > > > > > > > > > > > > And I am saying that there *is* need for input sections to prevent > > > > > > them > > > > > > from being automatically configured. > > > > > > > > > > Ooops, sorry, I hadn't understood that input devices were not desired > > > > > in > > > > > this bug report. > > > > > > > > > > I'm however wondering how this use case differs from simply using > > > > > Xvfb. > > > > > > > > Xvfb is deprecated, bitrotten, does not support xrandr and other > > > > extensions, .. > > > > > > Could it perhaps be replaced by a mere shell script which invokes Xorg, > > > giving it the sample xorg.conf you provided? That'd be a way easier > > > upgrade path for users than knowing about the dummy driver etc. > > > > For that the sample config has to live somewhere. It won't live in Xvfb > > package because while it's deprecated upstream it's not a reason for > > Debian to remove it. Or is it? > > It can be a reason for removing it. Or better, replacing it with the > proposed script. That said, the xorg.conf would better be maintained > under the xorg umbrella, officially replacing Xvfb. For that the dummy driver would have to support all the features of Xvfb. Some Xvfb options could be emulated with generating xorg.conf on the fly perhaps but the shared memory option is not implemented in dummy AFAIK and may be used by some automated tests. Thanks Michal -- 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/1357569213-sup-8...@virtual.ruk.cuni.cz
Bug#681781: dummy: Please include sample xorg.conf
Excerpts from Samuel Thibault's message of Mon Jan 07 15:01:28 +0100 2013: > Michal Suchanek, le Mon 07 Jan 2013 14:38:13 +0100, a écrit : > > Excerpts from Samuel Thibault's message of Mon Jan 07 14:24:24 +0100 2013: > > > Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit : > > > > Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 > > > > 2013: > > > > > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit : > > > > > > How are these devices not configured? > > > > > > > > > > Err, aren't you taking this thread for another one? See the subject, > > > > > this is about providing a sample xorg.conf. I'm here saying there > > > > > is no need for input sections, since they are already automatically > > > > > configured. > > > > > > > > And I am saying that there *is* need for input sections to prevent them > > > > from being automatically configured. > > > > > > Ooops, sorry, I hadn't understood that input devices were not desired in > > > this bug report. > > > > > > I'm however wondering how this use case differs from simply using Xvfb. > > > > Xvfb is deprecated, bitrotten, does not support xrandr and other > > extensions, .. > > Could it perhaps be replaced by a mere shell script which invokes Xorg, > giving it the sample xorg.conf you provided? That'd be a way easier > upgrade path for users than knowing about the dummy driver etc. For that the sample config has to live somewhere. It won't live in Xvfb package because while it's deprecated upstream it's not a reason for Debian to remove it. Or is it? Thanks Michal -- 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/1357567917-sup-8...@virtual.ruk.cuni.cz
Bug#681781: dummy: Please include sample xorg.conf
Excerpts from Samuel Thibault's message of Mon Jan 07 14:24:24 +0100 2013: > Michal Suchanek, le Mon 07 Jan 2013 14:01:35 +0100, a écrit : > > Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013: > > > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit : > > > > How are these devices not configured? > > > > > > Err, aren't you taking this thread for another one? See the subject, > > > this is about providing a sample xorg.conf. I'm here saying there > > > is no need for input sections, since they are already automatically > > > configured. > > > > And I am saying that there *is* need for input sections to prevent them > > from being automatically configured. > > Ooops, sorry, I hadn't understood that input devices were not desired in > this bug report. > > I'm however wondering how this use case differs from simply using Xvfb. Xvfb is deprecated, bitrotten, does not support xrandr and other extensions, .. Thanks Michal -- 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/1357565830-sup-1...@virtual.ruk.cuni.cz
Bug#681781: dummy: Please include sample xorg.conf
Excerpts from Samuel Thibault's message of Mon Jan 07 13:40:50 +0100 2013: > Michal Suchanek, le Mon 07 Jan 2013 13:33:11 +0100, a écrit : > > How are these devices not configured? > > Err, aren't you taking this thread for another one? See the subject, > this is about providing a sample xorg.conf. I'm here saying there > is no need for input sections, since they are already automatically > configured. And I am saying that there *is* need for input sections to prevent them from being automatically configured. Thanks Michal -- 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/1357563646-sup-8...@virtual.ruk.cuni.cz
Bug#696965: support for HW_SKIP_CONSOLE breaks use by blind people
On 7 January 2013 05:08, Peter Hutterer wrote: > On Sat, Jan 05, 2013 at 07:06:05PM +0100, Samuel Thibault wrote: >> Michal Suchanek, le Sat 05 Jan 2013 18:55:28 +0100, a écrit : >> > On 5 January 2013 02:10, Samuel Thibault wrote: >> > > Alan Coopersmith, le Mon 31 Dec 2012 17:46:47 -0800, a écrit : >> > >> On 12/31/12 05:36 PM, Samuel Thibault wrote: >> > >> > Michal Suchanek, le Mon 31 Dec 2012 19:22:13 +0100, a écrit : >> > >> >> why is that patch needed? >> > >> >> >> > >> >> It is quite non-obvious why would dummy driver require a console >> > >> >> under >> > >> >> any circumstances. It does not render anything anywhere so does not >> > >> >> use console for anything. >> > >> > >> > >> > The console *is* needed for keyboard input. >> > >> > >> > >> > Again, the use case is blind people who have use of possessing an >> > >> > actual >> > >> > screen, and thus don't have any, and thus have to use the dummy >> > >> > driver. >> > >> >> > >> So it sounds like that should be handled by the input driver, not the >> > >> output driver. >> > > >> > > Ok, that makes sense. Input drivers however don't currently have a way >> > > to request the core to callxf86OpenConsole, similar to the absence of >> > > the HW_SKIP_CONSOLE flag in the case of video drivers. >> > > >> > > What do you recommend to add to the InputDriverRec? A driverFunc method >> > > like video drivers? Something else? >> > >> > I still don't understand the problem. The evdev driver opens the evdev >> > device when loaded and reads input there. That happens even with dummy >> > video driver so long as you do not carefully prevent the evdev driver >> > from loading, does it not? >> >> It does not. See for instance the attached xorg.conf, then I run from >> vt1 >> >> xinit /usr/bin/fvwm -- :1 >> >> there is no VT switch, and pressing ^C 5s later kills the server (while >> we'd want ^C to just go to the server). The resulting Xorg.1.log is >> attached. > > while it shows the issue, this is not a good example. the config section for > the keyboard isn't referenced from the layout so it doesn't apply, and the > config for the mouse is ignored because input hotplugging is enabled. so > only the dummy driver section applies, the rest of this config has no effect. > >> What I understand is that evedev does open things, but since no VT was >> allocated, the evdev driver does not eat keypresses, i.e. from its point >> of view it's as if we had switched away from an allocated VT. > > evdev reads data off /dev/input/eventX and it doesn't need a console. > > but without xf86OpenConsole() and ioctl(KDSKBMODE), the events are also > sent to the console. this is your real problem, since both get the event and > you can kill your server. we've had this issue years back after switching to > evdev as standard driver, and then when we removed the EVIOCGRAB from evdev. > >> So what Alan suggested is that the evdev driver simply tells the core >> that it needs a VT to work properly. I'm now just asking which way that >> should be done. > > I'm not sure this is the right approach. evdev doesn't need a VT to work > properly, I've got a use-case here (automated testing) that works perfectly > well without a VT. plus, with hotplugging you don't actually know if and > when an evdev device will be added. > > so the solution here would be to only call xf86OpenConsole() when a keyboard > device comes up. on the plus side, if the evdev driver is broken this would > allow you to Ctrl+C the server. On the minus side, there's a window where > you can Ctrl+C the server until the device has been added. > > your use-case (or mine, depending on your POV) seems to need not a console > switch but an option to enable/disable keyboard input from being sent to the > console. this is the solution we should be looking at, imo. The evdev driver is loaded and can tell anything to the X server only when an evdev device is detected. Note that on x86 it is always loaded to handle acpi button but on other platforms it may be loaded only when an actual input device is attached. So even with hotpulg if it was the evdev driver telling the X server it would tell it only when a device actually exists. Also it is not sufficient to grab the terminal when a keyboard
Bug#681781: dummy: Please include sample xorg.conf
Excerpts from Samuel Thibault's message of Sat Jan 05 19:21:25 +0100 2013: > Michal Suchanek, le Wed 02 Jan 2013 11:27:04 +0100, a écrit : > > Excerpts from Samuel Thibault's message of Sun Dec 30 01:53:55 +0100 2012: > > > Section "Device" > > > Identifier "Configured Video Device" > > > Driver "dummy" > > > EndSection > > > > It is exactly because this is NOT sufficient that the sample > > configuration is needed. > > I've just tried it, see attached log. > > > The X server configures input drivers automagically. The above > > configuration sample avoids that. > > The attached log shows it doesn't. > > > The default mode list is very insufficient. That is why the additional > > modes are added in the configuration. > > Ah, if you want more than 1024x768, yes, of course. Otherwise my > experience shows 1024x768 does get configured. > > Samuel > [ 67138.290] (II) config/udev: Adding input device Logitech USB Keyboard > (/dev/input/event19) > [ 67138.290] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard > catchall" > [ 67138.290] (II) Using input driver 'evdev' for 'Logitech USB Keyboard' > [ 67138.290] (**) Logitech USB Keyboard: always reports core events > [ 67138.290] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event19" > [ 67138.290] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31d > [ 67138.290] (--) evdev: Logitech USB Keyboard: Found keys > [ 67138.290] (II) evdev: Logitech USB Keyboard: Configuring as keyboard > [ 67138.290] (**) Option "config_info" > "udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3:1.0/input/input19/event19" > [ 67138.290] (II) XINPUT: Adding extended input device "Logitech USB > Keyboard" (type: KEYBOARD, id 11) > [ 67138.290] (**) Option "xkb_rules" "evdev" > [ 67138.290] (**) Option "xkb_model" "geniuskb19e" > [ 67138.290] (**) Option "xkb_layout" "fr,brai" > [ 67138.290] (**) Option "xkb_variant" "oss," > [ 67138.290] (**) Option "xkb_options" > "compose:lwin,compose:rwin,nbsp:level3n,grp:shift_caps_toggle,grp_led:scroll,terminate:ctrl_alt_bksp,kpdl:kposs" > [ 67138.291] (II) config/udev: Adding input device Logitech USB Keyboard > (/dev/input/event20) > [ 67138.291] (**) Logitech USB Keyboard: Applying InputClass "evdev keyboard > catchall" > [ 67138.291] (II) Using input driver 'evdev' for 'Logitech USB Keyboard' > [ 67138.291] (**) Logitech USB Keyboard: always reports core events > [ 67138.292] (**) evdev: Logitech USB Keyboard: Device: "/dev/input/event20" > [ 67138.292] (--) evdev: Logitech USB Keyboard: Vendor 0x46d Product 0xc31d > [ 67138.292] (--) evdev: Logitech USB Keyboard: Found absolute axes > [ 67138.292] (II) evdev: Logitech USB Keyboard: Forcing absolute x/y axes to > exist. > [ 67138.292] (--) evdev: Logitech USB Keyboard: Found keys > [ 67138.292] (II) evdev: Logitech USB Keyboard: Configuring as mouse > [ 67138.292] (II) evdev: Logitech USB Keyboard: Configuring as keyboard > [ 67138.292] (**) Option "config_info" > "udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1.3/2-1.1.3:1.1/input/input20/event20" > [ 67138.292] (II) XINPUT: Adding extended input device "Logitech USB > Keyboard" (type: KEYBOARD, id 12) > [ 67138.292] (**) Option "xkb_rules" "evdev" > [ 67138.292] (**) Option "xkb_model" "geniuskb19e" > [ 67138.292] (**) Option "xkb_layout" "fr,brai" > [ 67138.292] (**) Option "xkb_variant" "oss," > [ 67138.292] (**) Option "xkb_options" > "compose:lwin,compose:rwin,nbsp:level3n,grp:shift_caps_toggle,grp_led:scroll,terminate:ctrl_alt_bksp,kpdl:kposs" > [ 67138.292] (II) evdev: Logitech USB Keyboard: initialized for absolute axes. > [ 67138.292] (**) Logitech USB Keyboard: (accel) keeping acceleration scheme 1 > [ 67138.292] (**) Logitech USB Keyboard: (accel) acceleration profile 0 > [ 67138.292] (**) Logitech USB Keyboard: (accel) acceleration factor: 2.000 > [ 67138.292] (**) Logitech USB Keyboard: (accel) acceleration threshold: 4 > [ 67138.292] (II) config/udev: Adding input device Logitech USB-PS/2 Optical > Mouse (/dev/input/event21) > [ 67138.292] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev > pointer catchall" > [ 67138.292] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical > Mouse' > [ 67138.292] (**) Lo
Bug#696965: support for HW_SKIP_CONSOLE breaks use by blind people
On 5 January 2013 23:04, Samuel Thibault wrote: > Michal Suchanek, le Sat 05 Jan 2013 22:47:20 +0100, a écrit : >> > there is no VT switch, and pressing ^C 5s later kills the server (while >> > we'd want ^C to just go to the server). The resulting Xorg.1.log is >> > attached. >> >> I don't think that an actual VT switch is required > > From the point of the user, it is. There is no reason why it should not > happen just like with other video drivers in the use case at stake. Those video drivers render graphics. The dummy driver does not. It's not the same case. > >> It would be quite a few drivers to modify > > We can proceed just like video devices: only modify the void input > driver into saying it doesn't need a VT, and the core then avoids > allocating a VT only if *only* the dummy video driver and void input > driver are used. Indeed, you could possibly say that the dummy driver does not need video output which then requires a VT switch and the void driver does not need a tty input which would require locking the tty. > >> On x86 there is always the ACPI button but on some platforms nothing >> like that is present so this flag would have to be set dynamically >> when an input device is plugged in if set bu the input driver. Also >> evdev handles keyboards and mice. Is plugging in a mouse enough to >> warrant locking the tty? Is presence of synaptics or wacom device? > > I'm surprised that the discussion ends up with this way of thinking: > shouldn't it be the converse, i.e. a VT is always allocated *except* if > that is explicitly asked for by a special configuration? Otherwise we'll > keep having users saying that their special use does not trigger a VT > allocation... But there is the problem. The dummy driver sets the flag because it does not need the tty. The evdev driver does need the tty but it has no flag to set because opening a tty is the default. The bug comes exactly from the thinking that switching tty is the default and only an exception to this rule is flagged. It would be much saner for the driver to say that it needs the tty if and when it needs it. Thanks Michal -- 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/caomqctsss5kva43yktdfc4htdqmsvkkknk6wkpjsbc2rad2...@mail.gmail.com
Bug#696965: support for HW_SKIP_CONSOLE breaks use by blind people
On 5 January 2013 19:06, Samuel Thibault wrote: > Michal Suchanek, le Sat 05 Jan 2013 18:55:28 +0100, a écrit : >> On 5 January 2013 02:10, Samuel Thibault wrote: >> > Alan Coopersmith, le Mon 31 Dec 2012 17:46:47 -0800, a écrit : >> >> On 12/31/12 05:36 PM, Samuel Thibault wrote: >> >> > Michal Suchanek, le Mon 31 Dec 2012 19:22:13 +0100, a écrit : >> >> >> why is that patch needed? >> >> >> >> >> >> It is quite non-obvious why would dummy driver require a console under >> >> >> any circumstances. It does not render anything anywhere so does not >> >> >> use console for anything. >> >> > >> >> > The console *is* needed for keyboard input. >> >> > >> >> > Again, the use case is blind people who have use of possessing an actual >> >> > screen, and thus don't have any, and thus have to use the dummy driver. >> >> >> >> So it sounds like that should be handled by the input driver, not the >> >> output driver. >> > >> > Ok, that makes sense. Input drivers however don't currently have a way >> > to request the core to callxf86OpenConsole, similar to the absence of >> > the HW_SKIP_CONSOLE flag in the case of video drivers. >> > >> > What do you recommend to add to the InputDriverRec? A driverFunc method >> > like video drivers? Something else? >> >> I still don't understand the problem. The evdev driver opens the evdev >> device when loaded and reads input there. That happens even with dummy >> video driver so long as you do not carefully prevent the evdev driver >> from loading, does it not? > > It does not. See for instance the attached xorg.conf, then I run from > vt1 > > xinit /usr/bin/fvwm -- :1 > > there is no VT switch, and pressing ^C 5s later kills the server (while > we'd want ^C to just go to the server). The resulting Xorg.1.log is > attached. I don't think that an actual VT switch is required but setting up the VT so that the input is not interpreted by the kernel is. It would be quite a few drivers to modify so perhaps making a server flag would be useful. On x86 there is always the ACPI button but on some platforms nothing like that is present so this flag would have to be set dynamically when an input device is plugged in if set bu the input driver. Also evdev handles keyboards and mice. Is plugging in a mouse enough to warrant locking the tty? Is presence of synaptics or wacom device? Thanks Michal -- 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/caomqctsnmoxaftb9uopbs5secek0dd3+0bgn1cvso6btmfu...@mail.gmail.com
Bug#696965: support for HW_SKIP_CONSOLE breaks use by blind people
On 5 January 2013 02:10, Samuel Thibault wrote: > Alan Coopersmith, le Mon 31 Dec 2012 17:46:47 -0800, a écrit : >> On 12/31/12 05:36 PM, Samuel Thibault wrote: >> > Michal Suchanek, le Mon 31 Dec 2012 19:22:13 +0100, a écrit : >> >> why is that patch needed? >> >> >> >> It is quite non-obvious why would dummy driver require a console under >> >> any circumstances. It does not render anything anywhere so does not >> >> use console for anything. >> > >> > The console *is* needed for keyboard input. >> > >> > Again, the use case is blind people who have use of possessing an actual >> > screen, and thus don't have any, and thus have to use the dummy driver. >> >> So it sounds like that should be handled by the input driver, not the >> output driver. > > Ok, that makes sense. Input drivers however don't currently have a way > to request the core to callxf86OpenConsole, similar to the absence of > the HW_SKIP_CONSOLE flag in the case of video drivers. > > What do you recommend to add to the InputDriverRec? A driverFunc method > like video drivers? Something else? > I still don't understand the problem. The evdev driver opens the evdev device when loaded and reads input there. That happens even with dummy video driver so long as you do not carefully prevent the evdev driver from loading, does it not? Thanks Michal -- 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/caomqcttfpntzfryqz-v5mcqoctbk8y0tq_ckxo7dbmg6igt...@mail.gmail.com
Bug#681781: dummy: Please include sample xorg.conf
Excerpts from Samuel Thibault's message of Sun Dec 30 01:53:55 +0100 2012: > Mmm, I believe the following would be enough: > > Section "Device" > Identifier "noscreendevice" > Driver "dummy" > EndSection > > Samuel It is exactly because this is NOT sufficient that the sample configuration is needed. The X server configures input drivers automagically. The above configuration sample avoids that. The default mode list is very insufficient. That is why the additional modes are added in the configuration. Thanks Michal -- 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/1357122311-sup-4...@virtual.ruk.cuni.cz
Bug#696965: [PATCH] support for HW_SKIP_CONSOLE breaks use by blind people
Hello, why is that patch needed? It is quite non-obvious why would dummy driver require a console under any circumstances. It does not render anything anywhere so does not use console for anything. Thanks Michal -- 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/CAOMqctT2Yq=ejenhbhvquzqurpfmd78engr4gc-zgpbd7r1...@mail.gmail.com
Bug#693989: /usr/bin/xcalc: buttons rendered incorrectly because non-existent font is selected
Package: x11-apps Version: 7.7~2 Severity: normal File: /usr/bin/xcalc Hello, xcalc usees a specific font for the sqrt and pi buttons. This font does not exist on my system. either xcalc should depend on whatever provides it or use the existing font. See the modified config file. Changes -adobe-symbol-*-*-*-*-*-120-*-*-*-*-*-* to -*-*-*-*-*-*-*-120-*-*-*-*-adobe-symbol Thanks Michal -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (171, 'unstable'), (151, 'experimental'), (101, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7.0-rc3-amd64 (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/dash Versions of packages x11-apps depends on: ii cpp 4:4.7.2-1 ii libc62.13-37 ii libpng12-0 1.2.49-1 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.5.0-1 ii libxaw7 2:1.0.10-2 ii libxcursor1 1:1.1.13-1 ii libxext6 2:1.3.1-2 ii libxft2 2.3.1-1 ii libxkbfile1 1:1.0.8-1 ii libxmu6 2:1.1.1-1 ii libxmuu1 2:1.1.1-1 ii libxrender1 1:0.9.7-1 ii libxt6 1:1.1.3-1 Versions of packages x11-apps recommends: ii xbitmaps 1.1.1-1 Versions of packages x11-apps suggests: ii mesa-utils 8.0.1-2+b3 -- Configuration Files: /etc/X11/app-defaults/XCalc changed: ! XCalc application class resource file XCalc.Title:Calculator XCalc.IconName: Calc XCalc.IconPixmap: calculator XCalc*Cursor: hand2 XCalc*Font: 8x13 XCalc*ShapeStyle: rectangle XCalc*Command.horizDistance:2 XCalc*Command.vertDistance: 2 XCalc*Command.width:40 XCalc*Command.height: 26 XCalc*Command.internalWidth:1 XCalc*bevel.background: black XCalc*bevel.horizDistance: 4 XCalc*bevel.vertDistance: 2 XCalc*bevel.screen.horizDistance: 6 XCalc*bevel.screen.vertDistance:2 XCalc*bevel.screen.defaultDistance: 0 XCalc*bevel.screen.Label.horizDistance: 4 XCalc*bevel.screen.Label.vertDistance: 2 XCalc*bevel.screen.Label.internalHeight:1 XCalc*bevel.screen.Label.internalWidth: 1 XCalc*bevel.screen.LCD.label: 888 XCalc*bevel.screen.LCD.fromHoriz: M XCalc*bevel.screen.LCD.horizDistance: 4 XCalc*bevel.screen.LCD.vertDistance:2 XCalc*bevel.screen.INV.fromVert:LCD XCalc*bevel.screen.INV.vertDistance:4 XCalc*bevel.screen.DEG.fromHoriz: INV XCalc*bevel.screen.DEG.fromVert:LCD XCalc*bevel.screen.DEG.horizDistance: 1 XCalc*bevel.screen.RAD.fromHoriz: DEG XCalc*bevel.screen.RAD.fromVert:LCD XCalc*bevel.screen.GRAD.fromHoriz: RAD XCalc*bevel.screen.GRAD.fromVert: LCD XCalc*bevel.screen.P.label: () XCalc*bevel.screen.P.fromHoriz: GRAD XCalc*bevel.screen.P.fromVert: LCD XCalc*bevel.screen.P.horizDistance: 2 !XCalc*ti.Geometry: 171x252 XCalc*ti.bevel.screen.LCD.width:186 XCalc*ti.bevel.screen.LCD.translations: #replace\n\ Ctrlc:quit()\n\ Ctrlh:clear()\n\ None0:digit(0)\n\ None1:digit(1)\n\ None2:digit(2)\n\ None3:digit(3)\n\ None4:digit(4)\n\ None5:digit(5)\n\ None6:digit(6)\n\ None7:digit(7)\n\ None8:digit(8)\n\ None9:digit(9)\n\ KP_0:digit(0)\n\ KP_1:digit(1)\n\ KP_2:digit(2)\n\ KP_3:digit(3)\n\ KP_4:digit(4)\n\ KP_5:digit(5)\n\ KP_6:digit(6)\n\ KP_7:digit(7)\n\ KP_8:digit(8)\n\ KP_9:digit(9)\n\ KP_Enter:equal()\n\ KP_Equal:equal()\n\ KP_Multiply:multiply()\n\ KP_Add:add()\n\ KP_Subtract:subtract()\n\ KP_Decimal:decimal()\n\ KP_Separator:decimal()\n\ KP_Divide:divide()\n\ KP_Tab:equal()\n\ Clear:clear()\n\ :.:decimal()\n\ :+:add()\n\ :-:subtract()\n\ :*:multiply()\n\ :/:divide()\n\ :(:leftParen()\n\ :):rightParen()\n\ :!:factorial()\n\ e:e()\n\ :^:power()\n\ p:pi()\n\ i:inverse()\n\ s:sine()\n\ c:cosine()\n\ t:tangent()\n\ d:degree()\n\ l:naturalLog()\n\ :=:equal()\n\ n:negate()\n\ r:squareRoot()\n\ space:clear()\n\ q:quit()\n\ Delete:clear()\n\ BackSpace:clear()\n\ ,:toggle()selection()\n XCalc*ti.button1.label: 1/x XCalc*ti.button1.translations: #override,:reciprocal()unset() XCalc*ti.button2.label: x\262 XCalc*ti.button2.translations: #override,:square()unset() XCalc*ti.button3.font: -*-*-*-*-*-*-*-120-*-*-*-*-adobe-symbol XCalc*ti.button3.label: \326\140 XCalc*ti.button3.tr
Bug#681781: dummy: Please include sample xorg.conf
Package: xserver-xorg-video-dummy Version: 1:0.3.5-2+b1 Severity: wishlist File: dummy Hello, It would be quite helpful to include a sample xorg.conf, preferebly installed at /etc/X11/xorg.conf.dummy or similar. Without a configuration file using the dummy driver is quite difficult. one such configuration file can be found at https://www.xpra.org/xorg.conf Thanks Michal ##Xdummy:## Section "ServerFlags" Option "DontVTSwitch" "true" Option "AllowMouseOpenFail" "true" Option "PciForceNone" "true" Option "AutoEnableDevices" "false" Option "AutoAddDevices" "false" EndSection ##Xdummy:## Section "InputDevice" Identifier "NoMouse" Option "CorePointer" "true" Driver "void" EndSection Section "InputDevice" Identifier "NoKeyboard" Option "CoreKeyboard" "true" Driver "void" EndSection ##Xdummy:## Section "Device" Identifier "Videocard0" Driver "dummy" #VideoRam 4096000 VideoRam 256000 EndSection ##Xdummy:## Section "Monitor" Identifier "Monitor0" HorizSync 10.0 - 300.0 VertRefresh 10.0 - 200.0 #The following modeline is invalid (calculator overflowed): #Modeline "32000x32000@0" -38917.43 32000 32032 -115848 -115816 32000 32775 32826 33601 Modeline "16384x8192@10" 2101.93 16384 16416 24400 24432 8192 8390 8403 8602 Modeline "8192x4096@10" 424.46 8192 8224 9832 9864 4096 4195 4202 4301 Modeline "5120x3200@10" 199.75 5120 5152 5904 5936 3200 3277 3283 3361 Modeline "3840x2880@10" 133.43 3840 3872 4376 4408 2880 2950 2955 3025 Modeline "3840x2560@10" 116.93 3840 3872 4312 4344 2560 2622 2627 2689 Modeline "3840x2048@10" 91.45 3840 3872 4216 4248 2048 2097 2101 2151 Modeline "2048x2048@10" 49.47 2048 2080 2264 2296 2048 2097 2101 2151 Modeline "2560x1600@10" 47.12 2560 2592 2768 2800 1600 1639 1642 1681 Modeline "1920x1200@10" 26.28 1920 1952 2048 2080 1200 1229 1231 1261 Modeline "1920x1080@10" 23.53 1920 1952 2040 2072 1080 1106 1108 1135 Modeline "1680x1050@10" 20.08 1680 1712 1784 1816 1050 1075 1077 1103 Modeline "1600x900@20" 33.92 1600 1632 1760 1792 900 921 924 946 Modeline "1440x900@20" 30.66 1440 1472 1584 1616 900 921 924 946 Modeline "1360x768@20" 24.49 1360 1392 1480 1512 768 786 789 807 #common resolutions for android devices (both orientations): Modeline "800x1280@20" 25.89 800 832 928 960 1280 1310 1315 1345 Modeline "1280x800@20" 24.15 1280 1312 1400 1432 800 819 822 841 Modeline "720x1280@25" 30.22 720 752 864 896 1280 1309 1315 1345 Modeline "1280x720@25" 27.41 1280 1312 1416 1448 720 737 740 757 Modeline "768x1024@25" 24.93 768 800 888 920 1024 1047 1052 1076 Modeline "1024x768@25" 23.77 1024 1056 1144 1176 768 785 789 807 Modeline "600x1024@25" 19.90 600 632 704 736 1024 1047 1052 1076 Modeline "1024x600@25" 18.26 1024 1056 1120 1152 600 614 617 631 Modeline "536x960@25" 16.74 536 568 624 656 960 982 986 1009 Modeline "960x536@25" 15.23 960 992 1048 1080 536 548 551 563 Modeline "600x800@25" 15.17 600 632 688 720 800 818 822 841 Modeline "800x600@25" 14.50 800 832 880 912 600 614 617 631 Modeline "480x854@25" 13.34 480 512 560 592 854 873 877 897 Modeline "848x480@25" 12.09 848 880 920 952 480 491 493 505 Modeline "480x800@25" 12.43 480 512 552 584 800 818 822 841 Modeline "800x480@25" 11.46 800 832 872 904 480 491 493 505 Modeline "320x480@50" 10.73 320 352 392 424 480 490 494 505 Modeline "480x320@50" 9.79 480 512 544 576 320 327 330 337 Modeline "240x400@50" 6.96 240 272 296 328 400 408 412 421 Modeline "400x240@50" 6.17 400 432 448 480 240 245 247 253 Modeline "240x320@50" 5.47 240 272 288 320 320 327 330 337 Modeline "320x240@50" 5.10 320 352 368 400 240 245 247 253 #resolutions for android devices (both orientations) #minus the status bar #38px status bar (and width rounded up) Modeline "800x1242@20" 25.03 800 832 920 952 1242 1271 1275 1305 Modeline "1280x762@20" 22.93 1280 1312 1392 1424 762 780 783 801 Modeline "720x1242@25" 29.20 720 752 856 888 1242 1271 1276 1305 Modeline "1280x682@25" 25.85 1280 1312 1408 1440 682 698 701 717 Modeline "768x986@25" 23.90 768 800 888 920 986 1009 1013 1036 Modeline "1024x730@25" 22.50 1024 1056 1136 1168 730 747 750 767 Modeline "600x986@25" 19.07 600 632 704 736 986 1009 1013 1036 Modeline "1024x562@25" 17.03 1024 1056 1120 1152 562 575 578 591 Modeline "536x922@25" 16.01 536 568 624 656 922 943 947 969 Modeline "960x498@25" 14.09 960 992 1040 1072 498 509 511 523 Modeline "600x762@25" 14.39 600 632 680 712 762 779 783 801 Modeline "800x562@25" 13.52 800 832 880 912 562 575 578 591 Modeline "480x810@25" 12.59 480 512 552 584 810 828 832 851 Modeline "848x442@25" 11.09 848 880 920 952 442 452 454 465 Modeline "480x762@25" 11.79 480 512 552 584 762 779 783 801 Modeline "800x442@25" 10.51 800 832 864 896 442 452 454 465 #32px status bar (no need for rounding): Modeline "320x448@50" 9.93 320 352 384 416 448 457 461 471 Modeline "480x288@50" 8.75 480 512 544 576 288 294 297 303 #24px s
Bug#642433: xserver-xorg-core: crashes on pressing random keys on the keyboard while screen locked
Package: xserver-xorg-core Version: 2:1.12.1.902-1 Followup-For: Bug #642433 Applied upstream in 472c2d1af75d8e321728589e377f73116adb29fa. Please update. Thanks Michal -- 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/20120613133612.19453.17094.report...@optiplex960.ruk.cuni.cz
Bug#608365: xserver-xorg-core: crashes on exit
Package: xserver-xorg-core Followup-For: Bug #608365 This should be fixed in 1.12 now. Thanks Michal -- 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/20120601095602.8196.73708.report...@optiplex960.ruk.cuni.cz
Bug#642433: xserver-xorg-core: crashes on pressing random keys on the keyboard while screen locked
Hello, Excerpts from Maarten Lankhorst's message of Wed May 23 12:30:48 +0200 2012: > Hey Michael, > > Op 23-05-12 11:13, Michal Suchanek schreef: > > Package: xserver-xorg-core > > Version: 2:1.12.1.902-1 > > Followup-For: Bug #642433 > > > > With 1.12.1 and 1.12.1.902-1 the X server crashes again. > > > > Attaching patch. > > > That patch looks like it belongs upstream. Have you tried contacting upstream > about it? > Yes, I have. Thanks Michal -- 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/1337783757-sup-7...@virtual.ruk.cuni.cz
Bug#642433: xserver-xorg-core: crashes on pressing random keys on the keyboard while screen locked
Package: xserver-xorg-core
Version: 2:1.12.1.902-1
Followup-For: Bug #642433
With 1.12.1 and 1.12.1.902-1 the X server crashes again.
Attaching patch.
VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI
Cedar PRO [Radeon HD 5450] [1002:68f9]
/etc/X11/xorg.conf does not exist.
Contents of /etc/X11/xorg.conf.d:
-
total 8
-rw-r--r-- 1 root root 129 Oct 6 2011 10-trackball-middle-emu.conf
-rw-r--r-- 1 root root 150 Oct 6 2011 10-trackball-middle-emu.conf~
KMS configuration files:
/etc/modprobe.d/radeon-kms.conf:
options radeon modeset=1
Kernel version (/proc/version):
---
Linux version 3.2.0-2-amd64 (Debian 3.2.16-1) (debian-ker...@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Apr 30 05:20:23 UTC 2012
Xorg X server log files on system:
--
-rw-r--r-- 1 root root 43446 Oct 7 2011 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 32234 May 2 13:06 /var/log/Xorg.!.log
-rw-r--r-- 1 root root 56401 May 23 10:28 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 51686 May 23 11:07 /var/log/Xorg.0.log
-- System Information:
Debian Release: wheezy/sid
APT prefers stable
APT policy: (900, 'stable'), (500, 'testing'), (410, 'unstable'), (200,
'experimental'), (111, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg-core depends on:
ii keyboard-configuration 1.68+squeeze2
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-32
ii libdrm2 2.4.33+git20120502.52887298-0ubuntu0sarvatt~precise
ii libgcrypt11 1.5.0-3
ii libpciaccess0 0.13.1-2
ii libpixman-1-0 0.24.4-1
ii libselinux1 2.1.9-2
ii libudev0164-3
ii libxau6 1:1.0.7-1
ii libxdmcp6 1:1.1.1-1
ii libxfont1 1:1.4.5-2
ii udev164-3
ii xserver-common 2:1.13+git-20120423113043~6a1fdcd
Versions of packages xserver-xorg-core recommends:
ii libgl1-mesa-dri 8.1~git20120503.1bd3dafe-0ubuntu0ricotz~precisenw1
Versions of packages xserver-xorg-core suggests:
pn xfonts-100dpi | xfonts-75dpi
pn xfonts-scalable
-- no debconf information
--- a/dix/getevents.c 2012-05-23 10:31:42.0 +0200
+++ a/dix/getevents.c 2012-05-23 10:34:38.0 +0200
@@ -1574,7 +1574,7 @@
/* Now turn the smooth-scrolling axes back into emulated button presses
* for legacy clients, based on the integer delta between before and now */
for (i = 0; i < valuator_mask_size(&mask); i++) {
-if (i >= pDev->valuator->numAxes)
+if ( !pDev->valuator || (i >= pDev->valuator->numAxes))
break;
if (!valuator_mask_isset(&mask, i))
Bug#673169: /usr/bin/xset: cannot set keyclick
Package: x11-xserver-utils Version: 7.7~3 Severity: normal File: /usr/bin/xset Hello, I wanted to check some application which seems to ignore keypresses at times but I cannot turn on keyclick. $ xset c on ; echo $? 0 but no clicks are produced. ii xserver-xorg-core 2:1.11.4-1Xorg X server - core server -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (900, 'stable'), (500, 'testing'), (410, 'unstable'), (200, 'experimental'), (111, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages x11-xserver-utils depends on: ii cpp 4:4.6.2-4 ii libc62.13-32 ii libice6 2:1.0.8-2 ii libx11-6 2:1.4.99.901-2 ii libxaw7 2:1.0.10-2 ii libxcursor1 1:1.1.13-1 ii libxext6 2:1.3.1-2 ii libxi6 2:1.6.0-1 ii libxmu6 2:1.1.1-1 ii libxmuu1 2:1.1.1-1 ii libxrandr2 2:1.3.2-2 ii libxrender1 1:0.9.7-1 ii libxt6 1:1.1.3-1 ii libxxf86vm1 1:1.1.2-1 x11-xserver-utils recommends no packages. Versions of packages x11-xserver-utils suggests: pn cairo-5c pn nickle pn xorg-docs-core -- no debconf information -- 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/20120516154454.17536.72606.report...@optiplex960.ruk.cuni.cz
Bug#661019: xserver-xorg-core: no longer an issue with 1.12.0
Package: xserver-xorg-core Severity: normal X server 1.12.0 now builds for me. Thanks Michal -- 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/20120308150740.30334.146.report...@optiplex960.ruk.cuni.cz
Bug#608365: xserver-xorg-core: attached patch should fix the crash on close
Package: xserver-xorg-core
Severity: normal
Hello
Attaching a patch which fixed the issue shortly after it was introduced.
It does not seem applied upstream so either there is a different fix or
this is still broken.
My X server crashes way earlier so can't tell.
Thanks
Michal
Index: xserver/hw/xfree86/modes/xf86Rotate.c
===
--- xserver.orig/hw/xfree86/modes/xf86Rotate.c 2011-10-11 13:24:11.0 +0200
+++ xserver/hw/xfree86/modes/xf86Rotate.c 2011-10-11 14:31:32.0 +0200
@@ -283,6 +283,7 @@
ScrnInfoPtr pScrn = crtc->scrn;
ScreenPtr pScreen = pScrn->pScreen;
xf86CrtcConfigPtr xf86_config = XF86_CRTC_CONFIG_PTR(pScrn);
+DrawablePtr screenDrawable = &pScreen->root->drawable;
int c;
/* Free memory from rotation */
@@ -300,12 +301,12 @@
/*
* Clean up damage structures when no crtcs are rotated
*/
-if (xf86_config->rotation_damage)
+if (screenDrawable && xf86_config->rotation_damage)
{
/* Free damage structure */
if (xf86_config->rotation_damage_registered)
{
- DamageUnregister (&pScreen->root->drawable,
+ DamageUnregister (screenDrawable,
xf86_config->rotation_damage);
xf86_config->rotation_damage_registered = FALSE;
DisableLimitedSchedulingLatency();
Bug#642433: closed by Cyril Brulebois (Re: Bug#642433: crashes on pressing random keys on the keyboard while screen locked)
Excerpts from Debian Bug Tracking System's message of Tue Feb 28 12:09:30 +0100 2012: > This is an automatic notification regarding your Bug report > which was filed against the xserver-xorg-core package: > > #642433: xserver-xorg-core: crashes on pressing random keys on the keyboard > while screen locked > > It has been closed by Cyril Brulebois . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Cyril Brulebois > by > replying to this email. > > Michal Suchanek (28/02/2012): > > Package: xserver-xorg-core > > Version: 2:1.11.99.902-1 > > Severity: normal > > > > Hello, > > > > this might be fixed with http://patchwork.freedesktop.org/patch/9199/ > > However, X does not build so can't tell. > > I'm not getting this and I see no trace, no log, *nothing* in your “bug > report” so closing. Get some glasses then. Thanks Michal -- 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/1330434166-sup-8...@virtual.ruk.cuni.cz
Bug#642433: crashes on pressing random keys on the keyboard while screen locked
Package: xserver-xorg-core Version: 2:1.11.99.902-1 Severity: normal Hello, this might be fixed with http://patchwork.freedesktop.org/patch/9199/ However, X does not build so can't tell. Thanks Michal -- 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/20120228105631.22981.57054.report...@optiplex960.ruk.cuni.cz
Bug#661158: closed by Julien Cristau (Re: Bug#661158: xserver-xorg-core: breaks libxi6)
Excerpts from Debian Bug Tracking System's message of Mon Feb 27 22:36:10 +0100 2012: > This is an automatic notification regarding your Bug report > which was filed against the xserver-xorg-core package: > > #661158: xserver-xorg-core: breaks libxi6 > > It has been closed by Julien Cristau . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Julien Cristau > by > replying to this email. > > On Fri, Feb 24, 2012 at 17:10:21 +0100, Michal Suchanek wrote: > > > Package: xserver-xorg-core > > Version: 2:1.11.99.902-1 > > Severity: important > > > > > > X server breaks libxi 1.3.6 causing xinput and gtk crashes. > > > > Working version is 2:1.4.5-1 > > > > broken 2:1.3-6 > > > > fallout #661021 #659728 > > > Can't be fixed in the server, this should be fixed in libXi. > Still the X server should add the Breaks: so that it is not installed with the broken libxi (which is in stable which means it will never be fixed in Debian). Thanks Michal -- 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/1330425672-sup-3...@virtual.ruk.cuni.cz
Bug#661158: xserver-xorg-core: breaks libxi6
Package: xserver-xorg-core Version: 2:1.11.99.902-1 Severity: important X server breaks libxi 1.3.6 causing xinput and gtk crashes. Working version is 2:1.4.5-1 broken 2:1.3-6 fallout #661021 #659728 -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jan 15 2010 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2081488 Feb 2 03:44 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8] /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 8 -rw-r--r-- 1 root root 129 Oct 6 17:46 10-trackball-middle-emu.conf -rw-r--r-- 1 root root 150 Oct 6 17:45 10-trackball-middle-emu.conf~ KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.2.0-1-amd64 (Debian 3.2.2-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Wed Feb 1 08:56:58 UTC 2012 -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (900, 'stable'), (500, 'testing'), (410, 'unstable'), (200, 'experimental'), (111, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-core depends on: ii 1.68+squeeze2 system-wide keyboard preferences ii 1:1.7.18-1.1Dynamic library for security audit ii 2.13-26 Embedded GNU C Library: Shared lib ii 2.4.31+git20120208.230ec7d7 Userspace interface to kernel DRM ii 1.5.0-3 LGPL Crypto library - runtime libr ii 0.12.902-1 Generic PCI access library for X ii 0.24.4-1pixel-manipulation library for X a ii 2.0.96-1SELinux runtime shared libraries ii 164-3 libudev shared library ii 1:1.0.6-1 X11 authorisation library ii 1:1.0.3-2 X11 Display Manager Control Protoc ii 1:1.4.4-1 X11 font rasterisation library ii 164-3 /dev/ and hotplug management daemo ii 2:1.12~20111018122132~df0dd common files used by various X ser Versions of packages xserver-xorg-core recommends: ii 8.0.0~git20120209+8.0.7a free implementation of the OpenGL Versions of packages xserver-xorg-core suggests: pn xfonts-100dpi | xfonts-75dpi (no description available) pn xfonts-scalable(no description available) -- no debconf information -- 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/20120224161021.823.58338.report...@optiplex960.ruk.cuni.cz
Bug#660990: /usr/lib/xorg/modules/input/evdev_drv.so: no debug symbols.
Attaching patch which fixes the issue for me.
diff -ur xserver-xorg-input-evdev-2.6.99.901/debian/changelog xserver-xorg-input-evdev-2.6.99.901.dbg/debian/changelog
--- xserver-xorg-input-evdev-2.6.99.901/debian/changelog 2012-02-23 16:23:25.0 +0100
+++ xserver-xorg-input-evdev-2.6.99.901.dbg/debian/changelog 2012-02-23 13:01:09.0 +0100
@@ -1,3 +1,9 @@
+xserver-xorg-input-evdev (1:2.6.99.901-1dbg1) experimental; urgency=low
+
+ * Build a debug package.
+
+ -- Michal Suchanek Thu, 23 Feb 2012 13:00:50 +0100
+
xserver-xorg-input-evdev (1:2.6.99.901-1) experimental; urgency=low
[ Timo Aaltonen ]
diff -ur xserver-xorg-input-evdev-2.6.99.901/debian/control xserver-xorg-input-evdev-2.6.99.901.dbg/debian/control
--- xserver-xorg-input-evdev-2.6.99.901/debian/control 2012-02-23 16:23:25.0 +0100
+++ xserver-xorg-input-evdev-2.6.99.901.dbg/debian/control 2012-02-23 16:27:00.0 +0100
@@ -68,3 +68,19 @@
http://www.X.org>
.
This package is built from the X.org xf86-input-evdev driver module.
+
+Package: xserver-xorg-input-evdev-dbg
+Architecture: linux-any
+Section: debug
+Depends:
+ ${misc:Depends},
+ xserver-xorg-input-evdev (= ${binary:Version})
+Description: X.Org X server -- evdev input driver
+ This package provides the driver for input devices using evdev, the Linux
+ kernel's event delivery mechanism. This driver allows for multiple keyboards
+ and mice to be treated as separate input devices.
+ .
+ More information about X.Org can be found at:
+ http://www.X.org>
+ .
+ This is the debug binary for the evdev driver.
Only in xserver-xorg-input-evdev-2.6.99.901.dbg/debian: control~
diff -ur xserver-xorg-input-evdev-2.6.99.901/debian/rules xserver-xorg-input-evdev-2.6.99.901.dbg/debian/rules
--- xserver-xorg-input-evdev-2.6.99.901/debian/rules 2012-02-23 16:23:25.0 +0100
+++ xserver-xorg-input-evdev-2.6.99.901.dbg/debian/rules 2012-02-23 12:57:27.0 +0100
@@ -1,5 +1,7 @@
#!/usr/bin/make -f
+pkg=xserver-xorg-input-evdev
+
# Install in debian/tmp to retain control through dh_install:
override_dh_auto_install:
dh_auto_install --destdir=debian/tmp
@@ -9,6 +11,10 @@
find debian/tmp -name '*.la' -delete
dh_install --fail-missing
+override_dh_strip:
+ dh_strip -p$(pkg)--dbg-package=$(pkg)-dbg
+
+
# That's a plugin, use appropriate warning level:
override_dh_shlibdeps:
dh_shlibdeps -- --warnings=6
Bug#657961: xserver-xorg-video-mach64: Needs rebuild for new X server abi
Package: xserver-xorg-video-mach64 Version: 6.9.0-1+b1 Severity: normal The ati driver depends on mach64 which is built only for old X abi. Due to this the ati driver is not installable. VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8] Kernel version (/proc/version): --- Linux version 3.2.0-rc3 (hramrach@OptiPlex960) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Thu Nov 24 13:33:54 CET 2011 Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [54.897] X.Org X Server 1.11.1.902 (1.11.2 RC 2) Release Date: 2011-10-28 -- 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/20120130100534.24691.65268.report...@optiplex960.ruk.cuni.cz
Bug#657960: xserver-xorg-video-r128: Needs rebuild for current X video abi
Package: xserver-xorg-video-r128 Version: 6.8.1-5+b2 Severity: normal The ati driver is unustallable because it depends on r128 and r128 is built for old X server abi. VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8] /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 8 -rw-r--r-- 1 root root 129 Oct 6 17:46 10-trackball-middle-emu.conf -rw-r--r-- 1 root root 150 Oct 6 17:45 10-trackball-middle-emu.conf~ Kernel version (/proc/version): --- Linux version 3.2.0-rc3 (hramrach@OptiPlex960) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Thu Nov 24 13:33:54 CET 2011 Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [54.897] X.Org X Server 1.11.1.902 (1.11.2 RC 2) -- 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/20120130100358.24558.69186.report...@optiplex960.ruk.cuni.cz
Bug#648222: Significant 2D performance regression with ColorTiling
On 10 November 2011 17:46, Alex Deucher wrote: > On Wed, Nov 9, 2011 at 12:36 PM, Iustin Pop wrote: >> Package: xserver-xorg-video-radeon >> >> Version: 1:6.14.3-1 >> Severity: minor >> >> Hi, >> >> The recent upgrade of xserver-xorg-video-radeon from 1:6.14.2-2 to >> 1:6.14.3-1 enabled ColorTiling for my card, which in turn caused a >> significant performance degradation in 2D (yes, I understand it should >> make 3D faster, but I didn't know it should slow down 2D applications). >> >> I'm using plain 2D environment (openbox, no compositing, anything) and >> plain xterm (bitmap fonts, no AA, etc.). The speed of display text has >> changed significantly enough that I can "see" my mutt refreshing the >> inbox and drawing the lines. >> >> Cat-ing a big (~4K lines of text) file on a full-screen xterm is: >> >> - 6.14.2-2 (low power profile): ~0.8s >> - 6.14.3 (high power) : ~3.1s >> - 6.14.3 (low power) : ~5.0s >> >> So it's more than 5x time slower, which makes it "unpleasant". >> >> Simply disabling ColorTiling makes the problem go away, and 6.14.3 is as >> fast as 6.14.2. >> > > Tiling will speed up all rendering (2D and 3D). However, it sounds > like you are using an environment that is mostly software rendering. > As such in order for the CPU to access tiled buffers, the GPU has to > copy them to a linear buffer before CPU can access it properly. FWIW I have color tiling enabled and have no speed issues in urxvt - TrueType fonts, AA enabled, etc. Unlike xterm urxvt (rxvt-unicode) uses some special font-rendering libraries, however. If I understand it correctly xterm would use the in-server bitmap font rendering which the X server can accelerate as much as it wants. Thanks Michal -- 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/caomqctt7a-m+1hy19gwwqkmqevbzt-5edgycwcao8s_+hov...@mail.gmail.com
Bug#605444: libgl1-mesa-dri-experimental: please install the llvmpipe driver
On 21 October 2011 22:34, Julien Cristau wrote: > On Thu, Feb 10, 2011 at 16:25:16 +0100, Michal Suchanek wrote: > >> On 9 February 2011 12:55, Cyril Brulebois wrote: >> >> > >> > a patch against debian-unstable/7.10-3 would be appreciated. >> > >> > KiBi. >> >> It's quite simple. It affects >> >> - swrast when dri-experimental is installed >> - gallium based drivers - fallbacks are now llvm based (currently r300?) >> >> Note that mesa currently builds r600g but does not ship it, perhaps it >> could be also added to dri-experimental. >> I am not sure how useful the version in 7.10 is but it should improve over >> time. >> > Does llvmpipe / swrastg actually work on non-x86? > I have no idea about that. All my non-x86 hardware (excluding amd64) consistently resists any attempts to install any reasonable operating system. Thanks Michal -- 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/caomqctrwwmrblubmn_+oe1ne9wvtt3_0oeyue1xdq-pfd...@mail.gmail.com
Bug#642435: xserver-xorg-core: keyboard and mouse input broken after X reset when X not on active VT
FDO bug https://bugs.freedesktop.org/show_bug.cgi?id=41145 -- 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/1316776686-sup-3...@virtual.ruk.cuni.cz
Bug#642433: xserver-xorg-core: crashes on pressing random keys on the keyboard while screen locked
FDO bug https://bugs.freedesktop.org/show_bug.cgi?id=41149 -- 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/1316776643-sup-2...@virtual.ruk.cuni.cz
Bug#642433: xserver-xorg-core: crashes on pressing random keys on the keyboard while screen locked
The 'Lock Desktop' key produces something very weird when pressed. I have no idea how to reproduce on a standard keyboard: ButtonPress event, serial 27, synthetic NO, window 0x241, root 0x151, subw 0x242, time 121788805, (42,35), root:(111,978), state 0x0, button 2, same_screen YES EnterNotify event, serial 27, synthetic NO, window 0x241, root 0x151, subw 0x0, time 121788805, (42,35), root:(111,978), mode NotifyGrab, detail NotifyInferior, same_screen YES, focus YES, state 512 KeymapNotify event, serial 27, synthetic NO, window 0x0, keys: 81 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ButtonRelease event, serial 27, synthetic NO, window 0x241, root 0x151, subw 0x242, time 121789061, (42,35), root:(111,978), state 0x200, button 2, same_screen YES Thanks Michal -- 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/1316718040-sup-1...@virtual.ruk.cuni.cz
Bug#642435: xserver-xorg-core: keyboard and mouse input broken after X reset when X not on active VT
Excerpts from Michal Suchanek's message of Thu Sep 22 20:46:25 +0200 2011: > Excerpts from Julien Cristau's message of Thu Sep 22 18:29:58 +0200 2011: > > On Thu, Sep 22, 2011 at 18:08:11 +0200, Michal Suchanek wrote: > > > > > Package: xserver-xorg-core > > > Version: 2:1.10.4-1 > > > Severity: normal > > > > > > Hello, > > > > > > was trying to start another X server and found this bug. > > > > > > # Xorg :1 & > > > > > > # DISPLAY=:1 xscreensaver& > > > # kill %2 > > > < you are switched to the X server> > > > > > > now input does not work > > > > > Is this reproducible with 1.11? > It is still reproducible, had a client still connected in the previous test. Thanks Michal -- 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/1316717415-sup-1...@virtual.ruk.cuni.cz
Bug#642433: xserver-xorg-core: crashes on pressing random keys on the keyboard while screen locked
Excerpts from Julien Cristau's message of Thu Sep 22 18:29:21 +0200 2011: > On Thu, Sep 22, 2011 at 17:42:25 +0200, Michal Suchanek wrote: > > > Package: xserver-xorg-core > > Version: 2:1.10.4-1 > > Severity: important > > > > I locked my screen to dust off my keyboard. > > > > While doing so the X server crashed. > > > Is it reproducible with 1.11? Yes, it is. Thanks Michal -- 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/1316717540-sup-7...@virtual.ruk.cuni.cz
Bug#642435: xserver-xorg-core: keyboard and mouse input broken after X reset when X not on active VT
Excerpts from Julien Cristau's message of Thu Sep 22 18:29:58 +0200 2011: > On Thu, Sep 22, 2011 at 18:08:11 +0200, Michal Suchanek wrote: > > > Package: xserver-xorg-core > > Version: 2:1.10.4-1 > > Severity: normal > > > > Hello, > > > > was trying to start another X server and found this bug. > > > > # Xorg :1 & > > > > # DISPLAY=:1 xscreensaver& > > # kill %2 > > < you are switched to the X server> > > > > now input does not work > > > Is this reproducible with 1.11? Don't know. It does not reset on last client disconnecting. Thanks Michal -- 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/1316717128-sup-9...@virtual.ruk.cuni.cz
Bug#642433: xserver-xorg-core: crashes on pressing random keys on the keyboard while screen locked
Package: xserver-xorg-core
Version: 2:1.10.4-1
Followup-For: Bug #642433
Sending stack trace:
Program received signal SIGSEGV, Segmentation fault.
0x0044719c in GetPointerEvents (events=0x230f390, pDev=0x22ff270,
type=6, buttons=0, flags=,
mask_in=0x7fffee0d1fb0) at ../../dix/getevents.c:1160
1160../../dix/getevents.c: No such file or directory.
in ../../dix/getevents.c
(gdb) bt full
#0 0x0044719c in GetPointerEvents (events=0x230f390, pDev=0x22ff270,
type=6, buttons=0, flags=,
mask_in=0x7fffee0d1fb0) at ../../dix/getevents.c:1160
scaled =
num_events = 1
ms = 112047063
event =
raw = 0x0
x = 0
y = 0
cx =
cy =
x_frac = 0
y_frac = 0
cx_frac =
cy_frac =
scr = 0x206d480
mask = {last_bit = 1 '\001', mask = "\003\000\000\000", valuators =
{666, 499, 0 }}
#1 0x0045df30 in miPointerMove (pDev=0x22ff270, pScreen=0x206d480,
x=666, y=499) at ../../mi/mipointer.c:576
i =
nevents =
valuators = {666, 499}
mask = {last_bit = 1 '\001', mask = "\003\000\000\000", valuators =
{666, 499, 0 }}
#2 miPointerWarpCursor (pDev=0x22ff270, pScreen=0x206d480, x=666, y=499) at
../../mi/mipointer.c:310
pPointer =
changedScreen = 0 '\000'
pScreenPriv = 0x1
#3 0x00525801 in xf86WarpCursor (pDev=0x22ff270, pScreen=0x206d480,
x=666, y=499)
at ../../../../hw/xfree86/common/xf86Cursor.c:473
sigstate = 0
#4 0x0045e42f in miPointerSetCursorPosition (pDev=0x22ff270,
pScreen=, x=,
y=, generateEvent=1) at ../../mi/mipointer.c:233
pScreenPriv = 0x0
#5 0x005670d3 in AnimCurSetCursorPosition (pDev=,
pScreen=0x206d480, x=,
y=, generateEvent=) at
../../render/animcur.c:261
as = 0x209ee50
ret =
#6 0x0043f2a2 in ProcWarpPointer (client=) at
../../dix/events.c:3311
dest = 0x20d0380
x = 666
y = 499
rc =
newScreen = 0x206d480
dev = 0x22ff270
tmp =
pSprite = 0x21b5000
stuff = 0x234eca8
#7 0x00432ee9 in Dispatch () at ../../dix/dispatch.c:431
clientReady = 0x22dbe50
result =
client = 0x22d3c00
nready = 0
icheck = 0x7e95f0
start_tick = 0
#8 0x00426ffe in main (argc=2, argv=, envp=) at ../../dix/main.c:287
i =
alwaysCheckForInput = {0, 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/2011092216.2103.10078.report...@optiplex960.ruk.cuni.cz
Bug#642433: xserver-xorg-core: crashes on pressing random keys on the keyboard while screen locked
Package: xserver-xorg-core Version: 2:1.10.4-1 Followup-For: Bug #642433 It is easily reproduced with 1) locking the screen 2) pressing Esc key 3) pressing 'Lock Desktop' key -- 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/20110922155103.31830.91272.report...@optiplex960.ruk.cuni.cz
Bug#627924: closed by Cyril Brulebois (Re: Bug#627924: libgl1-mesa-dri-experimental: no vmwgfx support)
Excerpts from Debian Bug Tracking System's message of Wed May 25 16:55:11 +0200 2011: > This is an automatic notification regarding your Bug report > which was filed against the libgl1-mesa-dri-experimental package: > > #627924: libgl1-mesa-dri-experimental: no vmwgfx support > > It has been closed by Cyril Brulebois . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Cyril Brulebois > by > replying to this email. > > Michal Suchanek (25/05/2011): > > Package: libgl1-mesa-dri-experimental > > Version: 7.10.2-2 > > Severity: wishlist > > Next time, add some text. Better yet, a patch. > > Tired of useless reports, closing. Tired of people uselessly closing reports of actual bugs. In search of a distribution with working X I guess. Regards Michal -- 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/1306336710-sup-7...@virtual.ruk.cuni.cz
Bug#624572: mesa: r300g "striped" and "flashing" shadows
Package: mesa Version: 7.10.2-1 Severity: normal In mesa 7.10 shadows in some applications runnning on r300 class hardware (r300g driver) can be non-contiguous. This results in some large shaded objects being striped and shadows on smaller objects flashing as they move through the scene. This is resolved with current mesa git (7.11). Note that another possible effect of this issue is that some objects have sharp totally black shadows where there are ususally none visible when the scene is rendered on different hardware or different driver version. -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (400, 'unstable'), (395, 'experimental'), (300, 'stable-i386'), (300, 'oldstable'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'experimental-i386'), (65, 'oldstable-i386') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20110429181116.10036.39102.report...@heretic.burning-in.hell
Bug#563203: xserver-xorg-video-vesa: does not use native panel resolution
On 4 April 2011 01:03, Cyril Brulebois wrote: > Cyril Brulebois (04/04/2011): >> what's the status with squeeze, sid, or experimental? > > FWIW: > 01:00:23 [ airlied] KiBi: I think you have to use i915resolution on those > > It'd be nice to try that if it doesn't work out of the box. > > KiBi. > With the Paulsbo stub driver it would work I expect. I think I can try the Squeeze live CD, don't have an experimental CD ready. Thanks Michal -- 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/BANLkTi=xeuq2dmaddhwa8ynr4ejwon1...@mail.gmail.com
Bug#619473: evdev: wheel emulation uses button numbers before mapping
On 24 March 2011 17:09, Julien Cristau wrote: > On Thu, Mar 24, 2011 at 11:36:22 +0100, Michal Suchanek wrote: > >> Package: xserver-xorg-input-evdev >> Version: 1:2.6.0-2 >> Severity: normal >> File: evdev >> >> >> The button which triggers wheel emulation is not affected by button >> remap. This is omewhat inconsistent and is not documented. >> >> eg if I swap left and right button and have the button 1 trigger wheel >> emulation it is still triggered by left button, not right button. >> > How are you swapping the buttons? xinput set-button-map "Logitech USB Trackball" 3 2 1 4 5 6 7 5 4 Thanks Michal -- 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/AANLkTi=iNL2brwsPCgN7bkPC=glhztjq7y91u8-nr...@mail.gmail.com
Bug#619473: evdev: wheel emulation uses button numbers before mapping
Package: xserver-xorg-input-evdev Version: 1:2.6.0-2 Severity: normal File: evdev The button which triggers wheel emulation is not affected by button remap. This is omewhat inconsistent and is not documented. eg if I swap left and right button and have the button 1 trigger wheel emulation it is still triggered by left button, not right button. -- 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/20110324103622.27990.88698.report...@heretic.burning-in.hell
Bug#619466: xserver-xorg-input-evdev: some keys do not produce events
On 24 March 2011 10:49, Cyril Brulebois wrote: > Michal Suchanek (24/03/2011): >> On my keyboard the extra keys other than the audio keys produce no >> events. xev reports nothing when one of the keys is pressed. This is >> quite odd for buttons like zoom-in, zoom-out, 1-5, email, home, MSN, >> star which are present on most multimedia keyboards. > > Try with evtest $device on a console, if there's nothing coming up, > talk to kernel people. If there's something: > http://bugs.freedesktop.org/ product=xorg, component=Input/evdev > Nothing is coming up with evtest even for keys that work (eg VolumeUp). Thanks Michal -- 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/AANLkTimjWimg5vV38j+XqCt3dzPtijn8YuL8tm=qy...@mail.gmail.com
Bug#558318: Missing trackball support
Package: xserver-xorg-input-evdev Followup-For: Bug #558318 You can set the options dynamically with xinput and some desktop environments have a configuration applet for that. I never managed to set any evdev options with udev. Doing so is undocumented as is setting options with xinput. On the other hand, the evdev man page refers to xorg.conf which documents xorg.conf.d, a (hopefully) platform independent way of configuring these devices (eg even on systems without udev). It realies on the platform to correctly provide the device IDs, though. Thanks Michal -- 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/20110324093542.25364.45966.report...@heretic.burning-in.hell
Bug#524590: reconnect a bluetooth keyboard is not possible..
Package: xserver-xorg-input-evdev Followup-For: Bug #524590 I guess this is like #584148 and the other reconnect bugs. Had one too. Should be gone with udev. Thanks Michal -- 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/20110324083510.25143.33241.report...@heretic.burning-in.hell
Bug#541212: xserver resets xkb configuration on first keypress
Package: xserver-xorg-input-evdev Followup-For: Bug #541212 This should not longer be an issue with X server 1.9. Thanks Michal -- 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/20110324083011.24963.77945.report...@heretic.burning-in.hell
Bug#618622: xserver-xorg-core: crash when resizing screen while running a fullscreen application
2011/3/17 Michel Dänzer : > On Don, 2011-03-17 at 11:44 +0100, Michal Suchanek wrote: >> 2011/3/17 Michel Dänzer : >> > On Don, 2011-03-17 at 11:07 +0100, Michal Suchanek wrote: >> >> >> >> ==28521== Invalid write of size 1 >> >> ==28521== at 0x4C26044: memcpy (mc_replace_strmem.c:497) >> >> ==28521== by 0x8FF277A: RADEONDownloadFromScreenCS >> >> (radeon_exa_funcs.c:667) >> >> ==28521== by 0x9693326: exaCopyDirty (exa_migration_classic.c:220) >> >> ==28521== by 0x9695D79: exaPrepareAccessReg_mixed >> >> (exa_migration_mixed.c:247) >> >> ==28521== by 0x969ED93: ExaCheckImageGlyphBlt (exa_unaccel.c:326) >> >> ==28521== by 0x56766D: miImageText8 (mipolytext.c:114) >> >> ==28521== by 0x4D07C6: damageImageText8 (damage.c:1547) >> >> ==28521== by 0x4399CC: doImageText (dixfonts.c:1559) >> >> ==28521== by 0x439A4F: ImageText (dixfonts.c:1604) >> >> ==28521== by 0x430342: ProcImageText8 (dispatch.c:2290) >> >> ==28521== by 0x4334D0: Dispatch (dispatch.c:431) >> >> ==28521== by 0x42575A: main (main.c:287) >> >> ==28521== Address 0xd4c0040 is 0 bytes after a block of size 5,242,880 >> > >> > Can you run valgrind with --db-attach=yes and get a full gdb backtrace >> > at this point? (With xserver-xorg-core-dbg and >> > xserver-xorg-video-radeon-dbg installed) >> >> It does not offer to attach a debugger at this error. > > But it does at other errors? > No, running # valgrind --db-attach=yes Xorg :1 just terminates after printing the m_mallocfree error. -- 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/AANLkTikV0ZsD74ZhwjCa3OW6a7mbv�xrqwkaolg...@mail.gmail.com
Bug#618622: xserver-xorg-core: crash when resizing screen while running a fullscreen application
2011/3/17 Michel Dänzer : > On Don, 2011-03-17 at 11:07 +0100, Michal Suchanek wrote: >> 2011/3/17 Michel Dänzer : >> > On Don, 2011-03-17 at 10:30 +0100, Michal Suchanek wrote: >> >> 2011/3/17 Michel Dänzer : >> >> > On Don, 2011-03-17 at 09:31 +0100, Michal Suchanek wrote: >> >> >> 2011/3/17 Michel Dänzer : >> >> >> > On Don, 2011-03-17 at 00:46 +0100, Michal Suchanek wrote: >> >> >> >> >> >> >> >> Running a fullscreen d3d application that changes screen mode (such >> >> >> >> as >> >> >> >> Vazteroids, in Wine) causes one screen to go blank and the other to >> >> >> >> switch to the resolution the application requested. >> >> >> >> >> >> >> >> When I run my script that sets the main screen to native resolution >> >> >> >> and >> >> >> >> reenables the other screen and exit the d3d application X crashes. >> >> >> > >> >> >> > Please try to provide more information about the crash. Preferably a >> >> >> > full gdb backtrace, but at least an X log file with a backtrace. >> >> >> >> >> >> It's a double free (abort) so there is no backtrace in the log. There >> >> >> is a gdb backtrace attached to the original report. >> >> > >> >> > Oh, I didn't notice the attachment, and you didn't mention it. >> >> > >> >> > Probably the fastest way to track down the problem would be to run the X >> >> > server in valgrind. >> >> >> >> A valgrind log showing some (probably unrelated) issues. >> >> >> >> As I need to run the X server as root to run in valgrind the >> >> environment is different and there is probably some piece missing. >> >> >> >> I can't reproduce the crash as root with valgrind or without. >> > >> > The X server always runs as root. You can run the clients from the same >> > user accounts as before. >> >> There are some issues like the Xsession script not making sure that >> there is at least one client running so that the X server does not >> reset and X server crashing instead of resetting but now valgrind >> aborts the X server as soon as I run the xrandr script, not after >> quitting the application as glibc does. > > [...] > >> ==28521== Invalid write of size 1 >> ==28521== at 0x4C26044: memcpy (mc_replace_strmem.c:497) >> ==28521== by 0x8FF277A: RADEONDownloadFromScreenCS >> (radeon_exa_funcs.c:667) >> ==28521== by 0x9693326: exaCopyDirty (exa_migration_classic.c:220) >> ==28521== by 0x9695D79: exaPrepareAccessReg_mixed >> (exa_migration_mixed.c:247) >> ==28521== by 0x969ED93: ExaCheckImageGlyphBlt (exa_unaccel.c:326) >> ==28521== by 0x56766D: miImageText8 (mipolytext.c:114) >> ==28521== by 0x4D07C6: damageImageText8 (damage.c:1547) >> ==28521== by 0x4399CC: doImageText (dixfonts.c:1559) >> ==28521== by 0x439A4F: ImageText (dixfonts.c:1604) >> ==28521== by 0x430342: ProcImageText8 (dispatch.c:2290) >> ==28521== by 0x4334D0: Dispatch (dispatch.c:431) >> ==28521== by 0x42575A: main (main.c:287) >> ==28521== Address 0xd4c0040 is 0 bytes after a block of size 5,242,880 > > Can you run valgrind with --db-attach=yes and get a full gdb backtrace > at this point? (With xserver-xorg-core-dbg and > xserver-xorg-video-radeon-dbg installed) > It does not offer to attach a debugger at this error. Thanks Michal -- 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/aanlktikzk7mnxorc6cqznderuilouwcnqghdqdnts...@mail.gmail.com
Bug#527139: Xsession: Re: does not prevent X server reset during session setup
Package: x11-common Version: 1:7.5+8 Followup-For: Bug #527139 Ok, so I try to run # valgrind Xorg :1 $ DISPLAY=:1 /etc/X11/Xsession and again, the X server resets in the middle of execution the session which can be easily observed as X server crash. -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (400, 'unstable'), (395, 'experimental'), (300, 'stable-i386'), (300, 'oldstable'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'experimental-i386'), (65, 'oldstable-i386') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-2-amd64 (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 x11-common depends on: ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip x11-common recommends no packages. x11-common suggests no packages. -- debconf-show failed -- 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/20110317101756.30756.14046.report...@heretic.burning-in.hell
Bug#618622: xserver-xorg-core: crash when resizing screen while running a fullscreen application
2011/3/17 Michel Dänzer : > On Don, 2011-03-17 at 09:31 +0100, Michal Suchanek wrote: >> 2011/3/17 Michel Dänzer : >> > On Don, 2011-03-17 at 00:46 +0100, Michal Suchanek wrote: >> >> >> >> Running a fullscreen d3d application that changes screen mode (such as >> >> Vazteroids, in Wine) causes one screen to go blank and the other to >> >> switch to the resolution the application requested. >> >> >> >> When I run my script that sets the main screen to native resolution and >> >> reenables the other screen and exit the d3d application X crashes. >> > >> > Please try to provide more information about the crash. Preferably a >> > full gdb backtrace, but at least an X log file with a backtrace. >> >> It's a double free (abort) so there is no backtrace in the log. There >> is a gdb backtrace attached to the original report. > > Oh, I didn't notice the attachment, and you didn't mention it. > > Probably the fastest way to track down the problem would be to run the X > server in valgrind. A valgrind log showing some (probably unrelated) issues. As I need to run the X server as root to run in valgrind the environment is different and there is probably some piece missing. I can't reproduce the crash as root with valgrind or without. Thanks Michal valgrind Xorg :1 ==20619== Memcheck, a memory error detector ==20619== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==20619== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==20619== Command: Xorg :1 ==20619== X.Org X Server 1.9.99.903 (1.10.0 RC 3) Release Date: 2011-2-24 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian Current Operating System: Linux heretic 2.6.37-2-amd64 #1 SMP Sun Feb 27 10:12:22 UTC 2011 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.37-2-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro console=ttyS0,115200n8r console=tty0 Build Date: 25 February 2011 02:25:58PM xorg-server 2:1.9.99.903-1 (Cyril Brulebois ) Current version of pixman: 0.21.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Thu Mar 17 09:57:18 2011 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Failed to load module "vesa" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0) (II) [KMS] Kernel modesetting enabled. ==20619== Syscall param ioctl(generic) points to uninitialised byte(s) ==20619==at 0x68FCE27: ioctl (syscall-template.S:82) ==20619==by 0x8937ED7: drmIoctl (in /lib/libdrm.so.2.4.0) ==20619==by 0x893B7C4: drmModeGetCrtc (in /lib/libdrm.so.2.4.0) ==20619==by 0x9034BC4: drmmode_pre_init (drmmode_display.c:592) ==20619==by 0x90319BE: RADEONPreInit_KMS (radeon_kms.c:630) ==20619==by 0x46B949: InitOutput (xf86Init.c:519) ==20619==by 0x42559C: main (main.c:205) ==20619== Address 0x7ff0005c0 is on thread 1's stack ==20619== ==20619== Syscall param ioctl(generic) points to uninitialised byte(s) ==20619==at 0x68FCE27: ioctl (syscall-template.S:82) ==20619==by 0x8937ED7: drmIoctl (in /lib/libdrm.so.2.4.0) ==20619==by 0x893B63B: drmModeGetEncoder (in /lib/libdrm.so.2.4.0) ==20619==by 0x9034D79: drmmode_pre_init (drmmode_display.c:938) ==20619==by 0x90319BE: RADEONPreInit_KMS (radeon_kms.c:630) ==20619==by 0x46B949: InitOutput (xf86Init.c:519) ==20619==by 0x42559C: main (main.c:205) ==20619== Address 0x7ff000618 is on thread 1's stack ==20619== ==20619== Syscall param ioctl(generic) points to uninitialised byte(s) ==20619==at 0x68FCE27: ioctl (syscall-template.S:82) ==20619==by 0x8937ED7: drmIoctl (in /lib/libdrm.so.2.4.0) ==20619==by 0x893BA74: drmModeGetProperty (in /lib/libdrm.so.2.4.0) ==20619==by 0x9035058: drmmode_pre_init (drmmode_display.c:1013) ==20619==by 0x90319BE: RADEONPreInit_KMS (radeon_kms.c:630) ==20619==by 0x46B949: InitOutput (xf86Init.c:519) ==20619==by 0x42559C: main (main.c:205) ==20619== Address 0x7ff0005e8 is on thread 1's stack ==20619== ==20619== Syscall param ioctl(generic) points to uninitialised byte(s) ==20619==at 0x68FCE27: ioctl (syscall-template.S:82) ==20619==by 0x8937ED7: drmIoctl (in /lib/libdrm.so.2.4.0) ==20619==by 0x893BA74: drmModeGetProperty (in /lib/libdrm.so.2.4.0) ==20619==by 0x903435F: drmmode_output_get_modes (drmmode_display.c:645) ==20619==by 0x482AED: xf86
Bug#618622: xserver-xorg-core: crash when resizing screen while running a fullscreen application
2011/3/17 Michel Dänzer : > On Don, 2011-03-17 at 00:46 +0100, Michal Suchanek wrote: >> >> Running a fullscreen d3d application that changes screen mode (such as >> Vazteroids, in Wine) causes one screen to go blank and the other to >> switch to the resolution the application requested. >> >> When I run my script that sets the main screen to native resolution and >> reenables the other screen and exit the d3d application X crashes. > > Please try to provide more information about the crash. Preferably a > full gdb backtrace, but at least an X log file with a backtrace. It's a double free (abort) so there is no backtrace in the log. There is a gdb backtrace attached to the original report. Thanks Michal -- 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/AANLkTi=KtYhGW4GVGnGbh_=d-bkr7ck4mdhom-ofi...@mail.gmail.com
Bug#618622: crash when resizing screen while running a fullscreen application
Package: xserver-xorg-core Version: 2:1.9.99.903-1 Followup-For: Bug #618622 Still a problem with current X. -- 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/20110317004059.3957.92404.report...@heretic.burning-in.hell
Bug#618622: crash when resizing screen while running a fullscreen application
Package: xserver-xorg-core Version: 2:1.9.4.901-1 Followup-For: Bug #618622 Can be reproduced with frozen-bubble as well except it is harder to trigger be cause it grabs keyboard. -- 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/20110317000446.31030.21212.report...@heretic.burning-in.hell
Bug#618375: xserver-xorg-core: when a module is reloaded verion of module not reported
Package: xserver-xorg-core Version: 2:1.9.4.901-1 Severity: minor When a module is unloaded and then loaded again to handle another device the version of the newly loaded module is not reported. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Jan 14 2008 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1926304 Mar 7 16:48 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV530LE [Radeon X1600/X1650 PRO] [1002:71c6] Xorg X server configuration file status: -rw-r--r-- 1 root root 754 Aug 29 2010 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "ServerFlags" Option "HandleSpecialKeys" "Always" Option "AllowDeactivateGrabs" "on" Option "AllowClesedownGrabs" "on" EndSection /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/i915-kms.conf: options i915 modeset=1 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 2.6.36-r600fence-amd64 (hramrach@OptiPlex960) (gcc version 4.4.5 (Debian 4.4.5-4) ) #1 SMP Sat Oct 30 15:04:31 CEST 2010 Xorg X server log files on system: -- -rw-r--r-- 1 root root 60451 Oct 27 22:23 /var/log/Xorg.1.log -rw-r--r-- 1 root root 519521 Mar 14 20:37 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [1530211.769] X.Org X Server 1.9.4 Release Date: 2011-02-04 [1530211.769] X Protocol Version 11, Revision 0 [1530211.769] Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian [1530211.770] Current Operating System: Linux heretic 2.6.36-r600fence-amd64 #1 SMP Sat Oct 30 15:04:31 CEST 2010 x86_64 [1530211.770] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.36-r600fence-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro console=ttyS0,115200n8r console=tty0 [1530211.770] Build Date: 20 February 2011 04:48:15AM [1530211.770] xorg-server 2:1.9.4-3 (Cyril Brulebois ) [1530211.770] Current version of pixman: 0.16.4 [1530211.770] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [1530211.770] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [1530211.770] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 11 21:56:31 2011 [1530211.907] (==) Using config file: "/etc/X11/xorg.conf" [1530211.907] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [1530211.974] (==) No Layout section. Using the first Screen section. [1530211.975] (==) No screen section available. Using defaults. [1530211.975] (**) |-->Screen "Default Screen Section" (0) [1530211.975] (**) | |-->Monitor "" [1530211.975] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [1530211.975] (==) Automatically adding devices [1530211.975] (==) Automatically enabling devices [1530212.032] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [1530212.032] Entry deleted from font path. [1530212.032] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [1530212.032] Entry deleted from font path. [1530212.032] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [1530212.032] Entry deleted from font path. [1530212.050] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [1530212.050] Entry deleted from font path. [1530212.050] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [1530212.050] Entry deleted from font path. [1530212.095] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins [1530212.095] (==) ModulePath set to "/usr/lib/xorg/modules" [1530212.095] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [1530212.095] (II) Loader
Bug#589839: /usr/bin/xgamma: Still cannot set gamma on multiple monitors attached to one screen
On 13 March 2011 15:39, Julien Cristau wrote: > On Sun, Mar 13, 2011 at 13:15:09 +0100, Michal Suchanek wrote: > >> Package: x11-xserver-utils >> Version: 7.6+1 >> Severity: normal >> File: /usr/bin/xgamma >> >> >> xgamma is still broken, it cannot set gamma on screens that have >> multiple monitors. >> >> -screen 1 gives error >> -screen 0.n affects the second screen of rany value of n >> > Not a bug. Use xrandr to change gamma for randr outputs. > Then this should be documented in xgamma(1) that the utility is in fact useless and superseded by xrandr. Thanks Michal -- 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/aanlktimajqqsrwyd-8otqppbcbjy8b2nf7s4ffhac...@mail.gmail.com
Bug#589839: /usr/bin/xgamma: Still cannot set gamma on multiple monitors attached to one screen
Package: x11-xserver-utils Version: 7.6+1 Severity: normal File: /usr/bin/xgamma xgamma is still broken, it cannot set gamma on screens that have multiple monitors. -screen 1 gives error -screen 0.n affects the second screen of rany value of n -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (400, 'unstable'), (395, 'experimental'), (300, 'stable-i386'), (300, 'oldstable'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'experimental-i386'), (65, 'oldstable-i386') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-r600fence-amd64 (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 x11-xserver-utils depends on: ii cpp 4:4.4.5-2 The GNU C preprocessor (cpp) ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libice6 2:1.0.7-1 X11 Inter-Client Exchange library ii libx11-6 2:1.4.1-5 X11 client-side library ii libxau6 1:1.0.6-1 X11 authorisation library ii libxaw7 2:1.0.9-2 X11 Athena Widget library ii libxcursor1 1:1.1.11-1 X cursor management library ii libxext6 2:1.2.0-2 X11 miscellaneous extension librar ii libxi62:1.4.1-1 X11 Input extension library ii libxmu6 2:1.1.0-1 X11 miscellaneous utility library ii libxmuu1 2:1.1.0-1 X11 miscellaneous micro-utility li ii libxrandr22:1.3.1-1 X11 RandR extension library ii libxrender1 1:0.9.6-1 X Rendering Extension client libra ii libxt61:1.0.9-2 X11 toolkit intrinsics library ii libxxf86vm1 1:1.1.1-1 X11 XFree86 video mode extension l x11-xserver-utils recommends no packages. Versions of packages x11-xserver-utils suggests: pn cairo-5c (no description available) pn nickle (no description available) pn xorg-docs-core (no description available) -- debconf-show failed -- 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/20110313121509.19760.11463.report...@heretic.burning-in.hell
Bug#478263: xdm: does not allow to log in when no password is set
Excerpts from Cyril Brulebois's message of Sun Mar 06 08:16:47 +0100 2011: > Cyril Brulebois (06/03/2011): > > if you'd like this bug to be looked at, you probably want to report > > it upstream (product xorg, component App/xdm): > > http://bugs.freedesktop.org/ > > Actually, man xdm says: > >xlogin.Login.allowNullPasswd > If set to ``true'', allow an otherwise failing password match to > succeed if the account does not require a password at all. The > default is ``false'', so only users that have passwords assigned > can log in. > This is a discrepancy between login(1) and xdm then. login(1) allows users with no password to log on without any issues or special settings. Thanks Michal -- 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/1299498232-sup-...@virtual.ruk.cuni.cz
Bug#566152: video-fbdev: nothing displayed after switching to console and back
Excerpts from Cyril Brulebois's message of Mon Feb 28 03:47:04 +0100 2011: > retitle 566152 xserver-xorg-video-fbdev: nothing displayed after switching to > console and back > thanks > > Michal Suchanek (21/01/2010): > > Package: xserver-xorg-video-fbdev > > Version: 1:0.4.1-1 > > Severity: normal > > File: video-fbdev > > > > > > After switching to console and back nothing is visible on the screen. > > > > Ir may be blank or in standby mode but it is not off. > > Might have been a kernel bug or so. Is it going better in squeeze or higher? > > If that's still happening, any chance you could trying querying DPMS > info? (From a console/ssh, that'd be “DISLAY=… xset q”, around the > bottom.) Should be fixed by KMS console. Thanks Michal -- 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/1298922662-sup-...@virtual.ruk.cuni.cz
Bug#509455: closed by Cyril Brulebois (Re: Bug#509455: xserver-xorg: keyboard and mouse driver not installed)
Excerpts from Debian Bug Tracking System's message of Fri Feb 25 21:57:09 +0100 2011: > This is an automatic notification regarding your Bug report > which was filed against the xserver-xorg package: > > #509455: xserver-xorg: keyboard and mouse driver not installed > > It has been closed by Cyril Brulebois . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Cyril Brulebois > by > replying to this email. > > Hi, > > Michal Suchanek (22/12/2008): > > For some reason installing X no longer installs the input drivers. > > > > I get no mouse nor keyboard input in X. > > > > With gdm installed this is somewhat problematic. > > not sure what you meant by “installing X” but we have several ways to > do so, as documented here: > http://packages.qa.debian.org/x/xorg-server/news/20110217T003248Z.html > > Also, gdm3 recommends xserver-xorg, so this bug can safely be closed. As you can see I had xserver-xorg installed and still did not get any input. xserver-xorg now depends on input-evdev so this should be no longer possible. Thanks Michal > > KiBi. > Package: xserver-xorg > Version: 1:7.3+18 > Severity: important > > > For some reason installing X no longer installs the input drivers. > > I get no mouse nor keyboard input in X. > > With gdm installed this is somewhat problematic. > > Thanks > > Michal > > > -- Package-specific info: > Contents of /var/lib/x11/X.roster: > xserver-xorg > > /var/lib/x11/X.md5sum does not exist. > > X server symlink status: > lrwxrwxrwx 1 root root 13 2008-12-22 15:49 /etc/X11/X -> /usr/bin/Xorg > -rwxr-xr-x 1 root root 1718580 2008-11-15 16:57 /usr/bin/Xorg > > Contents of /var/lib/x11/xorg.conf.roster: > xserver-xorg > > VGA-compatible devices on PCI bus: > 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 > > /etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum. > > Xorg X server configuration file status: > -rw-r--r-- 1 root root 1262 2008-12-22 16:01 /etc/X11/xorg.conf > > Contents of /etc/X11/xorg.conf: > # xorg.conf (X.Org X Window System server configuration file) > # > # This file was generated by dexconf, the Debian X Configuration tool, using > # values from the debconf database. > # > # Edit this file with caution, and see the xorg.conf manual page. > # (Type "man xorg.conf" at the shell prompt.) > # > # This file is automatically updated on xserver-xorg package upgrades *only* > # if it has not been modified since the last upgrade of the xserver-xorg > # package. > # > # If you have edited this file but would like it to be automatically updated > # again, run the following command: > # sudo dpkg-reconfigure -phigh xserver-xorg > > Section "ServerLayout" > Identifier "Default Layout" > Screen "Default Screen" > InputDevice "Generic Keyboard" "CoreKeyboard" > InputDevice "Configured Mouse" "CorePointer" > EndSection > > Section "InputDevice" > Identifier "Generic Keyboard" > Driver "kbd" > Option "XkbRules" "xorg" > Option "XkbModel" "pc105" > Option "XkbLayout" "us" > EndSection > > Section "InputDevice" > Identifier "Configured Mouse" > Driver "vmmouse" > EndSection > > Section "Device" > Identifier "Configured Video Device" > EndSection > > Section "Monitor" > Identifier "Configured Monitor" > EndSection > > Section "Screen" > Identifier "Default Screen" > Monitor "Configured Monitor" > EndSection > > > Xorg X server log files on system: > -rw-r--r-- 1 root root 8706 2008-12-22 16:01 /var/log/Xorg.0.log > > Contents of most recent Xorg X server log file > /var/log/Xorg.0.log: > > X.Org X Server 1.4.2 > Release Date: 11 June 2008 > X Protocol Version 11, Revision 0 > Build Operating System: Linux Debian (xorg-server 2:1.4.2-9) > Current Operating System: Linux debian-ghost 2.6.26-1-486 #1 Mon Dec 15 > 17:32:01 UTC 2008 i686 > Build Date: 15 November 2008 05:39:59PM > > Before reporting problems, check http://wiki.x.org > t
Bug#586353: xserver-xorg-core: input devices disabled by X server
On 27 February 2011 22:31, Cyril Brulebois wrote: > Hi, > > Michal Suchanek (18/06/2010): >> At the end of the log X server says that the input device has >> changed and will be disabled which is exactly what it did, leaving >> me with no input. > > still having this issue with squeeze or higher? Like Julien, I'm not > sure I get what you're trying to say, could you please rephrase what > you did, what didn't work, and what's expected? > I did nothing special, just changed some USB cabling while the machine was suspended, or possibly just unloaded the USB modules. The X server then refused to use any of the connected input devices, just as it said in the log. This probably does not apply to current X server, did not happen with any recent X version. Thanks Michal -- 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/AANLkTinxOQ92UVbm-WoawU6XEYBw2b6cHr-wO=yuq...@mail.gmail.com
Bug#538322: xserver-xorg: subpixel rendering broken on rotated screen
On 26 February 2011 12:10, Julien Cristau wrote: > On Sat, Feb 26, 2011 at 11:50:56 +0100, Michal Suchanek wrote: > >> On 26 February 2011 00:07, Cyril Brulebois wrote: >> > Hi, >> > >> > Michal Suchanek (24/07/2009): >> >> Subpixel rendering creates blue edges on the left and red on the >> >> right on non-rotaed screen .. and it does the same on a rotated >> >> screen. >> > >> > still happening in squeeze or higher? >> > >> > KiBi. >> > >> >> How would it not? >> > By being fixed? > >> Does X server provide any hints to the rendering libs about the >> packing of r/g/b in different parts of screen? >> > Yes. > > I'm not sure why you filed this bug against the X server though. > OK, X provides the information, although in not very practical format. So remaining issues (if any) would be in toolkits. Thanks Michal -- 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/AANLkTimez-Rjob8od76=w2abs7dej-h4+sftmpe74...@mail.gmail.com
Bug#538322: xserver-xorg: subpixel rendering broken on rotated screen
On 26 February 2011 00:07, Cyril Brulebois wrote: > Hi, > > Michal Suchanek (24/07/2009): >> Subpixel rendering creates blue edges on the left and red on the >> right on non-rotaed screen .. and it does the same on a rotated >> screen. > > still happening in squeeze or higher? > > KiBi. > How would it not? Does X server provide any hints to the rendering libs about the packing of r/g/b in different parts of screen? AFAIK the rendering libs operate on the assumption that it is the same on all screens, does not change, ... Thanks Michal -- 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/AANLkTimdDcWC2A6=t3vekdcvy8phzk0y3os8zzqmf...@mail.gmail.com
Bug#527139: /etc/X11/Xsession: does not prevent X server reset during session setup
On 26 February 2011 00:03, Cyril Brulebois wrote: > Hi, > > Michal Suchanek (05/05/2009): >> Running >> >> /etc/X11/Xsession >> >> does the X session setup and starts a session. >> >> However, it looks like the X server resets between merging ~/.Xresources >> and starting the final application. > > still having this issue? Any reason to think the X scripts have been updated to fix this issue? > > Anyway, wild guess, running a client, and the client's exiting makes X > shut down? No, it makes X reset. > >> the workaround is to start an application beforehand like >> >> xmag& >> /etc/X11/Xsession > > The fix is likely to pass -noreset. Which is not the default so Xsession should not assume that. > >> If I were to write/package another display manager I would likely >> need the Xsession script to perform correctly in absence of any >> other X client. > > Don't do that. Every time somebody writes/packages a DM, god kills a > kitten. Did not need to, somebody packaged nodm for me ;-) Perhaps I could look what *that* does. Thanks Michal -- 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/aanlktik1jnecrbctgtg+vkfebmqd2lrhsc4cuwdpk...@mail.gmail.com
Bug#527818: video-intel: i945 UXA X crash
On 23 February 2011 01:45, Cyril Brulebois wrote: > Hi Michal, > > Michal Suchanek (08/05/2009): >> Package: xserver-xorg-video-intel >> Version: 2:2.7.0-1 >> Severity: normal >> File: video-intel >> >> >> X crashed for no apparent reason. This was after a resume but resume >> normally works fine, even with this exact X server. > > what's the status in squeeze or sid? > > KiBi. > I was not using any Intel graphics recently. It's probably OK to close, X has changed a lot. Thanks Michal -- 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/aanlktims8wubavgy6ivcg5gxqqvyx6bsdzem_37mb...@mail.gmail.com
Bug#572880: is this still an issue?
Excerpts from Andres Cimmarusti's message of Tue Apr 13 17:16:09 +0200 2010: > Is this still a problem with the newer radeon driver in sid (also newer > kernel and mesa)? (make sure you upgrade libdrm-radeon1, > firmware-linux-nonfree and firmware-linux). If problem persists, could you > try getting newer 2.6.33 from experimental. NOTE: When enabling Kernel > modesetting, add radeon to /etc/modules and put options radeon modeset=1 in > /etc/modprobe.d/radeon-kms.conf (you might need to create the file). > > All these things didn't work for my card. If you use NetworkManager, there > was a change I made to it that solved all my suspend/hibernation problems. NM > has an option called network_sleep. It's disabled by default. I activated it > and my laptop was able to correctly suspend and hibernate. What it > effectively does, is to disconnect NM before suspending. > Hello, I am not using Network Manager, only wicd. However, I was not using that either in the past. To be sure I can add stopping wicd into the hibernate scripts. Due to the system being unreliable I don't use it much so I did not test with recent kernel from sid so far. All I can say it still locks up on every other suspend/resume cycle. Thanks Michal -- 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/1298360394-sup-7...@virtual.ruk.cuni.cz
Bug#539206: video-radeon: OSD flickering in mplayer/xv
2011/2/21 Cyril Brulebois : > Michal Suchanek (01/08/2009): >> Now I restarted X and observe flickering with overlay only. >> >> This seems somewhat random. > > Hi Michal, > > what's the status with sid/experimental's X stack? > > KiBi. > There is no support for overlay, only textured video, The issue is gone, though. Thanks Michal -- 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/AANLkTinjpi6Ke5HpOp7byZLL1bca-qkMOH=sJ5o-Aw=c...@mail.gmail.com
Bug#545569: video-radeon: improved with linux 2.6.36
On 21 February 2011 18:52, Cyril Brulebois wrote: > Hi, > > Michal Suchanek (03/02/2011): >> It is gone or mitigated to acceptable levels, probably with KMS >> updates in the current kernel. >> >> Can't easily reproduce the artifacts around mouse cursor either. > > should I close this report then? > Yes, recent enough versions of X server/radeon/Linux are in Sid. Thanks Michal -- 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/aanlktikuw2aks1anenta7gdgdgcahrk2dpmbremyq...@mail.gmail.com
Bug#605444: libgl1-mesa-dri-experimental: please install the llvmpipe driver
On 10 February 2011 16:45, Cyril Brulebois wrote: > tag 605444 patch > thanks > > Hi, > > thanks for the patch. > > Michal Suchanek (10/02/2011): >> It's quite simple. It affects >> - swrast when dri-experimental is installed > > looks sane enough at first glance. > >> - gallium based drivers - fallbacks are now llvm based (currently r300?) > > I'm not sure what the implications are here. > In general you get a different set of bugs. I am sure there are some bugs that happen with Debian builds and not my builds. The main difference would be llvm enabled, perhaps enabled debug. Thanks Michal -- 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/AANLkTikBSfr2FPoguQoa9ZbdX+4e=R57=z17dhsnj...@mail.gmail.com
Bug#605444: libgl1-mesa-dri-experimental: please install the llvmpipe driver
On 9 February 2011 12:55, Cyril Brulebois wrote:
>
> a patch against debian-unstable/7.10-3 would be appreciated.
>
> KiBi.
It's quite simple. It affects
- swrast when dri-experimental is installed
- gallium based drivers - fallbacks are now llvm based (currently r300?)
Note that mesa currently builds r600g but does not ship it, perhaps it
could be also added to dri-experimental.
I am not sure how useful the version in 7.10 is but it should improve over time.
Thanks
Michal
diff -urN mesa-7.10/debian/control mesa-7.10.mod/debian/control
--- mesa-7.10/debian/control 2011-02-09 20:00:17.0 +0100
+++ mesa-7.10.mod/debian/control 2011-02-09 19:56:29.0 +0100
@@ -11,7 +11,7 @@
libxdamage-dev, libxext-dev, autoconf, automake, x11proto-dri2-dev (>= 2.1),
linux-libc-dev (>= 2.6.31) [linux-any],
libx11-xcb-dev, libxcb-dri2-0-dev, libxcb-xfixes0-dev, python-libxml2,
- libtalloc-dev, libudev-dev [linux-any],
+ libtalloc-dev, libudev-dev [linux-any], llvm-dev,
Vcs-Git: git://git.debian.org/git/pkg-xorg/lib/mesa
Vcs-Browser: http://git.debian.org/?p=pkg-xorg/lib/mesa.git
Homepage: http://mesa3d.sourceforge.net/
diff -urN mesa-7.10/debian/libgl1-mesa-dri-experimental.install mesa-7.10.mod/debian/libgl1-mesa-dri-experimental.install
--- mesa-7.10/debian/libgl1-mesa-dri-experimental.install 2011-02-09 20:00:17.0 +0100
+++ mesa-7.10.mod/debian/libgl1-mesa-dri-experimental.install 2011-02-09 22:50:46.0 +0100
@@ -1 +1,2 @@
build/dri/lib/gallium/nouveau_dri.so usr/lib/dri
+build/dri/lib/gallium/swrastg_dri.so usr/lib/dri
diff -urN mesa-7.10/debian/patches/11-load-swrastg-before-swrast.diff mesa-7.10.mod/debian/patches/11-load-swrastg-before-swrast.diff
--- mesa-7.10/debian/patches/11-load-swrastg-before-swrast.diff 1970-01-01 01:00:00.0 +0100
+++ mesa-7.10.mod/debian/patches/11-load-swrastg-before-swrast.diff 2011-02-09 19:54:49.0 +0100
@@ -0,0 +1,15 @@
+--- mesa/src/glx/drisw_glx.c~ 2010-10-02 00:51:28.0 +0200
mesa/src/glx/drisw_glx.c 2010-10-26 22:40:48.0 +0200
+@@ -426,10 +426,10 @@
+void *driver = NULL;
+
+if (driver == NULL)
+- driver = driOpenDriver("swrast");
++ driver = driOpenDriver("swrastg");
+
+if (driver == NULL)
+- driver = driOpenDriver("swrastg");
++ driver = driOpenDriver("swrast");
+
+return driver;
+ }
diff -urN mesa-7.10/debian/patches/series mesa-7.10.mod/debian/patches/series
--- mesa-7.10/debian/patches/series 2011-02-09 20:00:17.0 +0100
+++ mesa-7.10.mod/debian/patches/series 2011-02-09 19:55:09.0 +0100
@@ -4,3 +4,4 @@
06_kfreebsd-ftbfs.diff
08-kfreebsd-gallium.diff
10-fix-talloc-linking.diff
+11-load-swrastg-before-swrast.diff
diff -urN mesa-7.10/debian/rules mesa-7.10.mod/debian/rules
--- mesa-7.10/debian/rules 2011-02-09 20:00:17.0 +0100
+++ mesa-7.10.mod/debian/rules 2011-02-09 19:58:06.0 +0100
@@ -91,6 +91,7 @@
confflags-dri = \
--with-driver=dri \
+ --enable-gallium-llvm \
--with-dri-drivers="$(DRI_DRIVERS)" \
--with-dri-driverdir=/usr/lib/dri \
--with-egl-platforms="$(EGL_DISPLAYS)" \
Bug#532170: xserver-xorg-core: Screen wakes from DPMS sleep
On 30 January 2011 06:27, Cyril Brulebois wrote: > Michal Suchanek (07/06/2009): >> Package: xserver-xorg-core >> Version: 2:1.6.1.901-2 >> Severity: normal > > Still happening with the X stack from squeeze/sid, or from > experimental? > >> However, after a minute or so the screen turns back on. >> >> I have no mice attached. > > Try and figure out if some events occur anyway. E.g. by running xev > and leaving your pointer in that window, noting the last lines, and > checking whether those changed when the screen comes back on. > > KiBi. > I am not sure how I resolved this but it's no longer an issue. iirc it was an issue with xscreensaver being configured not to turn the monitor off and it would actively turn it on. Thanks Michal -- 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/AANLkTik=6vchbrg6i22rnkabg43xnjmt2u0tbx+ky...@mail.gmail.com
Bug#568459: /usr/bin/setxkbmap: setting ctrl:nocaps with Caps Lock locks it
On 15 January 2011 03:29, Cyril Brulebois wrote: > Michal Suchanek (04/02/2010): >> When Caps Lock is on setting the ctrl:nocaps option locks the >> keyboard into typing uppercase. > > What else should happen? You asked it to become a Ctrl key. It did. > | ctrl:nocaps Make CapsLock an additional Ctrl > But when you ask it to become Caps Lock again it does not. It will not unlock the capslock anymore. Please close only bugs that have been fixed. Thanks Michal -- 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/aanlktins--x-8ab_8yv8y9oduypgbwd0hhg1pbdh9...@mail.gmail.com
Bug#474106: video-vesa: does not work on i815
Excerpts from Cyril Brulebois's message of Sat Jan 15 01:27:12 +0100 2011: > Brice Goglin (20/06/2008): > > Is it better with the latest X packages? > > What about now? > Sorry, when I tried to look for the board I could not find it so I cannot test this. Thanks Michal -- 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/1295089350-sup-6...@virtual.ruk.cuni.cz
Bug#608797: xserver-xorg-core: viewing large image in Firefox causes X server to abort
Excerpts from Julien Cristau's message of Wed Jan 05 17:19:57 +0100 2011: > On Wed, Jan 5, 2011 at 17:03:38 +0100, Michal Suchanek wrote: > > > I was totally expecting Firefox to try to allocate about a dozen of such > > pixmaps to store the uncompressed images. Where else would it put them? > > > Seriously, a 2GB pixmap? Nowhere at all. > Take http://veimages.gsfc.nasa.gov//7100/world.topo.bathy.200401.3x21600x21600.A2.jpg The image is 21600x21600 pixels. At 4 bytes per pixel (which is the preferred format for 24bpp images for alignment I guess) the size of the image is exactly 186624 - the size of the pixmap that failed to allocate. Rounding the dimension at 20k gives 1.5G underestimate of the size. Thanks Michal -- 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/1294254774-sup-...@virtual.ruk.cuni.cz
Bug#608797: xserver-xorg-core: viewing large image in Firefox causes X server to abort
Excerpts from Julien Cristau's message of Wed Jan 05 14:49:36 +0100 2011: > On Wed, Jan 5, 2011 at 09:33:53 +0100, Michal Suchanek wrote: > > > > Please attach a full backtrace from gdb. > > > > How do I? > > > > The X server just decides to quit, there is no report of crash neither > > in X log nor in kernel log. > > > You could put a breakpoint on FatalError. And find out what is > allocating such an insanely big pixmap. > Yes, it is slightly larger than expected, perhaps there is something like a few% padding for some alignment? I was totally expecting Firefox to try to allocate about a dozen of such pixmaps to store the uncompressed images. Where else would it put them? I will try to set up breakpoint in FatalError when I get to it. Thanks Michal -- 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/1294243157-sup-9...@virtual.ruk.cuni.cz
Bug#608797: xserver-xorg-core: viewing large image in Firefox causes X server to abort
Excerpts from Cyril Brulebois's message of Wed Jan 05 13:31:51 +0100 2011: > Michal Suchanek (05/01/2011): > > That's the best reportbug can do for resending a saved report I > > guess. > > It'd be nice to get this fixed. reportbug reportbug to the rescue? It's quite old #328531. > > > Try looking at some of the larger images at > > > > http://visibleearth.nasa.gov/view_detail.php?id=7100 > > I can't replicate it, even with 2+² images (and some time spent on > swap). Then it's probably something Firefox4 does that crashes the X server. > > > How do I? > > http://pkg-xorg.alioth.debian.org/xsf-docs/ > > > The X server just decides to quit, there is no report of crash > > neither in X log nor in kernel log. > > You're kidding right? You don't see a backtrace in your bugreport? > Those two backtraces have both X (mieqEnqueue+0x1ae) [0x4a6fde] on the top and obviously correspond to the two messages [ 1820.462][ 2104.059] [mi] EQ overflowing. The server is probably stuck in an infinite loop. which is a diagnostic unrelated to the Fatal server error: [ 8808.414] EXA: malloc failed for size 186624 bytes Thanks Michal -- 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/1294233702-sup-2...@virtual.ruk.cuni.cz
Bug#608797: xserver-xorg-core: viewing large image in Firefox causes X server to abort
Excerpts from Cyril Brulebois's message of Tue Jan 04 20:59:00 +0100 2011: > Hmm, broken forwarding? That's the best reportbug can do for resending a saved report I guess. > > > I searched for some large images to test a Firefox download bug. The > > images I found are so large they crash the X server. > > Care to share a link? Try looking at some of the larger images at http://visibleearth.nasa.gov/view_detail.php?id=7100 May be a bug in Firefox4 allocating X resources ad nauseam. > > > It is even possible to load the image, close the window and the X > > server still aborts *after* the window is closed. > > Please attach a full backtrace from gdb. How do I? The X server just decides to quit, there is no report of crash neither in X log nor in kernel log. Thanks Michal -- 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/1294216038-sup-7...@virtual.ruk.cuni.cz
Bug#601554: libgl1-mesa-dri: 7.9 now packaged
Package: libgl1-mesa-dri Severity: normal I guess this can be closed now. Thanks Michal -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (300, 'unstable'), (295, 'experimental'), (290, 'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'experimental-i386') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-r600fence-amd64 (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 libgl1-mesa-dri depends on: ii libc62.11.2-7Embedded GNU C Library: Shared lib ii libdrm-intel12.4.22-2Userspace interface to intel-speci ii libdrm-radeon1 2.4.22-2Userspace interface to radeon-spec ii libdrm2 2.4.22-2Userspace interface to kernel DRM ii libexpat12.0.1-4+lenny3 XML parsing C library - runtime li ii libgcc1 1:4.4.5-8 GCC support library ii libstdc++6 4.5.1-11The GNU Standard C++ Library v3 ii libtalloc2 2.0.1-1~bpo50+1 hierarchical pool based memory all libgl1-mesa-dri recommends no packages. Versions of packages libgl1-mesa-dri suggests: pn libglide3 (no description available) -- debconf-show failed -- 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/20101129233114.32307.30415.report...@heretic.burning-in.hell
Bug#605444: libgl1-mesa-dri-experimental: please install the llvmpipe driver
Package: libgl1-mesa-dri-experimental Version: 7.9+repack-1 Severity: normal The swrastg driver is not available in Mesa in Debian. When swrastg is compiled with llvm enabled it gives software speeds usable for demos on systems which lack 3D hardware or where the hardware is not supported. -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (300, 'unstable'), (295, 'experimental'), (290, 'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'experimental-i386') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-r600fence-amd64 (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 libgl1-mesa-dri-experimental depends on: ii libc62.11.2-7Embedded GNU C Library: Shared lib ii libdrm-nouveau1 2.4.22-2Userspace interface to nouveau-spe ii libdrm2 2.4.22-2Userspace interface to kernel DRM ii libexpat12.0.1-4+lenny3 XML parsing C library - runtime li ii libgcc1 1:4.4.5-8 GCC support library ii libstdc++6 4.5.1-11The GNU Standard C++ Library v3 ii libtalloc2 2.0.1-1~bpo50+1 hierarchical pool based memory all libgl1-mesa-dri-experimental recommends no packages. libgl1-mesa-dri-experimental suggests no packages. -- debconf-show failed -- 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/20101129232743.18483.45012.report...@heretic.burning-in.hell
Bug#601207: mesa: Mesa 7.9 requires libdrm-dev (>= 2.4.22) and libxcb1-dev (>= 1.6)
Package: mesa Followup-For: Bug #601207 While building the 32bit package I noticed that Mesa 7.9 dous not build with libdrm-dev 2.4.21 or libxcb1-dev 1.1-1.2 It works with the later versions available in debian which are 2.4.22 and 1.6 respectively. Thanks Michal -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-rc6-r600fence-smbinit-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20101030215546.7083.23432.report...@optiplex960.ruk.cuni.cz
Bug#601207: Info received (clarification)
I noticed one more missing bit: mesa now uses r300g by default. The package does not do install so it should pick it explicitly. Thanks Michal --- debian/libgl1-mesa-dri.install~ 2010-10-25 13:47:51.0 +0200 +++ debian/libgl1-mesa-dri.install 2010-10-27 10:28:39.0 +0200 @@ -1 +1,2 @@ build/dri/lib/*_dri.so usr/lib/dri/ +build/dri/lib/gallium/r300_dri.so usr/lib/dri/
Bug#601207: libgl1-mesa-dri: new upstream release
On 24 October 2010 15:36, Cyril Brulebois wrote: > Michal Suchanek (24/10/2010): >> > Bleh, don't specify versions we don't even ship… >> >> That's the point, I would not have to if there was a lib in Debian. > > Wrong. Version tracking is for tracking versions we ship, not your > particular pet build. Don't do that. > That's not my pet build, that's the package I have installed. And the issue applies to Debian so that's why I report it here. Thanks Michal -- 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/aanlktikc+tggehiz2jn6n82o1i-c4nq-pfr80j2uq...@mail.gmail.com
Bug#601207: libgl1-mesa-dri: new upstream release
On 24 October 2010 14:21, Cyril Brulebois wrote: > notfound 601207 7.9.0+git20100903.a5fd0396-0ubuntu0sarvatt > thanks > > Michal Suchanek (24/10/2010): >> Package: libgl1-mesa-dri >> Version: 7.9.0+git20100903.a5fd0396-0ubuntu0sarvatt > > Bleh, don't specify versions we don't even ship… That's the point, I would not have to if there was a lib in Debian. > >> Severity: wishlist >> Upstream has released mesa 7.9 > > Wishlist: send patches. I don't expect any are needed. I built mesa 7.9 without issues. I just install these packages for 32bit support which is hard to get on 64bit otherwise. Thanks Michal -- 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/aanlktimmqhdje_zkubn466f6jjoonbcqt+ukotovq...@mail.gmail.com
Bug#601207: libgl1-mesa-dri: new upstream release
Package: libgl1-mesa-dri Version: 7.9.0+git20100903.a5fd0396-0ubuntu0sarvatt Severity: wishlist Upstream has released mesa 7.9 -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (300, 'unstable'), (295, 'experimental'), (290, 'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'experimental-i386') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-rc4-r600fence-netpollirq-smbinit-amd64 (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 libgl1-mesa-dri depends on: ii libc6 2.11.2-5 Embedded GNU C Library: Shared lib ii libdrm-intel1 2.4.21-1~squeeze3 Userspace interface to intel-speci ii libdrm-nouveau12.4.21-1~squeeze3 Userspace interface to nouveau-spe ii libdrm-radeon1 2.4.21-1~squeeze3 Userspace interface to radeon-spec ii libdrm22.4.21-1~squeeze3 Userspace interface to kernel DRM ii libexpat1 2.0.1-4+lenny3XML parsing C library - runtime li ii libffi53.0.9-2 Foreign Function Interface library ii libgcc11:4.4.4-8 GCC support library ii libstdc++6 4.4.4-8 The GNU Standard C++ Library v3 ii libtalloc2 2.0.1-1~bpo50+1 hierarchical pool based memory all libgl1-mesa-dri recommends no packages. Versions of packages libgl1-mesa-dri suggests: pn libglide3 (no description available) -- debconf-show failed -- 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/20101024121352.14570.99722.report...@heretic.burning-in-hell
Bug#590462: video-radeon: gdb back trace
Package: xserver-xorg-video-radeon
Followup-For: Bug #590462
Sending a backtrace.
It is different from the previous one but seems to match the X log.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f24ee813700 (LWP 15761)]
0x7f24ead46424 in DRI2CopyRegion (pDraw=0x348e5e0, pRegion=0x7fff0ef29ef0,
dest=7, src=0)
at ../../../../hw/xfree86/dri2/dri2.c:328
328 ../../../../hw/xfree86/dri2/dri2.c: No such file or directory.
in ../../../../hw/xfree86/dri2/dri2.c
(gdb) bt
#0 0x7f24ead46424 in DRI2CopyRegion (pDraw=0x348e5e0,
pRegion=0x7fff0ef29ef0, dest=7, src=0)
at ../../../../hw/xfree86/dri2/dri2.c:328
#1 0x7f24ead4682b in do_get_buffers (pDraw=0x348e5e0, width=, height=,
attachments=0x2, count=, out_count=, has_format=1)
at ../../../../hw/xfree86/dri2/dri2.c:288
#2 0x7f24ead468a0 in DRI2GetBuffersWithFormat (pDraw=0x0, width=0x0,
height=0x0, attachments=0x3476850, count=16,
out_count=0x2da2970) at ../../../../hw/xfree86/dri2/dri2.c:307
#3 0x7f24ead4707e in ProcDRI2Dispatch (client=0x29a6600) at
../../../../hw/xfree86/dri2/dri2ext.c:287
#4 0x00448db4 in Dispatch () at ../../dix/dispatch.c:439
#5 0x00425b8a in main (argc=6, argv=0x7d8448, envp=) at ../../dix/main.c:285
(gdb) bt full
#0 0x7f24ead46424 in DRI2CopyRegion (pDraw=0x348e5e0,
pRegion=0x7fff0ef29ef0, dest=7, src=0)
at ../../../../hw/xfree86/dri2/dri2.c:328
pPriv =
pDestBuffer = (DRI2BufferPtr) 0x0
pSrcBuffer = (DRI2BufferPtr) 0x3476850
#1 0x7f24ead4682b in do_get_buffers (pDraw=0x348e5e0, width=, height=,
attachments=0x2, count=, out_count=, has_format=1)
at ../../../../hw/xfree86/dri2/dri2.c:288
region = {extents = {x1 = 0, y1 = 0, x2 = 375, y2 = 30903}, data = 0x0}
pPriv = (DRI2DrawablePtr) 0x2e5a400
buffers = (DRI2BufferPtr *) 0x2da2970
need_real_front = -1
need_fake_front = 1
have_fake_front = 1
front_format = 32
dimensions_match = 0
i = 2
#2 0x7f24ead468a0 in DRI2GetBuffersWithFormat (pDraw=0x0, width=0x0,
height=0x0, attachments=0x3476850, count=16,
out_count=0x2da2970) at ../../../../hw/xfree86/dri2/dri2.c:307
No locals.
#3 0x7f24ead4707e in ProcDRI2Dispatch (client=0x29a6600) at
../../../../hw/xfree86/dri2/dri2ext.c:287
stuff =
#4 0x00448db4 in Dispatch () at ../../dix/dispatch.c:439
result =
client = (ClientPtr) 0x29a6600
nready = 0
start_tick = 67000
#5 0x00425b8a in main (argc=6, argv=0x7d8448, envp=) at ../../dix/main.c:285
i = 1
alwaysCheckForInput = {0, 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/20100809103913.14332.17745.report...@ipx7a-ion.ruk.cuni.cz
Bug#590462: xserver-xorg-video-radeon: two more gdb backtraces
Excerpts from Michel Dänzer's message of Fri Aug 06 13:55:01 +0200 2010: > On Fre, 2010-08-06 at 13:47 +0200, Michal Suchanek wrote: > > > > The other crash is also reproducible: > > Are these really still crashes, not just SIGPIPEs? Those are normal when > a client terminates uncleanly. > > (I wouldn't have had to ask this if you had still included the > information about the signals...) > I'm quite sure they aren't SIGPIPES. I would get a SIGPIPE much earlier as some of the tests crash and had to disable reporting of those to get anything from gdb. Here is what I have in X log: Backtrace: 0: Xorg (xorg_backtrace+0x28) [0x4ac9b8] 1: Xorg (0x40+0x61939) [0x461939] 2: /lib/libpthread.so.0 (0x7f29c5e6d000+0xef60) [0x7f29c5e7bf60] 3: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2CopyRegion+0x64) [0x7f29c2dcc424] 4: /usr/lib/xorg/modules/extensions/libdri2.so (0x7f29c2dcb000+0x182b) [0x7f29c2dcc82b] 5: /usr/lib/xorg/modules/extensions/libdri2.so (DRI2GetBuffersWithFormat+0x10) [0x7f29c2dcc8a0] 6: /usr/lib/xorg/modules/extensions/libdri2.so (0x7f29c2dcb000+0x207e) [0x7f29c2dcd07e] 7: Xorg (0x40+0x48db4) [0x448db4] 8: Xorg (0x40+0x25b8a) [0x425b8a] 9: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f29c496dc4d] 10: Xorg (0x40+0x25739) [0x425739] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Thanks Michal -- 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/1281099378-sup-3...@virtual.ruk.cuni.cz
Bug#590462: xserver-xorg-video-radeon: two more gdb backtraces
Package: xserver-xorg-video-radeon
Version: 1:6.13.2~git2010080611
Followup-For: Bug #590462
The other crash is also reproducible:
(gdb) bt full
#0 send_buffers_reply (client=0x17dcf30, pDrawable=0x1762cd0,
buffers=0x1805770, count=3, width=375, height=46396)
at ../../../../hw/xfree86/dri2/dri2ext.c:214
rep = {type = 176 '°', pad1 = 243 'ó', sequenceNumber = 29041, length =
32767, width = 1903293376, height = 32767,
count = 1903293352, pad2 = 32767, pad3 = 21503568, pad4 = 0}
skip = 0
i =
#1 0x7f5d3cd3f09c in ProcDRI2Dispatch (client=0x17dcf30) at
../../../../hw/xfree86/dri2/dri2ext.c:290
stuff =
#2 0x00448db4 in Dispatch () at ../../dix/dispatch.c:439
result =
client = (ClientPtr) 0x17dcf30
nready = 0
start_tick = 95180
#3 0x00425b8a in main (argc=6, argv=0x7d8448, envp=) at ../../dix/main.c:285
i = 1
alwaysCheckForInput = {0, 1}
(gdb) bt full
#0 send_buffers_reply (client=0x2534af0, pDrawable=0x2d07b10,
buffers=0x2bb7780, count=2, width=375, height=32780)
at ../../../../hw/xfree86/dri2/dri2ext.c:214
rep = {type = 64 '@', pad1 = 255 'ÿ', sequenceNumber = 27408, length =
32767, width = 1796276048, height = 32767,
count = 1796276024, pad2 = 32767, pad3 = 35454544, pad4 = 0}
skip = 0
i =
#1 0x7f70a476c09c in ProcDRI2Dispatch (client=0x2534af0) at
../../../../hw/xfree86/dri2/dri2ext.c:290
stuff =
#2 0x00448db4 in Dispatch () at ../../dix/dispatch.c:439
result =
client = (ClientPtr) 0x2534af0
nready = 0
start_tick = 49720
#3 0x00425b8a in main (argc=6, argv=0x7d8448, envp=) at ../../dix/main.c:285
i = 1
alwaysCheckForInput = {0, 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/20100806114754.12419.47382.report...@ipx7a-ion.ruk.cuni.cz
Bug#590462: xserver-xorg-video-radeon: no longer crashes in ati driver
Package: xserver-xorg-video-radeon
Version: 1:6.13.2~git2010080611
Followup-For: Bug #590462
I tried applying the patch on ati driver git and the X server no longer
crashes in the radeon driver.
Thanks
Michal
#0 send_buffers_reply (client=0x1b17aa0, pDrawable=0x1a19d90,
buffers=0x1b8b440, count=2, width=51862, height=64610)
at ../../../../hw/xfree86/dri2/dri2ext.c:214
rep = {type = 80 'P', pad1 = 100 'd', sequenceNumber = 30854, length =
32767, width = 2022073440, height = 32767,
count = 2022073416, pad2 = 32767, pad3 = 23858768, pad4 = 0}
skip = 0
i =
#1 0x7f4b4a56409c in ProcDRI2Dispatch (client=0x1b17aa0) at
../../../../hw/xfree86/dri2/dri2ext.c:290
stuff =
#2 0x00448db4 in Dispatch () at ../../dix/dispatch.c:439
result =
client = (ClientPtr) 0x1b17aa0
nready = 0
start_tick = 3780
#3 0x00425b8a in main (argc=6, argv=0x7d8448, envp=) at ../../dix/main.c:285
i = 1
alwaysCheckForInput = {0, 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/20100806113055.6372.96915.report...@ipx7a-ion.ruk.cuni.cz
