Bug#430067: xserver-xorg: mplayer causes xserver crash
On Sun, 23 Sep 2007 11:44:33 +0200 Brice Goglin <[EMAIL PROTECTED]> wrote: > On Fri, Jun 22, 2007 at 08:47:29AM +0200, Brice Goglin wrote: > > clayton wrote: > > > Occasionally (not reliably repeatable) mplayer brings down X. > > > This backtrace from the attached log comes from the most recent > > > event. > > > > > > Backtrace: > > > 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8591] > > > 1: /lib/libc.so.6 [0xb7dbfe28] > > > 2: /usr/lib/xorg/modules/drivers//atimisc_drv.so [0xb7bd406e] > > > 3: /usr/bin/X [0x80dc8bf] > > > 4: /usr/lib/xorg/modules/extensions//libextmod.so(XvdiPutImage+0x174) > > > [0xb7c933$ > > > 5: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7c96398] > > > 6: /usr/bin/X [0x81549be] > > > 7: /usr/bin/X(Dispatch+0x19f) [0x808ed3f] > > > 8: /usr/bin/X(main+0x495) [0x8076e85] > > > 9: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7dabebc] > > > 10: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x80761a1] > > > > > > > Could you try xserver-xorg-video-ati 1:6.6.192-1 currently in > > experimental? > > > > The same bug has been reported upstream at the URL above, feel free > > to add some comments there if you think it may help. > > Ping? > > Please try xserver-xorg-video-ati 6.7.193 currently in experimental. Sorry for the delay, Brice, your request was caught up in a hardware change. I now have xserver-xorg-video-ati/experimental 1:6.7.194-1 installed and it seems to be working fine. Note that this problem was never reproducible at will so it is hard to know when it goes away. I haven't seen it for a while, but if it should show up again, I will let you know. Clayton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445100: xserver-xorg: Ctl-Alt-Fx has stopped working after a fresh install
On Thu, 04 Oct 2007 07:52:11 +0200 Brice Goglin <[EMAIL PROTECTED]> wrote: > Can you try with xserver-xorg-video-ati 1:6.7.194-1 current in > experimental? You nailed that one, Brice. The problem goes away with xserver-xorg-video-ati/experimental 1:6.7.194-1. I was hoping SCIM was having the same problem, but no luck with that one, still broken. You can close this bug report at your leisure. Clayton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445100: marked as done (xserver-xorg: Ctl-Alt-Fx has stopped working after a fresh install)
Your message dated Thu, 04 Oct 2007 10:30:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#445100: xserver-xorg: Ctl-Alt-Fx has stopped working after a fresh 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: 1:7.3+2 Severity: normal I just did a fresh install to a new hard-drive, everything up-to-date to the latest "testing". Now when I hit Ctl-Alt-F1, instead of getting a console, the keyboard and mouse are locked up. This happens at both the gdm login prompt and while logged into KDE. If I login through the network and kill X, function is restored. On the same machine using the same xorg.conf but a different hard drive with an old install, Ctrl-Alt-F1 works just fine. -- Package-specific info: 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-10-02 05:50 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1669528 2007-09-17 02:56 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) /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 2985 2007-10-02 06:50 /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"record" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" 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" "ExplorerPS/2" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "Rage Mobility" Driver "ati" BusID "PCI:01:00:00" EndSection Section "Monitor" Identifier "LCD" Option "DPMS" HorizSync 28-50 VertRefresh 43-75 EndSection Section "Screen" Identifier "Default Screen" Device "Rage Mobility" Monitor "LCD" DefaultDepth24 SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480"
Re: Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console
reassign 445104 xserver-xorg-core severity 445104 important thanks On Thu, Oct 4, 2007 at 11:01:47 +0200, Edward Welbourne wrote: > > Sounds like X is dying on vt switch. > I guess so. > > > I assume this doesn't happen when xscreensaver isn't running? > Indeed. > > > If X is indeed crashing, can you attach your X log after the crash? > > (should be /var/log/Xorg.0.log, or /var/log/Xorg.0.log.old after X has > > been restarted) > > In the interests of brevity, the follows the diff between my current > log and the last time I exercised the crash in the course of > reproducing the bug. If you want the whole log I can send that, but I > notice this does indeed include a backtrace ... > Thanks, I'm reassigning this bug to the X server. The complete log and your xorg.conf would be useful. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console
Processing commands for [EMAIL PROTECTED]: > reassign 445104 xserver-xorg-core Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console Bug reassigned from package `xscreensaver' to `xserver-xorg-core'. > severity 445104 important Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console Severity set to `important' from `critical' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#208683: Job position
Hello! My name is Sara Balhen, I work in the company « E-exchange Finland ». Our company is engaged in purchase of electronic currencies, such as e-gold, e-bullion, e-vocash, and other currencies. We search for the responsible, decent, operative person for work with our company. From our side we guarantee to you stable earnings and career grown. If you have interest in our offer write on ours e-mail: [EMAIL PROTECTED] . We will contact Koshka (16:26:23 2/10/2007) with you during 24 hours, we will give to you more information about our company and about work which we want to offer to you. Have successful day! Sincerely yours Sara. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#203942: E-exchange Job Offer
Hello! My name is Sara Balhen, I work in the company « E-exchange Finland ». Our company is engaged in purchase of electronic currencies, such as e-gold, e-bullion, e-vocash, and other currencies. We search for the responsible, decent, operative person for work with our company. From our side we guarantee to you stable earnings and career grown. If you have interest in our offer write on ours e-mail: [EMAIL PROTECTED] . We will contact Koshka (16:26:23 2/10/2007) with you during 24 hours, we will give to you more information about our company and about work which we want to offer to you. Have successful day! Sincerely yours Sara. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423014: console's last three lines become inaccessible once xdm start up
Incidentally, this bug has become unreproducible since I switched from using the old CRT to using a shiny new flat screen. Eddy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console
> Thanks, I'm reassigning this bug to the X server. The complete log and > your xorg.conf would be useful. OK. X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12) Current Operating System: Linux whorl 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 Build Date: 09 August 2007 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: Wed Oct 3 10:51:22 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Dell 2007FPb" (**) | |-->Device "Intel Corporation 82915G/GV/910GL Integrated Graphics Controller" (**) |-->Input Device "IBM-UK Keyboard" (**) |-->Input Device "Logitech 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 (==) RgbPath set to "/etc/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) Loader magic: 0x81e5140 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (++) using VT number 7 (WW) xf86OpenConsole: setpgid failed: Operation not permitted (WW) xf86OpenConsole: setsid failed: Operation not permitted (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2580 card 1028,0179 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2581 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 8086,2582 card 1028,0179 rev 04 class 03,00,00 hdr 80 (II) PCI: 00:02:1: chip 8086,2782 card 1028,0179 rev 04 class 03,80,00 hdr 80 (II) PCI: 00:1c:0: chip 8086,2660 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2662 card , rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2658 card 1028,0179 rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2659 card 1028,0179 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,265a card 1028,0179 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,265b card 1028,0179 rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,265c card 1028,0179 rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev d3 class 06,04,01 hdr 81 (II) PCI: 00:1e:2: chip 8086,266e card 1028,0179 rev 03 class 04,01,00 hdr 00 (II) PCI: 00:1f:0: chip 8086,2640 card , rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,266f card 1028,0179 rev 03 class 01,01,8a hdr 00 (II) PCI: 00:1f:2: chip 8086,2651 card 1028,0179 rev 03 class 01,01,8f hdr 00 (II) PCI: 00:1f:3: chip 8086,266a card 1028,0179 rev 03 class 0c,05,00 hdr 00 (II) PCI: 02:00:0: chip 14e4,1677 card 1028,0179 rev 01 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,4), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xdfd0 - 0xdfdf (0x10) MX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:28:0), (0,2,2), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xdfc0 - 0xdfcf (0x10) MX[B] (II) PCI-to-PCI bridge: (II) Bus 3: bridge is at (0:28:1), (0,3,3), BCTRL: 0x0002 (VGA_EN is cleared) (II) Bus 3 non-prefetchable memory range: [0] -1 0 0xdfb0 - 0xdfbf (0x10) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 4: bridge is at (0:30:0), (0,4,4), BCTRL: 0x0002 (VGA_
Bug#443584: works for me :-)
laptop:~/# xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0*60.0 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right x axis y axis) laptop:~/# xrandr --output S-video --set load_detection 1 laptop:~/# xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0*60.0 800x60060.3 640x48059.9 S-video connected (normal left inverted right x axis y axis) 800x60059.9 + 60.3 laptop:~/# xrandr --auto or laptop:~/# grandr grandr now shows both devices (S-video and LVDS) but when i click one and then the other it crashes. thou i can configure each device if i don't click the other one. (i'll report this to grandr developer) (grandr:4534): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed (grandr:4534): GLib-GObject-WARNING **: /tmp/buildd/glib2.0-2.14.1/gobject/gtype.c:3339: type id `0' is invalid (grandr:4534): GLib-GObject-WARNING **: can't peek value table for type `' which is not currently referenced Segmentation fault -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445266: xorg-server: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: xorg-server Tags: l10n patch Severity: wishlist Hi Could you please update the Brazilian Portuguese Translation? Attached you will find xorg-server-pt_BR.po.gz, it is update. It is encoded using UTF-8 and it is tested with msgfmt and also with podebconf-display-po Kind regards, - -- Eder L. Marques .''`. ** Debian GNU/Linux ** : :' : http://www.debian.org/ `. `' http://www.debianbrasil.org/ `-http://www.debian-ce.org/ Get Counted! http://www.linuxcounter.org/ Duvidas sobre o Debian? Visite o Rau-Tu: http://rautu.cipsga.org.br/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQIVAwUBRwTwyT9tnxvLkedtAQLo7w/8DV8KgxS4c1OKUJFWvzqhWoa+rF1cjjMK tKy1NWa5zw2UdM3asT6BkrIWAfyO0bteW1YVBxlvZLmzoTDUq8xRlslrJjxu0olA 1M6u9M6dMUQeMT+JWfBQvLlhz/+PouSZJJGXuW+InxGpG0uxaast6CRnV9/r8W17 8QZCpCasBDUFPaRoJ5KXN7iKFa3MTmqk+MYwsP8hAV6ujY92P1rEUpAI5PFVYsfJ AVo6xZjNx5RuIhRHbEk3/zNOfmsmF4lskCIZpkzfYU4WIvsjs1oy3e0lGWduE/wS RaQieNWvgY33uV6KIv8ECBDaN3wdGQlWzLGFQwW90/4Erf70uBYwY5nkjOgNXsJZ 0GQy2dZR0ndZwhdOmVzx5wpoqAv1zMBdd4nxXl9Dik3X5DA1ESTHqYN3EsJvggp/ AOU394/hX2sUaf4lg5P+AnE8OCGkd7PrUn1mOzC9UCi76+euSwv+3cU8H00aWUUS /nmMI8ScDrc3i6ThP+DNNthlCBqIhPN9pQudK2gg2yaf55nrd4KJeNxXiUP14V1H ZL1aXNjFNZvHUlKVIes4iqfJ+7/2KEB3U1M0hrjREfI0aPic+VcWcRqJp9cNH7CW nNoFCtz//K8VYJ8xICuXI9jLH9OhmqH+YPaOi0qLOC0Fdc9avC1AM5XZC8qco4pl V9KTHvml580= =d6Vu -END PGP SIGNATURE- xorg-server-pt_BR.po.gz Description: GNU Zip compressed data
Bug#443503: Mouse double clicks always
Hi Mike, I was hit by the same problem, and got it solved by adding `Option "CorePointer"' to my only InputDevice section referring to the device "/dev/input/mice". This stopped the unwanted double clicks from occurring. So try the following InputDevice section: Section "InputDevice" Identifier"Generic Mouse" Driver"mouse" Option"CorePointer" Option"Device""/dev/input/mice" Option"Protocol" "ImPS/2" Option"ZAxisMapping" "4 5" EndSection Hope this helps you and others fighting the same problem. Cheers Bernhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443936: xserver-xorg-video-mga: windowmaker and 1.9.99 get along terribly
> kls wrote: > > I finally got around to upgrading my laptop (ATI M6LY)'s install of > > sid, and found that this is *not* a problem in the mga driver. It's a > > problem in some other random xorg component, presumably > > libxcomposite1. > > > > To work around it, I have to disable both the Composite extension and > > AIGLX -- it seems that with only one disabled the other caused it to > > be re-enabled. > > > > (Any suggestions on tracing down what's actually wrong?) > > > > (e.g. > > Section "Extensions" > > Option "Composite" "disable" > > EndSection > > Section "ServerFlags" > > Option "AIGLX" "no" > > EndSection > > ) > > > > So I guess that means this bug should either be moved to a different > > package or closed. > > If I understand correctly, you are seeing WindowMaker being very slow on > both MGA and ATI with Xorg 7.3 (xserver-xorg-core 1.4) when > AIGLX/Composite is enabled? And it worked fine before? Does it help if > you switch to EXA on ATI? EXA shouldn't as bad as in MGA on your board. EXA on ATI is usable ( although I think it's barely perceptably slower than composite-less XAA ) but compositing/aiglx(?) still has the other non-speed related bugs: * wmnet's window contents being placed in the wrong location * windowmaker's shaped transient indicating which workspace I'm on isn't shaped * wmxmms quits with an obscure GDK error. (This happens even when not running under windowmaker) For the heck of it I tried xcompmgr, and on my ATI windowmaker's decorations are all differently wrong than on my MGA -- on the ATI they all seem to be in a "brighten only" mode, whereas on the MGA they're all pure transparent. Thank you, - Robert Jacobs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420203: not fixed for me
Sorry, but xserver-xorg-video-intel 2.1.1-4 does not resolve the flicker issue for me (Fujitsu Lifebook 5010d) VGA: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Neither does the patch bug-11917.diff by Eric Anholt. Cannot find the corresponding bug right now, but it tries to use BIOS modes instead of probed modes when the BIOS panel mode data doesn't match probed data. I'm not using any video bios patching such as 915resolution (should I?)
Bug#443936: xserver-xorg-video-mga: windowmaker and 1.9.99 get along terribly
On Thu, 2007-10-04 at 11:32 -0400, kls wrote: > > EXA on ATI is usable ( although I think it's barely perceptably slower > than composite-less XAA ) but compositing/aiglx(?) still has the other > non-speed related bugs: > > * wmnet's window contents being placed in the wrong location > * windowmaker's shaped transient indicating which workspace I'm on >isn't shaped > * wmxmms quits with an obscure GDK error. (This happens even when not >running under windowmaker) > > For the heck of it I tried xcompmgr, and on my ATI windowmaker's > decorations are all differently wrong than on my MGA -- on the ATI > they all seem to be in a "brighten only" mode, whereas on the MGA > they're all pure transparent. Can you provide screenshots? It's weird that merely enabling the Composite extension or AIGLX would cause this - they should have no effect unless their features are actively used by clients. (Also, AIGLX is not really enabled when the DRI is disabled, as in the log file of the original report.) Some older clients used to have trouble with Composite's ARGB visuals - does setting the environment variable XLIB_SKIP_ARGB_VISUALS=1 for running windowmaker make a difference? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#443936: xserver-xorg-video-mga: windowmaker and 1.9.99 get along terribly
> On Thu, 2007-10-04 at 11:32 -0400, kls wrote: > > > > EXA on ATI is usable ( although I think it's barely perceptably slower > > than composite-less XAA ) but compositing/aiglx(?) still has the other > > non-speed related bugs: > > > > * wmnet's window contents being placed in the wrong location > > * windowmaker's shaped transient indicating which workspace I'm on > >isn't shaped > > * wmxmms quits with an obscure GDK error. (This happens even when not > >running under windowmaker) > > > > For the heck of it I tried xcompmgr, and on my ATI windowmaker's > > decorations are all differently wrong than on my MGA -- on the ATI > > they all seem to be in a "brighten only" mode, whereas on the MGA > > they're all pure transparent. > > Can you provide screenshots? > > It's weird that merely enabling the Composite extension or AIGLX would > cause this - they should have no effect unless their features are > actively used by clients. (Also, AIGLX is not really enabled when the > DRI is disabled, as in the log file of the original report.) Some older I've reconfigured things so many times by now in the process of trying to figure things out... > clients used to have trouble with Composite's ARGB visuals - does > setting the environment variable > > XLIB_SKIP_ARGB_VISUALS=1 > > for running windowmaker make a difference? Putting that in the general environment fixes all the graphical errors I've yet noticed. Do you still want screenshots? - robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443936: xserver-xorg-video-mga: windowmaker and 1.9.99 get along terribly
On Thu, 2007-10-04 at 12:45 -0400, kls wrote: > > > clients used to have trouble with Composite's ARGB visuals - does > > setting the environment variable > > > > XLIB_SKIP_ARGB_VISUALS=1 > > > > for running windowmaker make a difference? > > Putting that in the general environment fixes all the graphical errors > I've yet noticed. Do you still want screenshots? I don't think that's necessary, thanks. Then this looks like a bug in windowmaker or bugs in the apps, depending on whether it also happens with other window managers. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#423014: console's last three lines become inaccessible once xdm start up
Edward Welbourne wrote: > Incidentally, this bug has become unreproducible since I switched from > using the old CRT to using a shiny new flat screen. > Strange, I am not sure what to do with this bug then. Will you have a chance to try the old CRT again? Are you sure the bug disappeared because you switched the display and not because of an upgrade at the same time? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#443584: marked as done (xrandr does not recognise conncted s-video)
Your message dated Thu, 04 Oct 2007 19:27:15 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#443584: works for me :-) 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.7.193-1 Severity: normal --- Please enter the report below this line. --- when i plug in an s-video line which is connected to a TV it does not get recognized by xrandr and i can't switch with Fn4 between LVDS and VGA-0, here is what i get from xrandr: laptop:~# xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024 VGA-0 disconnected (normal left inverted right x axis y axis) LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0 60.0* 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right x axis y axis) only after a reboot i can use Fn4 to switch the s-video output to watch on the TV but still it's not recognized with xrandr. also, i get these line in xorg log file: information RADEON(0): Output S-video has no monitor section information RADEON(0): Output S-video disconnected --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-686 Debian Release: lenny/sid 500 unstablewww.debian-multimedia.org 500 unstablemirror.isoc.org.il 500 testing mirror.isoc.org.il 500 experimentalwww.debian-multimedia.org 500 etchdebian.beryl-project.org 1 experimentalmirror.isoc.org.il --- Package information. --- Depends (Version) | Installed ==-+-= libc6 (>= 2.6.1-1) | 2.6.1-4 xserver-xorg-core (>= 2:1.4) | 2:1.4-2 --- End Message --- --- Begin Message --- Nadav Kavalerchik wrote: > laptop:~/# xrandr > Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024 > VGA-0 disconnected (normal left inverted right x axis y axis) > LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x > 0mm >1024x768 60.0*60.0 >800x60060.3 >640x48059.9 > S-video disconnected (normal left inverted right x axis y axis) > laptop:~/# xrandr --output S-video --set load_detection 1 > laptop:~/# xrandr > Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2304 x 1024 > VGA-0 disconnected (normal left inverted right x axis y axis) > LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x > 0mm >1024x768 60.0*60.0 >800x60060.3 >640x48059.9 > S-video connected (normal left inverted right x axis y axis) >800x60059.9 + 60.3 > laptop:~/# xrandr --auto > or > laptop:~/# grandr > > grandr now shows both devices (S-video and LVDS) but when i click one and > then > the other it crashes. thou i can configure each device if i don't click the > other one. (i'll report this to grandr developer) > Ok, good to know. I am closing this bug then. Having to enable load detection like this is a little bit boring, but disabling it by default fixes so many problems that it is better like this. Brice --- End Message ---
Processed: Re: Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console
Processing commands for [EMAIL PROTECTED]: > reassign 445104 xserver-xorg-video-intel Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console Bug reassigned from package `xserver-xorg-core' to `xserver-xorg-video-intel'. > forcemerge 431373 445104 Bug#431373: xserver-xorg-video-intel: sometimes crashes when switching back to X from a VC Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console Forcibly Merged 431373 445104. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#430067: xserver-xorg: mplayer causes xserver crash
Clayton wrote: > Sorry for the delay, Brice, your request was caught up in a hardware > change. I now have xserver-xorg-video-ati/experimental 1:6.7.194-1 > installed and it seems to be working fine. > > Note that this problem was never reproducible at will so it is hard to > know when it goes away. I haven't seen it for a while, but if it > should show up again, I will let you know. > Ok, let's wait until the end of October or so, and I'll close it then if I don't hear back from you. Thanks for the followup. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#420203: not fixed for me
Daniel Schwen wrote: > Sorry, but xserver-xorg-video-intel 2.1.1-4 does not resolve the flicker > issue for me (Fujitsu Lifebook 5010d) VGA: > 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM > Integrated Graphics Device (rev 02) > > Neither does the patch bug-11917.diff by Eric Anholt. Cannot find the > corresponding bug right now, but it tries to use BIOS modes instead of > probed modes when the BIOS panel mode data doesn't match probed data. > You are probably experiencing a different bug then. You should open a new bug report at bugzilla.freedesktop.org, copy all the above and at least post your config and log. > I'm not using any video bios patching such as 915resolution (should I?) > No, the BIOS tables that 915resolution modifies are not used anymore since Intel driver 2.0. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445104: xscreensaver: aborts X session if I let the log-back-in screen time out while switched to a virtual console
reassign 445104 xserver-xorg-video-intel forcemerge 431373 445104 thank you Edward Welbourne wrote: > 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8631] > 1: /lib/i686/cmov/libc.so.6 [0xb7e0b898] > 2: /usr/bin/X [0x80f9895] > 3: /usr/bin/X [0x80fa30a] > 4: /usr/bin/X(xf86_reload_cursors+0xbd) [0x80f9fcd] > 5: /usr/lib/xorg/modules/drivers//i810_drv.so [0xb7c31eb2] > 6: /usr/bin/X(xf86CrtcSetMode+0x279) [0x80f9169] > 7: /usr/bin/X(xf86SetDesiredModes+0x139) [0x80f9519] > 8: /usr/lib/xorg/modules/drivers//i810_drv.so [0xb7c35599] > 9: /usr/lib/xorg/modules//libxaa.so [0xb7aaf3f2] > 10: /usr/bin/X [0x80d08fc] > 11: /usr/bin/X [0x80ddcd8] > 12: /usr/lib/xorg/modules/extensions//libglx.so [0xb7ccd2ea] > 13: /usr/bin/X(xf86Wakeup+0x3bd) [0x80c9d4d] > 14: /usr/bin/X(WakeupHandler+0x59) [0x80929e9] > 15: /usr/bin/X(WaitForSomething+0x1ae) [0x81b88ee] > 16: /usr/bin/X(Dispatch+0x82) [0x808ec22] > 17: /usr/bin/X(main+0x495) [0x8076e85] > 18: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7df7050] > 19: /usr/bin/X(FontFileCompleteXLFD+0x1ed) [0x80761c1] > Looks like #431373 and the upstream bug at https://bugs.freedesktop.org/show_bug.cgi?id=12072 So I am merging with these bugs. Feel free to add any comments at the URL above if you think it could help. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to xdmx xdmx-tools xnest xorg-server xprint xprint-common xserver-xephyr xserver-xfbdev xserver-xorg-core xserver-xorg-core-dbg xserver-xorg-dev xvfb ...
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.8 > package xdmx xdmx-tools xnest xorg-server xprint xprint-common xserver-xephyr > xserver-xfbdev xserver-xorg-core xserver-xorg-core-dbg xserver-xorg-dev xvfb Ignoring bugs not assigned to: xdmx-tools xvfb xserver-xorg-core xnest xserver-xfbdev xserver-xorg-core-dbg xserver-xorg-dev xdmx xprint xorg-server xprint-common xserver-xephyr > tags 445266 + pending Bug#445266: xorg-server: [INTL:pt_BR] Brazilian Portuguese debconf templates translation Tags were: l10n patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xorg-server: Changes to 'debian-unstable'
debian/changelog |4 +++- debian/po/pt.po | 51 ++- debian/po/ru.po | 43 --- 3 files changed, 37 insertions(+), 61 deletions(-) New commits: commit dfc567efa056d27373420ac3dcec20b25afd025a Author: Christian Perrier <[EMAIL PROTECTED]> Date: Thu Oct 4 20:05:38 2007 +0200 Russian and Portuguese translation updates diff --git a/debian/changelog b/debian/changelog index 97fb232..a1541c7 100644 --- a/debian/changelog +++ b/debian/changelog @@ -15,8 +15,10 @@ xorg-server (2:1.4-4) UNRELEASED; urgency=low * Galician. Closes: #444764 * German. Closes: #444917 * Brazilian Portuguese. Closes: #445266 + * Russian. Closes: #443859 + * Portuguese. Closes: #445051 - -- Christian Perrier <[EMAIL PROTECTED]> Thu, 04 Oct 2007 20:01:43 +0200 + -- Christian Perrier <[EMAIL PROTECTED]> Thu, 04 Oct 2007 20:05:23 +0200 xorg-server (2:1.4-3) unstable; urgency=low diff --git a/debian/po/pt.po b/debian/po/pt.po index a98deb8..6823df4 100644 --- a/debian/po/pt.po +++ b/debian/po/pt.po @@ -1,16 +1,16 @@ -# Portuguese translation of xprint debconf messages. -# This file is distributed under the same license as the xprint package. -# Manuel Padilha <[EMAIL PROTECTED]>, 2006. -# -# +# Portuguese translation for xorg-server's debconf messages +# Copyright (C) 2007 Miguel Figueiredo +# This file is distributed under the same license as the xorg-server package. +# Miguel Figueiredo <[EMAIL PROTECTED]>, 2007. +# msgid "" msgstr "" -"Project-Id-Version: xprint 1:1.0.2-1\n" +"Project-Id-Version: xorg-server\n" "Report-Msgid-Bugs-To: [EMAIL PROTECTED]" -"POT-Creation-Date: 2007-09-18 20:35+0200\n" -"PO-Revision-Date: 2006-09-10 21:49+0100\n" -"Last-Translator: Manuel Padilha <[EMAIL PROTECTED]>\n" -"Language-Team: Native Portuguese <[EMAIL PROTECTED]>\n" +"POT-Creation-Date: 2007-09-18 07:46+0200\n" +"PO-Revision-Date: 2007-10-02 21:27+\n" +"Last-Translator: Miguel Figueiredo <[EMAIL PROTECTED]>\n" +"Language-Team: Portuguese <[EMAIL PROTECTED]>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -18,36 +18,22 @@ msgstr "" #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "Default printer resolution" msgid "Default printer resolution:" -msgstr "Resolução por omissão da impressora" +msgstr "Resolução de impressão pré-definida:" #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "" -#| "By default Xprint assumes a printer resolution of 600dpi. This should be " -#| "fine for the majority of printers today." msgid "" "By default, Xprint assumes a printer resolution of 600 dpi. This should be " "well suited for the majority of printers." msgstr "" -"O Xprint assume que a resolução por omissão das impressoras é 600dpi. Este " -"valor deve ser correcto para a maior parte das impressoras." +"Como pré-definição o Xprint assume que a resolução da sua impressora é de " +"600 dpi. Isto deve ser adequado para a maioria das impressoras." #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "" -#| "On certain 1200dpi printers, however, the image might appear squashed in " -#| "the corner of the page, or it might be blown up too large on 300dpi " -#| "printers. If you are experiencing these kinds of printing problems, you " -#| "may want to set the default printer resolution to a more appropriate " -#| "value. See /usr/share/doc/xprint-common/README.printing-problems.gz for " -#| "more details." msgid "" "On certain 1200 dpi printers, however, the image might appear squashed in " "the corner of the page, or it might be blown up too large on 300 dpi " @@ -55,9 +41,8 @@ msgid "" "set the default printer resolution to a more appropriate value. See /usr/" "share/doc/xprint-common/README.printing-problems.gz for more details." msgstr "" -"Contudo, em certas impressoras de 1200dpi a imagem pode aparecer esmagada " -"contra o canto da página, ou - em impressoras de 300dpi, exageradamente " -"ampliada. Se estiver a passar por este tipo de dificuldades pode " -"experimentar mudar o valor da resolução por omissão das impressoras para um " -"valor mais apropriado. Pode obter mais informação em /usr/share/doc/xprint-" -"common/README.printing-problems.gz." +"No entanto, nalgumas impressoras de 1200 dpi a imagem pode parecer encolhida " +"no canto da página, ou pode aparecer demasiado grande em impressoras de 300 " +"dpi. Se estiver a ter estes problemas de impressão, você pode querer definir " +"a resolução de impressão pré-definida para um valor mais apropriado. Para " +"mais detalhes veja /usr/share/doc/xprint-common/README.printing-problems.gz." diff --git a/debian/po/ru.po b/debian/po/ru.po index efe7efa..d7fd3c3 100644 --- a/debian/po/ru.po +++ b/debian/po/ru.po @@ -1,4 +1,4 @@ -# translation of xprint_1.0.2-1.ru.po to Russian +# translation of r
xorg-server: Changes to 'debian-unstable'
debian/changelog |3 - debian/po/pt_BR.po | 152 +++-- 2 files changed, 46 insertions(+), 109 deletions(-) New commits: commit d102be5ced63aa4002c2f88cade38a2acceafdba Author: Christian Perrier <[EMAIL PROTECTED]> Date: Thu Oct 4 20:02:41 2007 +0200 Brazilian translation update diff --git a/debian/changelog b/debian/changelog index 3f2fbc9..97fb232 100644 --- a/debian/changelog +++ b/debian/changelog @@ -14,8 +14,9 @@ xorg-server (2:1.4-4) UNRELEASED; urgency=low * Debconf translations: * Galician. Closes: #444764 * German. Closes: #444917 + * Brazilian Portuguese. Closes: #445266 - -- Christian Perrier <[EMAIL PROTECTED]> Tue, 02 Oct 2007 19:41:35 +0200 + -- Christian Perrier <[EMAIL PROTECTED]> Thu, 04 Oct 2007 20:01:43 +0200 xorg-server (2:1.4-3) unstable; urgency=low diff --git a/debian/po/pt_BR.po b/debian/po/pt_BR.po index 560fb9b..ef55ee4 100644 --- a/debian/po/pt_BR.po +++ b/debian/po/pt_BR.po @@ -1,61 +1,40 @@ -# -#Translators, if you are not familiar with the PO format, gettext -#documentation is worth reading, especially sections dedicated to -#this format, e.g. by running: -# info -n '(gettext)PO Files' -# info -n '(gettext)Header Entry' -# -#Some information specific to po-debconf are available at -#/usr/share/doc/po-debconf/README-trans -# or http://www.debian.org/intl/l10n/po-debconf/README-trans -# -#Developers do not need to manually edit POT or PO files. +# portmap Brazilian Portuguese translation +# Copyright (C) 2007 THE portmap'S COPYRIGHT HOLDER +# This file is distributed under the same license as the portmap package. +# Felipe Augusto van de Wiel (faw) <[EMAIL PROTECTED]>, 2007. +# Eder L. Marques (frolic) <[EMAIL PROTECTED]>, 2007. # msgid "" msgstr "" -"Project-Id-Version: xprint\n" +"Project-Id-Version: portmap 6.0-2\n" "Report-Msgid-Bugs-To: [EMAIL PROTECTED]" "POT-Creation-Date: 2007-09-18 20:35+0200\n" -"PO-Revision-Date: 2005-03-26 09:55-0300\n" -"Last-Translator: Andr� Lu�s Lopes <[EMAIL PROTECTED]>\n" -"Language-Team: Debian-BR Project <[EMAIL PROTECTED]>\n" +"PO-Revision-Date: 2007-10-03 17:17-0300\n" +"Last-Translator: Eder L. Marques (frolic) <[EMAIL PROTECTED]>\n" +"Language-Team: l10n Portuguese <[EMAIL PROTECTED]>\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=ISO-8859-1\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" +"pt_BR utf-8\n" +"X-Generator: KBabel 1.11.4\n" #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "Default printer resolution" msgid "Default printer resolution:" -msgstr "Resolu��o padr�o de impressoras" +msgstr "" #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "" -#| "By default Xprint assumes a printer resolution of 600dpi. This should be " -#| "fine for the majority of printers today." msgid "" "By default, Xprint assumes a printer resolution of 600 dpi. This should be " "well suited for the majority of printers." msgstr "" -"Por padr�o, o Xprint assume uma resolu��o de impress�o de 600dpi. Essa " -"resolu��o � adequada para a maioria das impressoras atuais." #. Type: string #. Description #: ../xprint-common.templates:2001 -#, fuzzy -#| msgid "" -#| "On certain 1200dpi printers, however, the image might appear squashed in " -#| "the corner of the page, or it might be blown up too large on 300dpi " -#| "printers. If you are experiencing these kinds of printing problems, you " -#| "may want to set the default printer resolution to a more appropriate " -#| "value. See /usr/share/doc/xprint-common/README.printing-problems.gz for " -#| "more details." msgid "" "On certain 1200 dpi printers, however, the image might appear squashed in " "the corner of the page, or it might be blown up too large on 300 dpi " @@ -63,87 +42,44 @@ msgid "" "set the default printer resolution to a more appropriate value. See /usr/" "share/doc/xprint-common/README.printing-problems.gz for more details." msgstr "" -"Em certas impressoras com resolu��o de 1200dpi, por�m, imagens podem " -"aparecer achatadas no canto da p�gina ou podem parecer muito grandes em " -"impressoras 300dpi. Caso voc� esteja tendo esses tipos de problemas de " -"impress�o, voc� pode desejar configurar a resolu��o padr�o da impressora " -"para um valor mais apropriado. Consulte o arquivo /usr/share/doc/xprint-" -"common/README.printing-problems.gz para maiores detalhes." - -#, fuzzy -#~ msgid "" -#~ "If you are experiencing these kinds of printing problems, you may want to " -#~ "set the default printer resolution to a different value." -#~ msgstr "" -#~ "Caso voc� esteja passando por esses tipos de problemas de impress�o, voc� " -#~ "pode desejar definir a resolu��o padr�o da impress�o para um valor que " -#~ "sua impressora possa utilizar." - -#~ msgid "" -#~ "This value is written into the *default-printer-re
Processed: setting package to xdmx xdmx-tools xnest xorg-server xprint xprint-common xserver-xephyr xserver-xfbdev xserver-xorg-core xserver-xorg-core-dbg xserver-xorg-dev xvfb ... ... ...
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.8 > package xdmx xdmx-tools xnest xorg-server xprint xprint-common xserver-xephyr > xserver-xfbdev xserver-xorg-core xserver-xorg-core-dbg xserver-xorg-dev xvfb Ignoring bugs not assigned to: xdmx-tools xvfb xserver-xorg-core xnest xserver-xfbdev xserver-xorg-core-dbg xserver-xorg-dev xdmx xprint xorg-server xprint-common xserver-xephyr > tags 443859 + pending Bug#443859: xorg-server: [INTL:ru] Russian debconf templates translation update Tags were: l10n patch Tags added: pending > tags 445051 + pending Bug#445051: xorg-server: [INTL:pt] Portuguese translation for debconf messages Tags were: l10n patch Tags added: pending > tags 445266 + pending Bug#445266: xorg-server: [INTL:pt_BR] Brazilian Portuguese debconf templates translation Tags were: pending l10n patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#444656: xserver-xorg-video-nv: Samsung LCD Syncmaster does not resume after dpms sleep
On 10/1/07, Brice Goglin <[EMAIL PROTECTED]> wrote: > > So your problem appeared between 2.1.3 and 2.1.5. There are only 8 > commits between there releases. The only one that really changes some > code is: > http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-nv.git;a=commitdiff_plain;h=b2db7d414400d80a5567d71eed9a7e94f1043a20;hp=07fb9f0b00fafe18bd33bddff23cbb4325eb50f8 > > Could you try applying on top of your rebuilt 2.1.3 and see whether it > causes the problem to occur? > > Thanks, > Brice > > I applied this patch, and it changed two source files. I rebuilt the package, which has a slightly different size so it definitely changed. The problem now appears, so this patch causes the problem. After installing the patched version of 2.1.3 I rebooted to be sure. The problem appeared after letting the monitor sleep for about three minutes. Power-cycling the monitor restores the image; nothing else can. Let me know if I can help further. Thanks for you interest in this, I've had fun learning how to do new things. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445313: blender crashes on startup in mga_dri.so
Package: libgl1-mesa-dri Version: 7.0.1-2 Severity: important Blender (2.45-1) crashes on startup in mga_dri.so: guessing 'blender-bin' == '/usr/bin/blender-bin' Compiled with Python version 2.4.4. Checking for installed Python... got it! /usr/bin/blender: line 46: 19547 Segmentation fault blender-bin "$@" I'm running kernel 2.6.22.5. Below is a backtrace from gdb, lspci -v output, and my Xorg.0.log. If any other information would be helpful, please let me know. Thanks, James Dietrich Here is the gdb backtrace: [snipped a bunch of Reading and Loaded symbols lines] Core was generated by `blender-bin'. Program terminated with signal 11, Segmentation fault. #0 _generic_read_RGBA_span_RGB565_MMX () at x86/read_rgba_span_x86.S:590 590 x86/read_rgba_span_x86.S: No such file or directory. in x86/read_rgba_span_x86.S (gdb) bt #0 _generic_read_RGBA_span_RGB565_MMX () at x86/read_rgba_span_x86.S:590 #1 0xb69523ef in mgaReadRGBASpan_565_MMX (ctx=0x8ad03b8, rb=0x8d0be00, n=5, x=32, y=251, values=0xb3d1d00c) at ../../../../../src/mesa/drivers/dri/common/spantmp2.h:427 #2 0xb6a16f28 in _swrast_get_dest_rgba (ctx=0x8ad03b8, rb=0x8d0be00, span=0x5) at swrast/s_span.c:1943 #3 0xb6a9cfee in _swrast_blend_span (ctx=0x8ad03b8, rb=0x8d0be00, span=0xbfb803f8) at swrast/s_blend.c:997 #4 0xb6a198d5 in _swrast_write_rgba_span (ctx=0x8ad03b8, span=0xbfb803f8) at swrast/s_span.c:1627 #5 0xb6a961f2 in rgba_aa_tri (ctx=0x8ad03b8, v0=0xbfb8086c, v1=0xbfb809cc, v2=0xbfb80b2c) at swrast/s_aatritemp.h:456 #6 0xb69335dc in mga_fallback_tri (mmesa=0x8acab10, v0=0xb3a8e020, v1=0xb3a8e040, v2=0xb3a8e060) at mgatris.c:291 #7 0xb692feb6 in triangle_fallback_flat (ctx=0x8ad03b8, e0=0, e1=1, e2=2) at ../../../../../src/mesa/tnl_dd/t_dd_tritmp.h:340 #8 0xb69e1725 in _tnl_render_triangles_verts (ctx=0x8ad03b8, start=0, count=3, flags=52) at tnl/t_vb_rendertmp.h:163 #9 0xb69e2b82 in run_render (ctx=0x8ad03b8, stage=0x8b18044) at tnl/t_vb_render.c:320 #10 0xb69da35b in _tnl_run_pipeline (ctx=0x8ad03b8) at tnl/t_pipeline.c:158 #11 0xb69da833 in _tnl_draw_prims (ctx=0x8ad03b8, arrays=0x8b06270, prim=0x8b04dcc, nr_prims=2, ib=0x0, min_index=0, max_index=5) ---Type to continue, or q to quit--- at tnl/t_draw.c:403 #12 0xb69d3a36 in vbo_exec_vtx_flush (exec=0x8b04ca8) at vbo/vbo_exec_draw.c:215 #13 0xb69cf6c8 in vbo_exec_FlushVertices (ctx=0x8ad03b8, flags=1) at vbo/vbo_exec_api.c:685 #14 0xb6a6c79e in _mesa_set_enable (ctx=0x8ad03b8, cap=3042, state=0 '\0') at main/enable.c:250 #15 0xb6a6caea in _mesa_Disable (cap=3042) at main/enable.c:961 #16 0x081553eb in ?? () #17 0x0be2 in ?? () #18 0x40c0 in ?? () #19 0x080b6202 in ?? () #20 0xb727d140 in ?? () from /lib/libc.so.6 #21 0x4130 in ?? () #22 0x4210 in ?? () #23 0x4200 in ?? () #24 0x4208 in ?? () #25 0x4110 in ?? () #26 0x002601e8 in ?? () #27 0x037f0c7f in ?? () #28 0x0888d6ec in ?? () #29 0x08d7bf00 in ?? () #30 0x08d7bf00 in ?? () ---Type to continue, or q to quit--- #31 0xbfb81198 in ?? () #32 0x0815a335 in ui_draw_but () Backtrace stopped: frame did not save the PC Current language: auto; currently asm (gdb) Here is the output from lspci -v: 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03) Subsystem: ASUSTeK Computer Inc. A7V133/A7V133-C Mainboard Flags: bus master, medium devsel, latency 8 Memory at e600 (32-bit, prefetchable) [size=32M] Capabilities: [a0] AGP version 2.0 Capabilities: [c0] Power Management version 2 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e280-e3df Prefetchable memory behind bridge: e3f0-e5ff Capabilities: [80] Power Management version 2 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) Subsystem: ASUSTeK Computer Inc. A7V133/A7V133-C Mainboard Flags: bus master, stepping, medium devsel, latency 0 Capabilities: [c0] Power Management version 2 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Flags: bus master, medium devsel, latency 32 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [size=1] [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 0370 (type 3, non-prefetchable) [size=1] I/O ports at d800 [size=16] Capabilities: [c0] Power Management version 2 00:04.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 16) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong
Bug#445313: blender crashes on startup in mga_dri.so
[EMAIL PROTECTED] wrote: > Package: libgl1-mesa-dri > Version: 7.0.1-2 > Severity: important > > Blender (2.45-1) crashes on startup in mga_dri.so: > guessing 'blender-bin' == '/usr/bin/blender-bin' > Compiled with Python version 2.4.4. > Checking for installed Python... got it! > /usr/bin/blender: line 46: 19547 Segmentation fault blender-bin > "$@" > > I'm running kernel 2.6.22.5. > > Below is a backtrace from gdb, lspci -v output, > and my Xorg.0.log. > > If any other information would be helpful, > please let me know. > Your backtrace would be better if you enter 'bt full' instead of 'bt' to display it. Anyway, I don't see any similar backtrace in the upstream bugzilla. I would be great if you could report this bug upstream at bugzilla.freedesktop.org, product Mesa. Let me know if you can't do so. thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428091: Disabling DDC
On Thu, 2007-10-04 at 08:37 +0200, Brice Goglin wrote:
> Andrew Ruthven wrote:
> > Okay, I've installed xserver-xorg-core-dbg, but how do I tell X.org to
> > use these debug modules instead?
> >
> There's nothing to do. The server still uses the same modules, but gdb
> will know where to look for the corresponding debugging symbols that
> xserver-xorg-core-dbg installed.
Really? I doesn't seem to be...
> > Program received signal SIGFPE, Arithmetic exception.
> > [Switching to Thread 0xb7c698c0 (LWP 4252)]
> > 0xb7b5407d in ?? () from /usr/lib/xorg/modules/drivers//mga_drv.so
> >
>
> Did you have such a SIGFPE before?
Nope. And when I run gdb /usr/bin/X11/Xorg it doesn't appear.
> You should enter "bt full" here (at soon as gdb catches a crash).
> Continuing like this gives the hand back to the server which catches its
> own crash and outputs the useless backtrace.
I had been using the Xdbg script which does the continue and just dumps
the log to a file.
I've just run gdb manually and grabbed the backtrace. Here it is:
(gdb) bt full
#0 0x in ?? ()
No symbol table info available.
#1 0xb7b06728 in ?? () from /usr/lib/xorg/modules/drivers//mga_drv.so
No symbol table info available.
#2 0x082193b8 in ?? ()
No symbol table info available.
#3 0xb7a7f000 in ?? ()
No symbol table info available.
#4 0x1c00 in ?? ()
No symbol table info available.
#5 0xbfea4998 in ?? ()
No symbol table info available.
#6 0xb7d48090 in malloc () from /lib/libc.so.6
No symbol table info available.
#7 0x08073c9c in AddScreen (pfnInit=0xb7b065d0, argc=1,
argv=0xbfea4b74)
at ../../dix/main.c:769
i = 0
scanlinepad =
depth =
bitsPerPixel = 1
k = 2
pScreen =
#8 0x080a7f5e in InitOutput (pScreenInfo=0x8204a00, argc=1,
argv=0xbfea4b74)
at ../../../../hw/xfree86/common/xf86Init.c:850
i = 0
j =
k =
scr_index = 136333824
modulelist =
optionlist = (pointer *) 0x8213558
layout =
screenpix24 =
pix24 = Pix24Use32
pix24From = X_DEFAULT
autoconfig =
generation = 1
#9 0x08074426 in main (argc=1, argv=0xbfea4b74, envp=0xbfea4b7c)
at ../../dix/main.c:369
i =
error = 136144064
xauthfile =
alwaysCheckForInput = {0, 1}
(gdb)
--
Andrew Ruthven, Wellington, New Zealand
At home: [EMAIL PROTECTED] | This space intentionally
|left blank.
signature.asc
Description: This is a digitally signed message part
Processed: Re: Bug#444656: xserver-xorg-video-nv: Samsung LCD Syncmaster does not resume after dpms sleep
Processing commands for [EMAIL PROTECTED]: > forwarded 444656 https://bugs.freedesktop.org/show_bug.cgi?id=12680 Bug#444656: xserver-xorg-video-nv: Samsung LCD Syncmaster does not resume after dpms sleep Noted your statement that Bug has been forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=12680. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#444656: xserver-xorg-video-nv: Samsung LCD Syncmaster does not resume after dpms sleep
forwarded 444656 https://bugs.freedesktop.org/show_bug.cgi?id=12680 thank you Tim Richardson wrote: >> http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-nv.git;a=commitdiff_plain;h=b2db7d414400d80a5567d71eed9a7e94f1043a20;hp=07fb9f0b00fafe18bd33bddff23cbb4325eb50f8 >> > I applied this patch, and it changed two source files. I rebuilt the > package, which has a slightly different size so it definitely changed. > > The problem now appears, so this patch causes the problem. After > installing the patched version of 2.1.3 I rebooted to be sure. The > problem appeared after letting the monitor sleep for about three > minutes. Power-cycling the monitor restores the image; nothing else > can. > I have forwarded your problem upstream at the URL above. Feel free to add any comment there if you think it could help. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445322: xserver-xorg: xserver dies when switching sessions
Package: xserver-xorg Version: 1:7.2-5 Severity: normal This bug is causing me big problems, but I guess it's peculiar to my setup or use (perhaps few people use multiple KDE sessions). It appeared perhaps a month or two ago. I use KDE and often have several user sessions running in different virtual terminals (vt7, vt8,...). The KDE menu provides a facility to "switch user" which can switch among existing sessions or make new ones. Sometimes, but not always, switching between sessions (or creating a new one, I think, but am less sure) kills the originating X session. It also sometimes messes up the target X session. In the most recent incident, the target X session did not respond to mouse clicks, though it responded to mouse movement. I killed the screensaver and several applications, and then the mouse clicks worked again. An Xorg.log from the time of a recent problem shows Backtrace: 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8631] 1: [0xb7f8a420] 2: /usr/bin/X [0x814aafe] 3: /usr/bin/X [0x814b942] 4: /usr/bin/X [0x8154a3e] 5: /usr/bin/X(Dispatch+0x19f) [0x808ed3f] 6: /usr/bin/X(main+0x495) [0x8076e85] 7: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d93050] 8: /usr/bin/X(FontFileCompleteXLFD+0x1ed) [0x80761c1] Fatal server error: Caught signal 11. Server aborting (is 0 or 8 the most recent?). I have since installed xserver-xorg-core-dbg, but have not been able to get the crash. My daughter thinks it happens when she scrolls the mouse wheel, but that didn't work for me. It seems more likely to happen after there has been a long period of inactivity. xorg and iceweasel often have very large VM's, at least several hundred MB. I have 2G physical RAM. There are a lot of potential culprits including KDE (maybe kdmctl) and my proprietary nvidia driver. The free nv driver doesn't work at all for me (bug 342817). One reason to suspect the former is that I have not seen a problem with the ctl-atl-Fn to switch, just the KDE switch user. A reason to suspect the latter (aside from the "all bets are off if you use it" problem) is that there have been no updates to the Debian packages of nvidia for at least a few months, and those packages are out of sync with the current kernels. I'm not sure exactly how of sync they can get before there is a problem; the package I have is for nvidia-kernel-2.6.18-5-686 and that still matches the kernel I'm on. However, there have been minor Debian version updates to the kernel since the nvidia package was created. My .xsession-errors (this is from the session switched into when the last problem occurred) shows lavalite: warning: blocked event processing for 1.7 secs! lavalite: warning: only 3% idle over the last 11 secs (at 1.0 FPS) lavalite: warning: only 7% idle over the last 10 secs (at 2.4 FPS) lavalite: warning: blocked event processing for 3.2 secs! QGDict::hashKeyString: Invalid null key akregator: ERROR: : couldn't create slave : Unable to create io-slave: klauncher said: Unknown protocol ''. akregator: ASSERT: "!icon.isEmpty()" in /home/adeodato/tmp/b/kdebase-3.5.7/./libkonq/konq_pixmapprovider.cc (81) ASSERT: "!icon.isEmpty()" in /home/adeodato/tmp/b/kdebase-3.5.7/./libkonq/konq_pixmapprovider.cc (81) ASSERT: "!icon.isEmpty()" in /home/adeodato/tmp/b/kdebase-3.5.7/./libkonq/konq_pixmapprovider.cc (81) ASSERT: "!icon.isEmpty()" in /home/adeodato/tmp/b/kdebase-3.5.7/./libkonq/konq_pixmapprovider.cc (81) lavalite: warning: blocked event processing for 2.0 secs! lavalite: warning: only 7% idle over the last 11 secs (at 2.4 FPS) lavalite is the screensaver I use, I think. I don't know what the significance of these messages is. There were also thousands of ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave errors in the log; I edited them out above. I'm a little puzzled how to proceed. Is the intent that we get assistance from the upstream list? There used to be a FAQ (#408293) and some online pages, but I can't find them, README.Debians in /usr/share/doc/, or anything else. For example, I don't know if there's a way to get more debugging output to help diagnose the problem (other than loading the debug symbols). It would be handy if .xsession-erros and Xorg.*.log had timestamps. Anyway, this looks like a really unpleasant problem to diagnose and fix. I'd appreciate any help you can offer. -- Package-specific info: 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 2006-06-03 09:08 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1736632 2007-08-09 10:39 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 PCIe] (rev a2) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -r--r--r-- 1 root root 4509 2007-10-
Bug#445322: xserver-xorg: xserver dies when switching sessions
reassign 445322 nvidia-glx forcemerge 432101 445322 thank you Ross Boylan wrote: > I use KDE and often have several user sessions running in different > virtual terminals (vt7, vt8,...). The KDE menu provides a facility to > "switch user" which can switch among existing sessions or make new > ones. > > Sometimes, but not always, switching between sessions (or creating a > new one, I think, but am less sure) kills the originating X session. > It also sometimes messes up the target X session. In the most recent > incident, the target X session did not respond to mouse clicks, though > it responded to mouse movement. I killed the screensaver and several > applications, and then the mouse clicks worked again. > > An Xorg.log from the time of a recent problem shows > Backtrace: > 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8631] > 1: [0xb7f8a420] > 2: /usr/bin/X [0x814aafe] > 3: /usr/bin/X [0x814b942] > 4: /usr/bin/X [0x8154a3e] > 5: /usr/bin/X(Dispatch+0x19f) [0x808ed3f] > 6: /usr/bin/X(main+0x495) [0x8076e85] > 7: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d93050] > 8: /usr/bin/X(FontFileCompleteXLFD+0x1ed) [0x80761c1] > This seems very similar to #432101. There's probably no symbol names in your backtrace because those symbols are hidden in the nvidia binary driver. When the crash occurs there like the one above, we can't do much about it unfortunately. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#445322: xserver-xorg: xserver dies when switching sessions
Processing commands for [EMAIL PROTECTED]: > reassign 445322 nvidia-glx Bug#445322: xserver-xorg: xserver dies when switching sessions Bug reassigned from package `xserver-xorg' to `nvidia-glx'. > forcemerge 432101 445322 Bug#432101: xserver-xorg-core: Crash when swithching to another X server Bug#445322: xserver-xorg: xserver dies when switching sessions Forcibly Merged 432101 445322. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445313: blender crashes on startup in mga_dri.so
On Thu, 2007-10-04 at 15:53 -0400, [EMAIL PROTECTED] wrote: > > #0 _generic_read_RGBA_span_RGB565_MMX () at > x86/read_rgba_span_x86.S:590 Looks like https://bugs.freedesktop.org/show_bug.cgi?id=12614#c6 . -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
32 sites for free
promo, 32 x x x sites free www 7promo dot cn Maxwellian reformatting Pewaukee celestialness wrapping divining promenades recapturer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445313: blender crashes on startup in mga_dri.so
On Thu, 04 Oct 2007 22:36:14 +0200, "Brice Goglin"
<[EMAIL PROTECTED]> said:
> Your backtrace would be better if you enter 'bt full' instead of 'bt' to
> display it.
Here it is:
Core was generated by `blender-bin'.
Program terminated with signal 11, Segmentation fault.
#0 _generic_read_RGBA_span_RGB565_MMX () at
x86/read_rgba_span_x86.S:590
590 x86/read_rgba_span_x86.S: No such file or directory.
in x86/read_rgba_span_x86.S
(gdb) bt full
#0 _generic_read_RGBA_span_RGB565_MMX () at
x86/read_rgba_span_x86.S:590
No locals.
#1 0xb69523ef in mgaReadRGBASpan_565_MMX (ctx=0x8ad03b8, rb=0x8d0be00,
n=5,
x=32, y=251, values=0xb3d1d00c)
at ../../../../../src/mesa/drivers/dri/common/spantmp2.h:427
i = 0
minx =
maxx =
mmesa = (mgaContextPtr) 0x8acab10
dPriv =
buf = 0xb5190f00
x1 = 5
n1 = 5
pitch = 3840
#2 0xb6a16f28 in _swrast_get_dest_rgba (ctx=0x8ad03b8, rb=0x8d0be00,
span=0x5)
at swrast/s_span.c:1943
pixelSize =
rbPixels = (void *) 0xb3d1d00c
#3 0xb6a9cfee in _swrast_blend_span (ctx=0x8ad03b8, rb=0x8d0be00,
span=0xbfb803f8) at swrast/s_blend.c:997
swrast = (SWcontext *) 0x8afb430
rbPixels =
#4 0xb6a198d5 in _swrast_write_rgba_span (ctx=0x8ad03b8,
span=0xbfb803f8)
---Type to continue, or q to quit---
at swrast/s_span.c:1627
rb = (struct gl_renderbuffer *) 0x8d0be00
numDrawBuffers = 1
rgbaSave = {"\000Ra", "\000\000Rc", "\000\000\000R",
"e\000\000",
"(\000\000", "\000(\000", "\000\000R\a", "\000\000\000t",
"\b\000\000",
"__in", "it__", "�\000\000", "s\n\000", "\000\000\001\t",
"\001\t\001\t",
"\001\t\001c", "\001\000\000", "\005\000\000", "\a\000\000",
"C\000\000",
"s�\000", "\000|\000", "i\001\000o", "\b\000\001d",
"\000\000Sn",
"\001\000\001d", "\000\000}\002", "\000x\206", "|\000\000i",
"\004\000D]",
"{\000}\004", "\000xf", "|\000\000i", "\006\000D]", "[\000}\003",
"\000t\b",
"i\t\000i", "\n\000|\004", "\000|\003", "\203\002\000}", "\003\000y*",
"\000t\v", "|\003\000d", "\001\000\203\002", "\000}\001",
"|\001\000i",
"\r\000\203", "\000}\002", "|\001\000i", "\016\000\203", "\000\001PW",
"q2\000\004", "t\017\000j", "\n\000o\a", "\000\001\001\001", "\001q2",
"\001Xq2", "\000W|\002", "\000o\005", "\001Pq\"", "\000\001q\"",
"\000W|\002", "\000p\r", "\001|\000", "i\020\000}", "\002\000n\001",
"\000\001|\002", "\000i\021", "d\002\000\203", "\001\000|",
"\000_\001",
"t\022\000|", "\000\000i\001", "\000\203\001", "|\000\000_",
"\023\000d",
"\000S(\003", "\000\000\000N", "R$\000", "\000s\001", "\000\000\n(",
"\024\000\000", "R_\000", "\000Rg", "\000\000R'", "\000\000\000R",
"a\000\000", "Rf\000", "\000R\005", "\000\000Rd", "\000\000\000t",
"\b\000\000", "file", "name", "R\000\000", "\000R\001",
"\000\000R\003",
"\000\000\000t", "\004\000\000", "file", "t\002\000", "\000fpt",
---Type to continue, or q to quit---
"\004\000\000", "read", "R3\000", "\000R.", "\000\000Rb",
"\000\000\000R",
"V\000\000", "t\003\000", "\000len", "t\021\000", "\000_Pr", "inte",
"r__l",
"inec", "nt(\005", "\000\000\000R", "_\000\000", "Rk\000", "\000Ra",
"\000\000Ri", "\000\000\000R", "\005\000\000", "(\000\000",
"\000(\000",
"\000\000R\a", "\000\000\000t", "\a\000\000", "__se", "tup",
"\001\000\000s", "*\000\000", "\000\001\n\001", "\b\001\006\001",
"\n\000\006\001", "\n\000\006\001", "\025\001\003\001",
"\017\001\f\001",
"\n\001\005\001", "\016\001\t\001", "\a\001\t\001", "\a\001\r\001",
"\022\001c\001", "\000\000\000\001", "\000\000\000\003",
"\000\000\000C",
"\000\000\000s", "M\000\000", "|\000\000i", "\001\000\203",
"�\005,�",
"\020ii\r", "`���", "Lŷ�",
"(���", "�\235\024�",
"�\005,�", "D�9�", "4�9�",
"��\023�", "\002\000��",
"\tP��", "�\005,�", "@�9�",
"�/��", "\220ŷ�",
"l%�\b", "�ŷ�",
"", "\001\000\000", "\ns!",
"\000\000Ty", "pe %",
"<���", "\220ŷ�",
"�Ʒ�", "�?\f�", "@\000\000",
"L�\023�", "$\234\023�",
"\203�+�", "�?\f�",
"\205�+�", "\207�+�", "\000\000\000",
"\000\000\000",
"\001\000\000", "�\000\000", "`���",
"\000\000(�", "\203�+�", "\\H\024�",
"�\210+�", "\001\000\000", "�/��",
"��9�", "\230Ʒ�",
"�Ʒ�", ""...}
buf = 0
swrast = (const SWcontext *) 0x8afb430
colorMask = 4294967295
origInterpMask = 0
origArrayMask = 553
chanType = 5121
---Type to continue, or q to quit---
shader = 0 '\0'
fb = (struct gl_framebuffer *) 0x8d0b9a0
output = 0
deferredTexture = 0 '\0'
#5 0xb6a961f2 in rgba_aa_tri (ctx=0x8ad03b8, v0=0xbfb8086c,
v1=0xbfb809cc,
v2=0xbfb80b2c) at swrast/s_aatritemp.h:456
startX =
coverage =
ix = -1279426056
left = 32
n = 5
pMin =
pMid =
pMax =
iy = 251
dxdy = -0.87012
xAdj = 0
x = 36.625068
Bug#443503: Mouse double clicks always
Bernhard, Thanks for the tip. It works with one mouse configured, and with the latest xorg packages. Next time I'll reboot I'll try it with 2 mice configure (like it was before I upgraded). Mick On 10/4/07, Bernhard Sputh <[EMAIL PROTECTED]> wrote: > > Hi Mike, > > I was hit by the same problem, and got it solved by adding > `Option "CorePointer"' to my only InputDevice section referring to the > device "/dev/input/mice". This stopped the unwanted double clicks from > occurring. > > So try the following InputDevice section: > > Section "InputDevice" > Identifier"Generic Mouse" > Driver"mouse" > Option"CorePointer" > Option"Device""/dev/input/mice" > Option"Protocol" "ImPS/2" > Option"ZAxisMapping" "4 5" > EndSection > > > Hope this helps you and others fighting the same problem. > > Cheers > Bernhard > > >
mesa: Changes to 'debian-unstable'
configs/debian-dri-default |2 +- debian/changelog |9 + 2 files changed, 10 insertions(+), 1 deletion(-) New commits: commit c3de7b5ade1a46c2abb4ebad40233c8c0e4101bf Author: David Nusinow <[EMAIL PROTECTED]> Date: Thu Oct 4 23:10:47 2007 -0400 Don't release just yet. diff --git a/debian/changelog b/debian/changelog index ee088f5..1d4da47 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -mesa (7.0.1-3) unstable; urgency=low +mesa (7.0.1-3) UNRELEASED; urgency=low * Disable building i915tex. It was previously only built on x86 and amd64. It was never commit 76556f82646d4a0db15a06e1392e24a6457b1642 Author: David Nusinow <[EMAIL PROTECTED]> Date: Thu Oct 4 22:49:27 2007 -0400 * Disable building i915tex. It was previously only built on x86 and amd64. It was never production-ready and relies on a kernel interface that never went upstream. diff --git a/configs/debian-dri-default b/configs/debian-dri-default index f92c7ed..2a01bf8 100644 --- a/configs/debian-dri-default +++ b/configs/debian-dri-default @@ -23,7 +23,7 @@ DRI_DIRS = mach64 mga r128 r200 r300 radeon s3v savage tdfx trident ARCH_X86 = i386 amd64 ifneq ($(findstring $(DEB_BUILD_ARCH), $(ARCH_X86)),) - DRI_DIRS += i810 i915 i915tex i965 sis unichrome + DRI_DIRS += i810 i915 i965 sis unichrome endif ifeq ($(DEB_BUILD_ARCH), sparc) diff --git a/debian/changelog b/debian/changelog index b67350d..ee088f5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +mesa (7.0.1-3) unstable; urgency=low + + * Disable building i915tex. +It was previously only built on x86 and amd64. It was never +production-ready and relies on a kernel interface that never went +upstream. + + -- David Nusinow <[EMAIL PROTECTED]> Thu, 04 Oct 2007 22:47:50 -0400 + mesa (7.0.1-2) unstable; urgency=low * Update to latest git (from mesa_7_0_branch) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mesa: Changes to 'debian-unstable'
On Fri, 2007-10-05 at 03:10 +, David Nusinow wrote: > > commit 76556f82646d4a0db15a06e1392e24a6457b1642 > Author: David Nusinow <[EMAIL PROTECTED]> > Date: Thu Oct 4 22:49:27 2007 -0400 > > * Disable building i915tex. > It was previously only built on x86 and amd64. Because the hardware only physically works with those. > It was never > production-ready and relies on a kernel interface that never went > upstream. Define 'production ready' - several customers of ours have it in production. It just requires a suitable drm snapshot. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
