Bug#353494: xserver-xorg: fails to start on Cyrix 6x86L CPU (SIGILL)
Brice Goglin wrote: Hi, About 2 years ago, you reported (or replied to) a bug in the Debian BTS regarding the X server not starting on a Cyrix 6x86 processor. Did any of you guys reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? Thanks, Brice I haven't checked recently because I decided to upgrade the machine in question from a Cyrix 486DX2 (which, I've since found out, doesn't support CPUID at all and should be excluded from any CPUID-based checks...) to a Pentium OverDrive, which works with no problems (aside from being slow, of course). -lee -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426286: Erratic Caps lock and Ctrl key behavior
Here is the output of /usr/share/bug/xserver-xorg-core/script 3>&1 from the correct machine. Please disregard the previous output as it was from another machine. Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2007-04-20 05:52 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1736280 2007-05-16 06:44 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) /etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 3218 2007-04-20 06:11 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg 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 /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/X11R6/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/X11R6/lib/X11/fonts/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/X11R6/lib/X11/fonts/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/X11R6/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/X11R6/lib/X11/fonts/75dpi" # path to defoma fonts FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"v4l" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "XkbVariant""nodeadkeys" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" EndSection Section "Device" Identifier "Intel Corporation 82852/855GM Integrated Graphics Device" Driver "i810" BusID "PCI:0:2:0" EndSection Section "Monitor" Identifier "LCD FP" Option "DPMS" HorizSync 28-49 VertRefresh 43-72 EndSection Section "Screen" Identifier "Default Screen" Device "Intel Corporation 82852/855GM Integrated Graphics Device" Monitor "LCD FP" DefaultDepth24 SubSection "Display" Depth 1 Modes "1024x768" EndSubSection SubSection "Display" Depth 4 Modes "1024x768" EndSubSection SubSection "Display" Depth 8 Modes "1024x768" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" EndSubSection SubSection "Display" Depth 24 Modes "1024x
Bug#426286: Erratic Caps lock and Ctrl key behavior
uh oh. that output was from the wrong machine. sorry. i will send from the correct machine... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426336: marked as done (xorg: X fails to map legacy ROM on recent IA64 kernels)
Your message dated Mon, 28 May 2007 13:26:23 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426336: xorg: X fails to map legacy ROM on recent IA64
kernels
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: xorg
Severity: important
Since patch 6d40fc514c9ea886dc18ddd20043a411816b63d1 went into the Linux kernel,
X has failed to work.
The relevant line in Xorg.0.log is:
Fatal server error:
xf86MapDomainMem(): mmap() failure
strace says:
open("/sys/class/pci_bus/:00/legacy_mem", O_RDWR) = 8
mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0) = -1
EINVAL (Invalid argument)
close(8)= 0
write(2, "mmap failure: Invalid argument\n", 31mmap failure: Invalid
argument
) = 31
write(2, "\nFatal server error:\n", 21) = 21
write(2, "xf86MapDomainMem(): mmap() fail"..., 36xf86MapDomainMem():
mmap() failure
) = 36
write(0, "xf86MapDomainMem(): mmap() fail"..., 36) = 36
write(2, "\n", 1
) = 1
write(0, "\n", 1) = 1
System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: ia64
Kernel: Linux 2.6.21-rc5-g6d40fc51-dirty (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Version: 2:1.3.0.0.dfsg-5
Upstream has fixed the problem.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
--- End Message ---
Bug#426286: Erratic Caps lock and Ctrl key behavior
On Sun, May 27, 2007 at 19:26:15 -0700, [EMAIL PROTECTED] wrote: > > Could you send the output of > > /usr/share/bug/xserver-xorg-core/script 3>&1 > > > see attached > Unfortunately that attachment is empty. Can you resend and make sure the information is there? Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426336: xorg: X fails to map legacy ROM on recent IA64 kernels
> "Brice" == Brice Goglin <[EMAIL PROTECTED]> writes: Brice> Peter Chubb wrote: >> Here it is. But the problem is that X is trying to map a 1M region >> from location 0; on this machine you can't do that safely, so the >> kernel prevents it. >> Brice> Right. Brice> Note for the BTS: for the record, see the header of [1], the Brice> patch has been merged in 2.6.22-rc1. >> X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol >> Version 11, Revision 0, Release 7.1.1 Build Operating System: >> UNKNOWN Current Operating System: Linux berry >> 2.6.21-rc5-g6d40fc51-dirty #20 SMP Mon May 28 10:48:11 EST 2007 >> ia64 >> Brice> Did you patch your 2.6.21-rc5 kernel with patches fron 2.6.22? I'm running current head-of-tree, as I'm developing patches for the upstream kernel. Brice> The corresponding fix has apparently been committed in Xorg in Brice> [2]. So Xserver 1.2 and above should be ok. You appear to be Brice> running Xserver 1.1.1. Is there any chance you try Brice> xserver-xorg-core 1.3 currently in unstable (you'll have to Brice> upgrade to libc6 2.5 to do so)? You could also have tried an Brice> earlier xserver-xorg-core 1.2 from snapshot.debian.net but I Brice> don't any 1.2 package built for ia64 there. I'm trying it now... (for some reason the last apt-get upgrade I did didn't upgrade this package; I think it was blocking on gcc-4.2-base) It works. Thanks for the help. Shall I close the bug, or will you? Peter C -- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au http://www.ertos.nicta.com.au ERTOS within National ICT Australia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423775: Problems using gdb to debug Xorg.
Le Fri, May 18, 2007 at 11:39:21AM +0200, Michel Dänzer a écrit : > On Fri, 2007-05-18 at 18:34 +0900, Charles Plessy wrote: > > > > I am not sure to understand the question, but after killing X, gdm > > restarts it for me. > > If the problem was a GPU lockup, that probably wouldn't succeed, the new > X server would hang again. I'm taking your non-understanding of the > question as that not being the case :), so it's probably not a GPU > lockup but more likely the other problem referenced. Hello Michel, Indeed, after a few days with the DRI disabled, I did not experience crashes anymore. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan
Bug#426336: xorg: X fails to map legacy ROM on recent IA64 kernels
Peter Chubb wrote: > Here it is. But the problem is that X is trying to map a 1M region > from location 0; on this machine you can't do that safely, so the > kernel prevents it. > Right. Note for the BTS: for the record, see the header of [1], the patch has been merged in 2.6.22-rc1. > X Window System Version 7.1.1 > Release Date: 12 May 2006 > X Protocol Version 11, Revision 0, Release 7.1.1 > Build Operating System: UNKNOWN > Current Operating System: Linux berry 2.6.21-rc5-g6d40fc51-dirty #20 SMP Mon > May 28 10:48:11 EST 2007 ia64 > Did you patch your 2.6.21-rc5 kernel with patches fron 2.6.22? The corresponding fix has apparently been committed in Xorg in [2]. So Xserver 1.2 and above should be ok. You appear to be running Xserver 1.1.1. Is there any chance you try xserver-xorg-core 1.3 currently in unstable (you'll have to upgrade to libc6 2.5 to do so)? You could also have tried an earlier xserver-xorg-core 1.2 from snapshot.debian.net but I don't any 1.2 package built for ia64 there. Brice [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=6d40fc514c9ea886dc18ddd20043a411816b63d1 [2] http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=bd0c829654903ca45543dfa59cda967c4fafd8ac -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415543: xorg: xserver crashes on beige G3 PowerMac
On May 27, 2007, at 5:31 PM, Brice Goglin wrote: Well, it is up to you to decide whether you want the problem to be fixed soon or not :) The question behind the question was (an I apologize for not asking it directly the first time around), in light of my "real" life situation, is your "real" life situation likely to allow you to take a look at this problem in a couple of weeks? If not, I can try to hurry-up the things I need to do to get the machine out of storage and available for experiments. But if it's convenient for you, I can take it at a more sedate pace. So we can (perhaps) do a better job of tracking down the problem. Debian cares much more about non-x86 architectures than many other distributions. However, since few people have powerpc, it takes time to debug when you need to find somebody with knowledge to reproduce the problem first :( Exactly. And I'm very glad you are willing to take the time to help me figure out this bug. Many thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426336: xorg: X fails to map legacy ROM on recent IA64 kernels
> "Brice" == Brice Goglin <[EMAIL PROTECTED]> writes: Brice> Peter Chubb wrote: >> Package: xorg Severity: important >> >> Since patch 6d40fc514c9ea886dc18ddd20043a411816b63d1 went into the >> Linux kernel, X has failed to work. >> >> The relevant line in Xorg.0.log is: >> >> Fatal server error: xf86MapDomainMem(): mmap() failure >> Brice> Please send the whole output of Brice> /usr/share/bug/xserver-xorg-core/script 3>&1 (as reportbug is Brice> supposed to do automatically). Brice> Brice Here it is. But the problem is that X is trying to map a 1M region from location 0; on this machine you can't do that safely, so the kernel prevents it. Contents of /var/lib/x11/X.roster: xserver-xfree86 xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 Aug 22 2006 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 3703048 Mar 8 03:43 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 3080 May 28 11:37 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf.dpkg-new (Xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf.dpkg-new manual page. # (Type "man xorg.conf.dpkg-new" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/xorg.conf.dpkg-new /etc/X11/xorg.conf.dpkg-new.custom # md5sum /etc/X11/xorg.conf.dpkg-new >/var/lib/xfree86/xorg.conf.dpkg-new.md5sum # dpkg-reconfigure xserver-xorg Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/share/fonts/X11/CID" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/share/fonts/X11/75dpi" EndSection Section "Module" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"record" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Generic Video Card" Driver "ati" EndSection Section "Monitor" Identifier "DELL" Option "DPMS" HorizSync 30-130 VertRefresh 48-170 EndSection Section "Monitor" Identifier "DEC" Option "DPMS" HorizSync 29-82 VertRefresh 50-150 EndSection Section "Screen" Identifier "Default Screen" Device "Generic Video Card" Monitor "Dell" DefaultDepth24 SubSection "Display" Depth 1 Modes "1920x1440" "1600x1200" "1280x1024" "1024x768" EndSubSection SubSection "Display" Depth 4 Modes "1920x1440" "1600x1200" "1280x1024" "1024x768" EndSubSection SubSection "Display" Depth 8 Modes "1920x1440" "1600x1200" "1280x1024" "1024x768" EndSubSection SubSection "Display" Depth 15 Modes "1920x1440" "1600x1200" "1280x1024" "1024x768" EndSubSection SubSection "Display" Depth 16
Bug#426286: Erratic Caps lock and Ctrl key behavior
> > When did this problem appear? >From the point of installation onwards. > Did you upgrade something as this time? I upgrade fairly regularly but the problem has persisted. > > Could the problem be related to switching to a VT console and then back > to X? Definitely not. I happens constantly when in X. > Or related to some applications? Not that I can tell. There is no discernable association of the problem with any applications. I do run KDE, if you think there might be some issue with it. > > Could you send the output of > /usr/share/bug/xserver-xorg-core/script 3>&1 see attached > so that we see your config and log (reportbug should have included this > output automatically in your first report). because I use a mailer which requires SSL and authentication, I cannot configure reportbug to send. I just sent the report with mutt. thanks for responding so rapidly.
Bug#426336: xorg: X fails to map legacy ROM on recent IA64 kernels
Peter Chubb wrote:
> Package: xorg
> Severity: important
>
> Since patch 6d40fc514c9ea886dc18ddd20043a411816b63d1 went into the Linux
> kernel,
> X has failed to work.
>
> The relevant line in Xorg.0.log is:
>
> Fatal server error:
> xf86MapDomainMem(): mmap() failure
>
Please send the whole output of
/usr/share/bug/xserver-xorg-core/script 3>&1
(as reportbug is supposed to do automatically).
Brice
>
>
> strace says:
>
> open("/sys/class/pci_bus/:00/legacy_mem", O_RDWR) = 8
> mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0) = -1
> EINVAL (Invalid argument)
> close(8)= 0
> write(2, "mmap failure: Invalid argument\n", 31mmap failure: Invalid
> argument
> ) = 31
> write(2, "\nFatal server error:\n", 21) = 21
> write(2, "xf86MapDomainMem(): mmap() fail"..., 36xf86MapDomainMem():
> mmap() failure
> ) = 36
> write(0, "xf86MapDomainMem(): mmap() fail"..., 36) = 36
> write(2, "\n", 1
> ) = 1
> write(0, "\n", 1) = 1
>
> System Information:
> Debian Release: lenny/sid
> APT prefers unstable
> APT policy: (990, 'unstable')
> Architecture: ia64
>
> Kernel: Linux 2.6.21-rc5-g6d40fc51-dirty (SMP w/1 CPU core)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/bash
>
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426336: xorg: X fails to map legacy ROM on recent IA64 kernels
Package: xorg
Severity: important
Since patch 6d40fc514c9ea886dc18ddd20043a411816b63d1 went into the Linux kernel,
X has failed to work.
The relevant line in Xorg.0.log is:
Fatal server error:
xf86MapDomainMem(): mmap() failure
strace says:
open("/sys/class/pci_bus/:00/legacy_mem", O_RDWR) = 8
mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0) = -1
EINVAL (Invalid argument)
close(8)= 0
write(2, "mmap failure: Invalid argument\n", 31mmap failure: Invalid
argument
) = 31
write(2, "\nFatal server error:\n", 21) = 21
write(2, "xf86MapDomainMem(): mmap() fail"..., 36xf86MapDomainMem():
mmap() failure
) = 36
write(0, "xf86MapDomainMem(): mmap() fail"..., 36) = 36
write(2, "\n", 1
) = 1
write(0, "\n", 1) = 1
System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: ia64
Kernel: Linux 2.6.21-rc5-g6d40fc51-dirty (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415543: xorg: xserver crashes on beige G3 PowerMac
It will take a little while for me to get to this. I put the machine in storage when Etch went "live". If there's still interest in the issue, I'll get it back out and we can do any experiments you want to do. Unfortunately, "real" life is taking a bit more time than usual recently (my boss got promoted and I'm down and dirty with getting his replacement installed...) so it may be a week or two before I can get to it. Is that OK? Rick PS: I'd sort of assumed that there was almost no interest in Debian for OldWorld PowerMacs, and not much more for PowerPC in general. Am I wrong? On May 25, 2007, at 6:00 PM, Brice Goglin wrote: Hi Rick, Could you send the output of /usr/share/bug/xserver-xorg-core/script 3>&1 so that we also see all details about your machine and config? It looks like you are using the fbdev driver on an ATI board. Did you try the ATI driver? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366072: gnome-control-center: Change screen resolution crashes Xorg 7.0
Hi, About a year ago, you reported a bug to the Debian BTS regarding a crash of the X server when changing resolution in gnome. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? 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#365749: xorg: No input from keyboard into the ADS program
Hi, About a year ago, you reported a bug to the Debian BTS regarding the ADS program not receiving keyboard input. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? 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#361796: xserver-xorg: Crashes when playing videos with kaffeine
Hi, About 2 years ago, you reported a bug to the Debian BTS regarding a crash of the X server while playing kaffeine. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and xserver-xorg-video-intel in unstable? 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#319112: xserver-xorg: X.org hangs with a blank screen on exit
On 5/27/07, Brice Goglin <[EMAIL PROTECTED]> wrote: Hi, About 2 years ago, you reported (or replied to) a bug in the Debian BTS regarding Xorg hanging with a blank screen at exit, apparently solved by option VBERestore. Did any of you guys reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? If not, I will close this bug in the next weeks. I (not the reporter) no longer use the VBERestore with the versions in unstable. Thanks, Santi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415543: xorg: xserver crashes on beige G3 PowerMac
Rick Thomas wrote: > It will take a little while for me to get to this. I put the machine > in storage when Etch went "live". If there's still interest in the > issue, I'll get it back out and we can do any experiments you want to do. > > Unfortunately, "real" life is taking a bit more time than usual > recently (my boss got promoted and I'm down and dirty with getting his > replacement installed...) so it may be a week or two before I can get > to it. > > Is that OK? Well, it is up to you to decide whether you want the problem to be fixed soon or not :) Since you seem to be the only one that reported this bug so far, it will be hard for us to debug without you helping (the other person who replied to the bug has unrelated problems). Waiting weeks or months is not a problem at all for us. > PS: I'd sort of assumed that there was almost no interest in Debian > for OldWorld PowerMacs, and not much more for PowerPC in general. Am > I wrong? Debian cares much more about non-x86 architectures than many other distributions. However, since few people have powerpc, it takes time to debug when you need to find somebody with knowledge to reproduce the problem first :( Cheers, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#353494: xserver-xorg: fails to start on Cyrix 6x86L CPU (SIGILL)
Hi, About 2 years ago, you reported (or replied to) a bug in the Debian BTS regarding the X server not starting on a Cyrix 6x86 processor. Did any of you guys reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#331697: /usr/X11R6/bin/X: crash with blender
Hi, About 2 years ago, you reported a bug to the Debian BTS regarding a crash of the X server while running blender. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? 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#319326: xserver-xorg: The xorg.conf file is not found althought it is present
Hi, About 2 years ago, you reported a bug to the Debian BTS regarding the xorg.conf file not being found by the server. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? 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#319112: xserver-xorg: X.org hangs with a blank screen on exit
Hi, About 2 years ago, you reported (or replied to) a bug in the Debian BTS regarding Xorg hanging with a blank screen at exit, apparently solved by option VBERestore. Did any of you guys reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core in unstable? 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#426286: Erratic Caps lock and Ctrl key behavior
Daniel O'Neill wrote: > Package: xserver-xorg-input-kbd > Version: 1:1.1.0-4 > > On a Thinkpad X40 keyboard - tried with both a standard american English > keyboard and german Deutsch one - there is something extremely bizarre > going on that seem to involve Caps Lock and Ctrl keys. Intermittently > the Caps lock seems to get activated even though the Caps Lock LCD > indicator light is off. Normally to fix it, shift + a character must be > pressed, after which releasing the Shift key will return keys to > lowercase. > > More troubling is that from time to time somehow the Ctrl key seems to > get stuck on. This can be extremely dangerous as subsequent keypresses > are now Ctrl-key combinations and have the potential to kill processes, > shut down terminals, etc. I still do not know how Ctrl key gets > untoggled in this state, but it is not by pressing the Ctrl key. > > When this problem initially occurred I thought perhaps there was some > severe problem with the keyboard. But changing the keyboard made no > difference. I also completely re-installed Debian but the problem > persisted. The problem does not, however, occur under non-Debian. > When did this problem appear? Did you upgrade something as this time? Could the problem be related to switching to a VT console and then back to X? Or related to some applications? Could you send the output of /usr/share/bug/xserver-xorg-core/script 3>&1 so that we see your config and log (reportbug should have included this output automatically in your first report). Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426286: Erratic Caps lock and Ctrl key behavior
Package: xserver-xorg-input-kbd Version: 1:1.1.0-4 On a Thinkpad X40 keyboard - tried with both a standard american English keyboard and german Deutsch one - there is something extremely bizarre going on that seem to involve Caps Lock and Ctrl keys. Intermittently the Caps lock seems to get activated even though the Caps Lock LCD indicator light is off. Normally to fix it, shift + a character must be pressed, after which releasing the Shift key will return keys to lowercase. More troubling is that from time to time somehow the Ctrl key seems to get stuck on. This can be extremely dangerous as subsequent keypresses are now Ctrl-key combinations and have the potential to kill processes, shut down terminals, etc. I still do not know how Ctrl key gets untoggled in this state, but it is not by pressing the Ctrl key. When this problem initially occurred I thought perhaps there was some severe problem with the keyboard. But changing the keyboard made no difference. I also completely re-installed Debian but the problem persisted. The problem does not, however, occur under non-Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375553: xserver-xorg: Server freezes switching to console and back
Hi Nicola, Thanks a lot for building and testing the latest release of the sis driver. I found a bug report upstream about problems when switching to console and back to X, see [1]. It's not a freeze like your problem, but at least it confirms that the driver has problem in this area. We'll see what happen (and hope the driver will get good maintenance in the future). Brice [1] https://bugs.freedesktop.org/show_bug.cgi?id=5842 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#82717: marked as done (xserver-xfree86: [s3virge] snow during refresh on ViRGE/DX or /GX rev 1)
Your message dated Sun, 27 May 2007 10:01:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line ping timeout, closing 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.2-1 I tried the 4.0 xfree86 on my Virge graphics card. However, whenever the content of the screen changes, there is some noise/snow on the screen. The problem does not exist with the version 3 server. I have attached a log of an xfree run. (This is the second submission of this bug. My last posting was unintentionally base64 encoded.) Best, Oliver Log: XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 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.18 i686 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Wed Jan 10 19:17:56 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 "Generic Monitor" (**) | |-->Device "Generic Video Card" (**) |-->Input Device "Generic Keyboard" (**) XKB: rules: "xfree86" (**) XKB: model: "pc104" (**) XKB: layout: "us" (**) |-->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 (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (--) PCI:*(0:15:0) S3 ViRGE/DX or /GX rev 1, Mem @ 0xe000/26 (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/libpex5.a (II) Module pex5: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.13.0 (II) Loading /usr/X11R6/lib/modules/extensions/libxie.a (II) Module xie: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.a (II) Module freetype: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.1.8 (II) Loading /usr/X11R6/lib/modules/fonts/libspeedo.a (II) Module speedo: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1
Bug#115618: marked as done (xserver-xfree86: [rendition] screen corruption on Verite 2100/2200 rev 6)
Your message dated Sun, 27 May 2007 10:01:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line ping timeout, closing 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-6 Hi, I recently upgraded XFree86 on an older machine, which includes a Diamond Stealth II S220 video card, which has been flashed to Diamond Multimedia's version 1.36 BIOS. This is a 4MB PCI video card with a Rendition Verite 2100 video chip. Startup of the X-server is by way of GDM. The problematic behavior is that the image of what should be a GDM log-in widget consists instead of several near- horizontal bands of gray on a bright-red background. The image resembles the result of incorrect monitor horizontal sync, except that the X pointer is intact and functions correctly overtop of the distorted image when the "hardware cursor" option is selected, but is part of the distorted image when "software cursor" is selected. Also, all hardware was functioning correctly prior to the XFree86 upgrade, and functions correctly now in VGA mode. Most X-windows functionality is not compromised -- by careful mouse movement and attention to the "text-input" curosr, it is possible to find the log-in window, type in a username and password, and log in successfully, as indicated by the appearance of wtmp/utmp entries. However, it is not possible to switch between virtual X-servers by means of control-Fx. (This last item may be my own misconfiguration, I have not investigated this yet.) This evidence suggests to me that, in this circumstance, the card is able to map images correctly to the monitor (i.e. the X cursor), but that the image has been assembled incorrectly in video memory. The X log file contains one anomolous warning about memory mapping, to which I draw your attention because I believe it to be particularly relevant. From "/var/log/XFree86.0.log": > (WW) Rendition(0): xf86UnMapVidMem: cannot find region for > [0xfe00,0x1000] System details: System is a 200 MHz Pentium MMX, 64 MB RAM, on a PCChips motherboard with Intel i430TX chipset. Video card is Diamond Stealth II S220 flashed to version 1.36 of the BIOS. Linux kernel version is 2.2.18pre21. All dependencies of xserver-xfree86-4.1.0-6 and -7 are satisfied. The video card is represented in /proc/pci as: Bus 0, device 9, function 0: VGA compatible controller: Rendition Verite 2100 (rev 6). Medium devsel. Fast back-to-back capable. Master Capable. Latency=64. Prefetchable 32 bit memory at 0xfe00 [0xfe08]. I/O at 0xd800 [0xd801]. XF86Config-4 file: == This file contains a custom mode used in testing to ensure that the monitor timings were *exactly* those of the manufacturer's specification. == FILE /etc/X11/XF86Config-4 begins == # 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" "pc101" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse
Bug#107208: marked as done (xserver-xfree86: [rendition] striped corruption and broken VT switching on Verite 2100/2200 rev 6)
Your message dated Sun, 27 May 2007 10:01:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line ping timeout, closing 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-1 Severity: important Tags: sid After upgrade from X 4.0.3 to X 4.1.0, screen became completely messed (it appeared to be working what it should but I was unable to see anything reasonable, just color stripes). I was even unable to return back to console with ctrl-alt-backspace, the screen left messed but the machine operated correctly. This bug was reproduced every time I started X 4.1.0 on the same machine. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux chem2 2.4.6 #1 Tue Jul 24 20:29:49 CEST 2001 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages xserver-xfree86 depends on: ii debconf 0.9.91 Debian configuration management sy ii libc6 2.2.3-9GNU C Library: Shared libraries an ii xserver-common4.1.0-1files and utilities common to all ii zlib1g1:1.1.3-15 compression library - runtime --- End Message --- --- Begin Message --- Closing this bug since I didn't get any reply from the submitter (or repliers) after my ping about a month ago (except from people that don't have the hardware anymore and thus can't try to reproduce). Additionally, some addresses are now invalid. If anybody ever reproduces this problem, feel free to reopen. Brice --- End Message ---
Bug#155232: marked as done (xserver-xfree86: [glint] accelerated scanline CPU to screen color expand fills ops broken plus other corruption on GLINT Permedia 4 rev 1)
Your message dated Sun, 27 May 2007 09:57:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line ping timeout, closing 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.2.0-0pre1v1 Severity: normal When I start X with xinit -- :2 vt09 -depth 24 -xf86config ./XF86Config-4_OVERLAY & (the XF86Config-4_OVERLAY is included here), X starts and I can run window managers, etc, but no letters are visible; not in xterms, not in menus, nowhere. (I can start xterms with different -bg colors. I get the right background color, but still no visible text, and no visible cursor). X works fine in 24 bit mode, and in 8 bit mode. (xdm won't start in 8-bit mode, and keeps failing until I have to power cycle the machine, but I can start a working 8-bit display without xdm and it works fine.) Oh, and I don't know what the difference is between 8,24 and 24,8 overlay, but I tried both, with identical results. Vadim ### 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/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 "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" # Load"pex5" Load"record" Load"speedo" Load"type1" Load"vbe" # Load"xie" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc102" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/mouse" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/mouse" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "3dlabs oxygen vx1" Driver "glint" VideoRam32768 # Option "UseFBDev" "true" Option "Overlay" "24,8" EndSection Section "Monitor" Identifier "P815-4" HorizSync 30-110 VertRefresh 50-160 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "3dlabs oxygen vx1" Monitor "P815-4" DefaultDepth24 SubSection "Display" Depth 1 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display"
