Bug#452268: Bug#451791: xserver-xorg-video-intel: Fonts and many other items fail to render legibly
On Sun, Aug 24, 2008 at 8:48 PM, Julien Cristau [EMAIL PROTECTED] wrote: Hi, you all reported font corruption in X using the intel driver with EXA acceleration enabled, on i965 chipsets. Are you using a framebuffer kernel driver? If /proc/fb is non-empty, please send its contents to the bug you reported. If it's empty, please report that also :) It is empty in my case. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#477547: please remove this transitional package
package: xlibs-data version: 1:7.3+10 Usertags: etch-transitional-packages Hi, this binary package seems to be a transitional package used to upgrade from sarge to etch, that can now be safely removed. If that is so, please fix the source package not to produce this binary package anymore. You can track the progress of this and other transitional packages at: http://wiki.debian.org/EtchTransitionalPackages Thanks, Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#477550: please remove this transitional package
package: xlibs-static-dev version: 1:7.3+10 Usertags: etch-transitional-packages Hi, this binary package seems to be a transitional package used to upgrade from sarge to etch, that can now be safely removed. If that is so, please fix the source package not to produce this binary package anymore. You can track the progress of this and other transitional packages at: http://wiki.debian.org/EtchTransitionalPackages Thanks, Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#477550: Bug#477547: please remove this transitional package
On Wed, Apr 23, 2008 at 10:10 PM, Julien Cristau [EMAIL PROTECTED] wrote: On Wed, Apr 23, 2008 at 21:33:16 +0200, Ondrej Certik wrote: package: xlibs-data version: 1:7.3+10 Usertags: etch-transitional-packages On Wed, Apr 23, 2008 at 21:34:04 +0200, Ondrej Certik wrote: package: xlibs-static-dev version: 1:7.3+10 Usertags: etch-transitional-packages Hi, this binary package seems to be a transitional package used to upgrade from sarge to etch, that can now be safely removed. If that is so, please fix the source package not to produce this binary package anymore. Unfortunately there are still packages (build-)depending on those. I filed bugs a while ago, you're welcome to fix them. In the mean time, no, they can't be safely removed from the archive. Thanks for the reply. I made a mistake then, I only did: $ apt-cache rdepends xlibs-data xlibs-data Reverse Depends: xkb-data-legacy xkb-data-legacy xcursor-themes xcursor-themes xbitmaps xbitmaps libx11-6 $ apt-cache rdepends xlibs-static-dev xlibs-static-dev Reverse Depends: x11proto-xf86vidmode-dev x11proto-xf86vidmode-dev x11proto-xf86misc-dev x11proto-xf86misc-dev x11proto-xf86dga-dev x11proto-xf86dga-dev x11proto-xf86bigfont-dev x11proto-xf86bigfont-dev x11proto-bigreqs-dev x11proto-bigreqs-dev libxfont-dev But all those packages only conflict or replace xlibs-data or xlibs-static-dev. So now I did: $ grep-dctrl -F Build-Depends -s Package xlibs-data /var/lib/apt/lists/ftp.cz.debian.org_debian_dists_unstable_main_source_Sources Package: enlightenment Package: pixmap Package: xtel $ grep-dctrl -F Build-Depends -s Package xlibs-static-dev /var/lib/apt/lists/ftp.cz.debian.org_debian_dists_unstable_main_source_Sources Package: enlightenment Package: gem Package: gl-117 Package: gvidm Package: wine For example for enlightement, you reported this a year ago already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419023 with no response at all. Ok, let's leave this bug open until the above packages are fixed and then remove it from archive. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458858: old xserver-xorg-video-intel 2:2.1.1-4 doesn't help either
But it also hangs, as it used to hang, when this driver was the newest one in sid: black screen, with the mouse pointer on and off periodically. This used to do, then I upgraded to newer intel, with the problems reported in this thread. Same with 2:2.2.0.90-2 which entered unstable today? I don't know, see below. Jan 6 18:06:52 dabl kernel: Unbalanced enable for IRQ 17 Jan 6 18:06:52 dabl kernel: BUG: at kernel/irq/manage.c:158 enable_irq() Jan 6 18:06:52 dabl kernel: [c014b54c] enable_irq+0x6e/0xa2 Jan 6 18:06:52 dabl kernel: [f8ba6da7] probe_hwif+0x5c2/0x693 [ide_core] Jan 6 18:06:52 dabl kernel: [f8ba954f] do_ide_setup_pci_device+0x37e/0x3d4 [ide_core] Jan 6 18:06:52 dabl kernel: [f8ba76e5] probe_hwif_init_with_fixup+0xe/0x88 [ide_core] Jan 6 18:06:52 dabl kernel: [c0190007] dquot_alloc_space+0xf4/0x13c Jan 6 18:06:52 dabl kernel: [f8ba967a] ide_setup_pci_device+0x43/0x75 [ide_core] Jan 6 18:06:52 dabl kernel: [f8838010] jmicron_init_one+0xf/0x12 [jmicron] Jan 6 18:06:52 dabl kernel: [c01d452f] pci_device_probe+0x36/0x57 Jan 6 18:06:52 dabl kernel: [c0227b06] really_probe+0xbd/0x146 Jan 6 18:06:52 dabl kernel: [c0227bd3] driver_probe_device+0x44/0xa5 Jan 6 18:06:52 dabl kernel: [c0227cb7] __driver_attach+0x0/0x79 Jan 6 18:06:52 dabl kernel: [c0227cfd] __driver_attach+0x46/0x79 Jan 6 18:06:52 dabl kernel: [c02271ae] bus_for_each_dev+0x37/0x59 Jan 6 18:06:52 dabl kernel: [c022798e] driver_attach+0x16/0x18 Jan 6 18:06:52 dabl kernel: [c0227cb7] __driver_attach+0x0/0x79 Jan 6 18:06:52 dabl kernel: [c0227460] bus_add_driver+0x5e/0x15f Jan 6 18:06:52 dabl kernel: [c01d468f] __pci_register_driver +0x6b/0x97 Jan 6 18:06:52 dabl kernel: [c013ed92] sys_init_module+0x1698/0x17cf Jan 6 18:06:52 dabl kernel: [f8843000] uhci_hcd_init+0x0/0xa8 [uhci_hcd] Jan 6 18:06:52 dabl kernel: [c015b75c] do_mmap_pgoff+0x564/0x6c4 Jan 6 18:06:52 dabl kernel: [f8ba50cf] ide_config_drive_speed+0x0/0x31e [ide_core] Jan 6 18:06:52 dabl kernel: [c0103d8c] syscall_call+0x7/0xb Jan 6 18:06:52 dabl kernel: === Jan 6 18:06:52 dabl kernel: ide0 at 0xbc00-0xbc07,0xb882 on irq 17 Jan 6 18:06:52 dabl kernel: Probing IDE interface ide1... This does not look good to me... IRQ problems can be bad... Let's hope it is only related to the jmicron driver. Can you try without it? Unfortunately, this is a production computer (I am not even sitting at it) that I need to work very reliably, so I just installed the vesa driver and we didn't experience a single hang since then. I don't want to mess up with it, as this is just a pain for people working with it, when it freezes. We solved the problem by not using the intel driver and as to me, I am ok with this solution. I know it's not very helpful to find the real bug. But I am always testing the latest intel driver on my other computer, where I am not afraid of freezing, as I can easily fix it, and I am experiencing those font problems as I always report. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451893: unreadable fonts and other rendering errors on intel
On Jan 8, 2008 8:22 AM, Brice Goglin [EMAIL PROTECTED] wrote: Hi, There's a new snapshop of the intel driver in experimental (2:2.2.0+git20080107-1) as well as a new xserver-xorg-core in unstable, could you guys test them and tell me whether they fix your rendering errors? The i855 boards should be fixed, but we still don't know much about other boards. Are we talking about the screwed up fonts (I have black boxes instead of fonts)? I have G965, and the driver from experimental doesn't fix the problem for me. Here is a fix, that I use: Section Device Identifier Generic Video Card #Driver vesa Driver intel Option AccelMethod XAA EndSection Important is the AccelMethod option. This works both with the sid and the experimental driver. If I comment out the AccelMethod option, it works neither in sid nor in experimental. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451893: unreadable fonts and other rendering errors on intel
Ok, thanks. And does adding Option FramebufferCompression off to the Device section help? (without AccelMethod XAA). I just tried that with the experimental driver and it doesn't help, i.e. by adding this option and disabling AccelMethod XAA all fonts get unreadable again. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458858: old xserver-xorg-video-intel 2:2.1.1-4 doesn't help either
So I installed the older driver: $ dpkg -l xserver-xorg-video-intel Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- hi xserver-xorg-v 2:2.1.1-4 X.Org X server -- Intel i8xx, i9xx display d But it also hangs, as it used to hang, when this driver was the newest one in sid: black screen, with the mouse pointer on and off periodically. This used to do, then I upgraded to newer intel, with the problems reported in this thread. Note: I am not sitting at this computer physically - I am only administering it over ssh and forwarding all complains here. :) I switched to vesa now. Also, most of the day, there were someone else running windows, without problems. So I don't think it's a hardware problem. Unless windows messup something, but I don't think so. It can also be a problem in the kernel 2.6.21. I noticed today (the previous weeks were fine): Jan 6 18:06:52 dabl kernel: Unbalanced enable for IRQ 17 Jan 6 18:06:52 dabl kernel: BUG: at kernel/irq/manage.c:158 enable_irq() Jan 6 18:06:52 dabl kernel: [c014b54c] enable_irq+0x6e/0xa2 Jan 6 18:06:52 dabl kernel: [f8ba6da7] probe_hwif+0x5c2/0x693 [ide_core] Jan 6 18:06:52 dabl kernel: [f8ba954f] do_ide_setup_pci_device+0x37e/0x3d4 [ide_core] Jan 6 18:06:52 dabl kernel: [f8ba76e5] probe_hwif_init_with_fixup+0xe/0x88 [ide_core] Jan 6 18:06:52 dabl kernel: [c0190007] dquot_alloc_space+0xf4/0x13c Jan 6 18:06:52 dabl kernel: [f8ba967a] ide_setup_pci_device+0x43/0x75 [ide_core] Jan 6 18:06:52 dabl kernel: [f8838010] jmicron_init_one+0xf/0x12 [jmicron] Jan 6 18:06:52 dabl kernel: [c01d452f] pci_device_probe+0x36/0x57 Jan 6 18:06:52 dabl kernel: [c0227b06] really_probe+0xbd/0x146 Jan 6 18:06:52 dabl kernel: [c0227bd3] driver_probe_device+0x44/0xa5 Jan 6 18:06:52 dabl kernel: [c0227cb7] __driver_attach+0x0/0x79 Jan 6 18:06:52 dabl kernel: [c0227cfd] __driver_attach+0x46/0x79 Jan 6 18:06:52 dabl kernel: [c02271ae] bus_for_each_dev+0x37/0x59 Jan 6 18:06:52 dabl kernel: [c022798e] driver_attach+0x16/0x18 Jan 6 18:06:52 dabl kernel: [c0227cb7] __driver_attach+0x0/0x79 Jan 6 18:06:52 dabl kernel: [c0227460] bus_add_driver+0x5e/0x15f Jan 6 18:06:52 dabl kernel: [c01d468f] __pci_register_driver +0x6b/0x97 Jan 6 18:06:52 dabl kernel: [c013ed92] sys_init_module+0x1698/0x17cf Jan 6 18:06:52 dabl kernel: [f8843000] uhci_hcd_init+0x0/0xa8 [uhci_hcd] Jan 6 18:06:52 dabl kernel: [c015b75c] do_mmap_pgoff+0x564/0x6c4 Jan 6 18:06:52 dabl kernel: [f8ba50cf] ide_config_drive_speed+0x0/0x31e [ide_core] Jan 6 18:06:52 dabl kernel: [c0103d8c] syscall_call+0x7/0xb Jan 6 18:06:52 dabl kernel: === Jan 6 18:06:52 dabl kernel: ide0 at 0xbc00-0xbc07,0xb882 on irq 17 Jan 6 18:06:52 dabl kernel: Probing IDE interface ide1... That could be related to the old problem with the jmicron driver, that was famous for not working with 2.6.18 kernels on intel core duo. So I'll try to upgrade to 2.6.23. This computer is giving me a headache... I welcome any tips. :) Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458858: few more hangs
It hanged yesterday twice, today once. This time the $ ls -l /var/log/Xorg.0.log -rw-r--r-- 1 root root 40724 2008-01-04 09:14 /var/log/Xorg.0.log is filed with binary zeros I think the severity of this bug should be raised, what do you think? Maybe the problem is not in the xserver-xorg package, but clearly the bug renders the computer unusable, and clearly, there is a bug somewhere. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458858: few more hangs
On Jan 4, 2008 12:56 PM, Brice Goglin [EMAIL PROTECTED] wrote: reassign 458858 xserver-xorg-video-intel retitle 458858 xserver-xorg-video-intel 2.2.0: PRB0_HEAD and PRB0_TAIL indicate ring buffer not flushed found 458858 2:2.2.0-1 severity 458858 important thank you Ondrej Certik wrote: I think the severity of this bug should be raised, what do you think? Maybe the problem is not in the xserver-xorg package, but clearly the bug renders the computer unusable, and clearly, there is a bug somewhere. Hi Brice, thanks for the reply. I am reassigning to xserver-xorg-video-intel and making the severity important. Some things you should try: * disabling EXA (Option AccelMethod XAA in the the Device section) I put Option AccelMethod XAA in there 3 hours ago and now it hung twice in a row. * downgrade to xserver-xorg-video-intel 2:2.1.1-4 (use snapshot.debian.net to get it) I am doing this now. Also, note that the following warnings may be caused by the crash of the *previous* session laeving the hardware in a bad state and thus breaking the new session. Trying after a hard reboot might make these warnings go away as explained for other error in hardware state in #452739. (WW) intel(0): PRB0_CTL (0x0001f801) indicates ring buffer enabled (WW) intel(0): PRB0_HEAD (0x98407814) and PRB0_TAIL (0xa738) indicate ring buffer not flushed (WW) intel(0): Existing errors found in hardware state. So, it could be interesting to reboot hard, look at the log of the very first crash and see whether these warnings are there or not. I read that bug report but I am not sure I understand. When X server hangs (for whatever reason), the log can always be accessed in the Xorg.0.log.old and it can also possibly leave the hardware in a bad state, so that when I restart, the X server hangs because of this bad state, right? So you suggestion is to always to hard reboot (shutdown, wait, powerup), right? And then look into Xorg.0.log.old Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458858: few more hangs
On Jan 4, 2008 7:50 PM, Brice Goglin [EMAIL PROTECTED] wrote: Ondrej Certik wrote: When X server hangs (for whatever reason), the log can always be accessed in the Xorg.0.log.old and it can also possibly leave the hardware in a bad state, so that when I restart, the X server hangs because of this bad state, right? Yes for instance some registers in the graphic board could be left in a inconsistent state after the crash, and launching a new session will try to understand these registers and fail. That said, I tend to think that the driver should be able to cleanup this mess instead of suffering from it. So you suggestion is to always to hard reboot (shutdown, wait, powerup), right? And then look into Xorg.0.log.old Well, you can look at the log before rebooting. But, you should avoid trying to debug using a log from a session that you launched after the crash of another session without a hard reboot. If you do: 1) hard reboot 2) start X, crash 3) start X, crash 4) start X, crash 5) hard reboot 6) start X, crash 7) hard reboot 8) start X, crash 9) start X, crash ... The log from (3), (4) and (9) may contains errors caused by the crash of the immediately-previous run, so you should not debug using this log. But the log from (2), (6) and (8) should be fine. Ah, that - well, we restart it every time. The Xserver doesn't let us to be killed or something, when it hangs. So that also answers your other question - those logs weren't influenced by bad registers in the hardware. I just installed the driver from September - so we'll see. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458858: few more hangs
On Jan 4, 2008 9:21 PM, Brice Goglin [EMAIL PROTECTED] wrote: Ondrej Certik wrote: Ah, that - well, we restart it every time. The Xserver doesn't let us to be killed or something, when it hangs. So that also answers your other question - those logs weren't influenced by bad registers in the hardware. Ok, good to know. Do you just hit a reset button or do you actually power off + power on ? The latter will cleanup registers for sure, I don't know about the former. Both. From now on, we'll try to power off + power on to be sure. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452268: all fonts are unreadable
On Nov 21, 2007 4:19 PM, Julien Cristau [EMAIL PROTECTED] wrote: reassign 452268 xserver-xorg-video-intel 2:2.2.0-1 forcemerge 439210 452268 kthxbye On Wed, Nov 21, 2007 at 15:19:45 +0100, Ondrej Certik wrote: I use unstable and in some recent upgrade (I think yesterday, or the day before that), all fonts became unreadable. When I start xterm in .xsession, the font is readable, but whenever I start gnome-session, or kde, or xfce, or kate, or openoffice or gnome-terminal from the xterm, it's completely unusable, because I cannot read anything - there are black rectangles instead of the letters in all fonts. So I did $ sudo apt-get remove --purge xserver-xorg-core changed sources.list from unstable to testing $ sudo apt-get update $ sudo apt-get install xorg and everything started to work again. So the bug is clearly in xorg somewhere. Any ideas? Yes, see #439210. Adding Option AccelMethod XAA to the device section in xorg.conf as a workaround should work. Confirming, that adding the Option AccelMethod XAA indeed fixes the problems for the current drivers in unstable. Thanks for the tip. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452268: all fonts are unreadable
Package: xserver-xorg Version: 1:7.2-5 Severity: serious --- Please enter the report below this line. --- I use unstable and in some recent upgrade (I think yesterday, or the day before that), all fonts became unreadable. When I start xterm in .xsession, the font is readable, but whenever I start gnome-session, or kde, or xfce, or kate, or openoffice or gnome-terminal from the xterm, it's completely unusable, because I cannot read anything - there are black rectangles instead of the letters in all fonts. So I did $ sudo apt-get remove --purge xserver-xorg-core changed sources.list from unstable to testing $ sudo apt-get update $ sudo apt-get install xorg and everything started to work again. So the bug is clearly in xorg somewhere. Any ideas? Please ask for more information, I don't know what could be relevant as I don't understand fonts much. Thanks, Ondrej This is my original 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 Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadtype1 Loadvbe 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 ImPS/2 Option Emulate3Buttons true EndSection Section Device Identifier Generic Video Card #Driver vesa Driver i810 EndSection Section Monitor Identifier BenQ FP93G Option DPMS EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor BenQ FP93G DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 640x350 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 640x350 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 640x350 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 640x350 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 640x350 EndSubSection SubSection Display Depth 24 Modes 1280x1024 1152x864 1024x768 832x624 800x600 720x400 640x480 640x350 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse EndSection Section DRI
Bug#447345: compiz doesn't seem to start
On 10/21/07, Brice Goglin [EMAIL PROTECTED] wrote: Ondrej Certik wrote: Package: compiz Version: 0.5.2-2 Severity: normal --- Please enter the report below this line. --- I have Intel 945GM, running xserver-xorg-video-intel. I followed: http://wiki.debian.org/Compiz and some other howtos, when I do: $ LIBGL_ALWAYS_INDIRECT=TRUE compiz --replace GLX_EXT_texture_from_pixmap is available with direct rendering. It stays like that, so it should be running. The windows have no borders, the ctrl-alt arrows doesn't work. Does http://bgoglin.livejournal.com/11253.html help? Wow, that works like a charm! Many thanks. This is enough to get compiz working on my laptop: $ gconftool --set /apps/compiz/general/allscreens/options/active_plugins \ --type list --list-type string \ '[gconf,png,svg,decoration,wobbly,fade,minimize,cube,rotate,zoom,scale,move,place,switcher,screenshot,resize]' $ compiz --replace GLX_EXT_texture_from_pixmap is not available with direct rendering. GLX_EXT_texture_from_pixmap is available with indirect rendering. Could this info please be added to: /usr/share/doc/compiz/README.Debian ? Thanks, Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447345: compiz doesn't seem to start
Package: compiz Version: 0.5.2-2 Severity: normal --- Please enter the report below this line. --- I have Intel 945GM, running xserver-xorg-video-intel. I followed: http://wiki.debian.org/Compiz and some other howtos, when I do: $ LIBGL_ALWAYS_INDIRECT=TRUE compiz --replace GLX_EXT_texture_from_pixmap is available with direct rendering. It stays like that, so it should be running. The windows have no borders, the ctrl-alt arrows doesn't work. I am using sid and gnome. $ cat /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 Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadvbe 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 ImPS/2 Option Emulate3Buttons true EndSection Section InputDevice Identifier Synaptics Touchpad Driver synaptics Option SendCoreEventstrue Option Device/dev/psaux Option Protocol auto-dev Option HorizScrollDelta 0 EndSection Section Device Identifier Generic Video Card Driver intel #Driver i810 BusID PCI:0:2:0 Option XAANoOffscreenPixmaps true Option AllowGLXWithComposite true Option RenderAccel true EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 28-51 VertRefresh 43-60 EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor Generic Monitor Option XAANoOffscreenPixmaps Option AddARGBGLXVisuals true DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse InputDevice Synaptics Touchpad Option AIGLX on EndSection Section DRI Mode0666 EndSection Section
Bug#434857: xserver crashes on exitting some (but not all) opengl applications
Package: xserver-xorg Version: 1:7.2-5 Severity: grave --- Please enter the report below this line. --- This is how to reproduce it: svn co http://pyglet.googlecode.com/svn/trunk pyglet cd pyglet python from pyglet.window import Window w = Window() w.close() and the xserver crashes. More information at: http://code.google.com/p/pyglet/issues/detail?id=115 (scroll down) You will see, that the server crashes after w.close(), but before the script ends. Important is the end of my /var/log/Xorg.0.log.old (II) Configured Mouse: ps2EnableDataReporting: succeeded Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list! Could not init font path element /usr/share/fonts/X11/Type1, removing from list! Could not init font path element /usr/share/fonts/X11/75dpi, removing from list! Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, removing from list! SetGrabKeysState - disabled SetGrabKeysState - enabled SetGrabKeysState - disabled SetGrabKeysState - enabled Backtrace: 0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8631] 1: /lib/i686/cmov/libc.so.6 [0xb7d8d208] 2: /usr/lib/xorg/modules/extensions//libGLcore.so(XMesaResizeBuffers+0x29) [0xa78ba1a9] 3: /usr/lib/xorg/modules/extensions//libGLcore.so [0xa78b6d80] 4: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c0290a] 5: /usr/bin/X(ReparentWindow+0x1a7) [0x807cfa7] 6: /usr/bin/X(ProcReparentWindow+0xd5) [0x808e775] 7: /usr/bin/X [0x8154aa1] 8: /usr/bin/X(Dispatch+0x19f) [0x808ed3f] 9: /usr/bin/X(main+0x495) [0x8076e85] 10: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d79030] 11: /usr/bin/X(FontFileCompleteXLFD+0x1e5) [0x80761a1] Fatal server error: Caught signal 11. Server aborting (II) intel(0): xf86UnbindGARTMemory: unbind key 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 1 (II) intel(0): xf86UnbindGARTMemory: unbind key 2 (II) intel(0): xf86UnbindGARTMemory: unbind key 3 (II) intel(0): xf86UnbindGARTMemory: unbind key 4 glxgears, gmsh work fine. ppracer crashes the xserver with the exact error above in the log, when exitting. I'll be happy to provide more information or try something. The problem is that I don't remember, when this error started to occur for the first time. I use fresh Debian unstable, the xserver-xorg-video-intel driver, but the same thing happens with the xserver-xorg-video-i810 driver from stable. Ondrej --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-1-686 Debian Release: lenny/sid 500 unstablepc232 500 unstableftp.cz.debian.org 500 unstabledebian.wgdd.de --- Package information. --- Depends(Version) | Installed -+-== xserver-xorg-core (= 2:1.3.0.0.dfsg-3) | 2:1.3.0.0.dfsg-11 xserver-xorg-video-all | OR xserver-xorg-video-1.0 | xserver-xorg-input-all | 1:7.2-5 OR xserver-xorg-input | debconf(= 0.5) | 1.5.14 OR debconf-2.0 | xkb-data | 1.0~cvs.20070721-1 OR xkb-data-legacy | xbase-clients| 1:7.2.ds2-2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434857: more information
We managed to find a workaround for this bug at: http://code.google.com/p/pyglet/issues/detail?id=115 see the comment 10 and the discussion below it. Do you know which package the bug is in? Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432110: i915: x server lockups
Subject: i915: x server lockups Package: libgl1-mesa-dri Version: 6.5.2-6 Severity: normal File: i915 Suddenly, the X server crashes sometimes with this output in /var/log/Xorg.0.log. Let me know if this bug report belongs to some other package. (II) Configured Mouse: ps2EnableDataReporting: succeeded Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x3ef80001 pgetbl_err: 0x0 ipeir: 0 iphdr: 1854680 LP ring tail: 480 head: 0 len: 1f801 start 0 Err ID (eir): 0 Err Status (esr): 1 Err Mask (emr): ffdf instdone: ffe5fafc instdone_1: f instpm: 0 memmode: 0 instps: 11e000 HW Status mask (hwstam): fffedffe IRQ enable (ier): 2 imr: fffe iir: 80 acthd: 0 dma_fadd_p: 7018 ecoskpd: 307 excc: 0 cache_mode: 6800/180 mi_arb_state: 44 IA_VERTICES_COUNT_QW 0/0 IA_PRIMITIVES_COUNT_QW 0/0 VS_INVOCATION_COUNT_QW 0/0 GS_INVOCATION_COUNT_QW 0/0 GS_PRIMITIVES_COUNT_QW 0/0 CL_INVOCATION_COUNT_QW 0/0 CL_PRIMITIVES_COUNT_QW 0/0 PS_INVOCATION_COUNT_QW 0/0 PS_DEPTH_COUNT_QW 0/0 WIZ_CTL 0 TS_CTL 0 TS_DEBUG_DATA 973b3d9e TD_CTL 0 / 0 space: 129912 wanted 131064 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8f26000 at 0xb7ed9000 Fatal server error: lockup (II) AIGLX: Suspending AIGLX clients for VT switch -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libgl1-mesa-dri depends on: ii libc6 2.5-11 GNU C Library: Shared libraries ii libdrm2 2.3.0-4Userspace interface to kernel DRM ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii libgl1-mesa-glx 6.5.2-6A free implementation of the OpenG libgl1-mesa-dri recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420203: xserver-xorg-video-intel: Wrong modes and refresh rates
The same problem here. the xrandr showed my only 800x600 and 640x480, but I was running on 1024x768 before the upgrade from i810 to intel. Removing the lines: HorizSync and VertRefresh in xorg.conf allowed the xrandr to find the 1024x768 resolution and everything is fine now. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
