Bug#175911: [mga] wrong modeline being sent to monitor at 1280x1024 on MGA G550 AGP rev 1]

2007-05-11 Thread Carsten Pfeiffer
Woohoo, this is great news! I just tested it and it worked right away. No more binary HAL necessary anymore. Thanks, Carsten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#345436: xlibs: Keyboard not working properly after upgrade to 6.9.0.dfsg.1-1

2006-01-05 Thread Carsten Pfeiffer
Hi, I also have a problem with the keyboard in X, namely I cannot produce accented characters like à with dead keys. It happens with both the keyboard and the kbd driver. I found the cause to be rooted in the following message in X log: expected keysym, got dead_diaresis: line 143 of

Bug#345436: #345436: xlibs: Keyboard not working properly after upgrade to 6.9.0.dfsg.1-1

2006-01-05 Thread Carsten Pfeiffer
See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291853 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#175911: problem persists (or reappeared)

2006-01-10 Thread Carsten Pfeiffer
With current Xorg 6.9 I'm experiencing similar problems. Xorg.0.log says (**) (MGA(0): *Default mode 1280x1024: 108.0 MHz, 64 kHz, 60.0. Hz (II) MGA80): Modeline 1280x1024 108.00 1280 1328 1440 1688 1024 1024 1028 1066 +hsync +vsync but my TFT receives 31,3 kHz and 29,3 Hz. Maybe I'm only

Bug#175911: works with framebuffer device!

2006-04-17 Thread Carsten Pfeiffer
I just upgraded to Xorg 7.0 in unstable and X still doesn't work without mga_hal. Using the Option Option UseFBDev true however, makes it work! So as long as Matrox doesn't supply a new mga_hal that works with Xorg 6.8.2 and nobody fixes mga_drv, you can use fbdev to get an X

Bug#175911: xserver-xfree86: [mga] wrong modeline being sent to monitor at 1280x1024 on MGA G550 AGP rev 1

2007-01-14 Thread Carsten Pfeiffer
On Saturday 13 January 2007 22:38, Brice Goglin wrote: Hi, A long time ago, you reported (or replied to) a bug in the Debian BTS regarding wrong modelines at 1280x1024 on a MGA board. The problem has been seen again in April 2006. Did any of you guys reproduce this problem very recently? If

Bug#460866: can't open display

2008-01-15 Thread Carsten Pfeiffer
Package: xvfb Version: 2:1.1.1-21etch1 xvfb in etch simply doesn't work for me. Whatever X-client I start with xvfb-run, it cannot connect to the DISPLAY. E.g. [EMAIL PROTECTED]:~ $ xvfb-run xterm xterm Xt error: Can't open display: :99 /usr/bin/xvfb-run: line 158: kill: (4889) - Kein passender

Bug#460866: can't open display

2008-01-15 Thread Carsten Pfeiffer
Am Dienstag, 15. Januar 2008 schrieben Sie: Thanks for the quick reply! I can't reproduce that. Please try to get more information about the problem (with the -e option to xvfb-run for a start). Here's what I get with -e (reproduced on two different systems, neither of these run an X

Bug#460866: can't open display

2008-02-05 Thread Carsten Pfeiffer
Am Dienstag, 5. Februar 2008 schrieb Julien Cristau: Running it under strace might explain what's going on here. It looks like the unix socket can't be created for some reason... OK, here's the log (using -f). HTH, Carsten xvfb.log.gz Description: GNU Zip compressed data signature.asc

Bug#460866: can't open display

2008-02-05 Thread Carsten Pfeiffer
Am Dienstag, 5. Februar 2008 schrieb Julien Cristau: There's something weird going on in your /tmp/.X11-unix directory. If /tmp/.X11-unix/X99 already exists, but /tmp/.X99-lock doesn't, then please clean up that socket and try again. OK, this is a leftover from a previous xvfb-run session.

Bug#460866: can't open display

2008-02-05 Thread Carsten Pfeiffer
Am Mittwoch, 6. Februar 2008 schrieb Julien Cristau: [pid 31171] write(2, Could not init font path element..., 103) = 103 [pid 31171] write(2, \nFatal server error:\n, 21) = 21 [pid 31171] write(2, could not open default font \'fix..., 35) = 35 [pid 31171] write(2, \n, 1) = 1 [pid

Bug#476198: (no subject)

2008-07-22 Thread Carsten Pfeiffer
I'm also having problems with xrandr. 1) I use a laptop without an external display connected 2) I suspend to disk 3) I plug the laptop into a docking station with an LCD connected 4) I wake up the laptop = the laptop display shows the correct output 5) I issue xrandr --auto = the

Bug#520167: [xserver-xorg-video-radeonhd] icons are garbled

2009-03-17 Thread Carsten Pfeiffer
Package: xserver-xorg-video-radeonhd Severity: normal --- Please enter the report below this line. --- Since the current version, many icons in KDE 3.x and GTK applications are garbled. Usually the lower part looks broken, as if some gibberish data was overlaid. --- System information. ---

Bug#520167: [xserver-xorg-video-radeonhd] icons are garbled

2009-03-17 Thread Carsten Pfeiffer
Thanks for the quick reply, and for noticing my old xserver version. I downgrade to those from unstable: $ dpkg -l xserver-xorg-video-radeon* xserver-xorg-core xserver-xorg | grep ^ii ii xserver-xorg 1:7.3+18 the X.Org X server

Bug#523905: xserver-xorg-input-evdev: Thinkpad trackpoint scrolling doesn't work anymore

2010-10-22 Thread Carsten Pfeiffer
Am Donnerstag, 21. Oktober 2010 schrieb Cyril Brulebois: Hi Cyril, I also got a new laptop (W510) and have had no such problems yet. Thanks and best regards, Carsten -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#623186: Works with 1:0.0.16+git20110411+8378443-1+b1

2011-06-27 Thread Carsten Pfeiffer
FWIW, the problem is gone with 1:0.0.16+git20110411+8378443-1+b1 nouveau is actually usable on my system now. Thanks, Carsten -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#1018176: xorg process leaks file descriptors until it's no longer functional

2022-08-26 Thread Carsten Pfeiffer
Package: xorg Version: 1:7.7+23 Severity: normal Dear Maintainer, since around 2022-08-10 I've noticed that over time the number of open file descriptors of the xorg process increases to near the process's limit of 1024. This happens about once per day, where the computer is on around 9h and put