Bug#446820: marked as done (xorg: X freezes on screensaver or strace)
Your message dated Thu, 18 Oct 2007 07:46:31 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#446820: Re : Re : Bug#446820: Re : Bug#446820: xorg: X freezes on screensaver or strace 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) ---BeginMessage--- Package: xorg Version: 1:7.3+2 Severity: grave Justification: causes non-serious data loss Recently I restarted my X server and took into account the last upgrade. Now it appears that when I go away and come back to unlock the screensaver, nothing responds. /usr/bin/X takes 99% of the CPU. I wanted to investigate, but attaching the process with strace -p freezes X in the same way (nothing at all is output by the strace). Then it needs to be killed with a SIGKILL. I reproduced the problem on a vanilla 2.6.23 kernel. Of course, this is annoying because all my session and open work are lost... -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.23-grsec Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Pierre Ynard wrote: Can you try adding Option BusType PCI in the Device section of your xorg.conf? Also, you could try changing AGP speed settings. Either in the BIOS, or in the Device section of xorg.conf with Option AGPMode 1 (1, 2, 4 and 8 are the possible values). Bus type PCI fixes the problem. So do AGP modes 1 and 2, but 4 and 8 crash. (There is no such AGP setting in my BIOS.) Ok so you seem to have an AGP hardware (I think it's the AGP bridge) that does not really like high-speed AGP things. You should probably keep one of the above options in your config for ever since the driver will probably never be able to detect such behavior automatically. I am closing this bug now since it seems hardware-only related. thanks, Brice ---End Message---
Bug#447098: xserver-xorg: keyboard and mouse failed on lenny to sid upgrade
Michael Gilbert wrote: Package: xserver-xorg Version: 1:7.3+2 Severity: normal when i upgraded from lenny to sid (xorg 7.2 to 7.3), my keyboard and mouse stopped working. after some work, i found that the xorg-server-input-kbd and xorg-server-input-mouse packages had not been installed during the upgrade. after installing those packages, the keyboard and mouse worked again. i very well may have done something wrong, because i was doing a lot at once. but it appears that at this point upgrades from xorg 7.2 to 7.3 are broken. How did you upgrade exactly? I've been upgrading multiple times between 7.2 and 7.3 when the latter was in experimental, I don't remember loosing my input packages like this as long as I was reading aptitude warnings/questions. There's an ABI bump for both input and video drivers between 7.2 (xserver-xorg-core 1.3 in testing) and 7.3 (1.4 in unstable). So if you upgrade xserver-xorg-core to unstable, you need to upgrade the drivers too, i.e. input-mouse, input-kbd, and your video driver package too. We have defined some conflicts to prevent you from having a driver from testing while you have xserver-xorg-core from unstable. But also, you must to have at least one input and one video driver from unstable to satisfy xserver-xorg-core dependencies. If (after the upgrade) you had xserver-xorg-core 1.4 installed without input-mouse and input-kbd, it means you had another input driver from unstable installed, for instance evdev or synaptics. Then, is it possible that you upgraded xserver-xorg-core alone (or xserver-xorg, which is tightly coupled to xserver-xorg-core), then apt-get or aptitude complained that it would conflict with your old input drivers (mouse and kbd) and thus proposed to remove them, and you would have said ok? Maybe /var/log/dpkg.log or /var/log/aptitude will help you remember what happened exactly? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446452: xserver-xorg-core: caseyresearch.com in iceape crashes xserver-xorg
On Sat, 13 Oct 2007 09:03:07 +0200 Julien Cristau [EMAIL PROTECTED] wrote: On Sat, Oct 13, 2007 at 14:52:18 +0800, clayton wrote: Package: xserver-xorg-core Version: 2:1.4-3 Severity: normal Navigating to http://www.caseyresearch.com/ in mozilla/iceape 1.0.10~pre070720-0etch3+lenny1 causes xserver to crash within seconds. In my current configuration it works every time. I am using gnash 0.7.2-1lenny1, should flash be an issue in the trigger. Please send us the X log file corresponding to the crash. Sorry for the delay, your request was caught up in a hard drive failure. And now that its all installed again, behavior remains the same: xorg crashes when I navigate to http://www.caseyresearch.com/ with mozilla/iceape. I took the opportunity during installation of trying before and after install of gnash, and sure enough, the crash only occurred with gnash installed. The full X log is attached, with the most relevant bit right here: Backtrace: 0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c644e] 1: [0xe420] 2: /usr/lib/xorg/modules/extensions//libGLcore.so(_mesa_Viewport+0x7d) [0xb6f1016d] 3: /usr/lib/xorg/modules/extensions//libglx.so [0xb7b3c4ad] 4: /usr/lib/xorg/modules/extensions//libglx.so(DoRender+0xdd) [0xb7b3398d] 5: /usr/lib/xorg/modules/extensions//libglx.so [0xb7b33aac] 6: /usr/lib/xorg/modules/extensions//libglx.so [0xb7b38006] 7: /usr/bin/X [0x814d34e] 8: /usr/bin/X(Dispatch+0x2bf) [0x808d0bf] 9: /usr/bin/X(main+0x48b) [0x807461b] 10: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7cd8050] 11: /usr/bin/X(FontFileCompleteXLFD+0x205) [0x8073991] Fatal server error: Caught signal 11. Server aborting Versions installed: iceape-browser/testing uptodate 1.0.10~pre070720-0etch3+lenny1 mozilla-plugin-gnash/testing uptodate 0.7.2-1lenny1 gnash/testing uptodate 0.7.2-1lenny1 libgnash0/testing uptodate 0.7.2-1lenny1 xserver-xorg-input-kbd/testing uptodate 1:1.2.2-3 xserver-xorg-video-savage/testing uptodate 1:2.1.3-3 xserver-xorg-video-s3/testing uptodate 1:0.5.0-4 xserver-xorg-video-v4l/testing uptodate 0.1.1-6 xserver-xorg/testing uptodate 1:7.3+2 xserver-xorg-video-neomagic/testing uptodate 1:1.1.1-8 xserver-xorg-video-imstt/testing uptodate 1:1.1.0-7 xserver-xorg-input-wacom/testing uptodate 0.7.7.11-1 xserver-xorg-video-sisusb/testing uptodate 1:0.8.1-9 xserver-xorg-video-vesa/testing uptodate 1:1.3.0-4 xserver-xorg-video-voodoo/testing uptodate 1:1.1.1-5 xserver-xorg-video-nv/testing uptodate 1:2.1.5-1 xserver-xorg-video-vga/testing uptodate 1:4.1.0-8 xserver-xorg-video-cirrus/testing uptodate 1:1.1.0-8 xserver-xorg-video-s3virge/testing uptodate 1:1.9.1-7 xserver-xorg-video-newport/testing uptodate 1:0.2.1-4 xserver-xorg-input-synaptics/testing uptodate 0.14.7~git20070706-1 xserver-xorg-video-intel/testing uptodate 2:2.1.1-4 xserver-xorg-video-tga/testing uptodate 1:1.1.0-9 xserver-xorg-video-mga/testing uptodate 1:1.4.7.dfsg.1-3 xserver-xorg-video-ark/testing uptodate 1:0.6.0-9 xserver-xorg-video-tseng/testing uptodate 1:1.1.1-4 xserver-xorg-video-ati/testing uptodate 1:6.6.193-3 xserver-xorg-video-rendition/testing uptodate 1:4.1.3.dfsg.1-4 xorg-docs/testing uptodate 1:1.4-2 xorg/testing uptodate 1:7.2-5 xserver-xorg-video-nsc/testing uptodate 1:2.8.3-2 xserver-xorg-video-i128/testing uptodate 1:1.2.1-4 xserver-xorg-input-mouse/testing uptodate 1:1.2.2-6 xserver-xorg-input-evdev/testing uptodate 1:1.2.0~git20070819-3 xserver-xorg-video-via/testing uptodate 1:0.2.2-5 xserver-xorg-video-tdfx/testing uptodate 1:1.3.0-6 xserver-xorg-video-i740/testing uptodate 1:1.1.0-7 xserver-xorg-video-fbdev/testing uptodate 1:0.3.1-4 xserver-xorg-video-apm/testing uptodate 1:1.1.1-10 xserver-xorg-core/testing uptodate 2:1.4-3 xserver-xorg-input-all/testing uptodate 1:7.3+2 xserver-xorg-video-cyrix/testing uptodate 1:1.1.0-8 xserver-xorg-video-sis/testing uptodate 1:0.9.3-5 xserver-xorg-video-glint/testing uptodate 1:1.1.1-8 xserver-xorg-video-vmware/testing uptodate 1:10.15.0-1 xserver-xorg-video-siliconmotion/testing uptodate 1:1.5.1-3 xserver-xorg-video-all/testing uptodate 1:7.3+2 xserver-xorg-video-dummy/testing uptodate 1:0.2.0-7 xserver-xorg-video-trident/testing uptodate 1:1.2.3-6 xserver-xorg-video-chips/testing uptodate 1:1.1.1-9 X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4-3) Current Operating System: Linux desktop1 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 Build Date: 29 September 2007 04:19:41PM 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: Thu Oct 18 14:23:46 2007 (==) Using config file: /etc/X11/xorg.conf (==)
Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/
On Wed, 2007-10-17 at 19:16 -0400, David Nusinow wrote: On Wed, Oct 17, 2007 at 09:46:54AM -0700, Warren Turkal wrote: On 10/17/07, Daniel Stone [EMAIL PROTECTED] wrote: Because it's not clearly in the domain of Xorg. x11-input makes sense, but then again, it's largely a system decision. OTOH, XKB can be used in the console, not just in X (hence why it's namespaced input.xkb and not input.x11.xkb or so), so that's why. Okay...so it's the domain of xkb? Even in that case, it seems there is a more appropriate place for it than hal. Also, as Michel mentions, everything else is already in hal-info, so eh. The latest release includes it, AIUI. Well, I really don't care where it comes from, as long as it's included. I think including it in our package until HAL gets it is probably the right move. More package churn on the server is probably going to be a fact of life for a while anyway. The reason I haven't really put much work in to input hotplug is because I've been focused on getting output autodetection in better shape. Once that's done, I'll get to this if no one else beats me to it. I think it would be better to listen to upstream and reassign this to hal-info... -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#447101: marked as done (xorg doesn't place binaries ins /usr/X11/bin)
Your message dated Thu, 18 Oct 2007 10:17:54 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#447101: xorg doesn't place binaries ins /usr/X11/bin 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) ---BeginMessage--- Package: xorg Version: 1:7.3+2 Severity: important Justification: fails to build from source /usr/X11R6/bin is a simple link to /usr/bin. This makes compiling a different version of X11 difficult and requires manually moving the X11 unique files from to /usr/bin to another directory. The /usr/X11/bin should always be kept and X11 unique files installed in it. This way, new versions may be tested an installed without the user having to compensate for this deficit. Dale -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-k7 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Versions of packages xorg depends on: ii eterm [x-terminal-emu 0.9.4.0debian1-2 Enlightened Terminal Emulator ii gnome-terminal [x-ter 2.18.2-1 The GNOME 2 terminal emulator appl ii konsole [x-terminal-e 4:3.5.7-4 X terminal emulator for KDE ii libgl1-mesa-glx [libg 7.0.1-2A free implementation of the OpenG ii libglu1-mesa 7.0.1-2The OpenGL utility library (GLU) ii mrxvt [x-terminal-emu 0.5.2+svn235-1 lightweight multi-tabbed X termina ii type-handling [not+sp 0.2.21 dpkg architecture generation scrip ii xbase-clients 1:7.3+2miscellaneous X clients - metapack ii xfonts-100dpi 1:1.0.0-4 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-4 75 dpi fonts for X ii xfonts-base 1:1.0.0-5 standard fonts for X ii xfonts-scalable 1:1.0.0-6 scalable fonts for X ii xkb-data 1.0~cvs.20070916-1 X Keyboard Extension (XKB) configu ii xserver-xorg 1:7.3+2the X.Org X server ii xterm [x-terminal-emu 229-1 X terminal emulator ii xutils1:7.3+2X Window System utility programs m Versions of packages xorg recommends: ii xorg-docs 1:1.4-2Miscellaneous documentation for th -- no debconf information ---End Message--- ---BeginMessage--- On Wed, Oct 17, 2007 at 22:38:45 -0700, dale wrote: Package: xorg Version: 1:7.3+2 Severity: important Justification: fails to build from source /usr/X11R6/bin is a simple link to /usr/bin. This makes compiling a different version of X11 difficult and requires manually moving the X11 unique files from to /usr/bin to another directory. The /usr/X11/bin should always be kept and X11 unique files installed in it. This way, new versions may be tested an installed without the user having to compensate for this deficit. No. The local admin can install stuff in /usr/local or /opt, /usr/X11R6/bin and /usr/bin/X11 are deprecated. Cheers, Julien ---End Message---
Bug#446935: xserver-xorg: Seems to lock up occasionally for no apparent reason
On Tue, Oct 16, 2007 at 08:36:25PM +0200, Brice Goglin wrote: Wim De Smet wrote: Package: xserver-xorg Version: 1:7.3+2 Severity: normal Hi, I've been having some problems with xorg locking up lately. It seems to happen most when I open a pdf in evince. Then the following happens. - evince starts up, buttons, window bar etc. show up correctly - pdf doesn't get rendered - mouse is still being rendered correctly, I can still move it etc but I can not click anything (no actions), I can not switch virtual desktop. Alt-tab etc. does not work. ctrl-alt-f1 does work, as well as ctrl-alt-backspace. I'm using xfce4 and the nvidia propietary drivers. I have no idea what's going on here. The only other thing I noticed is when I switch to console with ctrl-alt-f1 and back to the xserver stuff like this shows up in the logs: (II) Open ACPI successful (/var/run/acpid.socket) (II) NVIDIA(0): Setting mode 1280x1024 (II) Configured Mouse: ps2EnableDataReporting: succeeded and (from syslog): acpid: client connected from 12188[0:0] 1 client rule loaded But this looks like normal application behaviour (?). If you have any ideas for debugging this when it occurs again, please let me know. Can you reproduce without the nvidia binary driver? Hi, It took a while but I finally managed to reproduce it. Wasn't opening any pdf files this time so it doesn't seem to be related to that. Had just finished playing a video file, I closed the window, went to find deluge (bittorrent client) and noticed it had no window. When I clicked the taskbar icon to bring it into focus everything started freezing again. All this with the nv free driver. Sorry I forgot to save the log file. greets, Wim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: bug 440174 is forwarded to http://bugs.freedesktop.org/show_bug.cgi?id=12844
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.9 forwarded 440174 http://bugs.freedesktop.org/show_bug.cgi?id=12844 Bug#440174: xserver-xorg-video-ati: distorted colors on external VGA on Xpress 200M (RS400, 5a42) Noted your statement that Bug has been forwarded to http://bugs.freedesktop.org/show_bug.cgi?id=12844. 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#444457: Reproducible crash with xserver-xorg-core 2:1.4-2 and OOo-Impress
We believe that the bug you reported is fixed in the latest version of pixman, which is due to be installed in the Debian FTP archive: ... libpixman-1-0_0.9.5-3_i386.deb I use amd64, and I have libpixman-1-0 0.9.5-3 installed. I still can't use the X server (it crashes within seconds of starting). Any suggestions? Marc X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4-3) Current Operating System: Linux marc 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 Build Date: 29 September 2007 08:59:46PM 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: Thu Oct 18 09:22:53 2007 (==) Using config file: /etc/X11/xorg.conf (II) Module ddc already built-in (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (II) Module ddc already built-in (II) Module i2c already built-in (II) Module ddc already built-in (II) Module i2c already built-in expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc Backtrace: 0: X(xf86SigHandler+0x6a) [0x482daa] 1: /lib/libc.so.6 [0x2b9146650710] 2: /usr/lib/libpixman-1.so.0(pixman_blt_mmx+0x130) [0x2b9145a399a0] 3: /usr/lib/xorg/modules//libfb.so(fbCopyNtoN+0x26e) [0x2b91490c48ce] 4: /usr/lib/xorg/modules//libfb.so(fbCopyRegion+0x85) [0x2b91490c3765] 5: /usr/lib/xorg/modules//libfb.so(fbDoCopy+0x443) [0x2b91490c3d63] 6: /usr/lib/xorg/modules//libfb.so(fbCopyArea+0x4c) [0x2b91490c3ecc] 7: /usr/lib/xorg/modules//libxaa.so [0x2b91492e50ef] 8: /usr/lib/xorg/modules//libxaa.so [0x2b9149329c64] 9: X [0x524832] 10: X [0x4d6a2c] 11: X [0x4e63df] 12: X(miPointerUpdateSprite+0xdd) [0x4e03dd] 13: X(ProcessInputEvents+0x2c) [0x48353c] 14: X(Dispatch+0x7d) [0x44dfad] 15: X(main+0x47c) [0x436a1c] 16: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b914663cb44] 17: X(FontFileCompleteXLFD+0x259) [0x435d59] Fatal server error: Caught signal 11. Server aborting
Bug#444457: Reproducible crash with xserver-xorg-core 2:1.4-2 and OOo-Impress
On Thu, Oct 18, 2007 at 09:26:41 -0500, Marc F. Clemente wrote: We believe that the bug you reported is fixed in the latest version of pixman, which is due to be installed in the Debian FTP archive: ... libpixman-1-0_0.9.5-3_i386.deb I use amd64, and I have libpixman-1-0 0.9.5-3 installed. I still can't use the X server (it crashes within seconds of starting). Any suggestions? Hi, thanks for the feedback. Can you build pixman from http://www.freedesktop.org/~sandmann/pixman-0.9.6-testing.tar.gz and tell us whether it fixes the problem? It contains a different fix that was applied upstream. Thanks, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
pleace delete my email
pleace delete my email from your list -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#444457: Reproducible crash with xserver-xorg-core 2:1.4-2and OOo-Impress
On Thu, Oct 18, 2007 at 14:38:31 -0500, Marc F. Clemente wrote: I tried 0.9.6 but it makes no difference. I am not sure that I am having the same problem as everyone else. With a bit more testing, I found out that the problem only happens with I try to use dual-head configuration. If I use single monitor, it works fine. Maybe the problem is with xserver-xorg-video-ati? I upgraded it from 6.6.3-2 to 6.6.193-3 on 9/19/2007, but this is the first time I restarted the X server. I just tried xserver-xorg-video-ati from experimental (6.7.195-2) but it does not work on my system; it gives an error Requested Entity already in use!. So I downgraded to 6.6.3-2, and it started working again. Any thoughts? I'd need to see your X log and config. The config for dual head setup changes completely with the randr1.2-aware driver (ati 6.7.19x), see http://www.intellinuxgraphics.org/dualhead.html for some help. Cheers, Julien signature.asc Description: Digital signature
xserver-xorg-video-ivtvdev: Changes to 'upstream/tags/1.0.0'
New branch 'upstream/tags/1.0.0' available with the following commits: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-ivtvdev: Changes to 'upstream/trunk'
New branch 'upstream/trunk' available with the following commits: commit bfd21e06ccdfe3e9477407bd8cd93a8bbd9bc463 Author: hverkuil [EMAIL PROTECTED] Date: Sun Oct 14 16:35:04 2007 + Changelog - ChangeLog Add ChangeLog to the dist target. git-svn-id: http://ivtvdriver.org/svn/xdriver/[EMAIL PROTECTED] f93e8361-94ff-0310-af1b-c9b61a63ab7d commit 7ebe05c04228bc923d4ab2d0343932fa87048ea6 Author: hverkuil [EMAIL PROTECTED] Date: Sun Oct 14 16:25:34 2007 + Also update configure.ac git-svn-id: http://ivtvdriver.org/svn/xdriver/[EMAIL PROTECTED] f93e8361-94ff-0310-af1b-c9b61a63ab7d commit d7970f8f3d600b8371bd5db6e57f65eae7bb71ae Author: hverkuil [EMAIL PROTECTED] Date: Sun Oct 14 16:23:31 2007 + Continue with 1.0.1. git-svn-id: http://ivtvdriver.org/svn/xdriver/[EMAIL PROTECTED] f93e8361-94ff-0310-af1b-c9b61a63ab7d -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-ivtvdev: Changes to 'upstream/trunk'
README |6 ++ 1 file changed, 6 insertions(+) New commits: commit 804d2bdd30eef9e1eaf785996928cd894a558bcc Author: hverkuil [EMAIL PROTECTED] Date: Sun Oct 14 17:47:01 2007 + Update README with note regarding the MythTV interlacing settings. git-svn-id: http://ivtvdriver.org/svn/xf86-video-ivtv/[EMAIL PROTECTED] f93e8361-94ff-0310-af1b-c9b61a63ab7d diff --git a/README b/README index de38ba3..4d52737 100644 --- a/README +++ b/README @@ -31,6 +31,12 @@ replace it with 'ivtv-fb'. The ivtv framebuffer driver can be obtained from www.ivtvdriver.org. It is part of the ivtv package. It will be merged with kernel 2.6.24. +The latest MythTV subversion code has overhauled the video out +handling. By default it will select the 'Bob (2x)' deinterlacer for +Xv output. This is NOT compatible with the Xv overlay support for the +PVR-350. It won't crash, but the resulting image will be extremely poor. +So don't use that. + Xorg 7.x Servers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-ivtvdev: Changes to 'debian-unstable'
configure| 20 ++-- configure.ac |2 +- src/ivtv.c |2 +- 3 files changed, 12 insertions(+), 12 deletions(-) New commits: commit 804d2bdd30eef9e1eaf785996928cd894a558bcc Author: hverkuil [EMAIL PROTECTED] Date: Sun Oct 14 17:47:01 2007 + Update README with note regarding the MythTV interlacing settings. git-svn-id: http://ivtvdriver.org/svn/xf86-video-ivtv/[EMAIL PROTECTED] f93e8361-94ff-0310-af1b-c9b61a63ab7d diff --git a/README b/README index de38ba3..4d52737 100644 --- a/README +++ b/README @@ -31,6 +31,12 @@ replace it with 'ivtv-fb'. The ivtv framebuffer driver can be obtained from www.ivtvdriver.org. It is part of the ivtv package. It will be merged with kernel 2.6.24. +The latest MythTV subversion code has overhauled the video out +handling. By default it will select the 'Bob (2x)' deinterlacer for +Xv output. This is NOT compatible with the Xv overlay support for the +PVR-350. It won't crash, but the resulting image will be extremely poor. +So don't use that. + Xorg 7.x Servers commit bfd21e06ccdfe3e9477407bd8cd93a8bbd9bc463 Author: hverkuil [EMAIL PROTECTED] Date: Sun Oct 14 16:35:04 2007 + Changelog - ChangeLog Add ChangeLog to the dist target. git-svn-id: http://ivtvdriver.org/svn/xdriver/[EMAIL PROTECTED] f93e8361-94ff-0310-af1b-c9b61a63ab7d diff --git a/ChangeLog b/ChangeLog new file mode 100644 index 000..d5da1f9 --- /dev/null +++ b/ChangeLog @@ -0,0 +1,47 @@ +#1.0.0 - Renamed to ivtv_drv and xf86-video-ivtv for consistency with X11R7 + naming convention. + - When the ivtv X driver is loaded, it ensures the osd/framebuffer is switched + on, and both global local alpha are off. + - Remove obsolete text from the README. + - Delete obsolete xc directory. + - Reformatted code to Xorg style + - Fixed Xv support for IVTV versions 1.0.0 + - Removed dead code + - Other minor tweaks clean-ups to make the code more consistent. + - Tweaked configure.ac for a more graceful failure if the base requirements + aren't met. + - Add support for multiple PVR350's + - Add support for multiple 'resolutions', switchable via randr + - Add support for 8/16 bpp modes - XV not supported for 8bpp + - Add support for Virtual resolutions with panning + - Add support for Big-endian CPUs - induces speed penalty since cpu has to byte swap all data + - Takes advantage of improved dma if ivtv 0.10.0 + - Most ErrorF calls replaced with xf86DrvMsg + - New resolution/colour support only works if ivtv-fb is loaded WITHOUT 'osd_compat=1' + - compiles with Xorg 7.x as well as older X versions + - Add software scaling for images larger than 720x576 +#0.10.6 - Improved performance by only fixing up correct sized region + - should build against xorg corrrectly +#0.10.5 - Add autopaint colorkey support (XV_AUTOPAINTCOLORKEY) +#0.10.4 - Add colorkey support (XV_COLORKEY) +#0.10.2 - Fix device identification for /dev/video/1 type fb devices + - Allow ivtv/350 to scale up xv playback +#0.10.1 - Fix NTSC playback +#0.10 - Fix playback of non full height videos + - center video in screen + - revert PREP_FRAME code to same as 0.8 for now. +#0.9- first attempt at Xv + - Remove some ioctl calls we know will fail and aren't important. +#0.8 - fix error using fbdev option to specify device to use +#0.7 - frame buffer device now specified with fbdev again + - Configuration code is more like most pci cards instead of + framebuffer driver so less things go wrong + and error messages are more sensible + - Uses installed ivtv header file + - Probe does ivtvfb ioctl to ensure frame buffer is really ivtv. +#0.6 - Fix dma too large an area on full screen updates +#0.5 - Remove name conflicts +#0.4 - Sends data in multiples of 64K to keep ivtv happ(ish) + - Grabs the sum of the dirty regions and just updates that region. + - pointer passed to ivtv is not aligned on page boundaries so relies on + ivtv-0.1.10-pre2-ck108d or newer version of myth to work properly. diff --git a/Changelog b/Changelog deleted file mode 100644 index d5da1f9..000 --- a/Changelog +++ /dev/null @@ -1,47 +0,0 @@ -#1.0.0 - Renamed to ivtv_drv and xf86-video-ivtv for consistency with X11R7 - naming convention. - - When the ivtv X driver is loaded, it ensures the osd/framebuffer is switched - on, and both global local alpha are off. - - Remove obsolete text from the README. - - Delete obsolete xc directory. - - Reformatted code to Xorg style - - Fixed Xv support for IVTV versions 1.0.0 - - Removed dead code - - Other minor tweaks clean-ups to make the code more consistent. - - Tweaked configure.ac for a more graceful failure if the base
Bug#446441: xserver-xorg: The problem is in regexp
On Fri, Oct 19, 2007 at 10:54:54AM +0900, Michal Čihař wrote: Hi On Thu, 18 Oct 2007 21:19:02 -0400 David Nusinow [EMAIL PROTECTED] wrote: This part of the debconfage is going away when I get a chance to figure out what to do about sparc. In the future, you won't even bother to write this section to your xorg.conf unless you want to override the default, as it'll just load the right driver by default. The server and drivers in unstable can already do this. I did add a patch for some pci id's to radeonhd to do this too, although I don't think it's complete. You're right, it seems to work without specifying driver in config (I had to rebuild radeonhd from git anyway...). However as long as the debconf code is there, it should list all drivers. (I have no idea when you except to drop this debconf code, but it is far away, I think it should be fixed). Well, basically I'm telling you that the right fix at this point is to drop it. Again, sparc is really the only thing holding it back. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446441: xserver-xorg: The problem is in regexp
Hi On Thu, 18 Oct 2007 21:19:02 -0400 David Nusinow [EMAIL PROTECTED] wrote: This part of the debconfage is going away when I get a chance to figure out what to do about sparc. In the future, you won't even bother to write this section to your xorg.conf unless you want to override the default, as it'll just load the right driver by default. The server and drivers in unstable can already do this. I did add a patch for some pci id's to radeonhd to do this too, although I don't think it's complete. You're right, it seems to work without specifying driver in config (I had to rebuild radeonhd from git anyway...). However as long as the debconf code is there, it should list all drivers. (I have no idea when you except to drop this debconf code, but it is far away, I think it should be fixed). -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Bug#446442: I also hit this problem
I just ended up with the same issue, notes about this are here: https://bugs.freedesktop.org/show_bug.cgi?id=12843 -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/
reassign 446851 hal retitle 446851 Please package new upstream version which includes x11-input.fdi thanks On Thu, Oct 18, 2007 at 09:45:11AM +0200, Michel Dänzer wrote: On Wed, 2007-10-17 at 19:16 -0400, David Nusinow wrote: On Wed, Oct 17, 2007 at 09:46:54AM -0700, Warren Turkal wrote: On 10/17/07, Daniel Stone [EMAIL PROTECTED] wrote: Because it's not clearly in the domain of Xorg. x11-input makes sense, but then again, it's largely a system decision. OTOH, XKB can be used in the console, not just in X (hence why it's namespaced input.xkb and not input.x11.xkb or so), so that's why. Okay...so it's the domain of xkb? Even in that case, it seems there is a more appropriate place for it than hal. Also, as Michel mentions, everything else is already in hal-info, so eh. The latest release includes it, AIUI. Well, I really don't care where it comes from, as long as it's included. I think including it in our package until HAL gets it is probably the right move. More package churn on the server is probably going to be a fact of life for a while anyway. The reason I haven't really put much work in to input hotplug is because I've been focused on getting output autodetection in better shape. Once that's done, I'll get to this if no one else beats me to it. I think it would be better to listen to upstream and reassign this to hal-info... Ok, Daniel's message didn't hit my inbox for some reason, so I just saw the bit about it being in the new hal version. I'm reassigning this to hal since it looks like all the .fdi files that hal itself ships belong to that package, and x11-input.fdi is in that category. Sjoerd can reassign it if I got it wrong. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /etc/hal/fdi/policy/
Processing commands for [EMAIL PROTECTED]: reassign 446851 hal Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /usr/share/hal/fdi/policy/ Bug reassigned from package `xserver-xorg-core' to `hal'. retitle 446851 Please package new upstream version which includes x11-input.fdi Bug#446851: xserver-xorg-core: please copy (and improve) x11-input.fdi to /usr/share/hal/fdi/policy/ Changed Bug title to `Please package new upstream version which includes x11-input.fdi' from `xserver-xorg-core: please copy (and improve) x11-input.fdi to /usr/share/hal/fdi/policy/'. 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#446441: Info received (xserver-xorg: The problem is in regexp)
tags 446441 patch thanks Well I was wrong with underscore, it did also add other drivers which should be removed. Attached patch seems to work correctly for me. -- Michal Čihař | http://cihar.com | http://blog.cihar.com diff -ruNp xorg-7.3+2.orig/debian/xserver-xorg.postinst.in xorg-7.3+2/debian/xserver-xorg.postinst.in --- xorg-7.3+2.orig/debian/xserver-xorg.postinst.in 2007-09-17 05:21:48.0 +0900 +++ xorg-7.3+2/debian/xserver-xorg.postinst.in 2007-10-19 09:59:11.0 +0900 @@ -778,7 +778,7 @@ if [ -n $FIRSTINST ] || [ -n $RECONFI # v4l is not a display driver, and dummy is for advanced users. DRIVER_LIST=$(find $REAL_DRIVER_DIRS -name '*_drv.*' \ | sed 's|^.*/\([^/]*\)_drv\.[^\._]*|\1|g' \ - | egrep -v '(atimisc|dummy|r128|radeon|v4l)' | sort -u | xargs \ + | egrep -v '(atimisc|dummy|r128|radeon|v4l)$' | sort -u | xargs \ | sed 's/ /, /g' 2/dev/null) fi signature.asc Description: PGP signature
Processed: Re: Bug#446441: Info received (xserver-xorg: The problem is in regexp)
Processing commands for [EMAIL PROTECTED]: tags 446441 patch Bug#446441: xserver-xorg debconf won't permit radeonhd There were no tags set. Tags added: patch 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#446441: xserver-xorg: The problem is in regexp
Package: xserver-xorg Version: 1:7.3+2 Followup-For: Bug #446441 The fix for this is simple: Just add underscore to grepping for radeon in acquiring DRIVER_LIST. So doing s/|radeon|/|radeon_|/ in postints fixes this issue. -- Michal Čihař | http://cihar.com | http://blog.cihar.com
Bug#446441: xserver-xorg: The problem is in regexp
On Fri, Oct 19, 2007 at 09:44:03AM +0900, Michal Čihař wrote: Package: xserver-xorg Version: 1:7.3+2 Followup-For: Bug #446441 The fix for this is simple: Just add underscore to grepping for radeon in acquiring DRIVER_LIST. So doing s/|radeon|/|radeon_|/ in postints fixes this issue. This part of the debconfage is going away when I get a chance to figure out what to do about sparc. In the future, you won't even bother to write this section to your xorg.conf unless you want to override the default, as it'll just load the right driver by default. The server and drivers in unstable can already do this. I did add a patch for some pci id's to radeonhd to do this too, although I don't think it's complete. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
