Bug#583514: xserver-xorg-core: Resetting gdm puts Xorg at 100% CPU
Le 28/05/2010 00:59, Craig Small a écrit : Package: xserver-xorg-core Version: 2:1.7.7-1 Severity: grave Justification: renders package unusable If I reboot my computer, the gdm login screen comes up eventually. I can login to gdm and all the usual X things work fine. If I logout of gdm, it starts off ok, I get a flicker of the f1 screen then it all goes bad from there: * The screen goes blank * The numlock light on the keyboard goes out * The keyboard does not work, not even caps lock works, or ctrl-alt-f1 * Xorg goes to 99% cpu Restarting gdm just keeps the Xorg running, killing (only with SIGKILL works) just restarts another Xorg that goes to 99. Stopping gdm, then kill -9 Xorg stops it. Starting gdm again only makes another Xorg process that goes to 99%. The only way I think I can fix this is to reboot the computer, which is a bit drastic to just logout of gdm. It looks like a Xorg problem rather than gdm, as gdm just starts Xorg. - Craig -- 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 Dec 21 22:08 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1877152 May 5 02:26 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:05.0 VGA compatible controller: ATI Technologies Inc RS880 [Radeon HD 4200] /etc/X11/xorg.conf does not exist. Kernel version (/proc/version): Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010 First, you might want to use linux-image-2.6.32-5-amd64 Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582482: Dist-upgrade leads to compiz not starting
bts severity 582482 important thank you On 21/05/2010 08:45, Brent Clark wrote: Package: compiz Version: 0.8.4-4 Severity: critical Tags: squeeze sid Justification: breaks unrelated software Seriously, no. A computer works perfectly fine without compiz. It even works fine without X... #:/$ LIBGL_DEBUG=verbose compiz --replace --debug compiz (core) - Debug: Could not stat() file /home/bclark/.compiz/plugins/libcore.so : No such file or directory compiz (core) - Debug: Could not stat() file /usr/lib/compiz/libcore.so : No such file or directory libGL: OpenDriver: trying /usr/lib/dri/tls/i915_dri.so libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /home/bclark/.drirc: No such file or directory. compiz (core) - Debug: Could not stat() file /home/bclark/.compiz/plugins/libccp.so : No such file or directory Backend : ini Integration : true Profile : default Adding plugins Initializing core options...done compiz (core) - Debug: Could not stat() file /home/bclark/.compiz/plugins/libmove.so : No such file or directory Initializing move options...done compiz (core) - Debug: Could not stat() file /home/bclark/.compiz/plugins/libresize.so : No such file or directory Initializing resize options...done compiz (core) - Debug: Could not stat() file /home/bclark/.compiz/plugins/libplace.so : No such file or directory Initializing place options...done compiz (core) - Debug: Could not stat() file /home/bclark/.compiz/plugins/libdecoration.so : No such file or directory WARNING: Application calling GLX 1.3 function glXCreatePixmap when GLX 1.3 is not supported! This is an application bug! Initializing decoration options...done WARNING: Application calling GLX 1.3 function glXDestroyPixmap when GLX 1.3 is not supported! This is an application bug! Setting Update shadow_color compiz (core) - Debug: Could not stat() file /home/bclark/.compiz/plugins/libgconf.so : No such file or directory I am seeing the same messages and Compiz works fine. What did you upgrade when things broke? Did you recently switch to KMS/DRI2 for instance? Please send your Xorg.0.log. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575274: xserver-xorg-video-radeon: not ready for testing yet
Package: xserver-xorg-video-radeon Version: 1:6.12.192-2 Severity: serious Wait for the kernel to be ready in testing before migrating. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#574828: X freezing after upgrade in 1:7.5+5 with nv and nvidia drivers
pbi wrote: Package: xorg Version: 1:7.5+5 Severity: critical Tags: sid I have a Quadro NVS 440, (i.e. 2 GPU, 2 screens in twinview per GPU, and xinerama to unite both groups). Everything was working with nvidia proprietary driver. Now after the upgrade, the X server freezes the box with the nvidia driver. Upgrade from what ? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569430: Processed: found 569430 in 7.5+4
Debian Bug Tracking System wrote: found 569430 7.5+4 Please send the corresponding log. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-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
Ben Whyall wrote: An upgrade to the latest packages in unstable seems to have resolved my issue. Thanks for the help and assistance Which packages ? xserver-xorg-video-radeon 6.12.5 (uploaded today) ? which kernel are you running and which versino on this kernel package ? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572001: xserver-xorg-video-radeon: Display corruption with kernel 2.6.33
severity 572001 normal thank you Dietz Proepper wrote: Package: xserver-xorg-video-radeon Version: 1:6.12.99+git20100201.a887818f-1 Severity: grave Justification: renders package unusable Seriously ? No. It's not even a crash, which would only be important :) Under linux-2.6.33 with kms enabled I get serious display corruption as soon as I do opengl stuff, i.e. starting glxgears. After terminating glxgears, the corruption vanishes sometimes. The corruption looks like wrong timings looked way back as we had analogous displays, want to say, the picture seems to cycle through. With 2.6.32.7+kms everything works fine. I did not yet check, wether the same happens with .33 w/o kms. The machine is a Lenovo Z61m, mobile x1400 chipset. The xserver log below is not from 2.6.33, I can create one if needed. Why do you report against xserver-xorg-video-radeon if 2.6.33 seems to be the breaker here ? Which mesa do you have, by the way ? If OpenGL is enabled, you could compare Mesa 7.6.1 (in testing) and 7.7 (in unstable) in case you see a difference. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567756: xserver-xorg-input-all: keyboard not working after squeeze upgrade
David Wlazlo wrote: Hi, I think I just realised this bug may be closed. Is there any way of re-opening it or at least clarifying a solution for me please? The submitter of this bug said it was gone. If other people still have their own bug, then it may be a different problem and they need to open a different bug report. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570007: xkb-data: Keyboard doesn't work - Key events occur, but no Keysym is assigned
On Mon, Feb 15, 2010 at 08:59:08PM +0100, Paul M. wrote: Package: xkb-data Version: 1.7-2 Severity: grave Justification: renders package unusable After updating to xserver 1.7.5, the keyboard doesn't work, if I start the xserver (it doesn't matter which window manager). I get the following output if I start the xserver: www.inf.tu-dresden.de/~s5569359/xstart.log xev shows, that the key press events are recognized, but there is no keysym found e.g. a and Enter: www.inf.tu-dresden.de/~s5569359/c I tried several keymaps. Executing xmodmap -pk while a xsession gives a normal key table. xinitrc and xsession are empty. libx11-6 and all orther related packages are uptodate. Please send the output of /usr/share/bug/xserver-xorg/script 31 Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-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
On Thu, Feb 04, 2010 at 10:25:51PM +, Ben Whyte wrote: 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. [...] (EE) AIGLX error: Calling driver entry point failed (EE) AIGLX: reverting to software rendering (by the way) Do you have libgl1-mesa-dri installed ? [ 18.128886] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver [ 18.138542] fb1: radeondrmfb frame buffer device [ 18.138555] [drm] Initialized radeon 2.0.0 20080528 for :01:00.0 on minor 0 [ 46.093883] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id Assuming this is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/434190 you might want to load the fbcon kernel module. See this URL for details. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568309: xserver-xorg: starts but displays blank screen responds to ctrl alt f1
reassign 568309 xserver-xorg-video-radeon 1:6.12.4-3 thank you Ben Whyte wrote: Package: xserver-xorg Version: 1:7.5+3 Severity: grave Justification: renders package unusable My system fails to display the KDM boot manager but does respond to swapping to terminal. Using the VESA driver with the virtual directive removed I can get a login box but not suitable as it limits me to single screen and 1280x1024. Radeonhd, radeon or ati driver produce the same result. Can you try xserver-xorg-video-radeon from experimental ? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-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
Ben Whyte wrote: Section Device Identifier Configured Video Device Option UseFBDev true Why do you have FBDev here ? It's ignored according to the log. [ 795.019218] [drm] Setting GART location based on new memory map [ 795.019224] [drm] Can't use AGP base @0xf000, won't fit [ 795.019284] [drm] Loading RV670 CP Microcode [ 795.059544] [drm] Resetting GPU [ 795.186801] [drm] writeback test failed [ 807.512112] [drm] Resetting GPU [ 867.789081] [drm] Module unloaded This might be related to your problem. By the way, maybe you should try KMS, see http://bgoglin.livejournal.com/19346.html to enable it. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567563: Workarounds
Tarek Soliman wrote: This is caused by the fix to bug #555906 (enable KMS in the module) No, this is caused by KMS, not by the fix. Here's 2 different workarounds: 1 - enable KMS in the kernel What do you mean ? Set I915_KMS in the kernel config ? It shouldn't make any difference. Both enable KMS. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567756: xserver-xorg-input-all: keyboard not working after squeeze upgrade
Rick Thomas wrote: Package: xserver-xorg-input-all Version: 1:7.5+2 Severity: grave Justification: renders package unusable After upgrading my Squeeze system, my keyboard is non-responsive under X. By changing /etc/X11/default-display-manager from /usr/bin/gdm to /bin/false thus disabling gnome, I was able to use the console in text mode. So I'm assuming that it's not a hardware problem. I'm attaching /var/log/Xorg.0.log Please send the whole output of /usr/share/bug/xserver-xorg/script 31 Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564203: (no subject)
Alex Goebel wrote: Actually, the same (/very similar) problem appears when using the NVIDIA binary driver, directly after the 7.5+1 update. Reverting to testing fixes this. Unlikely that it's the nv driver only. Sorry. nv problems are well identified, and they are not even fixed in latest nv release, see http://lists.freedesktop.org/archives/xorg-announce/2009-December/001219.html nvidia binary problems are impossible to debug, and probably just related to their ugly binary compatibility glue layer not being updated to the new server ABI yet. So please don't mix unrelated issues. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562244: Xorg segfaults at startup
David Paleino wrote: Package: xserver-xorg-video-intel Version: 2:2.9.1-1 Severity: grave Hello, today I started my system, and Xorg segfaulted. Unfortunately I didn't notice this before, since I'm used to hibernate my system, and not fully shutdown it, but now it segfaulted from a clean boot. It does so both with sid and experimental versions, the log attached by the bugscripts is sid's, while the experimental one is located at: http://people.debian.org/~dapal/Xorg.0.log.experimental Please ask my any info you might need. Please install xserver-xorg-core-dbg and xserver-xorg-video-intel-dbg and catch a debugging backtrace with gdb. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562244: Xorg segfaults at startup
David Paleino wrote: On Thursday 24 December 2009 09:23:40, David Paleino wrote: Section Device Identifier Configured Video Device EndSection Adding: Driver vesa to the Device section makes X start, so it's definitely a bug in the intel driver. vesa and intel do not use the same features in the server. So it could just be a bug a some modern feature in the server that vesa doesn't care about. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560815: xserver-xorg-input-evdev: automatic discovery of input devices broken
tags 560815 +pending thank you Micha Feigin wrote: Package: xserver-xorg-input-evdev Version: 1:2.3.1-1 Severity: grave Justification: renders package unusable the xserver stopped automatically detecting input devices. On my laptop for some reason touchpad still works but keyboard, external keyboard and external mice don't work. This makes X unusable. setting OptionAllowEmptyInput false Allows defining these manually which allows bypassing the problem for now but this shouldn't be needed with new X There are several reasons for this: * latest xserver-xorg-core experimental packages are not built for amd64 yet * evdev needs http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-input-evdev.git;a=commitdiff;h=3eddc02011d7805d8f959b6ca626df33d1f6a90b;hp=7656675298b512645a06a34a7994dfbde9796ae4 Once we upload all Xorg 7.5 packages to unstable, it should work fine. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560126: xserver-xorg-video-radeon: Launching GL Apps Corrupts System
Leo L. Schwab wrote: Package: xserver-xorg-video-radeon Version: 1:6.12.3-1 Severity: critical Justification: breaks the whole system After launching virtually any GL screensaver, the system appears to become corrupted beyond usability. After exiting the screensaver, any one of several system-wide errors manifest themselves, preventing the launch of any new program (including programs to shut the system down). The only way to regain control of the system is a hard reboot. Among the errors observed so far: - Errors reporting system libraries are corrupt. - Errors reporting the requested program isn't a valid binary image. - Errors reporting a corrupt filesystem. - Running daemons, which were running fine before, suddenly reporting segfaults. This strongly suggests the graphics (or related) driver is clobbering random system memory. I've upgraded to the 'unstable' mesa libraries, and to the 2.6.32-rc8 kernel. Same problems. You may try upgrading to experimental now... I realize this report is terribly vague -- I haven't been able to more concretely characterize the problem. To reproduce on this system (at least, how I've been doing it): - Launch X, any window server/desktop environment. - Open a terminal. - Issue the command: xscreensaver-command -activate. Iterate until you get a GL screensaver. - Allow the screensaver to run for a few seconds, then press a key to exit back to the desktop. You should be unable to run any new program. More specifically, you should be unable to run any program that isn't cached. (Example: After exiting the screensaver, you can (probably) run 'xscreensaver-command' again, but attempts to run 'ls' or any other utility will likely fail.) I can't reproduce this on my Radeon X300 (rv370). When did this problem start? What did you upgrade when it started? Since nobody else has ever reported such a critical problem (while the radeon driver has many users), I suggest your check your installation (with debsums for instance) and maybe check your hardware as well (memtest, smartctl, is there some sort of memtest for video?). Something strange is going on here... Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552182: xorg: Impossible to load desktop (at least kde or xfce)
severity 552182 important thank you David wrote: Package: xorg Version: 1:7.4+4 Severity: critical Justification: breaks unrelated software Today I upgraded sid (i.e., from sid to sid) after having being about one month away from my computer. After rebooting, the boot process complaint that the root device was damaged, but fsck gave an error as well (maybe this has nothing to do with the bug, but just in case). After rebooting, things were apparently OK. But further problems: some application launched in KDE4, such as icedove or openoffice, could not write to my home directory or to /tmp (although my user had writing permissions), so such applications were useless (maybe this has nothing to do with the bug, but just in case). I tried rebooting and then everything broke. The login manager (kdm, then gdm) showed, I could make the log in, the screen went black for a second (as though the desktop were starting) but then back to the login manager (as though the initialization of the desktop had failed). The login was OK because I tried introducing a wrong password and the login manager complaint. I had the same problem with kdm and gdm, and when trying to start kde or xfce. I had the same problem both with the nvidia and nv drivers. I could successfully log in in a text terminal, by the way. I tried enquiring on the IRC chat, and although several unhappy people treated me as though I were stupid, they gave me the clue to see that the problem was in the X server. I am attaching Xorg.0.log. I am running reportbug after having started with an OpenSuse LiveCD and made chroot (so I am suppressing the information about the kernel, locales, etc, to prevent confusion). I am afraid I will not be able to provide further information, because I need the computer working so (unless you are so clever to fix the bug by my next working day :-) ) I will format. Please send the log of X when using the nv driver (we don't care about the nvidia binary) and please save it *after* a crash (likely /var/log/Xorg.0.log.old with a backtrace at the end). Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549898: hangs while setting up grub-pc
Package: grub-pc Version: 1.97~beta4-1 Severity: grave Justification: renders package unusable Installing grub-pc on my Dell PowerEdge 2950 hangs during postinst: Setting up grub-common (1.97~beta4-1) ... Installing new version of config file /etc/grub.d/30_os-prober ... Setting up grub-pc (1.97~beta4-1) ... (need ctrl-c) I tried with 1.97~beta3-1 and 1.97~beta4-1, same result. Two (similar) machines do this. I have 4 other older poweredge 2950 where grub-pc installs fine. Not sure what hardware difference could explain this, the software installation is pretty much the same. After trying to fix this a couple time and having to abort with ctrl-c, I see this in ps: 0 D root 14935 1 0 80 0 - 944 ? 07:26 ?00:00:00 grub-mkdevicemap --no-floppy 0 D root 15311 1 0 80 0 - 944 ? 07:33 ?00:00:00 grub-mkdevicemap --no-floppy 0 D root 15498 1 0 80 0 - 944 ? 07:58 ?00:00:00 grub-mkdevicemap --no-floppy 0 D root 15853 1 0 80 0 - 944 ? 07:58 ?00:00:00 grub-mkdevicemap --device-map=/tmp/device.map.pAT8GlfT --no-floppy 0 D root 15893 1 0 80 0 - 944 ? 08:01 ?00:00:00 grub-mkdevicemap --no-floppy So it looks like grub-mkdevicemap hangs here. These processes are not killable. I thought of rebooting the machine to cleanup these processes but I don't konw what the partial installation actually broke from my old grub1 install. device.map was left empty. I restored it. Which other files should I check before I can reboot? thanks, Brice -- Package-specific info: *** BEGIN /proc/mounts /dev/sda3 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/sda6 /mnt/scratch ext3 rw,relatime,errors=continue,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/device.map (hd0) /dev/sda *** END /boot/grub/device.map -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, lc_ctype=fr...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages grub-pc depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii grub-common 1.97~beta4-1 GRand Unified Bootloader, version ii libc6 2.9-25 GNU C Library: Shared libraries ii ucf 3.0021 Update Configuration File: preserv grub-pc recommends no packages. Versions of packages grub-pc suggests: pn desktop-base none (no description available) pn genisoimage none (no description available) -- debconf information: grub2/kfreebsd_cmdline: * grub2/linux_cmdline: console=ttyS1,57600 console=tty0 * grub-pc/chainload_from_menu.lst: true grub-pc/kopt_extracted: true grub-pc/install_devices: grub-pc/postrm_purge_boot_grub: false grub2/kfreebsd_cmdline_default: quiet * grub2/linux_cmdline_default: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549314: xorg: Xorg crashes at random, exactly once
Stefan Klinger wrote: Package: xorg Version: 1:7.4+4 Severity: critical Justification: causes serious data loss My Xorg session crashes without prior notice, roughly during the first 15 Minutes of working. However, I can trigger a crash by typing dmesg -n 9 as non-root user, wich normally prints 'klogctl: Operation not permitted'. This instantly teminates my session. Looks really strange... We need the backtrace of the crash. See the end of Xorg.0.log or Xorg.0.log.old Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548725: Note that git radeon driver still fails.
Eric Valette wrote: Julien Cristau wrote: On Mon, Sep 28, 2009 at 23:19:33 +0200, Eric Valette wrote: intel git works radeon git fails Wonder if I shall screw up another PV trying with nouveau ;-) intel git removed the call to xf86DiDGAInit. OK. The patch to fix it is there... http://lists.x.org/pipermail/xorg/2009-September/047428.html We are subscribed to upstream mailing lists obviously :) But we're waiting for somebody to confirm the fix before uploading a fixed package. Did you test it? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548873: Acknowledgement (xserver-xorg-video-radeon: Latest X server crashes on startup inside the radeon driver)
Philip Armstrong wrote: reassign 548873 xserver-xorg-core 2:1.6.4-1 thanks Addendum. Downgrading from xserver-xorg-core 2:1.6.4-1 to 2:1.6.3.901-1 fixes the problem. Refiled against xserver-xorg-core. And I merged it with the dozen of similar bug reports about this. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548851: Used to work but now segfault at startup
Peder Chr. Norgaard wrote: On Tuesday 29 September 2009, Julien Danjou wrote: At 1254204787 time_t, Julien Danjou wrote: Since today, I cannot start X anymore. I tried with 2.6.30 and 31, and it just segfaults. It used to work up to a couple of days ago without any problem. AFAIK I did not change anything, so this may be due to a recent upgrade of some packages (xserver ?) Installing the version from experimental solved the problem, FWIW. Excuse me, I have hit the very same problem. I would like to use your hint, but do not understand it: Installing which version of what package from experimental solves the problem? My own solution was to downgrade the xserver-xorg, but I find no xserver-xorg in experimental right now so I do not think that you are referring to xserver-xorg. He's talking about xserver-xorg-video-intel from experimental (2.8.99.902), but you should now even use 2.9.0 which entered unstable today. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548393: xserver-xorg-video-intel: xserver unusably slow after upgrade
John Franck wrote: Or if this is too difficult, could you please post the information about the bigmem kernel on the bug report before closing it so that others can find the same information? Thanks very much! John John Franck wrote: I was using the .30 kernel. I find, however, that after rebooting with a non-bigmem kernel that this does work. Is it possible to set the package to conflict with the bigmem kernel packages? I only found the information about the bigmem kernel after several hours of web searching. Thanks very much for your prompt response + I apologize that I was out of town. John Note for the BTS: John was using a -bigmem kernel (PAE enabled) which is incompatible with GEM up to 2.6.30. So he had to upgrade to 2.6.31 or use a non-bigmem to get acceleration back. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541254: just segfaults
Norbert Preining wrote: Package: xserver-xorg-core Version: 2:1.6.4-1 Severity: normal gdm too. Downgrading xserver-xorg-core to 2:1.6.3.901-1 fixes this problem. I got the following xorg.0.log fini: ... (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4edfe6] 1: /usr/bin/X(xf86SigHandler+0x39) [0x483699] 2: /lib/libc.so.6 [0x7ff22bf43db0] 3: /usr/bin/X(DGAAvailable+0x39) [0x4823c9] 4: /usr/bin/X(xf86DiDGAInit+0x30) [0x4ae200] 5: /usr/bin/X(xf86CrtcScreenInit+0x10d) [0x4aafad] 6: /usr/lib/xorg/modules/drivers//intel_drv.so [0x7ff22a74a64f] 7: /usr/bin/X(AddScreen+0x1c6) [0x432ac6] 8: /usr/bin/X(InitOutput+0x241) [0x46d361] 9: /usr/bin/X(main+0x200) [0x4331d0] 10: /lib/libc.so.6(__libc_start_main+0xe6) [0x7ff22bf305c6] This has nothing to do with this bug. This is another one that has been reported a hundred times today already. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547937: Loading of i915 with modeset=0 does not help
wzabo...@elektron.elka.pw.edu.pl wrote: I've found that some problems related to xserver-xorg-video-intel may be cured by adding modeset=0 when loading i915 module. I've tried that, but it didn't cure the problem. X windows crashed again a few minutes ago :-(. If you can't upgrade your kernel to 2.6.31 with the required fix, you should downgrade the intel driver to 2.7.1 and use EXA instead of UXA (Option AccelMethod EXA in section Driver of xorg.conf). An old package is available at http://people.debian.org/~bgoglin/rebuilds/Xserver1.6/intel-2.7.1/ Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546836: any information yet?
Brent S. Elmer Ph.D. wrote: Any information on this bug yet? Do you need any more information from me? mga is not really maintained upstream anymore so unless your problem is obvious, you will have to wait before getting a fix. You could try to rebuild the old mga driver against the new 1.6 server to see if the bug comes from the updated driver or from the updated server. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547496: xserver-xorg-core: terminates with signal 11
severity 547496 important thank you Thomas Koenig wrote: Subject: xserver-xorg-core: terminates with signal 11 Package: xserver-xorg-core Version: 2:1.6.3-1+b1 Justification: renders package unusable Severity: grave Hi, the x server just crashed on me twice after upgrade. A logfile is attached. Why don't you use the radeon driver? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547496: xserver-xorg-core: terminates with signal 11
Thomas Koenig wrote: On Sun, 2009-09-20 at 13:36 +0200, Brice Goglin wrote: Why don't you use the radeon driver? Tried it, it crashed just the same (see logfile). Try with an empty xorg.conf. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546836: [xserver-xorg-video-mga] black screen when X starts
Brent S. Elmer Ph.D. wrote: Package: xserver-xorg-video-mga Version: 1:1.4.11.dfsg-1 Severity: grave --- Please enter the report below this line. --- I upgraded xserver-xorg... that hit squeeze recently. I also updated xserver-xorg-video-mga. When I restarted X, I don't get a gdm login screen it is just black. I can still hear the ready to login sound that plays. I can blindly type the login information and hear the gnome login sound. The screen remains black. It is like the monitor has been put to sleep. I can do alt-F1 to go to a tty session. When it opens the session, the monitor slowly wakes up and I can see the session. There are no errors in the Xorg.0.log. I have a Matrox G550 card. I even tried removing xorg.conf and letting X set everything. It didn't make any difference. I tried /etc/init.d/gdm resgtart and X restarts and I can hear the ready to login sound but the screen is still black. I am submitting this bug report from a different computer because the other one is not very useful at the moment. What can I do to fix it? Please send your config and log. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539705: can we proceed?
Martin-Éric Racine wrote: Intel has all the paid developers in the world to look after that particular issue with their driver. Meanwhile, the rest of X works fine as it is. Intel from testing doesn't work with Xserver 1.6. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540077: xserver-xorg-video-intel: [UXA][GM965] Xorg crashes, X server fails to start
if wrote: Package: xserver-xorg-video-intel Version: 2:2.8.0-2 Justification: renders package unusable Severity: grave When did this problem appear? Which intel driver package did you have before ? (see /var/log/dpkg.log or /var/log/aptitude) Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540077: xserver-xorg-video-intel: [UXA][GM965] Xorg crashes, X server fails to start
if wrote: Problem appeared about few days ago, when 2.8.0-2 hit the unstable, i upgraded but didn't notice because didn't reboot. Version 2:2.7.1-1 was working since 2009-07-07, it was on hold since then because 2.7.99.901-2 was crashing with simular error (although i didn't report a bug that time as someone already did), and 2:2.3.2-2+lenny6 from testing requred downgrade for the whole xserver, and no UXA. Also, Ubuntu package 2:2.6.3-0ubuntu9.3 was useable as well. I tried to compile 2.8 branch from git today, and it's crashing with the same backtrace, in the same functions (i830_allocate_memory and i830_allocate_2d_emmory). You may downgrade to 2.7.1 with packages from http://people.debian.org/~bgoglin/rebuilds/Xserver1.6/intel-2.7.1/ Does UXA work there? (it is only mandatory since 2.7.99). Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525231: X freezes
On Wed, Jun 03, 2009 at 06:16:11AM +0200, Soeren Sonnenburg wrote: Yes, happens with 2.6.30-rc7+ and xorg-intel-git-current. AFAIK bugs are filed already. AFAIK it is not kernel dependent but happens with xserver-xorg-video-intel version 2.6.X and above (last version known to work is 2.4.X). Any improvement with intel 2.8.0 and 2.6.31-rc ? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538283: xserver-xorg-video-intel: Xorg eat too much resources
Tomas Frydrych wrote: I got to the bottom of my problem; the intel 2.8 driver requires KMS enabled No, KMS is not required. UMS is still supported (but upstream probably doesn't test it as much as KMS, so it might be more buggy). UMS was working fine in 2.8-rc3 on my i945. Not sure I tested with 2.8 but still... Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539051: xserver-xorg-video-nv: FTBFS: Missing Build-Depends
Daniel Schepler wrote: Package: xserver-xorg-video-nv Version: 1:2.1.14-1 Severity: serious From my pbuilder build log: ... stampdir/genscripts stampdir/prepare if ! [ `which quilt` ]; then \ echo Couldn't find quilt. Please install it or add it to the build-depends for this package.; \ exit 1; \ fi; \ if QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null next /dev/null 21; then \ echo -n Applying patches...; \ if QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null push -a -v stampdir/log/patch 21; then \ cat stampdir/log/patch; \ echo successful.; \ else \ cat stampdir/log/patch; \ echo failed! (check stampdir/log/patch for details); \ exit 1; \ fi; \ else \ echo No patches to apply; \ fi; \ stampdir/patch Couldn't find quilt. Please install it or add it to the build-depends for this package. make: *** [stampdir/patch] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 (Also, when I built it with DEB_BUILD_OPTIONS=parallel=3, the build process went ahead and ran autoreconf even though the patch had failed. That to me indicates that there's a missing dependency somewhere which could result in autoreconf being run on the unpatched code before the patching is done.) The problem is likely that the patching has been wrongly removed: the build target still depend on patch while there shouldn't be any patch rule in there... I'll look at it. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538283: xserver-xorg-video-intel: Xorg eat too much resources
Tomas Frydrych wrote: I am experiencing the same problems with the 2.6.30-1-686 kernel, so not using the bigmem kernel is not a solution to this bug. You just don't have the same bug. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535605: xorg -- general: X fonts severely broken.
severity 535605 important thank you On Fri, Jul 03, 2009 at 04:09:51PM +, Dean Menezes wrote: X fonts in input boxes (?) are broken -- all that displays is garbage when opening up an rxvt, xterm, etc.Conkeror displays fonts in webpage, but crashes when I type g to go to a new URL. Dialog boxes in stumpwm that ask for input also display garbage. Most of stumpwm's internal dialog boxes display fine, however the text in the Current frame popup does not display -- only the empty box and garbage otherwise. Please send the whole output of /usr/share/bug/xserver-xorg/script 31 Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525231: X freezes
On Wed, Jun 03, 2009 at 06:16:11AM +0200, Soeren Sonnenburg wrote: Yes, happens with 2.6.30-rc7+ and xorg-intel-git-current. AFAIK bugs are filed already. AFAIK it is not kernel dependent but happens with xserver-xorg-video-intel version 2.6.X and above (last version known to work is 2.4.X). Still no luck with intel 2.7.99.902 from experimental? Did you try with and without KMS? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535300: In fact it is xserver-xorg-video-intel after all
On Wed, Jul 01, 2009 at 01:58:08PM +0100, Sam Morris wrote: I downgraded drm-snapshot to the version in unstable and it didn't make any difference. I then downgraded xserver-xorg-video-intel to the version in unstable and everything is OK again! So I guess the problem started when 2009-06-19 00:28:54 upgrade xserver-xorg-video-intel-dbg 2:2.7.99.1-2 2:2.7.99.901-2 and I simply hadn't restarted my system since then, despite what the 'uptime' command tells me. Maybe it doesn't handle suspend/hibernation very well. :) It is better with 2.7.99.902 from experimental? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536287: xserver-xorg-video-intel: X apps break severely with Intel KMS (Kernel Modesetting)
On Wed, Jul 08, 2009 at 08:04:10PM +, Dean Menezes wrote: Package: xserver-xorg-video-intel Version: 2:2.7.1-1 Severity: grave Justification: renders package unusable When kernel mode setting is enabled, fonts render as garbage, making terminal emulators and other applications unusable. mplayer using x11 output also displays garbage, but xv output works fine. This does not occur if KMS is turned off Is it better with 2.7.99.902 from experimental ? If not, can you try a 2.6.31-rc kernel ? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534487: xserver-xorg-core crash
Matteo Sgalaberni wrote: I don't know if the crash described in this bug is the same of mine... my crash appeared after I upgraded. Upgraded to 1.6.2-1, same crash of 1.6.1.901-3. I found that this crash appear only with driver nvidia proprietary. This bug report is DRI2/intel specific (see the backtrace) while your crash is nvidia-specific (nothing in the backtrace). And we can't debug the nvidia proprietary driver. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537052: xserver-xorg-video-intel: [UXA G33] 2.7.99.902 crashes upon X initialization
Emilio Pozuelo Monfort wrote: Package: xserver-xorg-video-intel Version: 2:2.7.99.902-1 Severity: serious Tags: patch Justification: renders package unusable Hi, 2.7.99.902 crashes when X starts. Downgrading to .901 solves the issue. I've reported it upstream and there's a patch available that I've tested on top of .902-1 and it solves the crash. Assuming I am seeing the same problem here, people might want to know that only User modesetting seems to crash, KMS works fine here. So this bug is actually a good reason for people to try KMS now :) Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508476: Has it been reported upstream?
Ivan Baldo wrote: Hello. Has this problem been reported upstream? Thanks. As you may see in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508476 it has been reported at http://bugs.freedesktop.org/show_bug.cgi?id=21315 Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526169: even xdm login screen becomes unreadable rectangular chunks
jida...@jidanni.org wrote: OK, I see you have a new version. Well, before doing # dpkg -i xserver-xorg-video-intel_2%3a2.6.1-1_i386.deb dpkg: warning: downgrading xserver-xorg-video-intel from 2:2.7.99.901-1 to 2:2.6.1-1. # aptitude hold xserver-xorg-video-intel here on # uname -a Linux jidanni2 2.6.29-2-686 #1 SMP Sun May 17 17:56:29 UTC 2009 i686 GNU/Linux You still need to try with kernel 2.6.30... Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523953: xserver-xorg-video-intel: Trying kernel 2.6.29 + UXA
On Sun, Apr 26, 2009 at 04:38:58PM +0200, Apelete Seketeli wrote: Package: xserver-xorg-video-intel Version: 2:2.7.0-1 Severity: grave I changed my system configuration to Sid's 2.6.29 kernel and I configured my xorg to use UXA and disabled tiling. This seems to greatly improve the situation on my side. There's still a bit of tearing in videos, but overall it's working quite well now. Please refer to attached files if you need some more info. Any improvement with intel 2.7.1 or 2.7.99.1-2 from experimental? You might want to use a recent kernel such as 2.6.30-rc8. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526169: even xdm login screen becomes unreadable rectangular chunks
Does this still happen with intel 2.7.99.1-2 and kernel 2.6.30-rc8 or so? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526169: even xdm login screen becomes unreadable rectangular chunks
jida...@jidanni.org wrote: Does this still happen with intel 2.7.99.1-2 and kernel 2.6.30-rc8 or so? Ho ho ho, still a disaster, and even in experimental, there is no such a high numbered kernel yet. What about 2.6.30-rc7 if rc8 isn't available on http://kernel-archive.buildserver.net/debian-kernel/ yet ? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530512: compiz: fails to redraw windows and move them around
Oz Nahum wrote: Also, I reveted my xorg-server from 7.4 to 7.3 now I get a white screen trying to run compiz. If you downgrade xserver-xorg-core, you want to downgrade libgl1-mesa-dri as well. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527165: downgrading X
Martin Lemmen wrote: apt-get install xserver-xorg-core=2:1.4.2-10 doesn't work, the error message is Version 2:1.4.2-10 wasn't found. apt-cache policy xserver-xorg-core lists that vertsion as the only one availible in lenny, and also as the one installed. I'm pretty much stuck here. Run apt-get update and try apt-cache policy again 2:1.4.2-10 isn't available anymore. Lenny now has 2:1.4.2-10.lenny1 while testing has 2:1.4.2-11 Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527483: inventor: FTBFS: Undefined reference to `glwMDrawingAreaWidgetClass'
On Sat, May 09, 2009 at 01:06:59PM -0500, Steve M. Robbins wrote: Somehow GLw has lost glwMDrawingAreaWidgetClass: it is defined in GLwMDrawA.h, but isn't supplied in the lib. It used to be. What do I do now? Probably caused by the addition of --enable-motif in Mesa. It is not enabled by default and not enabled by the debian packaging either. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526169: can't even read the login screen
jida...@jidanni.org wrote: found 526169 2:2.7.99.1-1 severity 526169 grave retitle 526169 can't even read the login screen thanks 2:2.7.99.1-1 is a little better. At least the Debian logo is readable on the xdm login screen, but still not any other words. We need your full X log, as usual... Make sure you're using 2.6.29 or even 2.6.30-rc since recent intel drivers like recent kernels (2.7.99.1 enforces UXA which requires GEM anyway). Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523953: xserver-xorg-video-intel: Xserver crash whenever playing high resolution video
Apelete Seketeli wrote: Package: xserver-xorg-video-intel Version: 2:2.6.3-1 Severity: grave Justification: renders package unusable Xserver systematically restart when I try to play a video which resolution exceeds 1024x768 (that's my 12 panel max resolution). Anything lower plays fine, and if I set plugin to X Window System (No Xv) with gstreamer-properties I can even play those critically high resolution videos too. I tried playing these videos using the vesa driver instead, and everything played fine (even though it was dead slow), so it's definitely an Intel driver bug. Please send a backtrace of this crash. Matthias sent some but we need to know if yours is actually similar. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521720: Lastest libdrm2 breaks Xorg
reassign 521720 fglrx-driver forcemerge 521323 521720 thank you Jérôme Marant wrote: Package: libdrm2 Version: 2.4.5-2 Severity: serious Hi, After upgrading from 2.3.1-2 to 2.4.5-2, my Xorg failed to work properly. After downgrading to 2.3.1-2, situation is normal again. I do use latest Xorg from unstable along with fglrx non-free drivers, and kernel 2.6.26. Several people reported the same problem, all of them are using fglrx as well. Nobody using a free driver complained. So the fglrx binary driver is likely the problem here, merging and reassigning accordingly. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516852: Fixed version for gtk_file_system_error_quark?
Johan Walles wrote: Hi Brice! You said that upgrading gtk/ruby libs to unstable resolved the gtk_file_system_error_quark problem for you. What version of ruby-gnome2 do you have installed? I'd like to add a notfound version to http://bugs.debian.org/516852. Regards //Johan I don't have ruby-gnome2, but I have $ dpkg -l | grep gtk | grep ruby ii libgtk2-ruby 0.17.0~rc1-6 GTK+ bindings for the Ruby language ii libgtk2-ruby1.8 0.18.1-1+b1 GTK+ bindings for the Ruby language Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516028: xserver-xorg-input-all: Key and mouse acting weird after dist-upgrade Debian testing (escape sequence injection)
Mark wrote: On Thu, 19 Feb 2009 00:42:19 +0100 Brice Goglin brice.gog...@ens-lyon.org wrote: Don't be so sure. Please send your config and log. Here we are. Sorry for the last mail, as noted before, the system behaves unreliable, you never know which command you trigger while typing... Are you running X packages from testing or unstable ? If you have libxi6 1.2.0 from unstable, does it help if you downgrade it back to testing (1.1.4) ? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515946: libxi6 2:1.2.0-2 makes iceweasel and midori crash
Vincent Lefevre wrote: retitle 515946 libxi6 2:1.2.0-2 makes iceweasel (when selecting text) and midori crash thanks On 2009-02-18 16:18:29 +0100, Vincent Lefevre wrote: The bug comes from libxi6 2:1.2.0-2 (downgrading to 2:1.1.4-1 solves the problem). To summarize, when libxi6 2:1.2.0-2 is installed: * midori immediately crashes when it is started; * iceweasel crashes as soon as some text is selected (not just in iceweasel, but also in xterm, for instance). But emacs22-gtk and liferea don't seem to crash. Can you try with xserver-xorg-core 2:1.4.2-11? It looks like we had issues (eg #515734, #515905 and #515976) because libxi6 was built against newer input proto headers. The new xserver-xorg-core has been rebuilt with the same headers now and it seems to help. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516028: xserver-xorg-input-all: Key and mouse acting weird after dist-upgrade Debian testing (escape sequence injection)
Mark wrote: Package: xserver-xorg-input-all Version: 1:7.3+18 Severity: grave Justification: renders package unusable After a dist-upgrade of my Debian testing system to the bleeding edge a few days ago I had a problem after rebooting my system: - On the kdm logon screen I noticed a weird behaviour of my keyboard, I was not able to log in. - I switched to the console. On the console the keyboard behaved correctly. - I activated the automatic login feature in kdm and rebootet the system. - The system rebooted and directly logged into my KDE session. The system looked as before. - When typing on the keyboard, I noticed that every other key a new window opened, or another command executed. - I then noticed, that there is a pattern to this behaviour. - After starting xev and pressing the letter g two times I received this log: KeyPress event, serial 34, synthetic NO, window 0x301, root 0x88, subw 0x0, time 180149, (474,128), root:(475,171), state 0x0, keycode 42 (keysym 0x67, g), same_screen YES, XLookupString gives 1 bytes: (67) g XmbLookupString gives 1 bytes: (67) g XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x301, root 0x88, subw 0x0, time 180493, (474,128), root:(475,171), state 0x5, keycode 42 (keysym 0x47, G), same_screen YES, XLookupString gives 1 bytes: (07) XFilterEvent returns: False KeyPress event, serial 34, synthetic NO, window 0x301, root 0x88, subw 0x0, time 180859, (474,128), root:(475,171), state 0x5, keycode 42 (keysym 0x47, G), same_screen YES, XLookupString gives 1 bytes: (07) XmbLookupString gives 1 bytes: (07) XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x301, root 0x88, subw 0x0, time 181154, (474,128), root:(475,171), state 0x5, keycode 42 (keysym 0x47, G), same_screen YES, XLookupString gives 1 bytes: (07) XFilterEvent returns: False - Interestingly, although I pressed g twice, only the first event reflects that choice. The other events look as if I pressed control key. - Another strange fact is that I do have no repeating key functionality on the system anymore. If I want to write ggg I have to press the letter g three times (or actually six times for every second time I trigger a command, like new window, duplicate window, bookmark...) - The xorg.conf file did not change since quite some time. So I am very sure that the configuration is (still) OK. Don't be so sure. Please send your config and log. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514412: when user belongs to group video compiz crashes x-server
severity 514412 important thank you clue wrote: Package: compiz Version: 0.7.6-7 Severity: grave Justification: causes non-serious data loss When two users are logged in and one belongs to group video and you switch between the two users to the user belonging to video his X session gets a blank, black sreen. You can move mouse still around, and the pointer changes according to what is underneath it. But if you just click with the mouse X crashes always. If you do not click, you can still switch to the other users or to text console. Please send your config and log. If X crashes, we'll need to corresponding log (with a backtrace at the end). A debugging backtrace with gdb (from another machine through ssh) would help as well. To make things clear: you have 2 users logged in graphical sessions, right? So only the first one has DRI support and Compiz I guess (we want the log of this one then). By the way, Xserver crashes are usually severity important. Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513895: xserver-xorg-core: the sid package for powerpc is badly uploaded
José Jorge wrote: Package: xserver-xorg-core Version: 2:1.4.2-9 Severity: grave Justification: renders package unusable The package xserver-xorg-core_1.4.2-10_powerpc.deb stops downloading at 1.6MB from the four different mirros I have tested. It looks like it was badly submitted. To reproduce, just try downloading from oe of the mirrors : http://packages.debian.org/sid/powerpc/xserver-xorg-core/download Works fine here (I used ftp.fr.debian.org) Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513128: xserver-xorg-core: X server crashes every time when gnome-screensaver starts (after recent upgrade)
severity 513128 important thank you Dmitri Toptygin wrote: When X server dies, the last lines in the file .xsession-errors are We need /var/log/Xorg.0.log after the crash. It should contain a backtrace at the end. If X already restarted after the crash, the log has been renamed into /var/log/Xorg.0.log.old Section Device Identifier ATI Technologies, Inc. RV370 5B62 [Radeon X600 (PCIE)] Driver vesa BusID PCI:1:0:0 EndSection Why are you using vesa instead of radeon ? Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511837: Cannot properly install nVidia proprietary driver in Lenny
reassign 511837 nvidia-glx severity 511837 normal thank you Dmitry Baryshev wrote: Package: xserver-xorg-core Version: 2:1.4.2-10 Severity: critical nVidia proprietary driver (177.82) will be installed correctly, but will warn user that libwfb.so and libglx.so are not symlinks. I should remove that files and make symlinks by hand: $ cd /usr/lib/xorg/modules $ rm -f libwfb.so $ ln -s libnvidia-wfb.so.1 libwfb.so $ cd extensions/ $ rm -f libglx.so $ ln -s libglx.so.177.82 libglx.so But after any future X.org update, I will loose these changes. libglx.so and libwfb.so should probably be symlinks. Well, what about fixing the nvidia driver instead? dpkg diversions are probably an easy solution here. By the way, this bug report is faar away from being critical... Brice -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#499067: radeonhd: The screen remains black, altough there are no crashes
severity 499067 important retitle 499067 radeonhd: black screen with Mobility 3470 and 3GB of RAM (Asus Pro72S) thank you Alex wrote: The radeonhd driver is not able to show any image on the screen, while the vesa and ati drivers can. This $ looks a bit like the one described by the X.Org Wiki (http://www.x.org/wiki/radeonhd, the one with the Asus la$ more than 2 GB of memory). Did you try to pass mem=2048M or so to the kernel command line? It could be https://bugs.freedesktop.org/show_bug.cgi?id=16892 Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499238: xorg: No input possible after upgrade
Antoon Pardon wrote: Package: xorg Version: 1:7.3+16 Severity: grave Justification: renders package unusable After upgrading xorg and related packages, the computer no longer responds to mouse movements and keyboard input. It doesn't matter whether I try with gdm or via the console and startx. I tried to build a new xorg.conf with dexconf but that didn't make a difference. If you want us to debug anything, we need at least your xorg.conf and Xorg.0.log... Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
Hello, I have prepared savage 2.2.1-2 to fix this. Could all of you please test the package available at http://newpeople.debian.org/~bgoglin/savage/ and report back whether it works? I want to be sure it doesn't break for anybody. thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451791: xserver-xorg-video-intel: XAA on GM965 - no video player working
Kai Weber wrote: xserver-xorg-video-intel (2:2.3.2-2+lenny3) unstable; urgency=low [ Brice Goglin ] * Add 02_xaa_by_default_on_i965.diff to switch back to XAA on i965 by default to avoid many rendering problems, closes: #451791. With this patch, all my video players (totem, vlc, mplayer, xine) stopped working with error messages like that: The error was 'BadAlloc' (insufficient resources for operation) Yeah, we are aware of the problem, XAA and XV are not always friends. We are thinking of replacing the above force XAA patch into Force EXANoComposite on i965. BTW, I never had problems with font rendering. Let's say you're lucky :) We don't know what's causing this font rendering problem, but many people were affected on various i965 board models. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497116: xorg: random crashes on shutdown
severity 497116 important thank you Sten Heinze wrote: Package: xorg Version: 1:7.3+15 Severity: grave Justification: causes data loss No. xorg crashes randomly on shutdown, i.e. after the desktop environment shut down (closing programs and playing shutdown sound). The screen does not return to the normal console (tty1) but stays black instead and freezes the system (only switching off helps). This happened for me both with KDE 3 and 4 (each using the latest versions available in Debian). Unfortunately no information about the crash is recorded in the log files, and I did not find a clearly reproducable pattern. It usually happens once a day, although I start/shutdown the system only about 2-4 times a day. This is extremely annoying, in particular when losing data after working on it all day. You said the crash occurs on shutdown. Which data can you loose at this point? I am using Thinkpad X40 with an integrated Intel 855GM graphics controller. Please tell me if and how I can provide further help. Please send the whole output of /usr/share/bug/xserver-xorg/script 31 so that we see your config, log and hardware. Is the machine pingable after the crash? Can you restart X without any problem? It would be good if you could: * send us the log of the crashed session (if X already restarted, the previous log is moved to /var/log/Xorg.0.log.old) * catch a backtrace with gdb after installing xserver-xorg-core-dbg and xserver-xorg-video-intel-dbg. The easiest way is to connect through ssh from another machine, attach gdb with gdb -p $(pidof X), wait for the crash to occurs, and then ru bt full in gdb. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483989: xserver-xorg-video-savage: system freeze while starting X
On Sun, Jun 01, 2008 at 08:49:18PM +0200, Stefan Lippers-Hollmann wrote: Yes, it is completely dead, open ssh connections trying to gather last bits from tail -f /var/log/messages stall immediately (unfortunately the notebook has no serial connectors for a serial console), pings get no answer - a hard poweroff is the only recovery. Pinging again to make sure the bug didn't disappear by chance :) Otherwise, we need to decide between: 1) reverting to 2.1.3-5 which worked fine except bug #481739 (which looks strange to me) 2) reapplying 02_temporary_revert_pciaccess.diff and reverting 5 pciaccess commits (merging all of them in the 02_revert). Not sure how stable this one would be. Maybe we can start with (2) for now, and switch to (1) as the ultimate solution if needed before Lenny gets released? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496272: xserver-xorg: fonts and menu icons are blank in pristine lenny install
Mark Hedges wrote: But I just re-installed and now it is fine. Weird. What did you reinstall? The whole machine? Can you send the corresponding config and log? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496272: xserver-xorg: fonts and menu icons are blank in pristine lenny install
Mark Hedges wrote: Package: xserver-xorg Version: 1:7.3+15 Severity: grave Justification: renders package unusable I just installed lenny with the netinst installer on a Thinkpad X61. All the fonts are blank. gdm or kdm. I log into gnome and the fonts and menus are all blank. I can click on the menu, and the entries highlight, but they are all blank. It doesn't matter if I use the default xorg.conf file generated by dpkg or if I use the one that used to work with this system before my hard drive died. This is likely a duplicate of #451791 and friends. Does adding one of the following lines in the Device section help? Option AccelMethod XAA Option EXANoComposite Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494321: [xserver-xorg-video-intel] Error in I830WaitLpRing(), timeout for 2 seconds - reboot needed
severity 494321 important thank you Guido Guenther wrote: Package: xserver-xorg-video-intel Version: 2:2.3.2-2 Severity: serious X crashed with the attached output in Xorg.0.log when minimizing a Window with Compiz. Afterwards the monitor kind of blinked until I stopped gdm. Restarting gdm brought the blinking back but no solid picture. I had to reboot. Switching to XAA is usually a good workaround for this kind of problem. Option AccelMethod XAA in the Device section. I am downgrading severity to important to match many other Xorg crash/lockup reports. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490990: xorg: xserver fails to start on PowerPC G4 mac with ATI Rage128 PF/PRO AGP 4x TMDS
Rick Thomas wrote: Package: xorg Version: 1:7.3+12 Severity: important xserver fails to start on PowerPC G4 mac with ATI Rage128 PF/PRO AGP 4x TMDS following update to latest Lenny Add Driver r128 to your Device section for now. The server is autoloading radeon instead of r128, I am fixing this. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489051: Possible patch to solve unresolved symbol
mariodebian a écrit : Hi. I have made a small patch to solve this bug. I'm very newbie in this things excuse me if this patch isn't necesary... I don't know exactly from which version of Xorg this patch applies #if XORG_VERSION_MAJOR 1 XORG_VERSION_MINOR = 4 XORG_VERSION_PATCH 2 mode = xf86GTFMode(p-HDisplay, p-VDisplay, v, 0, 0); #else mode = xf86CVTMode(p-HDisplay, p-VDisplay, v, FALSE, FALSE); #endif Thanks, I just tested this on my Thinkpad T43 (Radeon Mobility X300), vesa 2.0 now starts fine and seems to behave as 1.3.0 did. I sent the patch to the upstream bug. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488762: Latest xserver-xorg-video-mga buggy
severity 488762 important retitle 488762 uses 1660x1024 instead of 1600x1200 thank you Svante Signell wrote: After upgrading the mga driver X-windows comes up in a resolution of 1660x1024 instead of 1600x1200 as expected. The screen is also partially shadowed making it almost impossible to see the desktop. The colors are also distorted. Downgrading to 1:1.4.8.dfsg.1-1 solves the problem. Xserver is 1:7.3+12 and the video card is a MGA G400 Dual head. Attaching xorg.conf, Xorg.0.log for versions 1:1.9.100.dfsg1-1 and 1:1.4.8.dfsg.1-1 What if you try to force 1600x1200 using Modeline+PreferredMode ? See section III.5 of http://wiki.debian.org/XStrikeForce/HowToRandR12 You might want to try the latest upstream git (branch randr-1.2) since mga 1.9.100 is experimental and a bit old. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486786: xserver-xorg-video-glint: startx results in Fatal X server error
forwarded 486786 https://bugs.freedesktop.org/show_bug.cgi?id=16060 thank you Mikael Lehikoinen wrote: Hi! I have the same problem on one of my old servers. When I searched on google before last weekend I found this upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=16060 Maybe it is the same bug? Looks right, thanks. Downgrading to 1.1.1-8 resolved my problem. I had to download an ubuntu package - i couldn't find it in debian's package pool. It's on snapshot.debian.net. I added to my TODO list for Lenny the need to revert the breakage from glint 1.2.0. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487527: xserver-xorg-video-radeon: replace/conflict
Riccardo Stagni wrote: Package: xserver-xorg-video-radeon Version: 1:6.8.191-2 Severity: serious Justification: Policy 7.something I guess your recent upload misses a replace/conflict with the previous version: Selecting previously deselected package xserver-xorg-video-radeon. Unpacking xserver-xorg-video-radeon (from .../xserver-xorg-video-radeon_6.8.191-2_i386.deb) ... dpkg: error processing /mirror/debian/pool/main/x/xserver-xorg-video-ati/xserver-xorg-video-radeon_6.8.191-2_i386.deb (--unpack): trying to overwrite `/usr/share/man/man4/radeon.4.gz', which is also in package xserver-xorg-video-ati dpkg-deb: subprocess paste killed by signal (Broken pipe) Oops, right, fixing this soon. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486786: xserver-xorg-video-glint: startx results in Fatal X server error
Daniel Lewart wrote: Package: xserver-xorg-video-glint Version: 1:1.2.0-1 Severity: grave Justification: renders package unusable xserver-xorg-video-glint 1.1.1-8 startx worked fine. xserver-xorg-video-glint 1.2.0-1 startx fails: Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x7e) [0x80c6a4e] 1: [0xe420] 2: /usr/bin/X11/X(InitOutput+0xa17) [0x80a9a87] 3: /usr/bin/X11/X(main+0x296) [0x80744c6] 4: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d7c450] 5: /usr/bin/X11/X(FontFileCompleteXLFD+0x201) [0x8073a31] Reverting back to 1.1.1-8 fixes the bug, right ? Given that there are very few users of this driver, even among the upstream devs, it would be very nice if you could locate which upstream commit broke this. Looking at http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-glint.git, I guess the pciaccess port (Dave Airlie's commits) are the best candidates for this breakage. Can you trying reverting these 4 patches and see if the bug disappears? (reverting less than 4 may lead to build failure from what I see in the logs). Also, it would be nice if you could catch a backtrace with gdb. And even better if you could catch a backtrace after rebuilding the driver with debug enabled (see [1]) and installing xserver-xorg-core-dbg. thanks, Brice [1] http://wiki.debian.org/HowToGetABacktrace -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486340: debian/copyright needs updating
Moritz Muehlenhoff wrote: I don't expect any problems, but that should be resolved upstream. Brice, can you take care of this? You probably know better who to prod. I just sent it to the intel-gfx list, I'll let you know what happens. If nothing comes, I'll open a bug report upstream. thanks a lot, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486340: debian/copyright needs updating
Moritz Muehlenhoff wrote: Thomas Viehmann wrote: the debian/copyright of xserver-xorg-video-intel is so outdated it has little to do with the rest of the package when it comes to who owns which copyrights. It would be good to go over the source and extract the relevant copyright notices. Note that per-file annotations are not required, so that copyright notices of files with the same license can easily be agglomerated. I can work on this unless anyone from the X Strike Force is already on it. Since Julien is in vacation, I am probably the only real candidate for doing this in XSF. But I have some other important XSF stuff to do right now so I'd be happy if you could do it. thanks Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482057: [compiz] compiz crashes when window are closed
severity 482057 important thank you Paolo Sala wrote: Package: compiz Version: 0.6.3~git20080115.0ea58487-1 Severity: grave --- Please enter the report below this line. --- Sometimes happens that compiz crashes; this happens when I close a window. In the logs I can find only: compiz.real[3630]: segfault at 0014 eip b79e95bb esp bfd20d70 error 4 You need to catch a backtrace with gdb (make sure you do not run gdb from a window wirthin compiz, ssh would be better). We cannot do anything without it. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480397: closed by Julien Cristau [EMAIL PROTECTED] (Re: Undelivered Mail Returned to Sender)
Thomas Koenig wrote: reopen 480397 [EMAIL PROTECTED] thanks If there's a problem with e-mail from my provider, maybe using my GCC account will work. Before closing, Julien actually said: You have two mouse devices here, you need to remove one of them (or both, since the server will create a default one if there's no mouse in xorg.conf anyway). You'll also need to remove the corresponding inputdevices from the ServerLayout section. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479724: xserver-xorg-core: xserver fails to start with a conf that has been good for half a year
Petri Kaurinkoski wrote: Hi Brice, I am sorry to disturb you more, but I have to revert back from closing the issue completely. I just noticed the virtual screens 1-6 changed to be shaded (I can not come up with a better description) while the X-window behaves as previously. The interesting part here is that when the system boots, the text is clear white text on black background, but after Xserver is started, the virtual screens go shaded. The texts are printed as expected, but they are hardly readable: it is as if a filter or curtain was drawn on to of the screen. I attach the Xorg.0.log if that gives you any clue about what is going on. This problem is unrelated to the previous one, please open a new bug about it. You might to check that you don't have the radeonfb kernel module loaded (check in lsmod). Send us the contents of /proc/fb so that we know for sure. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479724: xserver-xorg-core: xserver fails to start with a conf that has been good for half a year
Petri Kaurinkoski wrote: I updated my Debian/testing system yesterday as I regularly do almost every day, and after the updates Xserver would not start. I did not change the configuration files or install any additional packages. xserver complains to Xorg.0.log: Fatal server error: no screens found It could be caused by the RandR 1.2 support in the radeon driver not liking your obsolete lines in /etc/X11/Xorg.conf See below. Section Monitor IdentifierGeneric Monitor OptionDPMS HorizSync63.9 VertRefresh60 EndSection Please comment out HorizSync and VertRefresh above. Section Monitor IdentifierViewSonic VX2235wm Monitor OptionDPMS HorizSync65 VertRefresh60 EndSection Here too. Section Screen IdentifierDefault Screen DeviceATI Technologies Inc RV280 [Radeon 9200 SE] #MonitorGeneric Monitor MonitorViewSonic VX2235wm Monitor DefaultDepth24 SubSection Display Depth1 Modes1680x1050 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth4 Modes1680x1050 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth8 Modes1680x1050 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth15 Modes1680x1050 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth16 Modes1680x1050 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth24 Modes1680x1050 1280x1024 1024x768 800x600 640x480 EndSubSection EndSection Please comment out all the above Modes lines. If it doesn't help, you might want to try with no xorg.conf at all. Please send the corresponding log. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#476876: xserver-xorg-video-s3: S3 server crash/lockup with S3 Trio 64+
Gary Phillips wrote: Package: xserver-xorg-video-s3 Version: 1:0.4.1-5 Severity: critical Justification: breaks the whole system Digital Alpha PWS433au with 1GB RAM, Debian 4.0 (etch) S3 Trio 64+ video card (which works on this hardware with both Windows NT 4.0 and OpenVMS 8.3) Whether manually configured or set up with Xorg -configure, when X is run the display fills with random colored pixels, keyboard and mouse are disabled, and machine must be rebooted in order to recover control. When X is run with -probeonly, the only error it reports is Unable to find V_BIOS. When lspci -v is run, it reports that the Video ROM is present but [disabled]. Is there anything to configure in the Alpha BIOS or whatever to help this? Can something more recent than Etch? The S3 driver is been a bit updated since Etch, and the Xserver is much more recent. Trying Xorg fro; testing might be good, for instance. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463567: segfault when applying keyboard config fixed in Xserver 1.5?
Hello, All of you guys reported a crash of Xserver 1.4 (either on startup or later) when configuring by the keyboard layout. According to another person, the crash is fixed now. Could you please test the new 1.5-rc1 server? It's available in experimental as 1.4.99.901-2 and there's also a repository with all drivers rebuilt accordingly at deb http://pkg-xorg.alioth.debian.org/7.4/ ./ (note that DRI is disabled for now, so you might want to downgrade back after testing). Please report back to your own bug report (or to me) whether it helps. thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439973: Bug#471019: libgl1-mesa-glx: segfaults in glGetString(GL_EXTENSIONS) on amd64 when there is no GL context
According to upstream, this program isn't doing something valid. So I am closing this bug and CCing the one against boson. Brice bgoglin before I report a mesa bug, could anybody tell whether it is valid to call glGetString(GL_EXTENSIONS) without any GL context ? nh_ I'd be extremely surprised if it were nh_ after all, if you don't have a GL context, how would anybody know if you were even going to use direct rendering or not? nh_ last I checked, libGL wasn't psychic +idr bgoglin: It is not legal to query the GL extension string without a context. +idr bgoglin: You can't make *ANY* GL calls without a context. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469142: xserver-xorg-video-mach64: Conflicting files with xserver-xorg-video-ati
Michael Biebl wrote: Package: xserver-xorg-video-mach64 Version: 1:6.8.1~git20080301.d855d208 Severity: serious Justification: upgrade fails Hi, the upgrade of xserver-xorg-video-ati to the version in experimental failed, as xserver-xorg-video-mach64 has conflicting files with the old xserver-xorg-video-ati package. The problem very likely is a typo in the Replaces line in debian/control: s/xserver-xorg-driver-ati/xserver-xorg-video-ati/ The same is true for xserver-xorg-video-r128. Thanks, I got confused by the old ubuntu driver packages, uploading fixed packages soon. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469206: xserver-xorg-video-intel: The monitor is shut down after random time
severity 469206 important thank you ultrakiller wrote: when i use gnome after random time the monitor is shut down!! if i don't use this package the problem does not appears Do you really expect us to fix this bug without any other information? You are probably experiencing a lockup, as many people since Intel 2.2 arrived unfortunately. Please send the whole output of /usr/share/bug/xserver-xorg/script 31 so that we see your config and log. We need the /var/log/Xorg.0.log from *after* the crash. If you can't save /var/log/Xorg.0.log by logging on the machine through ssh after the lockup, you should restart the machine and look at /var/log/Xorg.0.log.old (this is were the old log is stored when a new session is started). To work around the problem, you should try adding Option AccelMethod EXA to the Device section of your /etc/X11/xorg.conf Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467086: xserver-xorg-core: Bad performances with certain Xorg.conf options
severity 467086 normal thank you Basically for weeks my computer has been kind of unusable while having Firefox or Konqueror open and I just realized why yesterday: I changed 2 options in my Xorg.conf and the perfomances have been back to normal. The options changed are: - Option AccelMethod from EXA to XAA - Nothing to Option XAANoOffScreenPixmaps True I am using a Radeon M9000 which is kind of dead so I underclock it, therefore no 3D acceleration is possible anymore and probably not much of 2D acceleration either So you want EXA (which is an 2D acceleration architecture) to be fast without hardware acceleration? I doubt that'll work... If XaaNoOffscreenPixmaps help, does it mean you are running Compiz or another compositing manager such as kwin with fancy effects? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451972: no longer supports xinerama across multiple graphics cards
martin f krafft wrote: Also, there's a maximum of 1280x1200 on screen 0. I really want 3840x1024 to put my three screens next to each other. Is this at all possible? When I try to add VGA-0, I get: piper:~# xrandr --output VGA-0 --auto --right-of DVI-0 xrandr: screen cannot be larger than 1280x1200 (desired size 2560x1024) You need something like Virtual 2560 1024 in xorg.conf (Subsection Display). See II.5 of http://wiki.debian.org/XStrikeForce/HowToRandR12 The server isn't capable of resizing the front buffer yet, that's why we need this line for now so that a large front buffer is allocated at startup even if not used. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451972: no longer supports xinerama across multiple graphics cards
martin f krafft wrote: I know we're in the middle of a transition from legacy xinerama to XRandR, but I still think it's a bug if a new version of X breaks the triple-head setup I have. It may seem that triple-head is mere geeky joy, but to me it's actually a requirement to get my work done. Sure, my mail wasn't meant to tell you to go to hell with your useless triple head :) Given some discussion with upstream, I was just checking whether your problem changed a bit recently. Given that I don't really like my xorg.conf anyway (it's old) and really want to move towards XRandR, I then simply removed xorg.conf and would like to go from here. X comes up, but it only speaks to one of the two ATI boards, and the screen is mirrored on the two attached displays. Mirror is the default behavior, it is meant to give you the login window on all monitors so that you can always login with a default config even if some monitors do not work correctly. See III.2 of http://wiki.debian.org/XStrikeForce/HowToRandR12 for xorg.conf based configuration. Having only one board work is what we need to get fixed... 1. use xrandr to create screen 2 on the second VGA port of the PCI:1:0:0 card and to put it right-of screen 1 attached to the first port. I don't know what output name to use for that. See above. 2. somehow teach X about the PCI:0:12:0 card and use xrandr to put the one display attached to its primary card left-of screen 1. Is this possible? Not sure about that unfortunately. If the driver doesn't even look at board 0:12:0, it doesn't look good. Maybe you need to restore 2 devices sections with the appropriate BusID lines? Not sure whether you need to restore some corresponding Screen and ServerLayout sections... Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466459: xserver-xorg-video-intel: intel driver loose/crash video at random
Fabrice Lorrain wrote: This driver has been unusable on my mac-mini (core 2 duo) since novembre (and on several intel chipset, from other bts entries). It has been crashing X at random resulting in lost of data of the current session and breaking any distants ones. (most notably my ongoing blobwars game ;-) If you feel like downgrading the severity, no lower than serious, please. This driver is not suitable for lenny. As reported by others, since the 2.2.x branch of intel driver, X is going randomly in some suspend mode, and the only way out of it is a plain reboot. Sucks. Do you have multiple outpus connected enabled when the crash happens? It seems to be related in some cases. Does Option FramebufferCompression false help? Can you try with some other kernels? I sometimes felt like 2.6.18 didn't cause any crash while =2.6.22 does. Not sure about 2.6.24 or later. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451972: no longer supports xinerama across multiple graphics cards
On Mon, Nov 19, 2007 at 09:11:33PM +0100, martin f krafft wrote: also sprach Brice Goglin [EMAIL PROTECTED] [2007.11.19.2042 +0100]: As soon as you have one board with a RandR 1.2 driver, you can't use any other board, even if its driver is different and does not support RandR 1.2. It just crashes the server. I am merging with the exiting relevant bugs (which are also RC). Thanks. Do note that I have two cards both using the same driver though, and the crash happens while moving from one screen to another, both on the *same* card. Martin, I am coming back to this bug since the upstream devs think the situation isn't as bad as it seems. At least, non-Xinerama case should work. http://lists.freedesktop.org/archives/xorg/2008-January/032219.html Do you have a uptodate X.org from unstable running with 2 ATI boards right now? If so, could you report what you currently observe? (Xorg.0.log and xorg.conf wouldn't be bad). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443274: dual-card setup doesn't work with X 1.4
On Sat, Sep 22, 2007 at 12:59:00PM +0200, Brice Goglin wrote: Ok, thanks for testing. So, to summarize: * The ATI driver 6.6.193 is broken in this board but 6.7.193 is fine. * Xserver 1.4 + ATI RandR 1.2 does not accept another board/driver in the config, and it might take time to get this fixed... I am retitling/reassigning back to the Xserver now that ATI driver issues are clarified. Aldemir, We are trying to make sure that Xserver 1.4 is really the problem here. So we want to know whether Xserver 1.3 works when a RandR 1.2 (such as ATI) and another one (such as MGA) are used at the same time. I just build a very recent snapshot of the ATI driver for testing/Lenny: http://people.debian.org/~bgoglin/rebuilds/ati-6.7.198-Xserver1.3/ Could you test it (after downgrading to xserver-xorg-core 1.3 from testing if necessary) and see whether it works with the MGA driver enabled at the same time? You'll just need a config with both drivers, probably very similar to what you had at the beginning of this bug report. You might need to try with and without some advanced config such as Screen 0 Screen 1 0 0 Screen 1 Screen 2 RightOf Screen 1 in the ServerLayout section. thanks in advance, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464353: xserver-xorg-video-intel: xserver is very unstable using the 2.2.x version of the driver
Florian Reitmeir wrote: Then please check if the issue is fixed in the latest upstream version. is there s simple way to test the lastest upstream version in debian 2:2.2.0.90-2 will be in unstable shortly (2.2.0.90-1 is a fake new upstream). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463924: compiz-kde
Пётр Козлов wrote: yes. Kwin from KDE4 installed. Ok, you should have a /usr/lib/libkdecorations.so.1 then, don't you? What does ldd /usr/bin/kde-window-decorator say? It seems to find libkdecorations.so.1 as expected here: $ ldd /usr/bin/kde-window-decorator [...] libkdecorations.so.1 = /usr/lib/libkdecorations.so.1 (0xb7cef000) [...] Brice
Bug#457722: xf86-input-fpit crashes/fails with Xserver 1.4
Hi, There's a new patch for the fpit driver bug at http://bugs.freedesktop.org/attachment.cgi?id=14026 See Peter's message below. Brice Original Message Subject:[Bug 14057] xf86-input-fpit crashes/fails with Xserver 1.4 Date: Tue, 29 Jan 2008 19:20:31 -0800 (PST) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] http://bugs.freedesktop.org/show_bug.cgi?id=14057 --- Comment #4 from Peter Hutterer [EMAIL PROTECTED] 2008-01-29 19:20:30 PST --- Created an attachment (id=14026) -- (http://bugs.freedesktop.org/attachment.cgi?id=14026) random patches trying to make fpit work again Please give the above patches a try. I don't know if they work, but they may just do. If the pointer still doesn't move, put an ErrorF() in before posting events (look for xf86PostMotionEvent) and print the conv_x/conv_y coordinates. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457722: trying freedesktop solutions
TreeBoy wrote: I have now tried commenting out the xf86XInputSetScreen call which I found on line 259. I tried it with the unadulterated Debian source which caused X to hang: I could only restart the machine by holding down the power button. I then tried it both with the is_core_pointer=0 and with is_core_pointer=1. They both produced the same result which is the last result I described: no pointer movement but output appearing from cat /dev/ttyS1. I'm afraid that I do not understand what try those two mean. I presume that the second item is related to freedesktop bug 10324, but I could not identify the test. Many thanks for all your help. Thanks, I have posted your reply on the freedesktop bugzilla (https://bugs.freedesktop.org/show_bug.cgi?id=14057). You should probably subscribe there and add yourself to CC: on this entry so that I don't have to stay in the middle :) Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
