Bug#345839: [radeon] 2nd head of dualhead setup got "messed up"
Paul Donohue wrote: > The problem is gone for me now. I'm currently using Xorg in Etch, and two > heads works fine with the radeon driver. I honestly can't remember when the > problem went away. > The problem is gone for me too. I'm using lenny. Last version of ATI driver changed the MetaModes head ordering (or the order of detection in the driver) than again redered it unusable but once I figured it out everything is back to normal. -- eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374986: xserver-xorg-video-ati: [2.6.17/radeon] Xserver and console dead, rt_sigaction looping, not killable
On Tue, Jun 19, 2007 at 11:15:56PM +0200, Brice Goglin wrote: > > Hi, > > About a year ago, you reported (or replied to) a bug to the Debian BTS > regarding the X server and console dying on a Radeon X800GTO board. Did > you reproduce this problem recently? With Xorg/Etch? With latest > xserver-xorg-core and drivers? If not, I will close this bug in the next > weeks. My card is an X300, but it seems to hit the same bug. I haven't tried lately, but will try again tomorrow after my exams. Thank you -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423425: Evtouch crashes X when setting date
Here is the backtrace from the X server when a crash occurs from setting the date and tapping the screen simultaneously: 0x40225938 in select () from /lib/libc.so.6 (gdb) continue Continuing. Program received signal SIGSEGV, Segmentation fault. 0x0015e62c in WaitForSomething () (gdb) bt #0 0x0015e62c in WaitForSomething () #1 0x00047f2c in Dispatch () #2 0x0002e48c in main () -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#154204: xserver-xfree86: [ati/r128] SEGV when memory tight and using Xv applications on Rage 128 RF rev 0
Le mardi 19 juin 2007, Brice Goglin a écrit : > Hi, > > About 5 years ago, you reported a bug to the Debian BTS regarding a > segfault of the X server when memory is tight and a Xv application is > running on a Rage 128 board. Did you reproduce this problem recently? > With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I > will close this bug in the next weeks. You can close it. > > Thanks, > Brice pgpV5rvFilWT5.pgp Description: PGP signature
Bug#407036: xserver-xorg: Server crashes each time after hibernate with suspend2
Hi Brice, ssh from another machine and screen is a good idea thanks. I tried that and gdb attaches properly to X but when I suspend the laptop it crashes (ie the whole machine crashes, not just the X server; I had to force a power down then power up again). That is even with the old xserver that normally suspends ok. I also tried again for a core file (I didn't have ulimit set properly and now I do), but no core file is created when the resume crashes my laptop (using the latest xserver-xorg-core). I do have the NoTrapSignals option set and it is recognized in the Xorg log file. So run out of things to try again ... Bruce On Sun, Jun 17, 2007 at 01:31:38PM +0200, Brice Goglin wrote: > Bruce MacDonald wrote: > > Hi, Any ideas for debugging this problem? I can't login from a second > > machine since the resume script has to remove and reinstall the > > network driver for both wired and wireless. I couldn't get a core dump > > by setting the NoTrapSignals option in ServerFlags. I tried a script > > suggested on x.org for server debugging but X would not start at all, > > from > > > > http://wiki.x.org/wiki/Development/Documentation/ServerDebugging > > > > But I've never debugged the X server before. > > > > Bruce > > > > One idea would be to keep gdb in a screen that you attach/detach from ssh: > * login through ssh before suspend, launch "screen", and attach "gdb -p > $(pidof X)" from there > * suspend/resume, and make sure the network is back > * login again by ssh again, reacquire the screen with something like > "screen -rd" > * once X has crashed, work in gdb with 'bt full' or so > > Somebody put some Debian-specific hints about debugging (including with > a coredump) at http://wiki.debian.org/XStrikeForce/XserverDebugging by I > never actually tried it. > > Brice > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#368367: xserver-xorg: [dexconf] xorg.conf a zero file if keyboard detection failed at install
On Sat 16 Jun 2007, Brice Goglin wrote: > > Did you recently reproduce this problem about xorg.conf being > incorrectly generated when keyboard detection failed? Still get an empty > xorg.conf? The submitter (Marc in CC:) didn't try recently. It would be > good to know if it's working better with latest Xorg packages. The last fresh install I did was a laptop recently, installing from scratch with an etch netinst cd, and I don't recall getting any questions about keyboard detection, it just worked. So I don't know whether the bug may still be triggered under de circumstances described in the bug report. Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#421854: xcb lock assertion with opera
Julien Cristau <[EMAIL PROTECTED]> writes: > For what it's worth, using the current libx11-6 package from > experimental and opera_9.21-20070510.6-shared-qt_en_i386.deb from > www.opera.com, I'm unable to reproduce the crash. Could the assertion > failure be related to the known java bug with xcb [0], rather than a > problem in opera itself? It's certainly a possible explanation. > I also get these messages when starting opera: > ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: ignored. > ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored. > These are most likely not important. It's an old workaround for java crashing due to having libraries loaded in the wrong order (libXt before libXm). Things have changed in various ways since we did that... (I think the crash problem is still there in principle, but it doesn't seem to be widespread.) eirik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429839: xserver-xorg-input-synaptics: Fails to respond to "on-the-fly" config changes viaa synclient, qsynaptics, etc
Package: xserver-xorg-input-synaptics Version: 0.14.7~git20070517-1 Severity: important The problem started after a recent update in Testing, and also applies to unstable. I can only alter touchpad config (eg enable/disable touchpad) by editing xorg.conf and restarting x. I have two laptops, a sony and a toshiba, and the problem applies to both of them. Here's xorg.conf on the sony: Section "Files" FontPath"/usr/share/X11/fonts/misc" FontPath"/usr/share/X11/fonts/cyrillic" FontPath"/usr/share/X11/fonts/100dpi/:unscaled" FontPath"/usr/share/X11/fonts/75dpi/:unscaled" FontPath"/usr/share/X11/fonts/Type1" FontPath"/usr/share/X11/fonts/100dpi" FontPath"/usr/share/X11/fonts/75dpi" FontPath"/usr/share/fonts/X11/misc" # path to defoma fonts FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load"i2c" Load"bitmap" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"type1" Load"vbe" Load"dbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" Option "XkbOptions""lv3:ralt_switch" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ExplorerPS/2" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "SHMConfig" "true" EndSection Section "Device" Identifier "Intel Corporation Mobile Integrated Graphics Controller" Driver "i810" BusID "PCI:0:2:0" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Intel Corporation Mobile Integrated Graphics Controller" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Depth 1 Modes "1280x800" EndSubSection SubSection "Display" Depth 4 Modes "1280x800" EndSubSection SubSection "Display" Depth 8 Modes "1280x800" EndSubSection SubSection "Display" Depth 15 Modes "1280x800" EndSubSection SubSection "Display" Depth 16 Modes "1280x800" EndSubSection SubSection "Display" Depth 24 Modes "1280x800" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "Synaptics Touchpad" EndSection Section "DRI" Mode0666 EndSection -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-input-synaptics depends on: ii libc6 2.5-9+b1 GNU C Library: Shared libraries ii libx11-62:1.0.3-7X11 client-side library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxi6 1:1.0.1-4X11 Input extension library ii xserver-xorg-core 2:1.3.0.0.dfsg-6 X.Org X server -- core server xserver-xorg-input-synaptics recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429839: xserver-xorg-input-synaptics: Fails to respond to "on-the-fly" config changes viaa synclient, qsynaptics, etc
On Wed, Jun 20, 2007 at 10:04:08AM -0500, James Allingham wrote: > Package: xserver-xorg-input-synaptics > Version: 0.14.7~git20070517-1 > Severity: important > > > The problem started after a recent update in Testing, and also applies > to unstable. I can only alter touchpad config (eg enable/disable > touchpad) by editing xorg.conf and restarting x. I have two laptops, a > sony and a toshiba, and the problem applies to both of them. Ah, yes that should be fixed with the next upload. synclient is not aware of the new driver options. About qsynaptics and friends, they will need to be aligned as well. Will ping their maintainers tomorrow. Thanks -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#154204: marked as done (xserver-xfree86: [ati/r128] SEGV when memory tight and using Xv applications on Rage 128 RF rev 0)
Your message dated Wed, 20 Jun 2007 19:24:03 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#154204: xserver-xfree86: [ati/r128] SEGV when memory tight and using Xv applications on Rage 128 RF rev 0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xfree86 Version: 4.1.0-16 Severity: important When I run video apps that use the xv extension (mostly use self compiled mplayer 0.90pre5, also happens with packaged xine), the X servers crashes about 1 in 10 times. It seems to be worse when I have more progams open, although I don't think it is affected by load other than memory. I think, also, it is memory related, since I used to have 384 MB RAM in my home machine (this one), but took some of the memory to university, so it only has 128MB now. Before I took the memory out, it never crashed. I can't be completely certain that no software had changed, but I am running woody, which has not changed much in the last 2 months since the problem started. I have run a RAM tester for a long time, and found no errors. My system is a Duron 700, 128Mb PC133 memory, VIA KT133 chipset, 686b southbridge, Powercolor AGP ATI RAGE 128 GL card, PCI RTL 8029 (ne2k compat) network card, Asus PC-200 (NCR/Symbios 53c810a) PCI SCSI card, ISA SB-16 sound card. Have tried using the build in sound with sb16 removed, no change. I am running woody, with a stock (as in Linus, not Debian) 2.4.18 kernel, using atyfb to give me 1024x768 fb consoles. The kernel is built with K7 optimisations, and all the neccesary stuff to make DRI work. After the crashes the machine is completely usable still, no futzed up vid modes. A nice and clean crash as far as they go :) Thanks Neilen P.S. I'm gonna try the 4.2 Xfree if it is sid yet and see if it helps. 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RF 01:00.0 Class 0300: 1002:5246 # XF86Config-4 (XFree86 server configuration file) generated by Dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config manual page. # (Type "man XF86Config" at the shell prompt.) Section "Files" # FontPath"unix/:7110"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "ServerFlags" EndSection Section "Module" Load"ddc" Load"GLcore" Load"dbe" Load"dri" Load"extmod" Load"glx" Load"pex5" Load"record" Load"xie" Load"bitmap" Load"freetype" Load"speedo" Load"type1" Load"vbe" Load"int10" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc101" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/ttyS0" Option "Protocol" "MouseMan" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Ati Rage 128 GL 32Mb" Driver "ati" EndSection Section "Monitor" Identifier "Proline 17" HorizSync 30-68 VertRefresh 50-85 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Ati Rage 128 GL 32Mb" Monit
Bug#368367: marked as done (xserver-xorg: [dexconf] xorg.conf a zero file if keyboard detection failed at install)
Your message dated Wed, 20 Jun 2007 19:27:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#368367: xserver-xorg: [dexconf] xorg.conf a zero file if keyboard detection failed at install has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xorg Version: 7.0.19 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Upon a fresh installation of X11 7.0, dexconf produces a zero-lenght xorg.conf, whenever automatic keyboard detection failed (debconf:high). A zero file is also produced at debconf:medium priority. At this priority, dexconf DOES inform the user that configuration failed and suggests running "dpkg-reconfigure xserver-xorg", but doing exactly that fixes nothing: the post-install script informs that is has NOT updated the config, because it thinks that /etc/X11/X has been modified (which is not the case). Trying "dpkg-reconfigure -p low xserver-xorg" does not solve it either; the user is still left with a zero-lenght xorg.conf. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEcIpMeXr56x4Muc0RAt/LAJ9PQpYcWXG6MsKO9jnDp8PxGBtQgACaAgEo GfK7TNFBBXs8fzAwYgkG1Qk= =IFax -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Paul Slootman wrote: > On Sat 16 Jun 2007, Brice Goglin wrote: > >> Did you recently reproduce this problem about xorg.conf being >> incorrectly generated when keyboard detection failed? Still get an empty >> xorg.conf? The submitter (Marc in CC:) didn't try recently. It would be >> good to know if it's working better with latest Xorg packages. >> > > The last fresh install I did was a laptop recently, installing from > scratch with an etch netinst cd, and I don't recall getting any > questions about keyboard detection, it just worked. So I don't know > whether the bug may still be triggered under de circumstances described > in the bug report. > Ok I am closing for now then. But, since neither of you guys did actually try to reproduce this exact problem, if anybody ever reproduces, he should feel free to reopen. Brice --- End Message ---
Bug#101002: xserver-xfree86: [ati/atimisc] pointer leaves trails on Mach64 GI rev 92
* Brice Goglin <[EMAIL PROTECTED]> [2007:06:20:19:43:19+0200] scribed: > Hi, > > About 6 years ago, you reported a bug to the Debian BTS regarding Xorg > with the ATI driver making pointer trails on a mach64 board. Did you > reproduce this problem recently? With Xorg/Etch? With latest > xserver-xorg-core and drivers? If not, I will close this bug in the next > weeks. > > Thanks, > Brice No, I have not witnessed this problem recently. I have not run such hardware in several years. -- Best Regards, mds mds resource - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Bug#112518: xserver-xfree86: [ati/atimisc] right-clicking in ddd randomly puts my monitor into powersave on Mach64 GT
Hi, About 6 years ago, you reported a bug to the Debian BTS regarding right-clicking in ddd randomly putting the monitor into powersave on a mach64 board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#149650: xserver-xfree86: [ati/atimisc] LCD backlight level mismanaged on Mach64 LB rev 220
Hi, About 5 years ago, you reported a bug to the Debian BTS regarding the backlight level of a LCD being mismanaged on a mach64 board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#251506: xserver-xfree86: [ati/radeon] Xinerama malfunctions on Radeon 9000/PRO If [regression from 4.3.0.dfsg.1-1]
Hi, About 3 years ago, you reported a bug to the Debian BTS regarding xinerama not working anymore on a Radeon 9000 Pro after upgrading XFree86. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#149650: xserver-xfree86: [ati/atimisc] LCD backlight level mismanaged on Mach64 LB rev 220
Uh, ohh. I still have that laptop but I do not use it anymore. I cannot remember that I had this problem in the last years I used it but I cannot tell anymore which server or driver I used then. I think it is safe to close the bug if noone else has reported something similar... Cheers, Olaf Am 20.06.2007 um 19:50 schrieb Brice Goglin: Hi, About 5 years ago, you reported a bug to the Debian BTS regarding the backlight level of a LCD being mismanaged on a mach64 board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- Dr. Olaf Stetzer ETH, Institute for Atmospheric and Climate Science Universitätsstrasse 16, CHN O16.3 CH-8092 Zurich, Switzerland Tel: +41 (0)44 63-36161 FAX: +41 (0)44 63-31058
Bug#110608: marked as done (xserver-xfree86: [ati/atimisc] display corruption at depth 24 on Mach64 LM rev 100)
Your message dated Wed, 20 Jun 2007 19:49:01 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#110608: xserver-xfree86: [ati/atimisc] display corruption at depth 24 on Mach64 LM rev 100 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xfree86 Version: 4.1.0-2 Every once in a while (I'm not sure why) a strange sort of image display error will pop up on my laptop (a Dell Inspiron 3800). The best way I could describe it would be that several vertical lines of red from the beginning of an object being displayed get displayed past the end of said object. For example, if I have something highlighted in my email client, at the start of the highlighted color one can see several very light blue lines like so: | | | | | | with sometimes varying height (this is unlikely, though), about one or two pixels apart, each a pixel wide. And just past the end of the highlighted color, one can see several very light red lines that follow the exact same pattern as the blue. This phenomenon occurs with several things on the screen; I can't tell exactly what determines which objects being displayed are to receive this. Taking a screenshot with the Gimp doesn't work; the pattern will show up on the screenshot only if it's showing up everywhere else at the same time :). This tends to flicker on and off seemingly randomly once it starts happening; I know of no way to remove or stop it. It only just started happening yesterday (as far as I know I changed nothing that day), and I've been running this version of the X server for about two and a half weeks now, so I'm rather mystified. I don't think this is a problem with the hardware; it doesn't show in the console or under Win98 insofar as I've tested. I intend to keep checking for it, though. /etc/X11/XF86Config-4: # XF86Config-4 (XFree86 server configuration file) generated by Dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config manual page. # (Type "man XF86Config" at the shell prompt.) Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "ServerFlags" EndSection Section "Module" Load"ddc" Load"GLcore" Load"dbe" Load"dri" Load"extmod" Load"glx" Load"pex5" Load"record" Load"xie" Load"bitmap" Load"freetype" Load"speedo" Load"type1" Load"vbe" Load"int10" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "PS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "ATI Rage Mobility" Driver "ati" Option "AGPMode" "1" Option "UseCCEFor2D" "false" EndSection Section "Monitor" Identifier "Dell Inspiron 3800 Display" HorizSync 30-60 VertRefresh 50-75 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Rage Mobility" Monitor
Bug#254288: xserver-xfree86: [ati/atimisc] poor support for color depths 16 and 24 on 264VT [Mach64 VT] rev 64
Hi, About 3 years ago, you reported a bug to the Debian BTS regarding color depths 16 and 24 not being well supported on a mach64 board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#112518: marked as done (xserver-xfree86: [ati/atimisc] right-clicking in ddd randomly puts my monitor into powersave on Mach64 GT)
Your message dated Wed, 20 Jun 2007 20:05:25 +0200 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: ddd Version: 1:3.3.1-4 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Every one and a while, when I right-click DDD's data-display area to bring up the popup menu, my monitor goes black. If I hold the mouse down for a while, my monitor (a ViewSonic GS790) says it's gone into DPMS. The second I let go of the mouse, all is back to normal. I can't find a way to reproduce the problem consistently, other than `use ddd for a while'. I just tried right-clicking repeatedly; no luck. At first I thought it was due to too much caffeine, or maybe staying up too late. But no, it happens even when I'm not tired, and have only had Sprite. [ I bet this qualifies as the oddest bug report you've ever gotten. No, I'm not making it up... I wish I were, because it's quite annoying. ] [ If this turns out to be an bug elsewhere, feel free to reassign... ] - -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux bohr 2.4.7 #3 SMP Fri Jul 27 17:05:49 EDT 2001 i686 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages ddd depends on: ii lesstif1 1:0.93.0-1OSF/Motif implementation released ii libc6 2.2.4-1 GNU C Library: Shared libraries an ii libelfg0 0.7.0-1 an ELF object file access library ii libncurses55.2.20010318-3Shared libraries for terminal hand ii libreadline4 4.2-5 GNU readline and history libraries ii libstdc++2.10-glibc2.2 1:2.95.4-0.010902 The GNU stdc++ library ii libxaw74.1.0-5 X Athena widget set library ii xlibs 4.1.0-5 X Window System client libraries -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7pZha5lsmI6uA7bQRAsOTAKCGFfErkW4SEqAIaQq4oVj+Dg2PtwCfS353 sjVD8OvxyBmYnVZSVLUbCR0= =BqkL -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Closing since the submitter's address is invalid. If anybody ever reproduces this problem, feel free to reopen. Brice --- End Message ---
Bug#101002: marked as done (xserver-xfree86: [ati/atimisc] pointer leaves trails on Mach64 GI rev 92)
Your message dated Wed, 20 Jun 2007 20:05:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#101002: xserver-xfree86: [ati/atimisc] pointer leaves trails on Mach64 GI rev 92 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: XFree86 Version 4.0.3 / X Window System Version: 4.0.3 Debian ==> Two nights ago, I did an apt-get dist-upgrade from potato 2.2r2 to testing, &c. The system boots properly; but, X does *not* work properly -- see attached XFree86.0.log. What to do? -- Best Regards, mds mds resource 888.250.3987 "Dare to fix things before they break . . . " "Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . " XFree86 Version 4.0.3 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 16 March 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.19 i686 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Fri Jun 15 01:58:26 2001 (==) Using config file: "/etc/X11/XF86Config-4" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "ViewSonic PT813" (**) | |-->Device "Generic Video Card" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (**) |-->Input Device "Configured Mouse" (**) |-->Input Device "Generic Mouse" (**) FontPath set to "unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/cyrillic,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.0.3, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.0.3, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000900c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1237 card , rev 02 class 06,00,00 hdr 00 (II) PCI: 00:07:0: chip 8086,7000 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7010 card , rev 00 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7020 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:10:0: chip 9004,8178 card , rev 00 class 01,00,00 hdr 00 (II) PCI: 00:11:0: chip 1002,4749 card 1002,4749 rev 5c class 03,00,00 hdr 00 (II) PCI: 00:12:0: chip 10b7,9055 card 10b7,9055 rev 34 class 02,00,00 hdr 00 (II) PCI: 00:13:0: chip 10b7,9055 card 10b7,9055 rev 24 class 02,00,00 hdr 00 (II) PCI: 00:14:0: chip 10b7,9055 card 10b7,9055 rev 30 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.0.3, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0
Bug#149650: marked as done (xserver-xfree86: [ati/atimisc] LCD backlight level mismanaged on Mach64 LB rev 220)
Your message dated Wed, 20 Jun 2007 20:08:18 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#149650: xserver-xfree86: [ati/atimisc] LCD backlight level mismanaged on Mach64 LB rev 220 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xfree86 Version: 4.1.0-16 I am running woody on a notebook with this videocard: ATI Technologies Inc 3D Rage LT Pro AGP-133 (rev dc) While I got fewer troubles with this card with each new release of the X-packages I now have a problem which seems to be new: When the notebook is inactive for a longer time, the LCD-panel's backlight is not restored correctly after resuming from the X-screensaver (I mean the default screen-blanking of X after a while of inactivity) . I have not configured any other screensaver. What actually happens is that when I move the mouse or hit a key after a long time of "black-screen) the panels nacklight shorty lightens an then falls back to black. I think that its just the state of the backlight which is handled incorrectly here. Interestingly this happens only when a really long time passed after the xserver blanked the screen. Branden, if its unclear what I want to say, please contact me! Thanks, Olaf (possibly this is a known bug which is already fixed in 4.2?) -- "Jazz is not dead, it just smells funny!" Frank Zappa --- End Message --- --- Begin Message --- Olaf Stetzer wrote: > Uh, ohh. I still have that laptop but I do not use it anymore. I cannot > remember that I had this problem in the last years I used it but I cannot > tell anymore which server or driver I used then. I think it is safe to > close the > bug if noone else has reported something similar... > > Cheers, > > Olaf Ok, closing then, thanks for the quick reply. If anybody ever reproduces this problem, feel free to reopen. Brice --- End Message ---
Bug#397197: DPMS-bug test scenario
I'm pleased to announce a reliable and fast test scenario: $ xset dpms 10 20 30 [wait 10 seconds] [screen goes blank (DPMS gets active)] $ xset -dpms [no DPMS kicks in, not even after 10 seconds] $ xset +dpms [wait 10 seconds] What I now expect is that DPMS suspends (or actually "standbys") the screen, but that does not happen. The screen stays visible, passing 10, 20, 30 and more seconds. Can anybody confirm that on other systems? I run X Window System Version 1.3.0 Release Date: 19 April 2007 The -dpms and +dpms (or probably something equivalent) gets used by video players to avoid black screens while watching a movie... I use mplayer and checked with "xset q" -> "DPMS is Disabled" but only while mplayer is running. That means for me that after the first invocation of mplayer DPMS does not work anymore. Greetings, Robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#273655: xserver-xfree86: [ati/radeon] blender crash
Hi, About 3 years ago, you reported a bug to the Debian BTS regarding a crash of blender on an ATI board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#268014: xserver-xfree86: [ati/atimisc] 'x11perf -seg500' reveals buggy line drawing on 3D Rage LT Pro rev 220
Hi, About 3 years ago, you reported a bug to the Debian BTS regarding x11perf -seg500 revealing a buggy line drawing on a 3D Rage Pro board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284245: xserver-xfree86: [ati/radeon] X server leaks memory when Xinerama enabled on Radeon RV100 QY [Radeon 7000/VE] rev 0
Hi, About 3 years ago, you reported a bug to the Debian BTS regarding a memory leak in the X server when Xinerama is enabled on a Radeon 7000 board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#145412: xserver-xfree86: [ati/atimisc] CPIO support disabled on ia64 (Debian patch #450), but MMIO not supported for Mach64 GR rev 39
On Tue, Jun 19, 2007 at 10:34:53PM +0200, Bruno Rodrigues wrote: > This bug was reported five years ago! I have no IA64 anymore to test > this, so from me you can safely close this bug with a can't-reproduce > or similar. > Last I tried (about a year ago) it was still the case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#289584: marked as done (xserver-xfree86: [ati/radeon] does not support unknown chipset (0x5960) rev 1 [Radeon 9250])
Your message dated Wed, 20 Jun 2007 20:31:48 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#289584: xserver-xfree86: [ati/radeon] does not support unknown chipset (0x5960) rev 1 [Radeon 9250] has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xfree86 Version: 4.3.0.dfsg.1-8 Severity: normal I have recently purchased a new P4 machine with a Gigabyte 8S648FX-RZ(-C) motherboard and a GV-R925128T Graphics accelerator card with (reportadly) the ATI Radeon 9250 chip. I installed the sytem from Woody debian 3.0r0 and updates from debian stable security updates and Sarge CD1&2 3/1/2005. The vesa driver will give a half hieght screen in the centre and about seven images across the screen. The ati driver does not work at all. the radeon driver can be manually modprobe'd in to work but does not load in from modules. radeonfs is loaded by system. -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 20 2005-01-05 12:23 /etc/X11/X -> /usr/bin/X11/XFree86 -rwxr-xr-x 1 root root 1745484 2004-09-28 22:09 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) /etc/X11/XF86Config-4 unchanged from checksum in /var/lib/xfree86/XF86Config-4.md5sum. XFree86 X server configuration file status: -rw-r--r-- 1 root root 3331 2005-01-08 19:44 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: # XF86Config-4 (XFree86 X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # This file is automatically updated on xserver-xfree86 package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xfree86 # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom # md5sum /etc/X11/XF86Config-4 >/var/lib/xfree86/XF86Config-4.md5sum # dpkg-reconfigure xserver-xfree86 Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/CID" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc101" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/ttyS0" Option "Protocol" "Microsoft" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifie
Bug#260171: Screen artifacts/flicker when using Radeon IGP with an external CRT
Hi, About 3 years ago, you reported a bug to the Debian BTS regarding some artifacts and the screen flickering when using a Radeon IGP board with an external CRT monitor. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#264228: X-Server crashes, when playing a mpeg video
Hi, About 3 years ago, you reported a bug to the Debian BTS regarding a crash of the X server while playing a mpeg video. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#261104: xserver-xfree86: [radeon] 9600 Dual DVI - false-color display on secondary head
Hi, About 3 years ago, you reported (or replied to) a bug in the Debian BTS regarding some wrong colors being displayed on the secondary head with a dual DVI Radeom 9600 board. Did any of you guys reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#145412: xserver-xfree86: [ati/atimisc] CPIO support disabled on ia64 (Debian patch #450), but MMIO not supported for Mach64 GR rev 39
Kyle McMartin wrote: > Last I tried (about a year ago) it was still the case. > with XFree86 (for instance with Debian Sarge) or with Xorg? The original bug was apparently related to a patch that we had for XFree86, but we don't seem to have anything similar anymore in Xorg. So the behavior might be very different now. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#320828: xserver-xorg: Sometimes crashes in ATI driver when resizing XV window
Hi, About 2 years ago, you reported a bug to the Debian BTS regarding a crash of the X server when resizing a XV window on an ATI board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#77025: marked as done (xserver-xfree86: [ati/atimisc] exhibits transient streaking during opaque moves on Mach64 GB rev 92)
Your message dated Wed, 20 Jun 2007 19:40:00 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#77025: xserver-xfree86: [ati/atimisc] exhibits transient streaking during opaque moves on Mach64 GB rev 92 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xfree86 Version: 4.0.1-3 Severity: normal Unfortunately there's no documentation of any ATI driver options that might help fix the transient streaking. It is most visible when opaque-dragging a large xterm window around. If this were an S3 card, I'd fix the problem with the "fifo_aggressive" option. -- System Information Debian Release: woody Architecture: i386 Kernel: Linux genki 2.2.17 #1 Sat Sep 16 22:35:51 EDT 2000 i686 Versions of packages xserver-xfree86 depends on: ii libc6 2.2-1 GNU C Library: Shared libraries an ii xserver-common4.0.1-3files and utilities common to all ii zlib1g1:1.1.3-11 compression library - runtime # XF86Config-4 (XFree86 server configuration file) generated by Dexter, the # Debian X Configuration tool. # # Edit this file with caution, and see the XF86Config manual page. # (Type "man XF86Config" at the shell prompt.) Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/75dpi" FontPath"/usr/lib/X11/fonts/100dpi" EndSection Section "ServerFlags" EndSection Section "Module" Load"ddc" Load"GLcore" Load"dbe" Load"dri" Load"extmod" Load"glx" Load"pex5" Load"record" Load"xie" Load"bitmap" Load"freetype" Load"speedo" Load"type1" Load"vbe" Load"int10" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "CorePointer" Option "Protocol" "PS/2" Option "Device""/dev/psaux" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "Generic Graphics Device" Driver "ati" EndSection Section "Monitor" Identifier "Generic Monitor" HorizSync 30-94 VertRefresh 50-75 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Generic Graphics Device" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Depth 1 Modes "1600x1200" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1600x1200" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1600x1200" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1600x1200" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1600x1200" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1600x1200" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "D
Bug#327098: Xserver-xorg radeon dual head monitor detection problem
Hi, About 2 years ago, you reported a bug to the Debian BTS regarding dual-head detection not working anymore with Xorg 6.8 and the ATI driver. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#101002: xserver-xfree86: [ati/atimisc] pointer leaves trails on Mach64 GI rev 92
Hi, About 6 years ago, you reported a bug to the Debian BTS regarding Xorg with the ATI driver making pointer trails on a mach64 board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364426: xserver-xorg-video-ati: display completely garbled with DRI, can even hard lock
Hi, Brice Goglin <[EMAIL PROTECTED]> wrote: > About a year ago, you reported a bug to the Debian BTS regarding the > display being garbled when DRI is enabled on an ATI board. Did you > reproduce this problem recently? With Xorg/Etch? With latest > xserver-xorg-core and drivers? If not, I will close this bug in the next > weeks. You can close the bug: I'm using Xorg from etch with the same graphic adapter, DRI enabled and it works fine. Thanks for taking care. Regards, -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358349: xserver-xorg: Xorg 6.9.0 blackens the screen on Samsung P30 laptop
Hi Vincent! About a year ago, you reported a bug to the Debian BTS regarding Xorg 6.9 giving a black screen on a Samsung P30 laptop with an ATI board while 6.8.2 worked. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364426: marked as done (xserver-xorg-video-ati: display completely garbled with DRI, can even hard lock)
Your message dated Thu, 21 Jun 2007 00:08:57 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#364426: xserver-xorg-video-ati: display completely garbled with DRI, can even hard lock has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xorg-video-ati Version: 1:6.5.7.3-3 Severity: important Hi, When commenting out the 'Load "dri"' line in the Module section of /etc/X11/xorg.conf, X works mostly fine. However, when uncommenting this line, I experience severe problems: - the display is completely garbled (and unstable: sort of flickering, etc.); the best I can do is recognize the color of the title bars of windows that tells me the window manager (wmaker) is running. - when typing the key sequence that should end my X session properly (by quitting wmaker), the whole system hard locks and I have to hit the reset button (I only tried this once!). Previously, just after my upgrade to X.org, my window manager was not started when running "startx" (because of a .Xauthority problem), and I could kill the X server properly with Ctrl-Alt-Backspace without triggering a hard lock. My kernel is compiled from kernel-source 2.4.27-10sarge2 (I am using a sid chroot). X was running fine with DRI enabled before I upgraded to X.org. lspci -v says for the video card: :03:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA]) Subsystem: C.P. Technology Co. Ltd: Unknown device 2072 Flags: bus master, stepping, 66MHz, medium devsel, latency 32, IRQ 11 Memory at d000 (32-bit, prefetchable) [size=128M] I/O ports at d000 [size=256] Memory at de00 (32-bit, non-prefetchable) [size=64K] Expansion ROM at [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Capabilities: [50] Power Management version 2 I am attaching the Xorg.0.log file for the DRI-enabled run that caused the hard lock I reported above. Thanks for any help regarding these problems. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.4.27 Locale: LANG=en_US.ISO-8859-15, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages xserver-xorg-video-ati depends on: ii libc6 2.3.6-7GNU C Library: Shared libraries ii xserver-xorg-core 1:1.0.2-5 X.Org X server -- core server xserver-xorg-video-ati recommends no packages. -- no debconf information _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/florent:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.12-1-686 i686 Current Operating System: Linux florent 2.4.27 #1 Fri Mar 24 10:25:27 CET 2006 i686 Build Date: 16 March 2006 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 23 13:16:38 2006 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Eizo FlexScan L767" (**) | |-->Device "ATI Radeon RV100 QY [Radeon 7000/VE]" (**) |-->Input Device "Generic Keyboard" (**) |-->Input Device "Configured Mouse" (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (**) FontPath set to "/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,/usr/share/fonts/X11/misc/,/usr/share/fonts/X11/TTF/,/usr/share/fonts/X11/OTF,/usr/share/fonts/X11/Type1/,/usr/share/fonts/X11/CID/,/usr/share/fonts/X11/100dpi/,/usr/share/fonts/X11/75dpi/" (==) RgbPath set to "/usr/share/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Drive
Bug#350341: xserver-xorg: screen corrupted (using Radeon 9100 IGP)
Hi, About a year ago, you reported a bug to the Debian BTS regarding the screen being corrupted on a Radeon 9100 IGP board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327099: marked as done (Xserver-xorg radeon dual head monitor detection problem)
Your message dated Thu, 21 Jun 2007 00:08:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xorg Version: 6.8.2.dfsg.1-6 Upgrading from XFree86 to Xorg broke my dual head xinerama setup. This same setup worked perfectly well with XFree86 4.3 lspci: :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Radeon 7000/Radeon VE Flags: bus master, stepping, 66MHz, medium devsel, latency 64 Memory at c000 (32-bit, prefetchable) [size=128M] I/O ports at b800 [size=256] Memory at cfef (32-bit, non-prefetchable) [size=64K] Expansion ROM at bfc0 [disabled] [size=128K] Capabilities: The following is the relevant info from Xorg.0.log: ... (II) RADEON(0): Connector0: DDCType-2, DACType-1, TMDSType-0, ConnectorType-3 (II) RADEON(0): Connector1: DDCType-3, DACType-0, TMDSType--1, ConnectorType-2 (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "DDC:ddc2" removed. (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "DDC:ddc2" removed. (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "DDC:ddc2" removed. (II) RADEON(0): DDC Type: 2, Detected Type: 0 (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "DDC:ddc2" removed. (II) RADEON(0): DDC Type: 3, Detected Type: 1 (II) RADEON(0): EDID data from the display on port 2--- (II) RADEON(0): Manufacturer: BNQ Model: 7659 Serial#: 3770 (II) RADEON(0): Year: 2004 Week: 32 (II) RADEON(0): EDID Version: 1.3 (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V (II) RADEON(0): Sync: Separate Composite (II) RADEON(0): Max H-Image Size [cm]: horiz.: 34 vert.: 27 (II) RADEON(0): Gamma: 2.20 (II) RADEON(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display ... (--) Chipset ATI Radeon VE/7000 QY (AGP/PCI) found (--) Chipset ATI Radeon VE/7000 QY (AGP/PCI) found ... (II) Loading sub module "radeon" (II) LoadModule: "radeon" (II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o (II) Loading sub module "radeon" (II) LoadModule: "radeon" (II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o ... (II) RADEON(0): Monitor name: BenQ FP731 (II) RADEON(0): (II) RADEON(0): Primary: Monitor -- CRT Connector -- VGA DAC Type -- Primary TMDS Type -- NONE DDC Type -- VGA_DDC (II) RADEON(0): Secondary: Monitor -- NONE Connector -- DVI-I DAC Type -- TVDAC/ExtDAC TMDS Type -- Internal DDC Type -- DVI_DDC ... (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled ... (WW) RADEON(1): Only one monitor detected, Second screen will NOT be created ... --- End Message --- --- Begin Message --- Closing since the submitter's address is invalid. If anybody ever reproduces this problem, feel free to reopen. Brice --- End Message ---
Bug#347956: xserver-xorg: [Radeon X800 GTO] does not restore console on failed startup
Hi, About a year ago, you reported a bug to the Debian BTS regarding the console not being restored properly when X fails to start on a Radeon X800GTO board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327098: marked as done (Xserver-xorg radeon dual head monitor detection problem)
Your message dated Thu, 21 Jun 2007 00:08:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xorg Version: (6.8.2.dfsg.1-6, 6.8.2.dfsg.1-5) Upgrading from XFree86 to Xorg broke my dual head xinerama setup. This same setup worked perfectly well with XFree86 4.3 lspci: :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Radeon 7000/Radeon VE Flags: bus master, stepping, 66MHz, medium devsel, latency 64 Memory at c000 (32-bit, prefetchable) [size=128M] I/O ports at b800 [size=256] Memory at cfef (32-bit, non-prefetchable) [size=64K] Expansion ROM at bfc0 [disabled] [size=128K] Capabilities: The following is the relevant info from Xorg.0.log: ... (II) RADEON(0): Connector0: DDCType-2, DACType-1, TMDSType-0, ConnectorType-3 (II) RADEON(0): Connector1: DDCType-3, DACType-0, TMDSType--1, ConnectorType-2 (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "DDC:ddc2" removed. (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "DDC:ddc2" removed. (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "DDC:ddc2" removed. (II) RADEON(0): DDC Type: 2, Detected Type: 0 (II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) RADEON(0): I2C device "DDC:ddc2" removed. (II) RADEON(0): DDC Type: 3, Detected Type: 1 (II) RADEON(0): EDID data from the display on port 2--- (II) RADEON(0): Manufacturer: BNQ Model: 7659 Serial#: 3770 (II) RADEON(0): Year: 2004 Week: 32 (II) RADEON(0): EDID Version: 1.3 (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V (II) RADEON(0): Sync: Separate Composite (II) RADEON(0): Max H-Image Size [cm]: horiz.: 34 vert.: 27 (II) RADEON(0): Gamma: 2.20 (II) RADEON(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display ... (--) Chipset ATI Radeon VE/7000 QY (AGP/PCI) found (--) Chipset ATI Radeon VE/7000 QY (AGP/PCI) found ... (II) Loading sub module "radeon" (II) LoadModule: "radeon" (II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o (II) Loading sub module "radeon" (II) LoadModule: "radeon" (II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o ... (II) RADEON(0): Monitor name: BenQ FP731 (II) RADEON(0): (II) RADEON(0): Primary: Monitor -- CRT Connector -- VGA DAC Type -- Primary TMDS Type -- NONE DDC Type -- VGA_DDC (II) RADEON(0): Secondary: Monitor -- NONE Connector -- DVI-I DAC Type -- TVDAC/ExtDAC TMDS Type -- Internal DDC Type -- DVI_DDC ... (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled ... (WW) RADEON(1): Only one monitor detected, Second screen will NOT be created ... --- End Message --- --- Begin Message --- Closing since the submitter's address is invalid. If anybody ever reproduces this problem, feel free to reopen. Brice --- End Message ---
Bug#354043: general: Failed to detect secondary monitor, MergedFB/Clone mode disabled
Hi, About a year ago, you reported a bug to the Debian BTS regarding a failure to detect the secondary monitor and mergedfb/clone mode being disabled on a Radeon board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348830: xserver-xorg: radeon driver rejects all resolutions (strange clock range) and have to exit
Hi, About a year ago, you reported a bug to the Debian BTS regarding the Radeon driver rejecting all resolutions. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348330: [radeon]: Second head stays black with traditional dual head setup
Hi, About a year ago, you reported a bug to the Debian BTS regarding the second head staying black with a regular dual head setup on a Radeon board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#360879: xserver-xorg: Xorg's radeon driver does not seem to support DVI on docking station
Hi, About a year ago, you reported a bug to the Debian BTS regarding Xorg's radeon driver having problem with the DVI output of your docking station. Did you reproduce this problem recently? With Xorg/Etch? With latest ATI driver 6.6.192 is currently in experimental? Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#346471: xserver-xorg: radeon M9 gets slower after a suspend/resume cycle?
Hi, About a year ago, you reported a bug to the Debian BTS regarding X being slower on Radeon M9 after suspend/resume. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350341: xserver-xorg: screen corrupted (using Radeon 9100 IGP)
On Thu, Jun 21, 2007 at 12:43:40AM +0200, Brice Goglin wrote: > About a year ago, you reported a bug to the Debian BTS regarding the > screen being corrupted on a Radeon 9100 IGP board. Did you reproduce > this problem recently? With Xorg/Etch? With latest xserver-xorg-core and > drivers? If not, I will close this bug in the next weeks. I don't believe I've actually seen the bug again since that day, so I assume it's either fixed or just incredibly unlikely. (And I've been tracking Sid on that machine that whole time.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#346471: xserver-xorg: radeon M9 gets slower after a suspend/resume cycle?
It's definetely not happening with etch: M9 is pretty happy after a supend/resume cycle. thanks graziano On Thu, Jun 21, 2007 at 12:36:48AM +0200, Brice Goglin wrote: > Hi, > > About a year ago, you reported a bug to the Debian BTS regarding X being > slower on Radeon M9 after suspend/resume. Did you reproduce this problem > recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If > not, I will close this bug in the next weeks. > > Thanks, > Brice > > -- +---+--+ | Graziano Obertelli| CS Dept. Rm 102 | | [EMAIL PROTECTED] | University of California | | (805) 893-5212| Santa Barbara, CA 93106 | +---+--+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#421523: xterm: Bug still exist in v226-1
Package: xterm Version: 226-1 Followup-For: Bug #421523 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.21-acer-1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages xterm depends on: ii libc6 2.5-11 GNU C Library: Shared libraries ii libfontconfig12.4.2-1.2 generic font configuration library ii libice6 1:1.0.3-2 X11 Inter-Client Exchange library ii libncurses5 5.6-3 Shared libraries for terminal hand ii libsm62:1.0.3-1 X11 Session Management library ii libx11-6 2:1.0.3-7 X11 client-side library ii libxaw7 1:1.0.3-3 X11 Athena Widget library ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar ii libxft2 2.1.12-2 FreeType-based font drawing librar ii libxmu6 1:1.0.3-1 X11 miscellaneous utility library ii libxt61:1.0.5-3 X11 toolkit intrinsics library ii xbitmaps 1.0.1-2Base X bitmaps Versions of packages xterm recommends: ii xutils 1:7.1.ds.3-1 X Window System utility programs -- no debconf information step to reproduce: 1. run xterm 2. run xfontsel 3. select font from xfontsel 4. change xterm's font via right click, menu VT font|selection crash dump: *** glibc detected *** xterm: munmap_chunk(): invalid pointer: 0x08081d6b *** === Backtrace: = /lib/i686/cmov/libc.so.6(cfree+0x1bb)[0xb7bc165b] xterm[0x805480e] /usr/lib/libXt.so.6[0xb7e18191] /usr/lib/libXt.so.6[0xb7e184cb] /usr/lib/libXt.so.6(XtDispatchEventToWidget+0x1e4)[0xb7e040f4] /usr/lib/libXt.so.6[0xb7e04aaf] /usr/lib/libXt.so.6(XtDispatchEvent+0xc7)[0xb7e03a67] xterm[0x806d46d] xterm[0x805ba66] xterm[0x805be4a] xterm[0x8067516] /lib/i686/cmov/libc.so.6(__libc_start_main+0xdc)[0xb7b6bebc] xterm[0x804d511] === Memory map: 08048000-0808f000 r-xp 08:06 950976 /usr/bin/xterm 0808f000-08094000 rw-p 00046000 08:06 950976 /usr/bin/xterm 08094000-080f8000 rw-p 08094000 00:00 0 [heap] b79c2000-b7a05000 rw-p b79c2000 00:00 0 b7a44000-b7a4e000 r-xp 08:06 48920 /lib/libgcc_s.so.1 b7a4e000-b7a4f000 rw-p 9000 08:06 48920 /lib/libgcc_s.so.1 b7a6c000-b7a7 r-xp 08:06 997929 /usr/lib/libXfixes.so.3.1.0 b7a7-b7a71000 rw-p 3000 08:06 997929 /usr/lib/libXfixes.so.3.1.0 b7a71000-b7a79000 r-xp 08:06 997921 /usr/lib/libXcursor.so.1.0.2 b7a79000-b7a7a000 rw-p 7000 08:06 997921 /usr/lib/libXcursor.so.1.0.2 b7a7a000-b7a7c000 rw-p b7a7a000 00:00 0 b7a7c000-b7a8f000 r-xp 08:06 359932 /lib/i686/cmov/libpthread-2.5.so b7a8f000-b7a91000 rw-p 00013000 08:06 359932 /lib/i686/cmov/libpthread-2.5.so b7a91000-b7a93000 rw-p b7a91000 00:00 0 b7a93000-b7a95000 r-xp 08:06 359020 /lib/i686/cmov/libdl-2.5.so b7a95000-b7a97000 rw-p 1000 08:06 359020 /lib/i686/cmov/libdl-2.5.so b7a97000-b7a9b000 r-xp 08:06 997922 /usr/lib/libXdmcp.so.6.0.0 b7a9b000-b7a9c000 rw-p 3000 08:06 997922 /usr/lib/libXdmcp.so.6.0.0 b7a9c000-b7a9e000 r-xp 08:06 997904 /usr/lib/libXau.so.6.0.0 b7a9e000-b7a9f000 rw-p 1000 08:06 997904 /usr/lib/libXau.so.6.0.0 b7a9f000-b7aae000 r-xp 08:06 997925 /usr/lib/libXpm.so.4.11.0 b7aae000-b7aaf000 rw-p e000 08:06 997925 /usr/lib/libXpm.so.4.11.0 b7aaf000-b7ab rw-p b7aaf000 00:00 0 b7ab-b7ace000 r-xp 08:06 1000791 /usr/lib/libexpat.so.1.0.0 b7ace000-b7ad rw-p 0001d000 08:06 1000791 /usr/lib/libexpat.so.1.0.0 b7ad-b7ad7000 r-xp 08:06 995880 /usr/lib/libXrender.so.1.3.0 b7ad7000-b7ad8000 rw-p 6000 08:06 995880 /usr/lib/libXrender.so.1.3.0 b7ad8000-b7aeb000 r-xp 08:06 994637 /usr/lib/libz.so.1.2.3 b7aeb000-b7aec000 rw-p 00012000 08:06 994637 /usr/lib/libz.so.1.2.3 b7aec000-b7b53000 r-xp 08:06 995440 /usr/lib/libfreetype.so.6.3.10 b7b53000-b7b56000 rw-p 00067000 08:06 995440 /usr/lib/libfreetype.so.6.3.10 b7b56000-b7c93000 r-xp 08:06 359017 /lib/i686/cmov/libc-2.5.so b7c93000-b7c94000 r--p 0013d000 08:06 359017 /lib/i686/cmov/libc-2.5.so b7c94000-b7c96000 rw-p 0013e000 08:06 359017 /lib/i686/cmov/libc-2.5.so b7c96000-b7c99000 rw-p b7c96000 00:00 0 b7c99000-b7cd3000 r-xp 08:06 51480 /lib/libncurses.so.5.6 b7cd3000-b7cdb000 rw-p 0003a000 08:06 51480 /lib/libncurses.so.5.6 b7cdb000-b7cdd000 rw-p b7cdb000 00:00 0 b7cdd000-b7dc5000 r-xp 08:06 996294 /usr/lib/libX11.so.6.2.0 b7dc5000-b7dc9000 rw-p 000e8000 08:06 996294 /usr/lib/libX11.so.6.2.0 b7dc9000-b7dde000 r-xp 08:06 994520 /usr/lib/libICE.so.6.3.0 b7dde000-b7ddf000 rw-p 00014000 08:06 994520 /usr/lib/libICE.so.6.3.0 b7ddf000-b7de1000 rw-p b7ddf000 00:00 0
Bug#397197: DPMS-bug test scenario
On Wed, 2007-06-20 at 20:08 +0200, Robert Siemer wrote: > I'm pleased to announce a reliable and fast test scenario: > > $ xset dpms 10 20 30 > [wait 10 seconds] > [screen goes blank (DPMS gets active)] > $ xset -dpms > [no DPMS kicks in, not even after 10 seconds] > $ xset +dpms > [wait 10 seconds] > > What I now expect is that DPMS suspends (or actually "standbys") the > screen, but that does not happen. The screen stays visible, passing 10, > 20, 30 and more seconds. > > Can anybody confirm that on other systems? Yes. Running xset dpms 10 20 30 again seems to fix it though, so probably the code handling xset +dpms doesn't re-enable something it should. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#254288: xserver-xfree86: [ati/atimisc] poor support for color depths 16 and 24 on 264VT [Mach64 VT] rev 64
I have since disposed of the machine with this video card, so I can't confirm whether this problem is reproducible anymore. Feel free to close this bug if nobody else can reproduce it. Cheers, Peter -Original Message- From: Brice Goglin [mailto:[EMAIL PROTECTED] Sent: Thursday, 21 June 2007 3:55 AM To: Peter Dey Cc: [EMAIL PROTECTED] Subject: Bug#254288: xserver-xfree86: [ati/atimisc] poor support for color depths 16 and 24 on 264VT [Mach64 VT] rev 64 Hi, About 3 years ago, you reported a bug to the Debian BTS regarding color depths 16 and 24 not being well supported on a mach64 board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429857: xserver-xorg-video-ati: TV-output and 3D graphics stopped working
On Wed, 2007-06-20 at 19:31 +0200, Till wrote: > > But unfortunately both TV-output and 3D graphics stopped working after > the upgrade. In fact, the "TVOutput" options seems to be removed from > the driver. The radeon driver has never supported TV out in any official release. > When I try to start a 3D application or game (tried keyjnote and > ppracer) the screen is just black or the textures are corrupted and > flickering. Which version of libgl1-mesa-dri do you have? Can you try 6.5.3-1 from experimental if you haven't? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#254288: marked as done (xserver-xfree86: [ati/atimisc] poor support for color depths 16 and 24 on 264VT [Mach64 VT] rev 64)
Your message dated Thu, 21 Jun 2007 08:39:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#254288: xserver-xfree86: [ati/atimisc] poor support for color depths 16 and 24 on 264VT [Mach64 VT] rev 64 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xfree86 Version: 4.3.0.dfsg.1-4 ATi driver seems to drop the blue bit at 24-bit colour. Red and yellow colours showing fine. Colours very messed up at 16-bit. Colours fine at 8-bit. I know I probably should be using the atimisc driver, but the X-server wont even start when atimisc is selected. [EMAIL PROTECTED] ~$ /sbin/lspci |grep -i VGA 00:11.0 VGA compatible controller: ATI Technologies Inc 264VT [Mach64 VT] (rev 40) -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx1 root root 20 Jun 15 2003 /etc/X11/X -> /usr/bin/X11/XFree86 -rwxr-xr-x1 root root 1898192 May 29 18:00 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: 00:11.0 VGA compatible controller: ATI Technologies Inc 264VT [Mach64 VT] (rev 40) 00:11.0 Class 0300: 1002:5654 (rev 40) /var/lib/xfree86/XF86Config-4.md5sum does not exist. XFree86 X server configuration file status: -rw-r--r--1 root root 2525 Jun 14 15:17 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/CID" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" # Load"glx" Load"int10" Load"record" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "macintosh" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "ATI Mach64 VT" Driver "ati" Option "UseFBDev" "yes" # BusID "PCI:0:11:0" VideoRam2048 EndSection Section "Monitor" Identifier "Generic Monitor" HorizSync 28-49 VertRefresh 43-72 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI Mach64 VT" Monitor "Generic Monitor" DefaultDepth8 SubSection "Display" Depth 8 Modes "1024x768" EndSubSection SubSection "Display" Depth 16 Modes "800x600" EndSubSection SubSection "Display" D
Instalatii Xenon pentru masina dumneavostra!
INSTALATII XENON PENTRU ORICE MASINA! PRETUL ESTE DE DOAR 550 RON cu montaj inclus! -nu necesita modificarea instalatiei electrice a masinii. -instalatiile sunt facute in HK si au cerficatele de calitate TUV, ISO si Emark! Instalatia este formata din : -2 ridicatoare de tensiune(balastre) -2 becuri xenon -cablurile de legatura care sunt plug and play -manual de instalare Instalatiile au garantie 18 luni de la data achizitionarii Pentru informatii si comenzi: 0724.811.889 sau [EMAIL PROTECTED] Cautam distribuitori in toata tara! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#273655: xserver-xfree86: [ati/radeon] blender crash
On Wed, 20 Jun 2007 20:21:03 +0200 Brice Goglin <[EMAIL PROTECTED]> wrote: > Hi, > > About 3 years ago, you reported a bug to the Debian BTS regarding a > crash of blender on an ATI board. Did you reproduce this problem > recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? > If not, I will close this bug in the next weeks. > > Thanks, > Brice > No more crash now with Xorg/Etch. Merci beaucoup. Frédéric
