Bug#1052681: no uploader
Timo Aaltonen schreef op di 26-09-2023 om 09:01 [+0300]: > Ben Tris kirjoitti 26.9.2023 klo 8.50: > > Source: xinit > > X-Debbugs-Cc: benatt...@gezapig.nl > > Severity: important > > > > Dear Maintainer, > > > > There is no uploader at this moment, it is required in this case I > > think. > > > > Debian Policy Manual, Release 4.6.2.0 > > 3.3 The maintainer of a package > > > > If the maintainer of the package is a team of people with a shared > > email > > address, the Uploaders control field must be > > present and must contain at least one human with their personal > > email > > address. > > > > Stop already, these bugreports are of no use. > Thank for the notion. I would like to know why this bug report is of no use.
Bug#1052681: no uploader
Source: xinit X-Debbugs-Cc: benatt...@gezapig.nl Severity: important Dear Maintainer, There is no uploader at this moment, it is required in this case I think. Debian Policy Manual, Release 4.6.2.0 3.3 The maintainer of a package If the maintainer of the package is a team of people with a shared email address, the Uploaders control field must be present and must contain at least one human with their personal email address.
Bug#1052680: no uploader
Source: xfonts-utils X-Debbugs-Cc: benatt...@gezapig.nl Severity: important Dear Maintainer, There is no uploader at this moment, it is required in this case I think. Debian Policy Manual, Release 4.6.2.0 3.3 The maintainer of a package If the maintainer of the package is a team of people with a shared email address, the Uploaders control field must be present and must contain at least one human with their personal email address.
Bug#1052679: no uploader
Source: xcursor-themes X-Debbugs-Cc: benatt...@gezapig.nl Version: 1.0.5-1 Severity: important Dear Maintainer, There is no uploader at this moment, it is required in this case I think. Debian Policy Manual, Release 4.6.2.0 3.3 The maintainer of a package If the maintainer of the package is a team of people with a shared email address, the Uploaders control field must be present and must contain at least one human with their personal email address.
Bug#1052662: no uploader
Source: twm Version: 1:1.0.10-1 Severity: important X-Debbugs-Cc: benatt...@gezapig.nl Dear Maintainer, There is no uploader at this moment, it is required in this case I think. Debian Policy Manual, Release 4.6.2.0 3.3 The maintainer of a package If the maintainer of the package is a team of people with a shared email address, the Uploaders control field must be present and must contain at least one human with their personal email address. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1052600: libxss: No uploader
Source: libxss Version: 1:1.2.3-1 Severity: important X-Debbugs-Cc: benatt...@gezapig.nl Dear Maintainer, There is no uploader at this moment, it is required in this case I think. Debian Policy Manual, Release 4.6.2.0 3.3 The maintainer of a package If the maintainer of the package is a team of people with a shared email address, the Uploaders control field must be present and must contain at least one human with their personal email address. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1052599: No uploader
Source: libxshmfence Version: 1.3-1 Severity: important X-Debbugs-Cc: benatt...@gezapig.nl Dear Maintainer, There is no uploader at this moment, it is required in this case I think. Debian Policy Manual, Release 4.6.2.0 3.3 The maintainer of a package If the maintainer of the package is a team of people with a shared email address, the Uploaders control field must be present and must contain at least one human with their personal email address. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Re: Bug#1036019: debian-installer: Broken X display with QEMU under UEFI with cirrus and std graphics
On Sun, 2023-05-14 at 19:40 +0200, Ben Hutchings wrote: [...] > This works for me with all the QEMU graphics devices. But I haven't > tested on real hardware. Now tested successfully on 2 custom desktops: - Asus P8Z68-V LX motherboard, Intel Core i5 2500 CPU, integrated GPU - ASRock B450 PRO4, AMD Ryzen 5 3600 CPU, Radeon RX580 GPU and 2 laptops: - Lenovo ThinkPad T420, Intel Core i5 2nd gen CPU, integrated GPU - Lenovo ThinkPad T460, Intel Core i5 6th gen CPU, integrated GPU Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Re: Bug#1036019: debian-installer: Broken X display with QEMU under UEFI with cirrus and std graphics
Control: tag -1 patch On Sun, 2023-05-14 at 00:21 +0200, Ben Hutchings wrote: [...] > So I suppose there's a regression in either efifb or fbdev_drv. I'm not spotting any functional changes in fbdev or the submodules it depends on between bullseye and bookworm. So this implicates either efifb or, as you mentioned, GRUB. > > Via QEMU, under BIOS and UEFI, results are: > > > > +-+-+-+-+ > > | Graphics | Bullseye 11.7 | Bookworm RC 2 | Daily builds | > > +-+++++++ > > | | BIOS | UEFI | BIOS | UEFI | BIOS | UEFI | > > +-+++++++ > > | | OK | OK | OK | KO-G | OK | KO-G | > > | -vga std| OK | OK | OK | KO-G | OK | KO-G | > > | -vga cirrus | OK | OK | OK | KO-S | OK | KO-S | > > | -vga qxl| OK | OK | OK | OK | OK | OK | > > | -vga virtio | OK | OK | OK | OK | OK | OK | > > | -vga vmware | OK | OK | OK | OK | OK | OK | > > +-+++++++ > > I started testing with QEMU and OVMF from unstable, and I'm instead > seeing Xorg failing to start in the same cases you see glitches. The > relevant error message seems to be this one: > http://codesearch.debian.net/show?file=xorg-server_2%3A21.1.7-3%2Fhw%2Fxfree86%2Ffbdevhw%2Ffbdevhw.c=504 [...] I tested with QEMU from bullseye and OVMF from unstable, and again I saw Xorg failing to start, rather than glitches. Weird. I also patched the kernel to report the internal screen_info structure and the fb_var_screeninfo structure passed in and out of FBIOPUT_VSCREENINFO. The key difference is: - With -vga qxl, screen_info says 32 bpp, X wants 32 bpp, the kernel agrees with that. - With -vga std or -vga cirrus screen_info says 24 bpp, X wants 32 bpp, and the kernel says 24 bpp. I think the problem is this GRUB has native drivers for Bochs and Cirrus that reprogram the framebuffer bit depth, and the kernel is then confused about what the bit depth is supposed to be. With QXL, GRUB doesn't have a native driver so it doesn't reconfigure the framebuffer. Unfortunately, with Secure Boot we have to use a monolithic GRUB build so I can't easily exclude video_bochs and video_cirrus to see if that improves matters. But what does works for me is: --- a/build/boot/x86/grub/grub-efi.cfg +++ b/build/boot/x86/grub/grub-efi.cfg @@ -5,7 +5,7 @@ else fi if loadfont $font ; then - set gfxmode=800x600 + set gfxmode=800x600x32 set gfxpayload=keep insmod efi_gop insmod efi_uga --- END --- A full patch is attached. This works for me with all the QEMU graphics devices. But I haven't tested on real hardware. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer From 49a5e562850e3ae4f64ed2d61bd582d8adedc393 Mon Sep 17 00:00:00 2001 From: Ben Hutchings Date: Sun, 14 May 2023 19:17:45 +0200 Subject: [PATCH] Always use 32 bpp for GRUB EFI graphical menu (Closes: #1036019) --- build/boot/x86/grub/grub-efi.cfg | 2 +- debian/changelog | 4 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/build/boot/x86/grub/grub-efi.cfg b/build/boot/x86/grub/grub-efi.cfg index 0a9a67d48..14708c7bc 100644 --- a/build/boot/x86/grub/grub-efi.cfg +++ b/build/boot/x86/grub/grub-efi.cfg @@ -5,7 +5,7 @@ else fi if loadfont $font ; then - set gfxmode=800x600 + set gfxmode=800x600x32 set gfxpayload=keep insmod efi_gop insmod efi_uga diff --git a/debian/changelog b/debian/changelog index 4624187fe..6be6864b5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,12 @@ debian-installer (20230428) UNRELEASED; urgency=medium + [ Cyril Brulebois ] * Bump Linux kernel ABI to 6.1.0-9. * Switch source format from 1.0 to 3.0 (native). + [ Ben Hutchings ] + * Always use 32 bpp for GRUB EFI graphical menu (Closes: #1036019) + -- Cyril Brulebois Thu, 27 Apr 2023 22:52:15 +0200 debian-installer (20230427) unstable; urgency=medium signature.asc Description: This is a digitally signed message part
Re: Bug#1036019: debian-installer: Broken X display with QEMU under UEFI with cirrus and std graphics
note, keeping the bundling in src:debian-installer for the > next few weeks makes us autonomous: we can enable and disable those > extra modules without requiring a new linux upload… so it's nasty but I > actually thought about the few advantages we were getting out of this! > > We should also be OK legal-wise, given we already have linux in > Built-Using via its udebs, so copying things around from linux-image > wouldn't change anything there, would it? > > Of course in the long run, if having those modules is desired, it will > be better to have them merged in linux and to drop the nasty code, e.g. > in a point release. [...] Definitely. I will spend some time investigating this, but I doubt I'll come up with a better fix in time. Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code. signature.asc Description: This is a digitally signed message part
Bug#1020391: mesa: Updates to 22.2 RCs cause blank screen on some VirtIO graphics
Hello Fabio, On 1/3/23 06:35, Fabio Pedretti wrote: > You don't provide many details, but at a quick search your issue may > be this one: > https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291 > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 I don't see how that issue is related to mine. It supposedly only occurs when XWayland is being used, while mine is happening on pure X11. Thanks, -- Ben Westover OpenPGP_signature Description: PGP signature
Bug#1020391: mesa: Updates to 22.2 RCs cause blank screen on some VirtIO graphics
Source: mesa X-Debbugs-Cc: m...@benthetechguy.net Version: 22.2.0~rc1-1 Severity: important Dear Maintainer, After updating to mesa 22.2.0~rc1-1 on my UTM virtual machine on macOS (which uses VirtIO graphics), LightDM and anything else using Mesa is just completely black except for a cursor. This is still present in the latest version. The default graphics option of UTM is virtio-ramfb-gl, which is GPU accelerated; I tested virtio-ramfb, and it doesn't have this issue, though it's not ideal as I can't resize the window and it's not GPU accelerated. I tested all of the *-gl accelerated graphics options, and they all have this issue. I also tested a normal virt-manager VM on Linux, and it doesn't have this issue. -- Ben Westover P.S. Also reported in #1017499, but turned out to be a separate issue. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 5.19.0-1-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled OpenPGP_signature Description: PGP signature
Bug#1017499: Upstream bug report
tags 1017499 + upstream -- I was about to report the bug upstream, but it looks like Leandro beat me to it. https://gitlab.freedesktop.org/mesa/mesa/-/issues/7117 -- Ben Westover signature.asc Description: PGP signature
Bug#1017499: Mentioned issue is not related
Correction: Issue #7071 is *not* related to this issue; it's a similar issue, but specific to Vivante hardware and the etnaviv driver. -- Ben Westover signature.asc Description: PGP signature
Bug#1017499: Related upstream issue
Upstream issue #7071 [1] seems to be related, with similar artifacts and the issue being first reported in Mobian, which shares the same mesa package as Debian. If this is true, the offending commit would be 53445284a427f79e94607dc4ca2f8bd8ac293356. -- Ben Westover [1] https://gitlab.freedesktop.org/mesa/mesa/-/issues/7071 OpenPGP_signature Description: OpenPGP digital signature
Bug#1017499: mesa: Updates to 22.2 RCs cause artifacts on nouveau and blank screen on VirtIO
On 8/16/22 11:57 PM, Ben Westover wrote: > I also updated my Debian virtual machine in UTM on macOS, which uses > VirtIO graphics, and LightDM is just completely black there except for > a cursor. The default graphics option of UTM is virtio-ramfb-gl, which is GPU accelerated. I just tested virtio-ramfb, and it doesn't have this issue, though it's not ideal as I can't resize the window and it's not GPU accelerated. I tested all of the *-gl accelerated graphics options, and they all have this issue. I also tested a normal virt-manager VM on Linux, and it doesn't have this issue. -- Ben Westover OpenPGP_signature Description: OpenPGP digital signature
Bug#1017499: mesa: Updates to 22.2 RCs cause artifacts on nouveau and blank screen on VirtIO
Source: mesa Version: 22.2.0~rc1-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, After updating to mesa 22.2.0~rc1-1 on my 2008 Dell Precision laptop with a Quadro FX 1700M GPU, I began experiencing artifacts [1] as soon as lightdm started, and they still remained after launching Xfce [2]. I also updated my Debian virtual machine in UTM on macOS, which uses VirtIO graphics, and LightDM is just completely black there except for a cursor. After updating to 22.2.0~rc2-1, the nouveau laptop's artifacts were limited to only foreground objects, such as the login box of lightdm [3] or the menu and panel of Xfce [4]. The virtual machine stayed the same. - -- Ben Westover [1] https://i.ibb.co/mcw7phd/IMG-20220816-231123.jpg [2] https://i.ibb.co/QpRZMwV/IMG-20220816-231401.jpg [3] https://i.ibb.co/y5F1dsJ/IMG-20220816-233627.jpg [4] https://i.ibb.co/7z3X5sy/IMG-20220816-233611.jpg - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOGnacqRhdU6eNmtFwxHF9U6JtpgFAmL8ZzkACgkQwxHF9U6J tphg4A/9Fv5e8+V6K2BAXqeoJQPI+JPRWEqe4dW7XnEkvZAWPDw9t6SG9bJYZMwK axwxL+Iobj90WyxGtsUbAjXjFbNJJ0gPorgA/0d83KpPzLwJEDgk1yZKs/vraO64 secD1BBQ04X07NEhZoTzNKbqrUCJUmgZk7R21OfAzTBXdYmMk7CAa4WVoVSgYNcu VP0+GsvmQhETgidDFa4QfrzT4bKEzWo/Vcp3jXWM6u+ovrVtYKvbovE9/M3kRMyJ 0PEZfMYxkq54ggIdT4dEbh7wYN1eGvfubodQ6pDyk+lxaZ00dVZdBcmGhH3RQGLz AClLDr7ZQ+dXz6/HZgd1KXx1PEteI7Cx58yUbJkDcGXS9ddbwfXDLdJYZ9rFYWet CMFuBILn15FxzpjObNjQANzc8xzFAUwMGjq5g0HcAByTslvDipkZtz1Gc5lRyygs ixH8WKWh6dJv54n8KMppjLsr9miJq5Azf82x2AlD5A2Z4xN1zAkagjeijZVZGJwn t8gy2TwK0GsJET2M/hlLRD/1qbPpB4BrUJJIqSTMuNOPUQyRvu0MlcQv8rVYmXCi E9I6o8nG/4k/MeSh/YFXdk49iet1w1fbwQ2GaIvA8FdS/kd7AEQD5p1rW4hcIbBQ ogaKc+2IP2ZHjsr1i5oH7eaE3GgYLRR8Ym5oKKh8Z4fh5oiMiCM= =DQZd -END PGP SIGNATURE-
Bug#964096: mesa: SIGSEGV in iris_dri.so using mpv/ffplay/vlc, Intel HD Graphics 530
Package: libgl1-mesa-dri
Version: 20.1.2-1
Severity: normal
mesa: SIGSEGV in iris_dri.so using mpv/ffplay/vlc, Intel HD Graphics 530
Dear Maintainer,
This is different from #959400.
I have a particular file [1] ripped from youtube, and trying to open it with
*any* of mpv, ffplay, or vlc results in the same few first seconds on audio,
and then a crash (SIGSEGV).
This bugs seems to happen with *every* Video I have available, no matter
whether it's webm or flv or mkv or mp4. Note that firefox has no trouble.
gdb points to stream_state in iris_blorp.c:62, which effectively dereferences
res=0x0. See backtrace below.
This is a different backtrace than #959400.
Before you ask: Yes, I can trigger #959400 by running glxgears. Again, this
seems to be a different bug from that.
Here's the relevant part of iris_blorp.c, function stream_state:
struct pipe_resource *res = NULL;
// …
u_upload_alloc(…, …, …, …, …, , …);
struct iris_bo *bo = iris_resource_bo(res);
The function iris_resource_bo() basically just reads from the given pointer.
My best guess: The function stream_state forgets to check from errors during
u_upload_alloc(). No idea why that would fail, but it does.
The function u_upload_alloc (u_upload_mgr.c:238) has two paths to return
nullptr, so this should be checked by stream_state.
Cheers,
Ben
EXAMPLE FILE
https://www.youtube.com/watch?v=D8EeWgXRYFc
Again, this seems to happen with basically every file, but just in case:
$ sha256sum 'Max Cooper - Supine Official video by Tom
Geraedts-D8EeWgXRYFc.mkv'
dbb4257a69ade0f888f10ebe86b5512e291c62f5b5dce33c989bade02496897b
GDB BACKTRACE
#0 stream_state (batch=0x5580c0f0, uploader=, size=12,
alignment=alignment@entry=64, out_offset=out_offset@entry=0x7fffce9c,
out_bo=out_bo@entry=0x0)
at ../src/gallium/drivers/iris/iris_blorp.c:62
#1 0x7fffe7d70251 in blorp_alloc_dynamic_state
(blorp_batch=0x7fffd7b0, blorp_batch=0x7fffd7b0, offset=0x7fffce9c,
alignment=64, size=)
at ../src/gallium/drivers/iris/iris_blorp.c:138
#2 blorp_emit_blend_state (params=0x7fffd050, batch=0x7fffd7b0) at
../src/intel/blorp/blorp_genX_exec.h:1080
#3 blorp_emit_pipeline (params=0x7fffd050, batch=0x7fffd7b0) at
../src/intel/blorp/blorp_genX_exec.h:1271
#4 blorp_exec (params=0x7fffd050, batch=0x7fffd7b0) at
../src/intel/blorp/blorp_genX_exec.h:2015
#5 iris_blorp_exec (blorp_batch=0x7fffd7b0, params=0x7fffd050) at
../src/gallium/drivers/iris/iris_blorp.c:310
#6 0x7fffe7f3b5a4 in blorp_clear (batch=batch@entry=0x7fffd7b0,
surf=surf@entry=0x7fffd7e0, format=ISL_FORMAT_B8G8R8X8_UNORM, swizzle=...,
swizzle@entry=..., level=level@entry=0, start_layer=0, num_layers=1, x0=0,
y0=0, x1=1280, y1=560, clear_color=..., color_write_disable=0x7fffd7d0)
at ../src/intel/blorp/blorp_clear.c:548
#7 0x7fffe7d4bb4d in clear_color
(ice=ice@entry=0x5580bc70, p_res=, level=, box=box@entry=0x7fffd8d0,
render_condition_enabled=render_condition_enabled@entry=true, format=, swizzle=..., color=...) at ../src/gallium/drivers/iris/iris_clear.c:389
#8 0x7fffe7d4c8bb in iris_clear (ctx=0x5580bc70, buffers=4,
scissor_state=, p_color=0x557d8e24, depth=,
stencil=)
at ../src/gallium/drivers/iris/iris_clear.c:680
#9 0x7fffe72dc2bb in st_Clear (ctx=0x557c6b20, mask=2) at
../src/mesa/state_tracker/st_cb_clear.c:540
#10 0x75cf601a in () at /lib/x86_64-linux-gnu/libSDL2-2.0.so.0
#11 0x75ce9911 in () at /lib/x86_64-linux-gnu/libSDL2-2.0.so.0
#12 0x75cef0bd in () at /lib/x86_64-linux-gnu/libSDL2-2.0.so.0
#13 0x5556659c in ()
#14 0x5556c9cf in ()
#15 0xc7f0 in main ()
(gdb) bt full
#0 stream_state (batch=0x7fffc81b8fe0, uploader=, size=12,
alignment=alignment@entry=64, out_offset=out_offset@entry=0x7fffcf7fbc5c,
out_bo=out_bo@entry=0x0)
at ../src/gallium/drivers/iris/iris_blorp.c:62
res = 0x0
ptr = 0x0
bo =
#1 0x7fffcdc40251 in blorp_alloc_dynamic_state
(blorp_batch=0x7fffcf7fc570, blorp_batch=0x7fffcf7fc570, offset=0x7fffcf7fbc5c,
alignment=64, size=)
at ../src/gallium/drivers/iris/iris_blorp.c:138
ice =
batch =
blend =
{YDitherOffset = 0, XDitherOffset = 0, ColorDitherEnable = false,
AlphaTestFunction = COMPAREFUNCTION_ALWAYS, AlphaTestEnable = false,
AlphaToCoverageDitherEnable = false, AlphaToOneEnable = false,
IndependentAlphaBlendEnable = false, AlphaToCoverageEnable = false}
state =
offset = 4294967295
size =
pos =
blend_state_offset = 0
urb_deref_block_size = GEN_URB_DEREF_BLOCK_SIZE_32
ice = 0x7fffc81b8b60
batch = 0x7fffc81b8fe0
scale =
skip_bits =
-- Package-specific info:
glxinfo:
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions
Bug#868333: Xorg: rotation of left monitor in dual screen (:0.1) traps mouse in right screen
Package: Xorg Version: 1:7.7+19 Severity: normal Firstly this is a true multi screen setup with :0.0 and :0.1 not just a multi monitor setup. When you rotate the left monitor (I use xrandr) you can no longer move the mouse over the left side of the right screen to the left monitor although you can easily move the mouse to the right. My suspicion is that the checks for moving the mouse left note that there is a gap between monitors due to the rotated screen now being narrower causing the failure. Note: ratpoison's banish commands are useful for troubleshooting this. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages Xorg depends on: ii libgl1-mesa-dri 13.0.6-1+b2 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libglu1-mesa 9.0.0-2.1 ii x11-apps 7.7+6+b1 ii x11-session-utils7.7+2+b1 ii x11-utils7.7+3+b1 ii x11-xkb-utils7.7+3+b1 ii x11-xserver-utils7.7+7+b1 ii xauth1:1.0.9-1+b2 ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-base 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 ii xfonts-utils 1:7.7+4 ii xinit1.3.4-3+b1 ii xkb-data 2.19-1 ii xorg-docs-core 1:1.7.1-1 ii xserver-xorg 1:7.7+19 ii xterm [x-terminal-emulator] 327-2 Xorg recommends no packages. Versions of packages Xorg suggests: ii x11-xfs-utils 7.7+2+b1 pn xorg-docs -- no debconf information
Bug#859461: xterm: seperate package for resize would be nice
Package: xterm Version: 312-2 Severity: wishlist Dear Maintainer, For those of us using a machine without a video card a serial console is quite useful, and in many cases that serial console is controled by xterm or similar terminal emulator (in my case it is almost always xterm and screen), due to the continued decrease in availability of hardware serial terminals (not much of a loss there). now one of the cool new features of using a modern terminal emulator with rs232 (in adition to utf8, 256 color, sixel graphics (sorry), etc.) is resizable terminal windows. This is not very dificult as long as you execute xterm's resize on the remote machine after each resize. (see: http://unix.stackexchange.com/questions/16578/resizable-serial-console-window) The one chalenge is in the case of machines that are not running any graphics software and do not need or want xterm installed, but do want xterm's resize. Which brings me to my request, split resize into a seprate package and depend on it to preserve existing functionality while allowing headless machines to install just resize.
Bug#848818: xterm: ctlseqs.txt is not rebuilt from ctlseq.ms
On Mon, Dec 19, 2016 at 3:48 PM, Thomas Dickey <dic...@his.com> wrote: > On Mon, Dec 19, 2016 at 02:39:27PM -0800, Ben Longbons wrote: >> The ctlseqs.txt file is not built from ctlseqs.ms if it is modified >> (which it should be, since it is wrong in a few places). > > I don't recall any bug reports on the topic. I was working on that when I hit this. Besides the one you mentioned, the xterm-specific `DECSED 3` is missing, for example. I'm sure there was something with one of the string controls too ... > ctlseqs.txt is part of the upstream sources, has been since June 2006. Source means "preferred format for modification", not "in a tarball somewhere". By your definititon, all of Windows is open-source. >> * Remove the -P options to preserve formatting, less can handle it. > > The makefile doesn't use -P. By using environment variables and extra pipe commands. But in any case, a version *without* stripping all that formatting info, viewable in the terminal, would be nice. > no. It's an ASCII file. Pretty bullets don't help much, considering that > less than 1% of the file uses that. For interesting typography, refer to > the PDF. That's a matter of opinion. Using the letter `o` for bullets is particular ugly to me. >> * -Thtml >> >> The html and pdf formats provide significant features not in the txt > > groff's html format isn't useful. I don't use that anymore: You mean the format that is identical to the format you produce, other than the (admittedly better) filenames for the included `.png`s? -Ben
Bug#848818: xterm: ctlseqs.txt is not rebuilt from ctlseq.ms
Package: xterm
Version: 327-2
Severity: serious
Justification: Policy 2.1
Dear Maintainer,
The ctlseqs.txt file is not built from ctlseqs.ms if it is modified
(which it should be, since it is wrong in a few places).
The command to bytewise-reproduce the existing file is:
$ groff -P{-c,-b,-o,-u} -Tascii -t -ms < ctlseqs.ms > ctlseqs.txt
Note: You need to add a build-dep on `groff`, not just `groff-base`,
in order to install the macro packages `-ms`.
But there are some *better* command variants.
* Remove the -P options to preserve formatting, less can handle it.
* -Tutf8 (better quotes/bullets; the VT fonts have everything they need).
* -Tpdf
* -Thtml
The html and pdf formats provide significant features not in the txt
version, though the PDF doesn't have a Table of Contents.
-Ben
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32, arm64
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xterm depends on:
ii libc6 2.24-8
ii libfontconfig1 2.11.0-6.7
ii libice6 2:1.0.9-1+b1
ii libtinfo5 6.0+20161126-1
ii libutempter01.1.6-3
ii libx11-62:1.6.4-2
ii libxaw7 2:1.0.13-1
ii libxft2 2.3.2-1
ii libxinerama12:1.1.3-1+b1
ii libxmu6 2:1.1.2-2
ii libxpm4 1:3.5.11-1+b1
ii libxt6 1:1.1.5-1
ii xbitmaps1.1.1-2
Versions of packages xterm recommends:
ii x11-utils 7.7+3
Versions of packages xterm suggests:
ii xfonts-cyrillic 1:1.0.4
-- no debconf information
Bug#848067: xorg: Xorg segfault in RRSetChanged at startup with MGA G550
Package: xorg
Version: 1:7.7+7
Severity: important
Dear Maintainer,
I'm attempting to run Xorg on a system with on-board Intel video and an
add-on PCI Matrix G550 card. I have configured the system BIOS to use
the G550 as the primary video card.
In this state, whenever I start Xorg, it segfaults. Curiously, this
happens even if I remove xserver-xorg-video-intel or if I remove
xserver-xorg-video-mga. I have not tried removing both, but I don't
expect that to produce a useful X server.
I have followed the instructions for generating a backtrace here:
http://pkg-xorg.alioth.debian.org/howto/use-gdb.html
Note that the xorg.conf incantation to disable "mga" doesn't seem to
have any effect, but I forgot to remove it.
--
Ben Harris, University of Cambridge Information Services. Tel: (01223) 748438
GDB backtrace:
#0 0x7fcbcf0c1067 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 2545
selftid = 2545
#1 0x7fcbcf0c2448 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7fcbd1cbdc98,
sa_sigaction = 0x7fcbd1cbdc98}, sa_mask = {__val = {2,
140726308285808, 140513363119559, 5, 0, 0, 140513328573736, 1,
140726308285808, 140513374837808, 140513363145445, 0,
140513328763664, 140513369829824, 140726308285568, 0}},
sa_flags = -775361120, sa_restorer = 0x7fcbd17b0980}
sigs = {__val = {32, 0 }}
#2 0x7fcbd155762e in OsAbort () at ../../os/utils.c:1361
No locals.
#3 0x7fcbd14324dc in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT)
at ../../../../hw/xfree86/common/xf86Init.c:1088
i =
#4 0x7fcbd1432596 in AbortDDX (error=error@entry=EXIT_ERR_ABORT)
at ../../../../hw/xfree86/common/xf86Init.c:1132
i =
#5 0x7fcbd155cef2 in AbortServer () at ../../os/log.c:783
No locals.
#6 0x7fcbd155dd5d in FatalError (
f=f@entry=0x7fcbd1588b28 "Caught signal %d (%s). Server aborting\n")
at ../../os/log.c:924
args = {{gp_offset = 24, fp_offset = 48,
overflow_arg_area = 0x7ffd659dae60,
reg_save_area = 0x7ffd659dad90}}
args2 = {{gp_offset = 8, fp_offset = 48,
overflow_arg_area = 0x7ffd659dae60,
reg_save_area = 0x7ffd659dad90}}
beenhere = 1
#7 0x7fcbd1554f7c in OsSigHandler (signo=11, sip=,
unused=) at ../../os/osinit.c:147
unused =
sip =
signo = 11
#8
No locals.
#9 RRSetChanged (pScreen=0x7fcbd1cb4c40) at ../../randr/randr.c:558
master =
mastersp = 0x0
#10 0x7fcbd14b6c34 in RRScreenSetSizeRange (
pScreen=pScreen@entry=0x7fcbd1cb4c40, minWidth=,
minHeight=, maxWidth=,
maxHeight=) at ../../randr/rrinfo.c:228
No locals.
#11 0x7fcbd1473925 in xf86RandR12CreateScreenResources12 (
pScreen=0x7fcbd1cb4c40) at ../../../../hw/xfree86/modes/xf86RandR12.c:1580
c =
pScrn =
config = 0x7fcbd1cb1c30
#12 xf86RandR12CreateScreenResources (pScreen=pScreen@entry=0x7fcbd1cb4c40)
at ../../../../hw/xfree86/modes/xf86RandR12.c:838
pScrn = 0x7fcbd1cb6060
config =
c =
width =
height =
mmWidth =
mmHeight =
#13 0x7fcbd14664f0 in xf86CrtcCreateScreenResources (screen=0x7fcbd1cb4c40)
at ../../../../hw/xfree86/modes/xf86Crtc.c:712
screen = 0x7fcbd1cb4c40
scrn =
config =
#14 0x7fcbd13f5404 in dix_main (argc=2, argv=0x7ffd659db508,
envp=) at ../../dix/main.c:213
pScreen = 0x7fcbd1cb4c40
i = 0
alwaysCheckForInput = {0, 1}
#15 0x7fcbcf0adb45 in __libc_start_main (main=0x7fcbd13df8e0 ,
argc=2, argv=0x7ffd659db508, init=, fini=,
rtld_fini=, stack_end=0x7ffd659db4f8) at libc-start.c:287
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -7903727559547672260,
140513365588197, 140726308287744, 0, 0, 7902298449705576764,
7910519680052767036}, mask_was_saved = 0}}, priv = {pad = {
0x0, 0x0, 0x7fcbd1561b10 <__libc_csu_init>, 0x7ffd659db508},
data = {prev = 0x0, cleanup = 0x0, canceltype = -782886128}}}
not_first_call =
#16 0x7fcbd13df90e in _start ()
No symbol table info available.
-- Package-specific info:
X server symlink status:
lrwxrwxrwx 1 root root 13 Dec 8 16:34 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2401376 Feb 11 2015 /usr/bin/Xorg
VGA-compatible devices on PCI bus:
--
04:00.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd.
Millennium G550 [102b:2527] (rev 01)
Xorg X server configuration file status:
-rw-r--r-- 1 root root 46 Dec 13 13:25 /etc/X11/xorg.conf
Contents of /etc/X11/xorg.conf:
---
Sect
Bug#831420: RM: xserver-xorg-input-vmmouse -- RoQA; obsolete and conflicts with kernel
Package: ftp.debian.org Severity: normal This is a driver for the VMware virtual mouse device. We now enable the Linux kernel driver for this device, so Xorg will support it through its generic libinput or evdev driver. Further, the kernel and Xorg vmmouse drivers cannot be used at the same time so the current linux-image packages break this package. Although this package might conceivably be useful on non-Linux kernels, it is currently only built for Linux so I don't think that's a reason to keep it.
Re: Bug#831286: installation-reports: Reiser4 (SFRN 4.0.1) linux-image-4.6.0-1+reiser4.0.1-amd64(4.6.3-1) d-i on Jessie successful install on HP Pavilion
Control: reassign -1 xserver-xorg-input-all 1:7.7+15 Control: retitle -1 Drop dependency on xserver-xorg-input-vmmouse Control: severity -1 important On Thu, 2016-07-14 at 12:18 +, j...@metztli-it.com wrote: [...] > Boot method: USB > Image version: > https://metztli.it/readOnlyEphemeral/metztli-jessie_4.6.3-1.iso > https://metztli.it/readOnlyEphemeral/metztli-jessie_4.6.3-1.SHA256SUM [...] > Comments/Problems: > > Reiser4 [Software Format Release Number (SFRN) 4.0.1]-enabled d-i on USB[*], > implemented expert install with Debian Desktop Environment GUI. > Custom kernel embedded as UDEB in Debian-Installer (d-i), automatically > downloaded kernel & matching reiser4progs from metztli.it. > d-i also fetched required linux-base 4.3 dependency from Jessie backports and > last d-i phase removed nfs-common and xserver-xorg-input-vmmouse[**] > - as it conflicted with custom kernel package. > > https://metztli.it/readOnlyEphemeral/jessie-reiser4-tlacatecolotl.png > > Sample install sequence originally illustrated on Debian Sid: > https://metztli.it/blog/index.php/ixiptli/reiser4-sfrn-4-0-1 > https://metztli.it/blog/index.php/ixiptli/installing-a-reiser4-patched-linux > > [*] > dd if=metztli-jessie_4.6.3-1.iso of=/dev/sdb bs=4M; sync > (where, of course, /dev/sdb represents [your] USB device) > > [**] Note removing xserver-xorg-input-vmmouse also removes > task-gnome-desktop, task-desktop, and input driver metapackage > xserver-xorg-input-all [...] This is definitely a bug in xserver-xorg-input-all. The kernel driver for the VMware mouse device is incompatible with Xorg's vmmouse driver but works with the generic evdev and libinput drivers. xserver-xorg- input-all must not depend on the vmmouse driver. However, the Xorg vmmouse driver will continue to be used in jessie. The custom kernel used in this image should not include the vmmouse driver and should not declare that it breaks xserver-xorg-input- vmmouse. This is what has been done in the jessie-backports kernel package. Ben. -- Ben Hutchings 73.46% of all statistics are made up. signature.asc Description: This is a digitally signed message part
Re: Bug#825916: installation-reports: Installing Debian with AMD/ATI Radeon graphics card does not go well
On Tue, 2016-05-31 at 12:34 +0200, scootergrisen wrote: > Package: installation-reports > Severity: important > > When i install Debian on computer with AMD/ATI Radeon graphics card it does no > go well. > > After installation there is problem booting into the graphical desktop (GNOME) > because it needs firmware-linux-nonfree and other packages to it seems. > > This is a big problem for a new user that wants to try Debian for the first > time and have no idea why the system cant start the graphical desktop and what > commands to type. > > I would at least expect to be able to start the desktop into some low > resolution mode like in Windows where you can get into the desktop even though > you dont have the correct driver. Yes, something should load a generic framebuffer driver if necessary. I don't know what that would be though. - I don't think it can be the kernel, as the kernel doesn't take that sort of policy decision - It can't be the X or Wayland server, because they don't run as root - I don't think it should be the display manager, because we have multiple implementations of that (gdm3, kdm, lightdm, ...) Maybe a systemd unit/init script provided by an X/WL base package? The other question is what the generic framebuffer driver would be, on x86. I just tried vga16fb, and gdm3 doesn't work on that - it seems to be repeatedly starting an X server that quickly crashes. efifb is presumably preferable on UEFI systems. uvesafb is another option but requires a userland helper. Ben. > Then maybe the user is able to find information on the web/IRC to fix the > problem. -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature. signature.asc Description: This is a digitally signed message part
Bug#799325: weston: won't start despite having an active logind session
Package: weston Version: 1.8.0-3 Severity: important Dear Maintainer, According to README.Debian, having an active logind session should be sufficient to start weston without being in the weston-launch group. This does not work. $ loginctl list-sessions SESSIONUID USER SEAT 198 1000 ben seat0 8 1000 ben seat0 262 1000 ben seat0 197128 sddm seat0 4 sessions listed. $ loginctl show-session 262 Id=262 Name=ben Timestamp=Thu 2015-09-17 14:33:40 PDT TimestampMonotonic=111440115978 VTNr=2 TTY=/dev/tty2 Remote=no Service=login Scope=session-262.scope Leader=25537 Audit=262 Type=tty Class=user Active=yes State=active IdleHint=no IdleSinceHint=1442525896738975 IdleSinceHintMonotonic=111715924138 $ weston-launch weston-launch: Permission denied. You should either: - enable systemd session support for weston-launch. - or add yourself to the 'weston-launch' group. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages weston depends on: ii adduser 3.113+nmu3 ii libc6 2.19-19 ii libcairo2 1.14.2-2 ii libcolord2 1.2.11-1 ii libdrm2 2.4.64-1 ii libegl1-mesa [libegl1-x11] 10.6.3-1 ii libgbm1 10.6.3-1 ii libgles2-mesa [libgles2]10.6.3-1 ii libglib2.0-02.44.1-1.1 ii libinput10 1.0.1-1 ii libjpeg62-turbo 1:1.4.1-2 ii liblcms2-2 2.6-3+b3 ii libmtdev1 1.1.5-1 ii libpam0g1.1.8-3.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpixman-1-0 0.32.6-3 ii libpng12-0 1.2.50-2+b2 ii libudev1225-1 ii libwayland-client0 1.8.1-1 ii libwayland-cursor0 1.8.1-1 ii libwayland-egl1-mesa [libwayland-egl1] 10.6.3-1 ii libwayland-server0 1.8.1-1 ii libx11-62:1.6.3-1 ii libx11-xcb1 2:1.6.3-1 ii libxcb-composite0 1.10-3+b1 ii libxcb-render0 1.10-3+b1 ii libxcb-shape0 1.10-3+b1 ii libxcb-shm0 1.10-3+b1 ii libxcb-xfixes0 1.10-3+b1 ii libxcb-xkb1 1.10-3+b1 ii libxcb1 1.10-3+b1 ii libxcursor1 1:1.1.14-1+b1 ii libxkbcommon0 0.5.0-1 Versions of packages weston recommends: ii libgl1-mesa-dri 10.6.3-1 weston suggests no packages. -- no debconf information
Bug#779515: Should enable the qxl kernel driver when installed
Source: xserver-xorg-video-qxl Version: 0.1.1-2 Severity: normal I've enabled the kernel's qxl driver, but disabled by default so that it doesn't conflict with wheezy's version of xserver-xorg-video-qxl. Please install a modprobe configuration file with the line: options qxl modeset=1 (When I tried this on a VM host with virt-manager and QEMU from sid, the qxl driver complained of missing features, so KMS still didn't work. However, the fall-back to UMS still worked.) Ben. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150301184754.9121.41900.report...@deadeye.wl.decadent.org.uk
Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption
Package: xserver-xorg-video-intel Version: 2:2.21.15-1+b2 Followup-For: Bug #725781 The upstream bug for this is: https://bugs.freedesktop.org/show_bug.cgi?id=59771 A couple of patches to libdrm were provided by upstream, but reports by testers are that neither of them fixed the problem. I'm discouraged by: Chris Wilson 2013-09-20 11:34:25 UTC The fix in libdrm lies unreviewed. In the meantime the default has changed to SNA which renders this code obsolete. The default in Debian is still UXA. So far as I know, we cannot use SNA. Ben -- 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/2013145940.4546.77496.reportbug@shade.edennet
Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption
Package: xserver-xorg-video-intel Version: 2:2.21.15-1+b2 Followup-For: Bug #725781 Correction, we *can* use SNA. My method for configuring was: X -configure (Interestingly, in my case this is not without errors, but it generates a usable config for my purposes; I'll check the error later/file a new bug if needed.) Then extract the intel driver section as /etc/X11/xorg.conf.d/intel.conf and edit to enable SNA: Section Device Option AccelMethod SNA Identifier Card0 Driver intel BusID PCI:0:2:0 EndSection I tried my steps (reported earlier) to reproduce the bug and now can no longer reproduce the issue with SNA. So it's looking good so far ... Ben -- 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/2013163811.5965.94135.reportbug@shade.edennet
Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption
On 11/11/13 01:39 PM, Julien Cristau wrote: Unreviewed and testers said it doesn't work aren't exactly the same. Which is it? A bit of both. Chris Wilson provided two patches. After applying the first patch, one tester said the problem was fixed. Chris then came up with a second patch which he thought would clear up the root cause of the problem. Two testers reported the second patch did not fix the issue, so Chris needs to review both patches to figure out what's wrong with his attempt to address the root cause. I guess we could try the first patch against the version in Debian, but before doing that, I would want to know why Chris went on to try to solve it a different way (which apparently failed). Here's the first patch which reportedly works: https://bugs.freedesktop.org/attachment.cgi?id=75820 Here are the comments between Chris and the testers regarding both patches: Chris Wilson 2013-03-03 10:05:29 UTC Created attachment 75820 [details] [review] Fix up fence counts My belief is that the error in fence counting is magnified through the clear_relocs() function, and if true this patch should fix up the leak. aux...@gmail.com 2013-05-03 13:39:13 UTC Glyph corruption has been absent for the past two days after I applied the patch, even after suspend to RAM. This seems to be fixed, thanks. [reply] [-] Comment 19 Chris Wilson 2013-05-08 16:45:15 UTC Created attachment 79029 [details] [review] Avoid overcounting fences for self-relocs I think this is the root cause of the miscounting issue. Please test without the other patch applied. [reply] [-] Comment 20 aux...@gmail.com 2013-05-08 20:05:26 UTC Empty windows and the message (EE) intel(0): Failed to submit batch buffer, expect rendering corruption: Resource deadlock avoided. just appeared with the second patch applied. [reply] [-] Comment 21 M.R 2013-05-11 18:20:42 UTC Second patch didn't fix it for me either. Atom N550 Desktop: GNOME 3.8 (Fedora 19) Patch applied on libdrm commit 040f6b015e Ben signature.asc Description: OpenPGP digital signature
Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption
Package: xserver-xorg-video-intel Version: 2:2.21.15-1+b2 Followup-For: Bug #725781 Neither the latest xserver-xorg-video-intel nor new kernel (3.11.6-2 unstable or 3.12~rc7-1~exp1 experimental) fix the problem. Furthermore, although my workaround switching the xrandr parameters back and forth does lessen lagginess after initially triggering the bug, I have discovered it actually is not a whole solution. From the point of first appearance of the error to when the Xserver is shutdown and restarted, neither mplayer nor vlc will display videos at all using their default video output. 'mplayer -vo xv' displays this error repeatedly: X11 error: BadAlloc (insufficient resources for operation) There is no video output. 'mplayer -vo x11' is fine. 'vlc -vv' outputs this error repeatedly: [0x7f1b94001248] xcb_xv vout display debug: cannot put image: X11 error 11 There is no video output. Ben -- 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/20131110223708.22928.1401.reportbug@shade.edennet
Bug#719144: weston: please update to latest upstream release
I tried uupdate plus the earlier attached patch, but it fails to install in the install stage. There are plenty of warnings earlier in the output. dh_install: weston missing files (usr/lib/*/weston-screensaver), aborting -- 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/CA+XNFZPs=wvcjcx1ad0o8vufyrm9hp3j8wkq9cvrjuycisv...@mail.gmail.com
Bug#719144: weston: please update to latest upstream release
Since wayland 1.2 hit testing in september, the weston package cannot be installed at all. -- 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/CA+XNFZNt=tUer-Vp+rOuB98nfiZHLabLxHt2w1=yz_zuaap...@mail.gmail.com
Re: Removing old unmaintained X drivers
On Sat, 2013-09-28 at 10:16 -0500, Bob Tracy wrote: On Sat, Sep 28, 2013 at 02:29:05PM +0100, Jurij Smakov wrote: On Thu, Sep 26, 2013 at 10:26 PM, Julien Cristau jcris...@debian.orgwrote: (...) xserver-xorg-video-sis (...) The SiS chipset was, unfortunately, really popular with manufacturers of relatively expensive micro PeeCees (EzGo, Jadetec, etc.), which were essentially notebook hardware crammed into a small desktop case. Here's a link with good pics: http://www.tomshardware.com/reviews/smallest,530-2.html and see also http://www.snotmonkey.com/work/ezgo/ for detailed specs. It's based on the P4, and I've got one of them. Case has the footprint of a shuttle, but is about half the height. If I *could* switch video cards, I'd do it in a heartbeat because SiS video cards have given me nothing but grief through the years. In the unsolved wontfix ubuntu bug list for the driver, mention is made of the fact XAA support went bye-bye, and the attempted use of EXA causes looping segfaults on X server startup. Only current workaround is to disable acceleration. Truly a case of bad breath is better than no breath. This sounds like a good reason to remove it, unless both vesa and fbdev also fail on this hardware. Ben. -- Ben Hutchings The world is coming to an end. Please log off. signature.asc Description: This is a digitally signed message part
Improving hardware support in Debian stable
This mail is a follow-up to yesterday's meeting at DebConf: https://penta.debconf.org/penta/schedule/dc13/event/1013.en.html (recordings not yet available, but should be soon) I don't think anyone took notes at the time, but I think there was general consensus that: 1. compat-drivers should be packaged separately from linux, and should build a separate binary package per subsystem (and per flavour). This should remove the risk of regressions for hardware that's already supported. 2. The installer should install whichever of these binary packages are needed (presumably with the aid of discover). 3. Mesa drivers for new chips should be packaged with different names and only bound to the new PCI IDs. Mesa can then automatically load whichever driver is appropriate. 4. The new/updated drivers potentially get updated at every point release. We won't attempt to support multiple new versions of a driver per suite. There is a risk of regression for those using them, but this is no worse than the current situation where users must update the entire kernel or X server from another suite which is updated even more frequently. I don't think X video drivers and libdrm modules were explicitly addressed, but presumably they can be handled similarly to Mesa drivers? Hardware support in the installer itself wasn't addressed within the meeting proper, but after later discussion it was obvious that compat-drivers must build udebs to be included in installer images. Now there is a potential problem with the installer, in that the updated kernel modules would always be 'installed' in the initrd, whereas on the installed system they would only be installed if necessary. So if a backported driver has a regression in support for older hardware, it would not affect the installed sytem but *would* affect the installer. I'm not sure how to get around that. Possibly the new modules should be renamed and have their PCI IDs restricted. But this is not ideal as it will force people to configure module options differently, and it will require new logic in initramfs-tools to find the updated drivers. I'll keep thinking about how to solve this, but would appreciate suggestions from others... Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#668828: Updating found versions and confirming workaround
found 668828 xserver-xorg-video-nouveau/1:1.0.1-5 thanks This bug affects my iMac G5 running Debian 7.1 (wheezy). In my case, the main symptom was that emacs23 didn't display any text when moved into the bottom half of the screen. The xorg.conf file in message #45 works around the problem for me. -- Ben Harris -- 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/alpine.deb.2.02.1306170102050.29...@puff.ds.cam.ac.uk
Re: Bug#572754: Closing
On Thu, 2013-06-06 at 09:26 +0800, Paul Wise wrote: Control: reopen -1 Control: found -1 3.9.4-1 The bug is still reproducible with Linux from jessie. Well I wonder whether it's really a kernel bug anyway. It's surely up to the X server and DDX to decide what to render when you switch back to its VT, whether or not the kernel is doing modesetting for it. X maintainers, could you comment on this? Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. signature.asc Description: This is a digitally signed message part
Bug#708091: libgl1-mesa-glx:i386: Also happening to me
Package: libgl1-mesa-glx Version: 8.0.5-4 Followup-For: Bug #708091 Dear Maintainer, Preparing to replace libgl1-mesa-glx:i386 8.0.5-4 (using .../libgl1-mesa-glx_8.0.5-4+b1_i386.deb) ... Unpacking replacement libgl1-mesa-glx:i386 ... dpkg: error processing /var/cache/apt/archives/libgl1-mesa-glx_8.0.5-4+b1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-mesa-glx/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-glx:i386 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libgl1-mesa-glx:i386 depends on: ii libc6 2.17-2 ii libdrm22.4.40-1~deb7u2 ii libgcc11:4.8.0-7 ii libglapi-mesa 8.0.5-4 ii libstdc++6 4.8.0-7 ii libx11-6 2:1.5.0-1 ii libx11-xcb12:1.5.0-1 ii libxcb-glx01.8.1-2 ii libxcb11.8.1-2 ii libxdamage11:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxxf86vm11:1.1.2-1 ii multiarch-support 2.13-38 Versions of packages libgl1-mesa-glx:i386 recommends: ii libgl1-mesa-dri 8.0.5-4+b1 libgl1-mesa-glx:i386 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/20130514214819.29002.35660.report...@thor.lan
Re: 702668: not possible to select screen left of other screen, only clone mode is possible (solved)
On Sat, 2013-04-06 at 11:14 +, Jaap van Wingerde wrote: Bug 702668 is solved with package linux-image-3.2.0-4-amd64. The problem with loading radeon firmware still exists. [...] How is this a problem? You have chosen not to install it. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Bug#703276: Same Issue
Hi, i am having the exact same issue and i think the symptoms are the same like i have written in Bug #680514 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680514 )? Can you please try to reproduce it by clicking on the OpenGL-Screensavers in the KDE-Settings? I have manually installed the kernel 3.2.41-2-amd64 from the unstable repo and the problem still exists. With the old 35-2-amd64 kernel there are no problems. So at the moment i have to use an outdated kernel. Regards Bentallica -- 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/trinity-17fe5766-1c0c-49e4-a42c-09ab8186dae3-1365004897174@3capp-gmx-bs61
Bug#680514: More Information
Hi, as i have written yesterday, i can reproduce this issue by clicking on the names of the OpenGL-Screensavers in the KDE Settings. When I do that, X freezes and i only can move the mouse. In the Xorg.0.log.old are the same problems with [mi] EQ overflow continuing like in the files from message #45. So far, so bad. Another thing i have found out is that with the old kernel 3.2.35-2-amd64 there are no problems with this issue. So maybe it is related to #703276 bug? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703276 Regards Bentallica -- 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/trinity-5474d8d4-c05d-4336-bceb-096d253fb4b7-1365004857961@3capp-gmx-bs61
Bug#680514: Maybe a way to reproduce
Hi, i am having the same problem i think. I have a HD3000 IGPU on a i5-2500K Desktop CPU and i'm running Debian Wheezy with KDE. The way to reproduce the issue is to click or change very fast the screensaver in the KDE-Settings. You have to change the OpenGL- Screensavers very fast by clicking on the names of them. After a few clicks (5-15) the Xserver freezes and i'm only able to move the mouse, nothing more. Regards Bentallica -- 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/trinity-09470a13-42c2-4b07-963e-19fdbdb364f8-1364827602212@3capp-gmx-bs52
Re: Bug#702668: RV350 AQ: not possible to select screen left of other screen, only clone mode is possible
On Sat, 2013-03-09 at 13:11 -0800, Jonathan Nieder wrote: # regression severity 702668 important quit Hi, Jaap van Wingerde wrote: Version: 3.2.35-2 [...] It is not possible to select a screen right or left of other screen, only clone mode is possible (gnome-control-center display). With linux-image-3.2.0-3-amd64 this works perfect. [...] [ 31.122989] pci :01:00.0: putting AGP V3 device into 8x mode [ 31.425620] [drm] Setting GART location based on new memory map [ 31.425750] [drm] Loading R300 Microcode [ 31.455633] platform radeon_cp.0: firmware: agent aborted loading radeon/R300_cp.bin (not found?) [ 31.456061] [drm:radeon_do_init_cp] *ERROR* Failed to load firmware! [...] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV350 AQ [Radeon 9600] [1002:4151] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. A9600SE [1043:c004] Thanks for reporting. Is the firmware-linux-nonfree package installed? Either way, please attach output from reportbug --template xserver-xorg-video-radeon In version 3.2.35-1 I changed radeon to disable KMS when firmware is not installed, because this generally doesn't work. Previously the driver would try to continue and this would often cause memory corruption or a blank screen. However, for the older chips such as the R300 family radeon should be able to do KMS without any firmware (only 3D acceleration will be disabled, as before). I changed the driver again in 3.2.39-1 to revert to the previous behaviour for these chips. Jaap, please try the current version from unstable (3.2.39-2). Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way. signature.asc Description: This is a digitally signed message part
Re: Bug#697029: [ilk] using GNOME 3 makes computer sluggish after a few minutes
On Sat, 2013-02-23 at 12:05 -0800, Jonathan Nieder wrote:
found 697029 linux/3.7.3-1~experimental.1
tags 697029 - wontfix
affects 697029 + release-notes
quit
Hi,
Chris Wilson wrote:
The performance issue on 3.7 is not due to the missed irq, but a
combination of using UXA and VT-d. In order to workaround an erratum
on Ironlake, every time we touch the GPU's page tables, we have to
idle the GPU before doing so. This causes extremely noticeable display
lag.
For reference, the workaround seems to be implemented by:
commit 6fbcfb3e467adb414e235eeefaeaf51ad12f2461
Author: David Woodhouse dw...@infradead.org
Date: Sun Sep 25 19:11:14 2011 -0700
intel-iommu: Workaround IOTLB hang on Ironlake GPU
commit 5c0422878fcdc279ae9a8e8b66972a15b5efb67f
Author: Ben Widawsky b...@bwidawsk.net
Date: Mon Oct 17 15:51:55 2011 -0700
drm/i915: ILK + VT-d workaround
However the latter is applied only to Ironlake M (mobile). So either
there are two different bugs or there is some confusion about which
chips have the bug.
Pierre AUSSAGUEL wrote:
Appending intel_iommu=off seems to fix the problem (I tested a few
days befor posting).
Daniel Vetter wrote:
Since we can't fix the hw, closing this as wontfix. Thanks for
reporting this issue anyway.
That makes this a distro issue, I suppose.
Ben and X team, any ideas? Would it makes sense to disable
intel_iommu by default on this hardware and require intel_iommu=on to
reenable it?
Use of an IOMMU is in part a performance vs security trade-off. I tend
to think that security settings should have consistent defaults, as
otherwise users may assume that a security feature is enabled when it is
not.
Aside from that, the Intel IOMMU can be enabled separately per device
(except behind PCI bridges). Since IGPs aren't real PCI(e) devices and
Intel has not always validated their interaction with the IOMMU, they
often don't work with it. There is already a kernel parameter to
disable it for the IGP ('intel_iommu=igfx_off') and a quirk to do so
automatically for the G4x and GM45. Maybe the thing to do is to log a
message about this parameter when enabling the workaround for Ironlake.
Should GNOME somehow detect that it should use classic
mode by default when the iommu is enabled?
I think this would be a very poor heuristic.
If we can't come up with a workaround, this should be mentioned in the
release notes to prevent a regression on upgrade. Please feel free to
remind me in that case so I can come up with some wording (though I
also wouldn't mind if someone else does).
Graphics rendering may be very slow on Intel 'Ironlake M' GPUs (PCI ID
8086:0046) when an IOMMU (VT-d) is enabled. The IOMMU functionality can
be disabled for the GPU by adding the kernel parameter
'intel_iommu=igfx_off'.
(The identification of which devices are affected may need to be
revised.)
Ben.
--
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
signature.asc
Description: This is a digitally signed message part
Bug#692092: I believe I found the cause of the problem.
I reported this bug, one thing I noticed was this, This machine only has an AGP aperature of 8MB in the bios, I know, I set it, but this software clearly thinks it has 128mb available, this might be the cause of the hung gpu? , anyone know, im not a software expert, but thats my theory. Hope some developer sees this and it proves useful. DRM Information from dmesg: ---snippet [0.970788] Linux agpgart interface v0.103 [0.970915] agpgart-intel :00:00.0: Intel 845G Chipset [0.970951] agpgart-intel :00:00.0: detected gtt size: 131072K total, 131072K mappable [0.971083] agpgart-intel :00:00.0: detected 8192K stolen memory [0.971278] agpgart-intel :00:00.0: AGP aperture is 128M @ 0xf000 [5.820425] [drm] Initialized drm 1.1.0 20060810 [6.007835] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [6.007841] [drm] Driver supports precise vblank timestamp query. [6.027907] [drm] initialized overlay support [6.140964] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 13 [6.203152] fbcon: inteldrmfb (fb0) is primary device [6.328171] fb0: inteldrmfb frame buffer device [6.328175] drm: registered panic notifier [6.328603] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 36.512021] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung - This machine only has an AGP aperature of 8MB in the bios, I know, I set it, but this software clearly thinks it has 128mb available, this might be the cause of the issue, anyone know? -- 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/caejuth5_c3xytqwmhytifx5jkoydeckmmp-_kb5mlf7-8ut...@mail.gmail.com
Bug#681796: Hitting this without suspend
I am also hitting this bug but I don't have to suspend. It happens maybe once a week while using Xorg. The X server dies and then Kdm (?) puts up a new login screen. I can log back in and then resume work. Can't pin it on any one action although it appears to be related to using the touchpad on my Acer 1810tz laptop. I'm running Ubuntu 12.04 fully up to date. LMK how I can help track it down. I could attach gdb to the Xorg server on one the TTYs but I don't know if I could swap over to it (ctrl-alt-F1) after Xorg crashes and is sitting in gdb. -Ben McCann -- 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/5013b15c.5070...@gmail.com
Bug#579185: x11-xserver-utils: weird xkeystone executable
Package: x11-xserver-utils
Version: 7.6+3
Followup-For: Bug #579185
Dear Maintainer,
I managed to get xkeystone to work by commenting out a couple lines.
--- xkeystone~ 2011-07-02 11:25:46.0 -0700
+++ xkeystone 2012-04-03 07:52:18.0 -0700
@@ -496,8 +496,8 @@
text = (string[3]) { no solution, ... };
m_available = false;
}
- for (int i = 0; i 3; i++)
- Label::relabel (label[i], text[i]);
+/* for (int i = 0; i 3; i++)
+ Label::relabel (label[i], text[i]);*/
}
quad_t quad = Quad::new (nichrome, callback);
With this patch, there are a few labels on the screen that read Matrix
instead of whatever information they are supposed to show. By default,
xkeystone shows only a white screen and outputs these error messages for me:
~$ xkeystone
Unhandled exception deadlock ({sem = semaphore 1 (0), owner = owner = %86},
%86)
/usr/share/nickle/mutex.5c:49: raise deadlock (m, Thread::current ());
acquire (composite)
/usr/share/nickle/nichrome.5c:189: twixt (Mutex::acquire
(widget.nichrome.drawing); Mutex::release (widget.nichrome.drawing))
resize (composite)
/usr/bin/xkeystone:500: Label::relabel (label[i], text[i]);
callback (composite)
/usr/share/nickle/nichrome-box.5c:303: item.configure (item.contained,
child_layout, child_geometry);
configure (composite, composite, composite)
/usr/share/nickle/nichrome.5c:414: nichrome.configure (nichrome);
draw (composite)
/usr/share/nickle/nichrome.5c:542: draw (nichrome);
main_loop (composite)
/usr/bin/xkeystone:556: main ();
^CUnhandled exception signal (2)
/usr/share/nickle/nichrome.5c:530: Semaphore::wait (read_event);
event_reader ()
/usr/share/nickle/nichrome.5c:534: event_reader ();
main_loop (composite)
/usr/bin/xkeystone:556: main ();
~$
With my patch, those problems go away, but of course it is not an
optimal solution. Best would be to catch the mutex exception and
handle it properly.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core)
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-xserver-utils depends on:
ii cpp 4:4.6.2-4
ii libc6 2.13-26
ii libice6 2:1.0.7-2
ii libx11-6 2:1.4.4-4
ii libxau6 1:1.0.6-4
ii libxaw7 2:1.0.9-3
ii libxcursor1 1:1.1.12-1
ii libxext6 2:1.3.0-3
ii libxi6 2:1.4.5-1
ii libxmu6 2:1.1.0-3
ii libxmuu1 2:1.1.0-3
ii libxrandr2 2:1.3.2-2
ii libxrender1 1:0.9.6-2
ii libxt6 1:1.1.1-2
ii libxxf86vm1 1:1.1.1-2
x11-xserver-utils recommends no packages.
Versions of packages x11-xserver-utils suggests:
ii cairo-5c 1.4
ii nickle 2.74-1
ii xorg-docs-core 1:1.6-1
-- 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/cao+cpom6fcl+dai8fcq1vj0ms-fjs7jwv7hgcx5cpugjc6y...@mail.gmail.com
xorg: Thanks for packaging xorg!
Thank you very much for the considerable amount of ongoing work to bring us the X windowing system. In recent years, it has been so unproblematic that I find it more reliable than Linux! That makes it ubiquitous but almost imperceptible – a good thing – and hence probably almost thankless. This is my contribution to reversing that. Have a great Valentine's Day 2012. -- \ “I believe our future depends powerfully on how well we | `\ understand this cosmos, in which we float like a mote of dust | _o__) in the morning sky.” —Carl Sagan, _Cosmos_, 1980 | Ben Finney -- 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/20120213145057.14153.77482.report...@fuschia.local.whitetree.org
Bug#635137: Sometimes hangs after suspend resume
Package: compiz Version: 0.8.4-4 Severity: important After suspending and resuming my laptop (Thinkpad T61 with Intel GM965 GPU) compiz sometimes appears to hang, leaving the X display blank except for the mouse pointer. The kernel, GPU and X server are still working: the mouse pointer is responsive and I can switch between virtual consoles. I can recover by stopping compiz (kill -9) and starting it again. Next time this happens, I will try to attach to compiz with gdb. It might be helpful to build a debug symbol package so that I can provide more details. Ben. -- System Information: Debian Release: wheezy/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'oldstable-proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages compiz depends on: ii compiz-core 0.8.4-4OpenGL window and compositing mana ii compiz-gnome 0.8.4-4OpenGL window and compositing mana ii compiz-gtk0.8.4-4OpenGL window and compositing mana ii compiz-plugins0.8.4-4OpenGL window and compositing mana compiz recommends no packages. Versions of packages compiz suggests: ii compizconfig-settings-manager 0.8.4-2Compizconfig Settings Manager -- 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/2011071127.15192.32358.reportbug@localhost
Re: Bug#616093: Possible Solution
On Thu, 2011-03-03 at 16:13 +0100, Martin Künstner wrote:
Hello,
after searching for QFont::fromString: Invalid description 'Sans
Serif,10,5,0,50,0'
I found that i have to install ibus.
After installing ibus everything now works for me.
Going back to your original message (which I didn't see before, as this
bug was reassigned):
on the file open dialog libre office get stuck and the whole system gets
frozen
no user interaction is possible any more
mous is moving but every otner action is no more possible
you cant even change to console via STRG+F1
You need to use the Alt key as well.
system is not more responding
This really sounds like LibreOffice (or more likely an extension to LO)
has grabbed and then not released the keyboard and mouse. Applications
can override normal window focus temporarily ('grab') for purposes like
drag-and-drop, but unfortunately this is not automatically released when
you release the mouse buttons. If an application fails to release its
grab it can effectively break the entire desktop session in the way you
described. However, the console switching keystrokes should still work.
Could you temporarily remove ibus and test that Strg-Alt-F1 works when
the system is in this state?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
Re: Bug#616093: Possible Solution
On Sun, 2011-03-06 at 17:13 +0100, Martin Künstner wrote:
Am Sonntag, den 06.03.2011, 15:54 + schrieb Ben Hutchings:
On Thu, 2011-03-03 at 16:13 +0100, Martin Künstner wrote:
Hello,
after searching for QFont::fromString: Invalid description 'Sans
Serif,10,5,0,50,0'
I found that i have to install ibus.
After installing ibus everything now works for me.
Going back to your original message (which I didn't see before, as this
bug was reassigned):
on the file open dialog libre office get stuck and the whole system gets
frozen
no user interaction is possible any more
mous is moving but every otner action is no more possible
you cant even change to console via STRG+F1
You need to use the Alt key as well.
system is not more responding
This really sounds like LibreOffice (or more likely an extension to LO)
has grabbed and then not released the keyboard and mouse. Applications
can override normal window focus temporarily ('grab') for purposes like
drag-and-drop, but unfortunately this is not automatically released when
you release the mouse buttons. If an application fails to release its
grab it can effectively break the entire desktop session in the way you
described. However, the console switching keystrokes should still work.
Could you temporarily remove ibus and test that Strg-Alt-F1 works when
the system is in this state?
I meant Strg-Alt-F1
and it did not respond.
The system does not respond at all:
even Strg-Alt-Backspace to Kill X
Well, that key combination is now disabled by default.
or Strg-Alt-F1 to F6 did do anything.
Everything is blocked.
OK, that does sound like something more serious than an unreleased grab.
But I cannot see what difference ibus could make.
I think the BUG is in KDM.
I don't think so. kdm gets out of the way once you have logged in.
Ben.
In this log file i found the log message
QFont::fromString: Invalid description 'Sans Serif,10,5,0,50,0'
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]
On Sun, 2011-03-06 at 13:08 -0500, Alex Deucher wrote: On Fri, Mar 4, 2011 at 8:50 PM, Ben Hutchings b...@decadent.org.uk wrote: On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote: severity 616301 critical thanks No, not unless it will affect a large proportion of users. My system locks up whenever I click on a YouTube video link since yesterday. I can probably live without YouTube :), but in any case this shouldn't happen. This isn't a singled out case nor in exotic, possibly faulty, hardware. It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon HD card (one of the standard configurations) and this is on a stock squeeze system. The findings so far seem to suggest this is a Mesa issue; I'd probably file it under Linux kernel bugs (or even DoS bugs) but I'm not sure where to properly file such bugs in the post-KMS stack world. If there is a kernel driver involved then it should be assigned to the kernel. Even without KMS, a Mesa driver should be considered untrusted and should not be able to trigger a crash or hang. With KMS, this applies to the X driver too. With or without KMS, the userspace acceleration drivers can certainly cause GPU hangs if the 3D engine is programmed with some combination of commands it doesn't like. You can't solve the halting problem but you can implement a watchdog, can't you? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]
On Sun, 2011-03-06 at 19:49 -0500, John D. Hendrickson and Sara Darnell wrote: I haven't heard of many chips that won't hang given the wrong instructsion whether it's GPU or keyboard controller. Of course. This is why the kernel driver filters the commands going to the GPU - the commands come from unprivileged applications (the Mesa driver is just a shared library) and should not be trusted. Sounds like more than a driver issue but a choice of driver issue. How are you going to have it both ways without an ammount of care you have no time for? having interrupting access / watchdog is nice if your driver can do that Ben Hutchings wrote: [...] Don't top-post. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: iMac-G3 fails to boot with 2.6.37-1-powerpc (Bug#614221)
On Sat, 2011-03-05 at 20:43 +, Ben Hutchings wrote:
[...]
* Has anyone tested 2.6.37-{1,2} on a non-Mac system yet, and does
vga16fb work there?
I'm still interested in the answer to this.
[...]
* Could some Mac users test and report whether i915 or nouveau can
successfully take over the display from offb in 2.6.37 or 2.6.38-rc6?
i915 on a powerpc, eh? What was I thinking?
I've now talked briefly to the DRI and powerpc upstream maintainers, and
the answer is that radeon is mostly broken on at least 32-bit powerpc
while nouveau is in better shape but not quite stable yet. So I'm going
to revert most of the FB configuration changes I made in 2.6.37-1 for
the next upload to unstable.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
Bug#616301: xserver-xorg-video-radeon:screen goes black, system hangs after 2sec:[youtube(FF/Opera)-reset req.]
On Fri, 2011-03-04 at 21:01 +0200, Faidon Liambotis wrote: severity 616301 critical thanks No, not unless it will affect a large proportion of users. My system locks up whenever I click on a YouTube video link since yesterday. I can probably live without YouTube :), but in any case this shouldn't happen. This isn't a singled out case nor in exotic, possibly faulty, hardware. It's on a standard 1½-year old Dell OptiPlex 780 desktop with a Radeon HD card (one of the standard configurations) and this is on a stock squeeze system. The findings so far seem to suggest this is a Mesa issue; I'd probably file it under Linux kernel bugs (or even DoS bugs) but I'm not sure where to properly file such bugs in the post-KMS stack world. If there is a kernel driver involved then it should be assigned to the kernel. Even without KMS, a Mesa driver should be considered untrusted and should not be able to trigger a crash or hang. With KMS, this applies to the X driver too. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#606913: xserver-xorg-video-intel: X configure fails due to not being able to find devices
Package: xserver-xorg-video-intel Version: 2:2.13.0-4 Severity: important X -configure produces the error below. Old configuration file worked fine before updates. Running X without a configuration file works (at default resolution) but xrandr reports: xrandr: Failed to get size of gamma for output default And cannot make changes to display. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Sep 28 2009 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1733512 Dec 2 00:16 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) /etc/X11/xorg.conf does not exist. Kernel version (/proc/version): Linux version 2.6.32-5-686 (Debian 2.6.32-29) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Dec 10 16:12:40 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 14394 Dec 12 23:16 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-686 i686 Debian Current Operating System: Linux peach 2.6.32-5-686 #1 SMP Fri Dec 10 16:12:40 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=c94854b3-da40-42f7-b137-fd6ba1e2ed03 ro quiet splash Build Date: 02 December 2010 01:08:37AM xorg-server 2:1.7.7-10 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Dec 12 23:16:55 2010 (II) Loader magic: 0x81ec060 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 7 (--) PCI:*(0:0:2:0) 8086:2a42:1028:02aa Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7, Mem @ 0xf6c0/4194304, 0xe000/268435456, I/O @ 0xefe8/8 (--) PCI: (0:0:2:1) 8086:2a43:1028:02aa Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7, Mem @ 0xf6b0/1048576 List of video drivers: sisusb openchrome rendition mga ark ati nouveau v4l voodoo i128 s3 r128 radeon ztv tseng intel geode apm vmwlegacy siliconmotion cirrus neomagic mach64 i740 savage s3virge vmware trident sis chips tdfx radeonhd nv fbdev vesa (II) LoadModule: sisusb (II) Loading /usr/lib/xorg/modules/drivers/sisusb_drv.so (II) Module sisusb: vendor=X.Org Foundation compiled for 1.7.6.901, module version = 0.9.3 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: openchrome (II) Loading /usr/lib/xorg/modules/drivers/openchrome_drv.so (II) Module openchrome: vendor=http://openchrome.org/; compiled for 1.7.7, module version = 0.2.904 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: rendition (II) Loading /usr/lib/xorg/modules/drivers/rendition_drv.so (II) Module rendition: vendor=X.Org Foundation compiled for 1.7.7, module version = 4.2.3 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: mga (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so (II) Module mga: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.4.11 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: ark (II) Loading /usr/lib/xorg/modules/drivers/ark_drv.so (II) Module ark: vendor=X.Org Foundation compiled for 1.7.6.901, module version = 0.7.2 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: ati (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so (II) Module ati: vendor=X.Org Foundation compiled for 1.7.7, module version = 6.13.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: nouveau (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so (II) Module nouveau: vendor=X.Org Foundation compiled for 1.7.7, module version = 0.0.15 Module class: X.Org Video Driver ABI class:
Bug#606514: xorg: Missing modules force downgrade to fbdev / loss of modes, capabilities
Package: xorg Version: 1:7.5+8 Severity: important I'm really sorry; I don't know what package this bug belongs to. This seems like a good place to start. A recent upgrade (I upgrade every couple of weeks) broke X with the following symptoms: 1) Display failed to find 1680x1050 and dropped to 1280x1024 instead. 2) Refused to connect to external monitor (both DVI through docking station and LCD projector through VGA cable). 3) KDE systemsettings only found default rather than LVDS1 and DVI1 etc; xrandr complained similarly. 4) Screen brightness control through xbacklight returned an error. Xorg.0.conf seemed to show (I'm not too good at reading them) that the Intel driver had loaded, but that the FBdev driver claimed the PCI slot. In the past, the Intel driver was used. NOTE that reportbug picked up the post-workaround (below) xorg.0.log, which I'm leaving in as a baseline. I will attach the failed one separately as soon as I get the bugID. I thought it might be related to #606288, but I believe not, because I could switch VTs and my system did not lock. Workaround: modprobe i915 killed X, but GDM restarted and now the system seems to be using the Intel driver (the above symptoms disappeared). I will add this line to /etc/modules, but that's a kludge. Again, sorry to assign the bug so vaguely; a developer will know what to do with it. So perhaps this bug should be reassigned to some facility that is in charge of loading modules? I'm sorry I can't dig into this right now, but I'd love to provide more info if you email me questions. I'm on a ThinkPad T61... lspci's output follows. 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HBM (ICH8M-E) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) 15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba) 15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) 15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21) 15:00.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev ff) 15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11) 15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11) -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 May 1 2008 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1733512 Dec 1 17:16 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 3676 Sep 30 10:26 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # -*- sh -*- # xorg.conf (X.Org X Window System server configuration file) # # This file was
Re: Please update debian-x@ description
On 12/02/2010 10:38 AM, Cyril Brulebois wrote: Hi folks! On http://lists.debian.org/debian-x/ one can read: | Debian XFree86 packaging It'd be nice to have this instead: | Debian X.Org packaging The following long description might be better than the current one: | Discussion about the X Window System within Debian. This is not a | user support list; this list is intended for those who deal with the | source code and with the bugreports. Better, except I would say bug reports, not bugreports -- I really dislike this trend to make jargon into compound words :P Cheers, Ben -- 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/4cf7b0b9.3040...@sanctuary.nslug.ns.ca
Bug#601190: x11-xserver-utils: Xgamma man page should cross reference xrandr
Package: x11-xserver-utils Version: 7.5+2 Severity: minor Tags: patch The xgamma man page should have a link in the SEE ALSO section to the xrandr man page which also supports changing the display gamma. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages x11-xserver-utils depends on: ii cpp 4:4.4.5-1 The GNU C preprocessor (cpp) ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library ii libx11-6 2:1.3.3-3 X11 client-side library ii libxau6 1:1.0.6-1 X11 authorisation library ii libxaw7 2:1.0.7-1 X11 Athena Widget library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxi62:1.3-4X11 Input extension library ii libxmu6 2:1.0.5-2 X11 miscellaneous utility library ii libxmuu1 2:1.0.5-2 X11 miscellaneous micro-utility li ii libxrandr22:1.3.0-3 X11 RandR extension library ii libxrender1 1:0.9.6-1 X Rendering Extension client libra ii libxt61:1.0.7-1 X11 toolkit intrinsics library ii libxxf86vm1 1:1.1.0-2 X11 XFree86 video mode extension l x11-xserver-utils recommends no packages. Versions of packages x11-xserver-utils suggests: pn cairo-5c none (no description available) pn nicklenone (no description available) ii xorg-docs-core1:1.5-1Core documentation for the X.org X -- no debconf information --- xgamma.1.orig 2010-07-24 08:03:37.0 -0700 +++ xgamma.12010-10-24 02:37:53.0 -0700 @@ -91,7 +91,7 @@ The gamma values are passed to the Xserver with 3 decimal places of accuracy. .SH SEE ALSO -xvidtune(1) +xrandr(1), xvidtune(1) .SH AUTHORS Kaleb S. Keithley, X Consortium. .br
Re: Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets
On Sun, Sep 05, 2010 at 02:25:25PM +0200, Cesare Leonardi wrote: On 09/04/2010 08:00 PM, Soenke wrote: the recent update of linux-image-2.6.32 to 2.6.32-21 disables KMS for i8xx chipsets. This causes the xorg-video-intel driver to hang on X startup on my system. Yes, the situation for your i855 and previous intel chipset is in a bad shape. For example look this (but there are other similar reports): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594623 It's both a kernel and a xserver-xorg-video-intel problem, but more the latter. The kernel team is probably waiting to know if KMS should be enabled or not for these chipsets and is working in concert with the Ubuntu one for a common solution. [...] The Debian kernel team works closely with the X Strike Force regarding DRM/KMS drivers, and we generally follow their advice on what options and patches to use. We're not working with Ubuntu on this, though we did follow their lead in blacklisting those chips. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20100907122723.ga11...@decadent.org.uk
Bug#595758: synclient: man page and -h disagree about valid options
Package: xserver-xorg-input-synaptics Version: 1.2.2-2 Severity: minor synclient -h lists different options from what the man page specifies, and one of these is invalid (-?). $ synclient -h Usage: synclient [-s] [-m interval] [-h] [-l] [-V] [-?] [var1=value1 [var2=value2] ...] -m monitor changes to the touchpad state (implies -s) interval specifies how often (in ms) to poll the touchpad state -l List current user settings -V Print synclient version string and exit -? Show this help message var=value Set user parameter 'var' to 'value'. Neither the help nor the man page say what -s is (maybe use SHM? see syndaemon man page). Usage says -h is valid but does not say it shows the help message. Both Usage and the man page say -? is valid, too, whereas empirical evidence says it is not; using it results in an 'invalid option' error message. The man page says: For the -m and -h options, SHM must be enabled by setting the option SHMConfig on in your XOrg/XFree86 configuration. But even though SHMConfig is not on, -h does appear to work. Maybe they meant -s? -- 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/20100906130727.31880.81549.report...@lear.nslug.ns.ca
Bug#593893: Bug#593890: Share bug 499344: Wrong cursor when oxygencursors are installed
On 22-Aug-2010, Magnus Holmgren wrote: On söndagen den 22 augusti 2010, Julien Cristau wrote: On Sat, Aug 21, 2010 at 23:41:49 +0200, Magnus Holmgren wrote: severity 499344 minor clone 499344 -1 -2 -3 -4 reassign -1 comixcursors reassign -2 dmz-cursor-theme reassign -3 chameleon-cursor-theme reassign -4 xcursor-themes Why? It should be clear from the bug report log The general problem is clear. But in cloning this report, you haven't shown where each of the packages needs to be fixed. Your list doesn't really help me find what needs to be fixed in the package. Can you please improve these reports by showing what you think is missing in each of the packages. -- \ “Give a man a fish, and you'll feed him for a day; give him a | `\religion, and he'll starve to death while praying for a fish.” | _o__) —Anonymous | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Bug#593893: Bug#593890: Share bug 499344: Wrong cursor when oxygencursors are installed
On 22-Aug-2010, Ben Finney wrote: Can you please improve these reports by showing what you think is missing in each of the packages. Also, if I might ask further: can you please show your source for the cursor name associations you are requesting. Probably something in the Qt docs? -- \“The problem with television is that the people must sit and | `\keep their eyes glued on a screen: the average American family | _o__) hasn't time for it.” —_The New York Times_, 1939 | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Bug#587618: xserver-xorg: Periodically x switches between virual desktops randomly and at speed
On 30/06/10 14:47, Julien Cristau wrote: On Wed, Jun 30, 2010 at 13:53:42 +0100, Ben Whyall wrote: Attached are the files you asked for. The period when it happened is towards the bottom of the xinputtest.txt file. It's difficult to be more precise as it jumped round 6 or 7 times before allowing me ot move to correct workspace and stop the trace. Weird, the only thing that may be suspicious is devices 10 and 11 (Microsoft 2.4GHz Transceivers) switching around from keyboard to mouse and vice versa halfway in the trace: And now 10 is a slave keyboard and 11 is a slave pointer.. EVENT type 1 (DeviceChanged) device: 2 (11) reason: SlaveSwitch Reporting 7 classes: Class originated from: 11 Buttons supported: 13 Button labels: Button Left Button Middle Button Right Button Wheel Up Button Wheel Down Button Horiz Wheel Left Button Horiz Wheel Right Button Side Button Extra Button Unknown Button Unknown Button Unknown Button Unknown Button state: Class originated from: 11 Keycodes supported: 248 Class originated from: 11 Detail for Valuator 0: Label: Abs X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 1: Label: Abs Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 2: Label: Abs Gas Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 3: Label: Abs Brake Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 11 Detail for Valuator 4: Label: Abs Misc Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative If that's not it then the problem may not be recorded in the trace. Not sure how to debug then. Cheers, Julien Hi Julien Just some additional information the mouse, keyboard is a microsoft wireless desktop and connected via a bluetooth usb dongle. Also it is connected via a kvm, I am pretty sure I havent switched mid trace, but I wonder if its worth trying to reproduce this without the kvm in the way. Ben -- 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/4c2ba108.9010...@whyall-systems.co.uk
Bug#568886: Regression: Hsync/Vrefresh incorrectly detected
On Sun, Mar 14, 2010 at 4:24 AM, Brice Goglin brice.gog...@ens-lyon.org wrote: Can you try upgrading xserver-xorg-video-radeon to 6.12.5 in unstable or even 6.12.191 in experimental with a recent kernel and KMS ? Retested. The bug still exists in xserver-xorg-video-radeon 6.12.6 (latest in testing) and 6.13.0 (in unstable). I enabled KMS for 6.13.0 and it did not help. --Ben -- 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/l2g47e8c68d1004180855w29d641dai41c9c501ab3a7...@mail.gmail.com
Bug#576393: qemu-kvm provokes segfault in X server
On Sun, 2010-04-04 at 10:05 +0200, Julien Cristau wrote:
any chance you can get a backtrace from gdb (with xserver-xorg-core-dbg
installed)?
Here's a backtrace and local variables for each frame.
Ben.
(gdb) bt
#0 0x080b4eec in DGAProcessPointerEvent (pScreen=value optimized out,
event=0xa336400, mouse=0xa332418)
at ../../../../hw/xfree86/common/xf86DGA.c:1097
#1 0x0809fd29 in mieqProcessDeviceEvent (dev=0xa332418, event=0xa336400,
screen=0x8b15368) at ../../mi/mieq.c:404
#2 0x0809feac in mieqProcessInputEvents () at ../../mi/mieq.c:471
#3 0x080b1437 in ProcessInputEvents ()
at ../../../../hw/xfree86/common/xf86Events.c:165
#4 0x08074040 in Dispatch () at ../../dix/dispatch.c:407
#5 0x0806693a in main (argc=9, argv=0xffc31114, envp=0xffc3113c)
at ../../dix/main.c:285
(gdb) info locals
butc = 0xa3328a0
ev = {header = 255 '\377', type = ET_Motion, length = 408, time = 0,
deviceid = 0, sourceid = 0, detail = {button = 0, key = 0}, root_x = 0,
root_x_frac = 0, root_y = 0, root_y_frac = 0,
buttons = '\000' repeats 31 times, valuators = {mask = \000\000\000\000,
mode = \000\000\000\000, data = {0 repeats 36 times}, data_frac = {
0 repeats 36 times}}, mods = {base = 0, latched = 0, locked = 0,
effective = 0}, group = {base = 0 '\000', latched = 0 '\000',
locked = 0 '\000', effective = 0 '\000'}, root = 0, corestate = 0,
key_repeat = 0}
(gdb) up
#1 0x0809fd29 in mieqProcessDeviceEvent (dev=0xa332418, event=0xa336400,
screen=0x8b15368) at ../../mi/mieq.c:404
404 ../../mi/mieq.c: No such file or directory.
in ../../mi/mieq.c
(gdb) info locals
screenNum = value optimized out
handler = 0x80b5050 DGAHandleEvent
master = value optimized out
mevent = {any = {header = 192 '\300', type = 0, length = 0, time = 0},
device_event = {header = 192 '\300', type = 0, length = 0, time = 0,
deviceid = -3995384, sourceid = -3995540, detail = {button = 4290971752,
key = 4290971752}, root_x = 36423, root_x_frac = 1.06619174e-33,
root_y = 10100, root_y_frac = 1.06620166e-33,
buttons =
\340\021\v\b4'\261\b\001\000\000\000\310\261\b\000|E\n\000\000\000\000\210\326=\367\000\000\000,
valuators = {
mask = \001\216r, incomplete sequence \367, mode = |E\n|\003,
data = {1024, 0 repeats 33 times, 145827636, 167522360}, data_frac = {
135587579, 32, 32, -144928780, -3993944, -143223808, 29, 99, 0, 43,
43, -144928780, 32, -3993944, -3993980, 32, 1, -3993800, 32, 0, 0,
-143223760, 35, 2110102, -3993980, 43, -3994604, 0, 0, -147770984,
172098632, 172099432, -3995160, -147910644, 172098632, 172099432}},
mods = {base = 330, latched = 18, locked = 1, effective = 4290972176},
group = {base = 0 '\000', latched = 0 '\000', locked = 0 '\000',
effective = 0 '\000'}, root = 4151408674, corestate = 171500120,
key_repeat = 1}, changed_event = {header = 192 '\300', type = 0,
length = 0, time = 0, deviceid = -3995384, flags = -3995540,
masterid = -3995544, sourceid = -143487417, buttons = {
num_buttons = 145827528, names = {145827700, 145827636, 134943200,
145827636, 1, 145827528, 172325888, 0, 4148024968, 0, 4151479809,
172325888, 892, 1024, 0 repeats 33 times, 145827636, 167522360,
135587579, 32, 32, 4150038516, 4290973352, 4151743488, 29, 99, 0, 43,
43, 4150038516, 32, 4290973352, 4290973316, 32, 1, 4290973496, 32, 0,
0, 4151743536, 35, 2110102, 4290973316, 43, 4290972692, 0, 0,
4147196312, 172098632, 172099432, 4290972136, 4147056652, 172098632,
172099432, 330, 18, 1, 4290972176, 0, 4151408674, 171500120, 1,
171569982, 0, 4290973196, 4290972176, 4147031323, 136180172, 4,
4290972176, 4290973224, 0, 7845976, 2160918528, 330, 18, 1,
4290972176, 4294902655, 4294902048, 4294967295, 136004405, 16, 0, 43,
0, 0, 0, 0, 0, 0, 2147483648, 49167, 0, 1073709056, 0, 3355443200,
16387, 0, 0, 0, 2356019200, 49166, 0, 3222178926, 288, 18875263, 0,
136004405, 0, 0, 0, 8064, 65535, 0, 0, 0, 0, 0, 0, 7845976,
2160918528, 0, 2147483648, 4294902655, 4294902048, 4294967295,
136004405, 16, 0, 43, 0, 0, 0, 0, 0, 0, 2147483648, 49167, 0,
1073709056, 0, 3355443200, 16387, 0, 0, 0, 2356019200, 49166, 0,
3222178926, 288, 18875263, 0, 136004405, 0, 0, 0, 8064, 65535, 0, 0,
0, 0, 0, 0, 0, 0, 0, 2147483648, 49167, 0, 0, 2147483648, 16383, 0, 0,
3355443200, 16387, 0, 0, 0, 0, 0, 0, 2356019200, 49166, 0, 0,
2356019200, 49166, 0...}}, num_valuators = 0, valuators = {{min = 0,
max = 0, resolution = 135579312, mode = 0 '\000', name = 0}, {
min = 136265120, max = 0, resolution = 0, mode = 0 '\000', name = 0}, {
min = 0, max = 0, resolution = 0, mode = 0 '\000', name = 0}, {
min = 0, max = 0, resolution = 0, mode = 0 '\000', name = 0}, {
min = 0, max = 0, resolution = 0, mode = 0 '\000
Bug#576393: qemu-kvm provokes segfault in X server
Package: xserver-xorg Version: 1:7.5+5 Severity: important I've been exercising graphics in qemu-kvm a bit more and have seen the host's X server crash a couple of times. I expect I can reproduce it again if you want me to gather more information. The backtrace from Xorg.0.log.old is: Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ad72b] 1: /usr/bin/X (0x8048000+0x5a8a5) [0x80a28a5] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xf7770410] 3: /usr/bin/X (mieqProcessDeviceEvent+0xb9) [0x809fd29] 4: /usr/bin/X (mieqProcessInputEvents+0x6c) [0x809feac] 5: /usr/bin/X (ProcessInputEvents+0x17) [0x80b1437] 6: /usr/bin/X (0x8048000+0x2be40) [0x8073e40] 7: /usr/bin/X (0x8048000+0x1e93a) [0x806693a] 8: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe5) [0xf74a3b55] 9: /usr/bin/X (0x8048000+0x1e521) [0x8066521] Segmentation fault at address 0x64 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Ben. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Mar 18 2009 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1712764 Mar 23 22:13 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 2802 Feb 13 16:40 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDevicenipple CorePointer InputDevicetouchpad CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/lib/xorg/modules FontPath /usr/share/fonts/X11/misc FontPath /usr/share/fonts/X11/cyrillic FontPath /usr/share/fonts/X11/100dpi/:unscaled FontPath /usr/share/fonts/X11/75dpi/:unscaled FontPath /usr/share/fonts/X11/Type1 FontPath /usr/share/fonts/X11/100dpi FontPath /usr/share/fonts/X11/75dpi FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath built-ins EndSection Section Module Load glx Load record Load dri Load extmod Load dbe Load dri2 EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier nipple Driver mouse Option Protocol auto Option Device /dev/input/mouse0 Option ZAxisMapping 4 5 6 7 EndSection Section InputDevice Identifier touchpad Driver synaptics Option Protocol events Option Device /dev/input/mouse1 Option SHMConfig on EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option NoAccel # [bool] #Option SWcursor # [bool] #Option ColorKey # i #Option CacheLines# i #Option Dac6Bit # [bool] #Option DRI # [bool] #Option NoDDC # [bool] #Option ShowCache # [bool] #Option XvMCSurfaces # i #Option PageFlip # [bool] Identifier Card0 Driver intel VendorName Intel Corporation BoardName Mobile GM965/GL960 Integrated Graphics Controller BusID PCI:0:2:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 49555 Dec 28 15:56 /var/log/Xorg.20.log -rw-r--r-- 1 root root 4543 Feb 13 16:35 /var/log/Xorg.1.log -rw-r--r-- 1 root root 31032 Apr 4 05:40
Re: Packagaing nouveau firmware
On Mon, 2010-03-29 at 07:23 +0200, Sven Joachim wrote: On 2010-03-29 03:36 +0200, Ben Hutchings wrote: On Fri, 2010-03-26 at 18:43 +0100, Sven Joachim wrote: Followed by the text of the actual license. Since Nvidia does not distribute the files themselves and their license only allows redistribution of unmodified files, it seems that if the files are copyrightable they are also undistributable, but I'm no legal expert. I think this is legally risky and ftpmaster will probably not allow it. Yeah. I'll mention this problem in xserver-xorg-video-nouveau's README.Debian and include a script to download and install the firmware. I don't think you need to mention it. An alternative to the nouveau-firmware package would be to backport Marcin Kościelnicki's ctxprogs generator that is included in 2.6.34. It generates the GPU initialization data on the fly, so no firmware is needed. Right, I think we may have to do that. Actually, that generator is only for NV50 cards (for NV40 cards there is already a generator in 2.6.33), which is what I have here. I don't know if there are any other supported cards which still need external firmware. After this change, external firmware/ctxprogs are optional for all cards (it will only be used if you set module parameter nouveau_ctxfw=1). Commit d5f3c90d4f3ad6b054f9855b7b69137b97bda131 is what you would need to cherry-pick. I applied this to the 2.6.33.1 kernel, and the result seems to work fine (I'm using it right now). This also gets rid of any MODULE_FIRMWARE stuff, making it possible to include nouveau.ko in the intitramfs without hitting #575241. :-) I have cherry-picked that and a couple of following bug fixes. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Packagaing nouveau firmware
On Fri, 2010-03-26 at 18:43 +0100, Sven Joachim wrote: On 2010-03-26 16:26 +0100, Ben Hutchings wrote: On Fri, 2010-03-26 at 10:51 +0100, Sven Joachim wrote: Thanks for the explanation. Speaking of the firmware, is anyone working on packaging it? Ubuntu has a package¹ in multiverse which works fine for me and could be used as a base, although it should probably named firmware-nouveau for consistency. [...] I'll have a look at that. I heard there were some concerns about licencing a while back, as they were apparently large blobs extracted from the Nvidia drivers and might be copyrightable. They are not that large compared to the whole Nvidia driver (biggest file is 33K), but they might be copyrightable. The debian/copyright file of the Ubuntu package says: These files are firmware-like programs for initialising GPU context-switching. They were extracted from memory-mapped IO traces of the nvidia binary driver initialising the hardware. They were not generated by reverse-engineering the source code of the binary driver. . It is unclear to me whether these files are actually copyrightable. It seems that these programs are likely to be generated by the driver at runtime rather than being hand-written. The nouveau driver takes this approach for nv4x cards. If they are copyrightable, they should fall under the nvidia binary driver's licence, below. Followed by the text of the actual license. Since Nvidia does not distribute the files themselves and their license only allows redistribution of unmodified files, it seems that if the files are copyrightable they are also undistributable, but I'm no legal expert. I think this is legally risky and ftpmaster will probably not allow it. Do you know what happened about that? The latest thing I could find is a thread on the ubuntu-x list in February, starting at https://lists.ubuntu.com/archives/ubuntu-x/2010-February/000773.html. I don't know if any progress has been made since then. An alternative to the nouveau-firmware package would be to backport Marcin Kościelnicki's ctxprogs generator that is included in 2.6.34. It generates the GPU initialization data on the fly, so no firmware is needed. Right, I think we may have to do that. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Bug#572067: linux-libc-dev: Can not install, file conflict with libdrm
On Fri, 2010-03-05 at 10:59 +0100, Julien Cristau wrote: On Fri, Mar 5, 2010 at 04:03:15 +, Ben Hutchings wrote: On Mon, 2010-03-01 at 13:50 +0100, Jens-Michael Hoffmann wrote: Package: linux-libc-dev Version: 2.6.33-1~experimental.2 Severity: normal When trying to install linux-libc-dev from experimental, dpkg shows the following error message: dpkg: error processing /var/cache/apt/archives/linux-libc-dev_2.6.33-1~experimental.2_amd64.deb (--unpack): trying to overwrite '/usr/include/drm/nouveau_drm.h', which is also in package libdrm-dev 0:2.4.18-2 It makes no sense to have the DRM headers split between libdrm-dev and linux-libc-dev. I'm happy to have libdrm-dev provide them all. What do you want to do? I think we should go back to libdrm-dev installing the headers. I sent a patch to dri-devel a few days ago that makes libdrm install its headers in $(includedir)/libdrm so they don't conflict with the ones installed by the kernel, waiting for some feedback on that… I have committed changes to remove /usr/include/drm from linux-libc-dev. Please give libdrm-dev a versioned dependency on linux-libc-dev (= 2.6.32-10). Ben. -- Ben Hutchings I say we take off; nuke the site from orbit. It's the only way to be sure. signature.asc Description: This is a digitally signed message part
Bug#572067: Processed: reassign 572592 to linux-libc-dev, forcibly merging 572067 572592
On Fri, 2010-03-05 at 19:37 +0100, Bastian Blank wrote: reassign 572067 libdrm-dev thanks The linux kernel is source of the drm headers in the meantime. It *is*, but it shouldn't be. Let's fix this now. Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg signature.asc Description: This is a digitally signed message part
Re: Bug#572067: linux-libc-dev: Can not install, file conflict with libdrm
On Mon, 2010-03-01 at 13:50 +0100, Jens-Michael Hoffmann wrote: Package: linux-libc-dev Version: 2.6.33-1~experimental.2 Severity: normal When trying to install linux-libc-dev from experimental, dpkg shows the following error message: dpkg: error processing /var/cache/apt/archives/linux-libc-dev_2.6.33-1~experimental.2_amd64.deb (--unpack): trying to overwrite '/usr/include/drm/nouveau_drm.h', which is also in package libdrm-dev 0:2.4.18-2 It makes no sense to have the DRM headers split between libdrm-dev and linux-libc-dev. I'm happy to have libdrm-dev provide them all. What do you want to do? Ben. -- Ben Hutchings Q. Which is the greater problem in the world today, ignorance or apathy? A. I don't know and I couldn't care less. signature.asc Description: This is a digitally signed message part
Re: [ubuntu-x] Status of kernel X drivers
On Sun, 2010-02-21 at 23:20 +, Ben Hutchings wrote: [...] I think this is something we will also consider doing in Debian. A year from now I expect nv to be dead and radeon UMS to be removed upstream, making it impractical to backport new hardware support. Given that, the maintenance burden for 2.6.33 drm should be lower. But this is really outside my area of expertise and certainly not my decision to make. I understand that the X maintainers would be happy with this. Do I hear any objections from the kernel team? We should probably also consider what this means for drm on the 2.6.32-stable branch. Should the drm developers still send patches there as well, where applicable? If all the distributions using 2.6.32 use the backported drm, should we ask Greg K-H to pull that? This is yet to be considered. Ben. -- Ben Hutchings Horngren's Observation: Among economists, the real world is often a special case. signature.asc Description: This is a digitally signed message part
Re: [ubuntu-x] Status of kernel X drivers
On Thu, 2010-02-18 at 14:40 -0800, Bryce Harrington wrote: [...] From apw's Kernel Summary, about why we are going with 2.6.32: The primary decision for the kernel team at UDS is to choose the base kernel version for the release. For Lucid this will be 2.6.32. This version has just released providing the maximum stabalisation time, it also is expected to be the kernel of choice for long term releases from other distributions.[1] If other distros are pulling the 2.6.33 drm on top of their 2.6.32 for their long term releases as sounds like is the case[2], then this would be a fairly significant divergence on our part for no real gain. [...] 2: http://cvs.fedoraproject.org/viewvc/rpms/kernel/F-12/drm-upgrayedd.patch?view=log Fedora has been backporting drm (and nouveau) for a long time but it's not so clear what means for RHEL. I think this is something we will also consider doing in Debian. A year from now I expect nv to be dead and radeon UMS to be removed upstream, making it impractical to backport new hardware support. Given that, the maintenance burden for 2.6.33 drm should be lower. But this is really outside my area of expertise and certainly not my decision to make. We should probably also consider what this means for drm on the 2.6.32-stable branch. Should the drm developers still send patches there as well, where applicable? If all the distributions using 2.6.32 use the backported drm, should we ask Greg K-H to pull that? Ben. -- Ben Hutchings 73.46% of all statistics are made up. signature.asc Description: This is a digitally signed message part
Bug#568309: starts but displays blank screen responds to ctrl alt f1
Package: xserver-xorg-video-radeon Version: 1:6.12.99+git20100201.a887818f-1 Severity: normal Hi this problem got worse after following your instructions, I know get the background for KDM but nothing more. The X log seems to suggest that the server is in an infinite loop. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Jan 28 21:47 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1710344 Jan 20 23:01 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc RV670PRO [Radeon HD 3850] /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1163 Feb 4 09:05 /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 InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout gb EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier Configured Video Device Driver radeon EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor SubSection Display Depth 24 Virtual 3200 1080 EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 37284 Feb 4 09:15 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.4 Release Date: 2010-01-08 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-trunk-686 i686 Debian Current Operating System: Linux Thor 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 root=/dev/mapper/thor-root ro quiet Build Date: 20 January 2010 10:52:55PM xorg-server 2:1.7.4-2 (bgog...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Feb 4 09:13:11 2010 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device Configured Video Device (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81e7680 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 1002:9505:1002:9505 ATI Technologies Inc RV670PRO [Radeon HD 3850] rev 0, Mem @ 0xe000/268435456, 0xf900/65536, I/O @ 0x8000/256, BIOS @ 0x/131072 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.4, module version = 1.0.0 Module class:
Bug#568309: starts but displays blank screen responds to ctrl alt f1
I dont think that will work as the card is an AGP card. Ben On 04/02/10 11:30, Michel Dänzer wrote: On Thu, 2010-02-04 at 09:21 +, Ben Whyte wrote: Package: xserver-xorg-video-radeon Version: 1:6.12.99+git20100201.a887818f-1 Severity: normal Hi this problem got worse after following your instructions, I know get the background for KDM but nothing more. The X log seems to suggest that the server is in an infinite loop. Do things work better with AGP disabled? To disable it, with KMS pass radeon.agpmode=-1 on the kernel command line. Without KMS, specify Option BusType PCIE in xorg.conf. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568309: starts but displays blank screen responds to ctrl alt f1
Package: xserver-xorg-video-radeon Severity: normal Tried both of these settings at the same time and it caused to things to happen, I loose video from shortly after grub until the xserver starts. I get a distorted kdm background mouse moves around but no keyboard response including ctrl alt del to restart x server. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Jan 28 21:47 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1710344 Jan 20 23:01 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc RV670PRO [Radeon HD 3850] /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1218 Feb 4 22:17 /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 InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout gb EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier Configured Video Device Option UseFBDev true Option BusType PCIE Driver radeon EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor SubSection Display Depth 24 Virtual 3200 1080 EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 35578 Feb 4 22:21 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.4 Release Date: 2010-01-08 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-trunk-686 i686 Debian Current Operating System: Linux Thor 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 root=/dev/mapper/thor-root ro quiet radeon.agpmode=-1 Build Date: 20 January 2010 10:52:55PM xorg-server 2:1.7.4-2 (bgog...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Feb 4 22:21:35 2010 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device Configured Video Device (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81e7680 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 1002:9505:1002:9505 ATI Technologies Inc RV670PRO [Radeon HD 3850] rev 0, Mem @ 0xe000/268435456, 0xf900/65536, I/O @ 0x8000/256, BIOS @ 0x/131072 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II)
Re: A python2.6-minimal v2.6.4-4-i386 install/upgrade bug?
On 28-Jan-2010, Phillip Pi wrote: Matthias Klose and I believe there is a possible bug with python2.6-minimal v2.6.4-4-i386 install/upgrade. Please kindly see below for our discussion and logs, and let me know if I need to report it and how I can resovle this. Yes, I have reported the same bug in report #567745 URL:http://bugs.debian.org/567745. You can join that discussion to keep the information about this bug in one place. -- \ “I guess we were all guilty, in a way. We all shot him, we all | `\ skinned him, and we all got a complimentary bumper sticker that | _o__) said, ‘I helped skin Bob.’” —Jack Handey | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Re: loading kernel mode setting drivers
On Mon, 2010-01-25 at 00:56 +0100, Julien Cristau wrote: On Tue, Jan 12, 2010 at 01:34:45 +0100, Marco d'Itri wrote: On Jan 12, Julien Cristau jcris...@debian.org wrote: Marco, what do you think of switching to this, or at least using its fb part? I do not mind explicitly blacklisting each fb driver, but I would like to have a way to semi-automatically generate the list. Is there any? I suppose something like find /lib/modules/$(uname -r)/kernel/drivers/video -type f|while read mod; do echo blacklist $(basename $mod .ko); done could work (possibly excluding some generic and backlight drivers, if those should be autoloaded?). What about my suggestion of removing the MODULE_DEVICE_TABLE declarations from fb modules, so they do not appear in modules.pcimap etc? Did you see any problem with that? Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Re: loading kernel mode setting drivers
Julien Cristau wrote:
On Mon, Jan 25, 2010 at 00:27:48 +, Ben Hutchings wrote:
What about my suggestion of removing the MODULE_DEVICE_TABLE
declarations from fb modules, so they do not appear in modules.pcimap
etc? Did you see any problem with that?
Dropping those and udev's blacklist would be fine as far as I'm
concerned. Not sure what this means for people with custom kernel,
since they'd lose the blacklist too, but I don't care much either way.
I suppose we don't really want this level of coupling between udev and
the kernel. So I'm happy to recommend your recipe to Marco, but with a
restriction to PCI drivers:
find /lib/modules/$(uname -r)/kernel/drivers/video -type f | {
while read mod; do
/sbin/modinfo $mod | grep -q '^alias: *pci' \
echo blacklist $(basename $mod .ko)
done
}
Ben.
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.
signature.asc
Description: This is a digitally signed message part
Re: loading kernel mode setting drivers
On Thu, 2009-12-31 at 18:24 +, Julien Cristau wrote: [...] One possible way to fix this, I guess, would be to replace this blacklist entry with a list of blacklisted fb drivers, to allow i915 (and later radeon and nouveau) being loaded automatically on boot. Is this feasible? Are there other/better solutions? That sounds like it might be a problem to maintain. Would it be feasible for each X video driver to blacklist the conflicting fb driver(s), in the same way that KMS-capable X video drivers set module parameters to enable KMS? Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Re: Nouveau kernel driver
On Tue, 2010-01-05 at 22:15 +, Chris Lamb wrote: Ben Hutchings wrote: I'd like to pull nouveau from 2.6.33 into Debian's 2.6.32. I'm hoping this would allow for replacement of nv and its dodgy source with nouveau This sounds like a good idea, but I should probably point out that I don't think we will be able to replace nv in squeeze with nouveau. Why not? Does it not support all the same hardware as nv, or is it still too unstable? Would this this affect whether you want to spend time on it now? As you imply, we get this for free by waiting for .33, and I will have to get some -snapshot packages into testing anyway.. squeeze will be released with 2.6.32. The release of .33 will be too close to the freeze date. Ben. -- Ben Hutchings Horngren's Observation: Among economists, the real world is often a special case. signature.asc Description: This is a digitally signed message part
Nouveau kernel driver
I'd like to pull nouveau from 2.6.33 into Debian's 2.6.32. I'm hoping this would allow for replacement of nv and its dodgy source with nouveau (I realise nouveau has its own issues with non-free bits, but they're more easily separable). Does this sound like a good idea? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#383465: Replacement of xserver-xorg-video-nv
Is nouveau likely to be in good enough shape to replace nv for squeeze? Ben. -- Ben Hutchings If at first you don't succeed, you're doing about average. signature.asc Description: This is a digitally signed message part
Bug#469706: xserver-xorg-video-intel: Still occuring I have I915
Package: xserver-xorg-video-intel Version: 2:2.8.0-2 Severity: normal This is still occuring on my machine. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2009-08-12 20:54 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1689976 2009-08-06 17:55 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 0 2009-08-12 20:53 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Xorg X server log files on system: -rw-r--r-- 1 root root 22375 2009-08-14 22:32 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.6.3 Release Date: 2009-7-31 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30.4-dsa-ia32 i686 Debian Current Operating System: Linux Thor 2.6.30-1-686 #1 SMP Mon Aug 3 16:18:30 UTC 2009 i686 Build Date: 06 August 2009 04:49:57PM xorg-server 2:1.6.3-1+b1 (bui...@murphy.debian.org) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Aug 14 22:32:30 2009 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. (II) Loader magic: 0x6c0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on linux (++) using VT number 7 (--) PCI:*(0:0:2:0) 8086:2572:1458:2572 Intel Corporation 82865G Integrated Graphics Controller rev 2, Mem @ 0xf000/134217728, 0xfa00/524288, I/O @ 0xc000/8 (II) Open ACPI successful (/var/run/acpid.socket) (II) System resource ranges: [0] -1 0 0x - 0x (0x1) MX[B] [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x (0x1) IX[B] (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.6.3, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.6.3, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.6.3, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: record (II) Loading /usr/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor=X.Org Foundation compiled for 1.6.3, module version = 1.13.0 Module class: X.Org Server Extension ABI
Bug#541716: xterm: colorBDMode is dead
Package: xterm Version: 244-2 Severity: normal My bash prompt is set to %B(%?)%#%b , which should print some stuff in bold. Man pages, mutt, and other packages print some stuff in bold. The xterm resource colorBDMode when set to true tells xterm to print bold text in colour. But as of the last xterm update, bold text is printed in oh-so-sexy black-on-black when colorBDMode is on. My xterm xresources are: xterm*VT100*colorBDMode: on xterm*VT100*colorBD: red xterm.VT100*colorULMode: on xterm.VT100*underLine:off xterm*VT100*colorUL: magenta xterm.VT100.titeInhibit: true xterm.VT100*dynamicColors: on xterm*metaSendsEscape:true xterm*highlightSelection: true xterm*scrollBar:true xterm*saveLines:1500 xterm*reverseWrap: true xterm*visualBell: true xterm*scrollTtyOutput: False xterm*scrollKey:True xterm*foreground: white xterm*background: black xterm*cursorColor: red xterm*locale: true Disabling colorBDMode gives me standard bold, as it should. Thanks! -Ben -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (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 xterm depends on: ii libc6 2.9-24GNU C Library: Shared libraries ii libfontconfig1 2.6.0-4 generic font configuration library ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libncurses55.7+20090803-1+b1 shared libraries for terminal hand ii libx11-6 2:1.2.2-1 X11 client-side library ii libxaw72:1.0.6-1 X11 Athena Widget library ii libxft22.1.13-3 FreeType-based font drawing librar ii libxmu62:1.0.4-2 X11 miscellaneous utility library ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii xbitmaps 1.0.1-2 Base X bitmaps Versions of packages xterm recommends: ii x11-utils 7.4+1 X11 utilities ii xutils1:7.4+4X Window System utility programs m Versions of packages xterm suggests: pn xfonts-cyrillic none (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
Bug#541307: xserver-xorg: x locks requires reboot
Package: xserver-xorg Version: 1:7.4+3 Severity: important On entering X and using applications for a short period X locks up and the keyboard becomes unusable. The mouse continues to move but clicks are not responded too. The only solution is to log in remotely using ssh and reboot. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2009-08-12 20:54 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1689976 2009-08-06 17:55 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 0 2009-08-12 20:53 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Xorg X server log files on system: -rw-r--r-- 1 root root 22441 2009-08-13 08:54 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.6.3 Release Date: 2009-7-31 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30.4-dsa-ia32 i686 Debian Current Operating System: Linux Thor 2.6.30-1-686 #1 SMP Mon Aug 3 16:18:30 UTC 2009 i686 Build Date: 06 August 2009 04:49:57PM xorg-server 2:1.6.3-1+b1 (bui...@murphy.debian.org) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Aug 13 08:54:55 2009 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/Type1 does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. (II) Loader magic: 0x6c0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on linux (++) using VT number 7 (--) PCI:*(0:0:2:0) 8086:2572:1458:2572 Intel Corporation 82865G Integrated Graphics Controller rev 2, Mem @ 0xf000/134217728, 0xfa00/524288, I/O @ 0xc000/8 (II) Open ACPI successful (/var/run/acpid.socket) (II) System resource ranges: [0] -1 0 0x - 0x (0x1) MX[B] [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x (0x1) IX[B] (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.6.3, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.6.3, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.6.3, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading
Bug#541105: xorg: Xorg CPU useage 50%
Package: xorg Version: 1:7.4+3 Severity: important When starting up my xserver, xorg is using 505 of CPU whilst idling causes slow performance and responsiveness in system. I have an Intel i915 graphics card I believe. Thanks Ben -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xorg depends on: ii eterm [x-terminal-emulator] 0.9.5-2Enlightened Terminal Emulator ii konsole [x-terminal-emulator] 4:4.3.0-1 X terminal emulator for KDE 4 ii libgl1-mesa-dri 7.5-3 A free implementation of the OpenG ii libgl1-mesa-glx [libgl1] 7.5-3 A free implementation of the OpenG ii libglu1-mesa 7.5-3 The OpenGL utility library (GLU) ii x11-apps 7.4+2 X applications ii x11-session-utils 7.3+1 X session utilities ii x11-utils 7.4+1 X11 utilities ii x11-xfs-utils 7.4+1 X font server utilities ii x11-xkb-utils 7.4+3 X11 XKB utilities ii x11-xserver-utils 7.4+2 X server utilities ii xauth 1:1.0.3-2 X authentication utility ii xfonts-100dpi 1:1.0.0-4 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-4 75 dpi fonts for X ii xfonts-base 1:1.0.0-6 standard fonts for X ii xfonts-scalable 1:1.0.0-7 scalable fonts for X ii xfonts-utils 1:7.4+2X Window System font utility progr ii xinit 1.1.1-1X server initialisation tool ii xkb-data 1.6-1 X Keyboard Extension (XKB) configu ii xorg-docs-core1:1.4-5Core documentation for the X.org X ii xserver-xorg 1:7.4+3the X.Org X server xorg recommends no packages. Versions of packages xorg suggests: pn xorg-docs none (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
Bug#535061: /usr/bin/xfontsel: xfontesel reports no usuable fonts
Package: x11-utils Version: 7.4+1 Severity: important File: /usr/bin/xfontsel When running xfontsel I get xfontsel Warning: Unable to load any usable ISO8859 font Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Error: Aborting: no font found It also seems to be effecting Eterm which reports Eterm: Error: Unable to load font -misc-fixed-medium-r-semicondensed--13-*-*-*-c-*-iso10646-1. Falling back on k14 Eterm: FATAL: Couldn't load the fallback font either. Giving up. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.29-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages x11-utils depends on: ii cpp4:4.3.3-9 The GNU C preprocessor (cpp) ii libc6 2.9-18GNU C Library: Shared libraries ii libfontconfig1 2.6.0-4 generic font configuration library ii libfontenc11:1.0.4-3 X11 font encoding library ii libfreetype6 2.3.9-5 FreeType 2 font engine, shared lib ii libgl1-mesa-glx [libgl 7.4.4-1 A free implementation of the OpenG ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libsm6 2:1.1.0-2 X11 Session Management library ii libx11-6 2:1.2.1-1 X11 client-side library ii libxaw72:1.0.5-2 X11 Athena Widget library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft22.1.13-3 FreeType-based font drawing librar ii libxi6 2:1.2.1-2 X11 Input extension library ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxmu62:1.0.4-1 X11 miscellaneous utility library ii libxmuu1 2:1.0.4-1 X11 miscellaneous micro-utility li ii libxrender11:0.9.4-2 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension ii libxv1 2:1.0.4-1 X11 Video extension library ii libxxf86dga1 2:1.0.2-1 X11 Direct Graphics Access extensi ii libxxf86vm11:1.0.2-1 X11 XFree86 video mode extension l ii x11-common 1:7.4+3 X Window System (X.Org) infrastruc ii zlib1g 1:1.2.3.3.dfsg-14 compression library - runtime x11-utils recommends no packages. Versions of packages x11-utils suggests: ii mesa-utils7.4.4-1Miscellaneous Mesa GL utilities -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535061: /usr/bin/xfontsel: xfontesel reports no usuable fonts
When running xfontsel I get xfontsel Warning: Unable to load any usable ISO8859 font Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Error: Aborting: no font found It also seems to be effecting Eterm which reports Eterm: Error: Unable to load font -misc-fixed-medium-r-semicondensed--13-*-*-*-c-*-iso10646-1. Falling back on k14 Eterm: FATAL: Couldn't load the fallback font either. Giving up. What xfonts-* packages do you have installed? Cheers, Julien sudo dpkg -l xfonts* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++--- un xfonts-100dpinone (no description available) un xfonts-75dpi none (no description available) rc xfonts-base 1:1.0.0-6standard fonts for X un xfonts-cyrillic none (no description available) ii xfonts-encodings 1:1.0.2-3Encodings for X.Org fonts ii xfonts-mathml2Type1 Symbol font for MathML un xfonts-misc none (no description available) un xfonts-scalable none (no description available) ii xfonts-terminus 4.28-1 Fixed-width fonts for fast reading un xfonts-terminus-oblique none (no description available) ii xfonts-utils 1:7.4+1 X Window System font utility programs un xfontsel none (no description available) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
emerald window decorator for compiz
I'm wondering if someone wouldn't mind packaging the emerald compiz window decorator. From what I've been able to research, it's officially supported by the compiz team and kept in-sync with latest versions of compiz. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508126: xine-ui: ctrl/shift key press emulation implementation broken
On Sat, 2009-01-03 at 18:00 +0100, Julien Cristau wrote:
On Fri, Jan 2, 2009 at 15:30:01 +, Ben Hutchings wrote:
#508126: x11-utils: xprop -spy does not handle destruction properly
the xprop patch looks reasonable afaict, so go ahead and NMU. somebody
should also forward that patch to bugs.freedesktop.org.
Thanks, done. The NMU-diff follows.
Ben.
diff -Nru x11-utils-7.3+2/debian/changelog x11-utils-7.3+2+nmu1/debian/changelog
--- x11-utils-7.3+2/debian/changelog2008-05-30 15:21:43.0 +0100
+++ x11-utils-7.3+2+nmu1/debian/changelog 2009-01-03 22:22:41.0
+
@@ -1,3 +1,11 @@
+x11-utils (7.3+2+nmu1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Make xprop -spy exit cleanly when target window is destroyed
+(closes: #508126)
+
+ -- Ben Hutchings b...@decadent.org.uk Sat, 03 Jan 2009 22:22:40 +
+
x11-utils (7.3+2) unstable; urgency=low
* Relax Replaces on xutils and xbase-clients to allow further updates.
diff -Nru x11-utils-7.3+2/debian/patches/05_xprop_spy_exit_on_destroy.diff
x11-utils-7.3+2+nmu1/debian/patches/05_xprop_spy_exit_on_destroy.diff
--- x11-utils-7.3+2/debian/patches/05_xprop_spy_exit_on_destroy.diff
1970-01-01 01:00:00.0 +0100
+++ x11-utils-7.3+2+nmu1/debian/patches/05_xprop_spy_exit_on_destroy.diff
2009-01-03 22:21:48.0 +
@@ -0,0 +1,50 @@
+This patch by Ben Hutchings b...@decadent.org.uk.
+
+xprop -spy should exit cleanly when the target window is destroyed.
+The current behaviour is that it sometimes dies with a BadWindow error
+and sometimes hangs around after the target has been destroyed.
+
+We fix this by listening for destroy events but also catching
+BadWindow errors (and BadMatch, which may sometimes be received
+instead of BadWindow). We print a new-line before exiting from the
+error handler, since we may have generated partial output for a
+property change.
+
+--- x11-utils.orig/xprop/xprop.c
x11-utils/xprop/xprop.c
+@@ -1596,6 +1596,19 @@
+
+ static int spy = 0;
+
++static int (*old_error_handler)(Display *dpy, XErrorEvent *ev);
++
++static int spy_error_handler(Display *dpy, XErrorEvent *ev)
++{
++if (ev-error_code == BadWindow || ev-error_code == BadMatch) {
++ /* Window was destroyed */
++ puts();
++ exit(0);
++}
++
++return old_error_handler(dpy, ev);
++}
++
+ int
+ main (int argc, char **argv)
+ {
+@@ -1738,9 +1750,14 @@
+ XEvent event;
+ const char *format, *dformat;
+
+- XSelectInput(dpy, target_win, PropertyChangeMask);
++ XSelectInput(dpy, target_win, PropertyChangeMask | StructureNotifyMask);
++ old_error_handler = XSetErrorHandler(spy_error_handler);
+ for (;;) {
+ XNextEvent(dpy, event);
++ if (event.type == DestroyNotify)
++ break;
++ if (event.type != PropertyNotify)
++ continue;
+ format = dformat = NULL;
+ if (props) {
+ int i;
diff -Nru x11-utils-7.3+2/debian/patches/series
x11-utils-7.3+2+nmu1/debian/patches/series
--- x11-utils-7.3+2/debian/patches/series 2008-02-01 00:21:49.0
+
+++ x11-utils-7.3+2+nmu1/debian/patches/series 2009-01-03 22:22:05.0
+
@@ -1,2 +1,3 @@
02_xev_flush_standard_output.diff
04_xlsfonts_do_not_spew_usage_on_connection_error.diff -p0
+05_xprop_spy_exit_on_destroy.diff
--- END ---
--
Ben Hutchings
The world is coming to an end. Please log off.
signature.asc
Description: This is a digitally signed message part
Bug#508126: xine-ui: ctrl/shift key press emulation implementation broken
I need some guidance on how to deal with the following related bugs: #374644: xine-ui: ctrl/shift key press emulation implementation broken #506001: xine-ui: xine causes left ctrl keyup events every 20 seconds These are the same bug: xine-ui suppresses screensavers by injecting fake keystrokes, which may be received by other windows. It also suppresses gnome-screensaver cleanly, so we could disable the key injection code without affecting GNOME users. However, this would be a regression for users of the X server screensaver, xscreensaver or the KDE screensaver. My proposed fix involves using xdg-screensaver, which supports all the different screensavers. However, this suffers from the following bugs: #508125: xdg-screensaver: Race in suspend/resume can lead to process leak #508126: x11-utils: xprop -spy does not handle destruction properly I do not think that these are, in themselves, RC. I have now proposed fixes for all of these, and the result appears to be robust. Should I NMU with these fixes? Should any of these bugs be down/upgraded? Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Bug#463373: xkb-data: Patch resolving the issue
Package: xkb-data Version: 1.4-1 Followup-For: Bug #463373 Yes, that patch also resolves the issue. -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508126: x11-utils: xprop -spy does not handle destruction properly
This patch seems to do the job. Firstly we listen for destroy events.
However, since window destruction is asynchronous with other clients, we
may receive a BadWindow (or BadMatch, due to id reuse) error while
reporting a property change. So secondly we catch these errors.
Possibly we should print a new-line before exiting in this case, since
the error received when we have generated partial output for a property
change.
Ben.
diff -Nru x11-utils.orig/xprop/xprop.c x11-utils/xprop/xprop.c
--- x11-utils.orig/xprop/xprop.c
+++ x11-utils/xprop/xprop.c
@@ -1596,6 +1596,18 @@
static int spy = 0;
+static int (*old_error_handler)(Display *dpy, XErrorEvent *ev);
+
+static int spy_error_handler(Display *dpy, XErrorEvent *ev)
+{
+if (ev-error_code == BadWindow || ev-error_code == BadMatch) {
+ /* Window was destroyed */
+ exit(0);
+}
+
+return old_error_handler(dpy, ev);
+}
+
int
main (int argc, char **argv)
{
@@ -1738,9 +1750,14 @@
XEvent event;
const char *format, *dformat;
- XSelectInput(dpy, target_win, PropertyChangeMask);
+ XSelectInput(dpy, target_win, PropertyChangeMask | StructureNotifyMask);
+ old_error_handler = XSetErrorHandler(spy_error_handler);
for (;;) {
XNextEvent(dpy, event);
+ if (event.type == DestroyNotify)
+ break;
+ if (event.type != PropertyNotify)
+ continue;
format = dformat = NULL;
if (props) {
int i;
--- END ---
--
Ben Hutchings
All the simple programs have been written, and all the good names taken.
signature.asc
Description: This is a digitally signed message part
Bug#508126: x11-utils: xprop -spy does not handle destruction properly
Package: x11-utils Version: 7.3+2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I would expect xprop -spy to exit cleanly when the target window is destroyed. The actual behaviour is that it sometimes dies with a BadWindow error and sometimes hangs around after the target has been destroyed. This causes problems for xdg-screensaver, which relies on it to exit when the target is destroyed. Ben. - -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages x11-utils depends on: ii cpp4:4.3.2-2 The GNU C preprocessor (cpp) ii libc6 2.7-16GNU C Library: Shared libraries ii libfontconfig1 2.6.0-3 generic font configuration library ii libfontenc11:1.0.4-3 X11 font encoding library ii libfreetype6 2.3.7-2 FreeType 2 font engine, shared lib ii libgl1-mesa-glx [libgl 7.0.3-6 A free implementation of the OpenG ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libsm6 2:1.0.3-2 X11 Session Management library ii libx11-6 2:1.1.5-2 X11 client-side library ii libxaw72:1.0.4-2 X11 Athena Widget library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft22.1.12-3 FreeType-based font drawing librar ii libxi6 2:1.1.4-1 X11 Input extension library ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxmu62:1.0.4-1 X11 miscellaneous utility library ii libxmuu1 2:1.0.4-1 X11 miscellaneous micro-utility li ii libxrender11:0.9.4-2 X Rendering Extension client libra ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension ii libxv1 2:1.0.4-1 X11 Video extension library ii libxxf86dga1 2:1.0.2-1 X11 Direct Graphics Access extensi ii libxxf86vm11:1.0.2-1 X11 XFree86 video mode extension l ii x11-common 1:7.3+18 X Window System (X.Org) infrastruc ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime x11-utils recommends no packages. Versions of packages x11-utils suggests: ii mesa-utils7.0.3-6Miscellaneous Mesa GL utilities - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJPKu079ZNCRIGYgcRArrAAJ9+Q/XMiifbNJ+faDU1ir0IEa0yFwCfeUI+ jdkCoYzWKur9YQ/M5Zw+F5Q= =v+q5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502675: closed by Julien Cristau [EMAIL PROTECTED] (Bug#502675: fixed in libdrm 2.3.1-2)
Julien Cristau [EMAIL PROTECTED] wrote: libdrm (2.3.1-2) unstable; urgency=high . * Remove from the source package a bunch of files that are only used by the kernel drm component. This gets rid of the mga, r128 and radeon microcode, and thus closes: #502675. Thanks, Ben Hutchings! Shouldn't this be removed from the orig tarball? I don't see any point in patching it out. Ben. signature.asc Description: This is a digitally signed message part
Bug#502675: libdrm: Binary firmware in driver source
Package: libdrm Version: 2.3.1-1 Severity: serious Justification: Policy 2.2.1 The libdrm source package includes the DRM drivers mga, r128, radeon which include sourceless firmware images. These could all be removed from the source package since the drivers are built as part of linux-2.6. Ben. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491979: [Fwd: Re: Bug#490601: fails with many xio errors when started from xdm]
Forwarded Message From: Ben Hutchings [EMAIL PROTECTED] To: Tuomo Valkonen [EMAIL PROTECTED] Cc: Ion general [EMAIL PROTECTED] Subject: Re: Bug#490601: fails with many xio errors when started from xdm Date: Mon, 21 Jul 2008 01:00:41 +0100 I got a report of a weird and unreproducible error in Ion3 startup: http://bugs.debian.org/490601 BadMatch is not a documented error code for XGetWindowProperty which sends X_GetProperty requests. However, the implementation in Xorg appears to return BadMatch if and only if it's passed a reference to a drawable that isn't a window: http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=blob;hb=8822110d7d6b684f373fc883aeb7cab9734e9ddb;f=dix/dixutils.c#l197 I don't understand how the server coordinates window changes with the WM. Is it possible that a window can be completely deleted before the WM has handled it? In that case there is presumably a race condition where a window could disppear and another drawable be created with the same id. This seems like a bug in Xorg, but we presumably need to work around it. The obvious patch is below. Ben. --- ion3.orig/ioncore/rootwin.c +++ ion3/ioncore/rootwin.c @@ -58,10 +58,11 @@ static char msg[128], request[64], num[32]; /* Just ignore bad window and similar errors; makes the rest of - * the code simpler. + * the code simpler. Due to a Xorg bug, window lookups may fail + * with BadMatch instead of BadWindow. */ if((ev-error_code==BadWindow || -(ev-error_code==BadMatch ev-request_code==X_SetInputFocus) || +ev-error_code==BadMatch || (ev-error_code==BadDrawable ev-request_code==X_GetGeometry)) ignore_badwindow) return 0; --- END --- -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette' signature.asc Description: This is a digitally signed message part
