[Ubuntu-x-swat] [Bug 686592] [NEW] Tooltips/menus often not visibile until mouse moved over where they should appear
Public bug reported: It happens quite often that tooltips / menus are not displayed until the cursor is moved over the area where they should appear. Following observations: - This does not appear to be a bug in a specific driver, can reproduce it with xorg-intel, xorg-ati and fglrx - This does not appear to be a bug in either compiz, nor mesa: under gnome, it is most easily reproducable with compiz enabled, but for instance on KDE the problem is easier to reproduce without any compositing manager running at all. - This is a regression compared to xorg-1.8 (or generally ubuntu 10.04). A typical example video is attaced. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xserver-xorg-core 2:1.9.0-0ubuntu7.1 ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Tue Dec 7 15:26:45 2010 DkmsStatus: fglrx, 8.791, 2.6.35-23-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MachineType: LENOVO 2767C99 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=d7213666-2c15-4bce-91bb-5b44893e399b ro quiet splash ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SourcePackage: xorg-server dmi.bios.date: 08/02/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET89WW (3.19 ) dmi.board.name: 2767C99 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET89WW(3.19):bd08/02/2010:svnLENOVO:pn2767C99:pvrThinkPadT400:rvnLENOVO:rn2767C99:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2767C99 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-23-generic ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. https://bugs.launchpad.net/bugs/686592 Title: Tooltips/menus often not visibile until mouse moved over where they should appear ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 686592] Re: Tooltips/menus often not visibile until mouse moved over where they should appear
** Attachment added: Example video https://bugs.launchpad.net/bugs/686592/+attachment/1758528/+files/out.ogv -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. https://bugs.launchpad.net/bugs/686592 Title: Tooltips/menus often not visibile until mouse moved over where they should appear ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
Status updates: - The cause of the issue is not X anymore - The issue has been fixed in the latest nvidia beta driver, see http://www.nvnews.net/vbulletin/showthread.php?p=2255561 - The issue does still affect fglrx with unknown status ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Fix Released ** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Also affects: fglrx Importance: Undecided Status: New ** Changed in: nvidia-drivers-ubuntu Status: New = In Progress ** Changed in: fglrx Status: New = Confirmed ** Changed in: vino (Ubuntu) Status: Confirmed = Fix Released -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
In karmic it should be no problem: - Uninstall any nvidia packages installed from the ubuntu repos - Download the beta driver and make it executable (chmod +x /path/to/NVIDIA-Linux-(x86|x86_64)-256.25.run) - Switch to a virtual terminal (i.e. ctrl+alt+f2), login - Stop X: sudo service gdm stop - Check you've installed the build-essential package: sudo apt-get install build-essential - Install the driver: sudo /path/to/NVIDIA-Linux-(x86|x86_64)-256.25.run - Reboot For lucid users it is more complicated, for example see http://www.ubuntugeek.com/howto-install-nvidia-drivers-manually-on-ubuntu-10-04-lucid-lynx.html (haven't tested myself). On 05/22/2010 06:21 PM, Diver wrote: Is there a way to install this version (256.25) of nvidia drivers on Karmic? -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
Actually since the issue has been reported to the nvidia devs only about a month ago I'd say they have been really quick. Anyhow, for lucid users which don't want to fiddle around too much it may be more convenient to look if the updated driver appears in the proprietary-video-improvements PPA (https://launchpad.net/~albertomilone/+archive/proprietary-video-improvements) some time soon instead of installing manually (though I have no idea if and when it will appear). On 05/22/2010 11:37 PM, KruyKaze wrote: About time but i'm still happy i'll try it when i get home. Did anyone have issues installing on lucid64? On Sat, May 22, 2010 at 10:52 AM, Sandro Manimanisan...@gmail.com wrote: In karmic it should be no problem: - Uninstall any nvidia packages installed from the ubuntu repos - Download the beta driver and make it executable (chmod +x /path/to/NVIDIA-Linux-(x86|x86_64)-256.25.run) - Switch to a virtual terminal (i.e. ctrl+alt+f2), login - Stop X: sudo service gdm stop - Check you've installed the build-essential package: sudo apt-get install build-essential - Install the driver: sudo /path/to/NVIDIA-Linux-(x86|x86_64)-256.25.run - Reboot For lucid users it is more complicated, for example see http://www.ubuntugeek.com/howto-install-nvidia-drivers-manually-on-ubuntu-10-04-lucid-lynx.html (haven't tested myself). On 05/22/2010 06:21 PM, Diver wrote: Is there a way to install this version (256.25) of nvidia drivers on Karmic? -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a direct subscriber of the bug. Status in AMD fglrx video driver: Confirmed Status in NVIDIA Drivers Ubuntu: In Progress Status in GNOME Remote Desktop: Incomplete Status in X.Org X server: Confirmed Status in “vino” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “vino” package in Fedora: Unknown Bug description: Binary package hint: compiz When using the nvidia-restricted or some ATI drivers and compiz desktop effects the vnc server will not refresh the screen. This is being caused by the xserver not getting damaged by the nvidia-restricted drivers (see https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/245for details). Linked bugs confirm this is not an issue on intel chipsets or nv driver. Steps to reproduce: Enable desktop-effects (default) with nvidia-restricted, virtualBox's display or some ATI driver like RV610 Enable remote desktop Connect with VNC Results: You see a screen snapshot of your desktop but if you click a menu item there are no updates to the screen. Notes: If you close and restart the vnc session, you get an updated snapshot but still no refreshes. Workarounds: Use the -noxdamage argument with vncviewer. This is really inefficient and bandwidth hungry since the whole screen refreshes. Kill compiz and use a different wm (metacity). [Tested with nvidia] Run compiz with the --use-root-window option, eg: compiz --replace --use-root-window This bug has been confirmed by many others with linked reports. Might be an issue with xorg since there is a report of ATI drivers with similar issues in https://bugs.launchpad.net/bugs/328559 . To unsubscribe from this bug, go to: https://bugs.launchpad.net/fglrx/+bug/353126/+subscribe -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
For all those affected with nVidia hardware, nvidias Aaron Plattner has just announced that the issue will be investigated, see http://www.nvnews.net/vbulletin/showthread.php?p=2239566 . -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
The problem is fixed as far as all open drivers are concerned. The issue with the binary driver remains and will probably remain as long as no- one with hardware that is affected cares to report the issue to the respective places (i.e. nvnews for nvidia, virtualbox bug tracker for virtualbox, and http://ati.cchtml.com/ for ATI cards). -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
From what I can see the issue has never been brought up at nvnews, which is apparently one of the only ways to report problems with the binary nvidia driver to their developers. I'd suggest someone who is affected might want to try to point out the issue there (any maybe there is some similar forum concerning the fglrx driver). -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
Look: software evolves, and sometimes API breaks and things like that are necessary. While you may be unhappy about the situation, there is indeed nothing the open community can do if the developers behind the closed source drivers do not want to react on the issue. That is, if they really do not want to, maybe the issue has simply not been brought to their attention. So, please, if you care about this issue being fixed as we all do here, why do you not take the step and try to obtain at least some sort of feedback from their developers by posting the problem there - i.e. for the nvidia driver to start with? I'd to it myself but I have no nvidia card atm to provide specific information if they require it, and really, it is not such a big deal to send them a few words. On 04/20/2010 01:08 PM, Dan Burke wrote: This was not brought up at nvnews because it was not originally a Binary Blob issue. Whatever was changed in xorg to fix this apparently requires a driver fix too. At any rate, I tested my ATI box and the results were as one might predict: Radeon driver + Compiz: Works FGLRX driver + Compix: Does not work I guess at this point I'll unsubscribe from this thread as any hope at getting this fixed has now been lost, since it's going to be categorized into that blackhole of binary driver issues. I hope whatever changes xorg made to fix the original bug are somehow directly made known to all driver vendors. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
May I point out that the last person actually stating that it had the problem with intel graphics was back in september 2009, in comment 144? Since then, the issue has only been confirmed on binary drivers (except lunix which still needs to verify), while there are several reports of things working fine with open drivers. So would people willing to complain please actually try out the newest packages with the newest open source drivers and report if they actually still _do_ have the issue? On 04/19/2010 09:25 PM, Dan Burke wrote: Comment #141 confirmed this is a bug with Intel drivers. So this is not limited to binary blobs. And the reason there are so many comments on this bug is because developers have ignored this bug and instead left the community to fend for itself and come up with half baked (if well intentioned) fixes which do not address the underlying regression from 8.10. Please do not mark this bug as fixed until someone confirms it is fixed. Just because an updated version of xorg is in Lucid doesn't mean this bug is fixed. in fact, there are several reports of the contrary. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
First of all do a sudo apt-get autoremove to remove all those packages. A side of that, you appear to have some residuals from the xorg-driver-fglrx package which no longer exists. Try to sudo apt-get purge xorg-driver-fglrx. If that does not work, your package database may be messed up from some previous attempts. You can either manually remove the files / edit the package database at your own risk or simply install a clean beta 2. Anyhow this issue is specific to your installation and not a general issue. On 04/09/2010 08:54 PM, HX_unbanned wrote: NO! It does not / still is bugged! Here is terminal log: lina...@linards-desktop:~$ sudo apt-get install -f [sudo] password for linards: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: pwgen libfreebob0 plasma-dataengines-workspace python-pygoocanvas kdelibs4c2a libprocessui4 docvert libtaskmanager4 libqimageblitz4 libboost-regex1.38.0 libpackagekit-glib2-12 libkscreensaver5 libsolidcontrolifaces4 python-beaker kdebase-runtime-data-common twolame kdelibs-data libgoocanvas-common python-sqlalchemy libxmu-headers libknotificationitem1 openoffice.org-hyphenation-en-us liblualib50 libass3 libservlet2.4-java gnumeric-common libplasma-geolocation-interface4 libexiv2-5 python-nose gnumeric-doc nautilus-sendto-empathy libswt-gtk-3.4-java libsqlite0-dev libphp-pclzip python-gtkspell alsaplayer-alsa libpackagekit-qt-12 sdparm libx264-67 mysql-server-core-5.1 install-package jpegoptim python-celementtree libksgrd4 fuseiso9660 kdebase-runtime-bin-kde4 fckeditor libkworkspace4 libcelt0 libfltk1.1 libavahi-qt3-1 python-sip4 libplasmagenericshell4 libkfontinst4 libxmu-dev openbsd-inetd libjline-java openoffice.org-thesaurus-en-au libwmf-bin openoffice.org-hyphenation libffado1 libntlm0 openoffice.org-thesaurus-en-us libgoffice-0-8 python-packagekit libiso9660-5 libiso9660-7 packagekit libkephal4 kdebase-workspace-data software-properties-kde ksysguardd libplasmaclock4 liblcms1-dev libxml++2.6-2 proftpd-basic libweather-ion4 kdebase-workspace-kgreet-plugins rhino libsolidcontrol4 khelpcenter4 libumlib0 librsvg2-bin mjpegtools akonadi-server update-manager-kde packagekit-backend-apt python-wnck python-elementtree liblua50 libmng-dev libplasma-applet-system-monitor4 libswt-cairo-gtk-3.4-jni libprocesscore4 gstreamer0.10-gnonlin libsensors-dev libgoocanvas3 optipng empathy-common libgnomecups1.0-1 libswt-gtk-3.4-jni libgoffice-0-8-common libswt-mozilla-gtk-3.4-jni Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. lina...@linards-desktop:~$ sudo apt-get install fglrx Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: pwgen libfreebob0 plasma-dataengines-workspace python-pygoocanvas kdelibs4c2a libprocessui4 docvert libtaskmanager4 libqimageblitz4 libboost-regex1.38.0 libpackagekit-glib2-12 libkscreensaver5 libsolidcontrolifaces4 python-beaker kdebase-runtime-data-common twolame kdelibs-data libgoocanvas-common python-sqlalchemy libxmu-headers libknotificationitem1 openoffice.org-hyphenation-en-us liblualib50 libass3 libservlet2.4-java gnumeric-common libplasma-geolocation-interface4 libexiv2-5 python-nose gnumeric-doc nautilus-sendto-empathy libswt-gtk-3.4-java libsqlite0-dev libphp-pclzip python-gtkspell alsaplayer-alsa libpackagekit-qt-12 sdparm libx264-67 mysql-server-core-5.1 install-package jpegoptim python-celementtree libksgrd4 fuseiso9660 kdebase-runtime-bin-kde4 fckeditor libkworkspace4 libcelt0 libfltk1.1 libavahi-qt3-1 python-sip4 libplasmagenericshell4 libkfontinst4 libxmu-dev openbsd-inetd libjline-java openoffice.org-thesaurus-en-au libwmf-bin openoffice.org-hyphenation libffado1 libntlm0 openoffice.org-thesaurus-en-us libgoffice-0-8 python-packagekit libiso9660-5 libiso9660-7 packagekit libkephal4 kdebase-workspace-data software-properties-kde ksysguardd libplasmaclock4 liblcms1-dev libxml++2.6-2 proftpd-basic libweather-ion4 kdebase-workspace-kgreet-plugins rhino libsolidcontrol4 khelpcenter4 libumlib0 librsvg2-bin mjpegtools akonadi-server update-manager-kde packagekit-backend-apt python-wnck python-elementtree liblua50 libmng-dev libplasma-applet-system-monitor4 libswt-cairo-gtk-3.4-jni libprocesscore4 gstreamer0.10-gnonlin libsensors-dev libgoocanvas3 optipng empathy-common libgnomecups1.0-1 libswt-gtk-3.4-jni libgoffice-0-8-common libswt-mozilla-gtk-3.4-jni Use 'apt-get autoremove' to remove them. The following extra packages will be installed: fglrx-amdcccle The following NEW packages will be installed: fglrx fglrx-amdcccle 0
[Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
wild.ideas: That being the case, perhaps someone ought to prove it out by installing the Nvidia drivers from the 8.04 era into a fresh install of 9.10 and demonstrating that binary nvidia + compiz + xdamage enabled = no problem. Or has this been done already? That cannot be done since those drivers do not support the current kernel / xserver. One reason drivers get updated is exactely to provide support for these newer software pieces. Has anyone ever managed to get a statement from a nvidia employee at nvnews concerning this issue? -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
The remote desktop solution in Ubuntu uses the VNC backend which can't read from hardware accelerated display That's hardly true, testing on a few xserver 7.5 machines (running fedora 12 but that should not make any difference) * intel + compiz + xdamage enabled = no problem * open source radeonhd + compiz + xdamage enabled = no problem * binary nvidia + compiz + xdamage enabled = screen does not refresh * binary nvidia + compiz + xdamage disabled = no problem Hence it really looks like only the binary drivers (at least nvidia, haven't tested fglrx) are affected. And when using binary drivers, disabling xdamage in gconf: /desktop/gnome/remote_access/disable_xdamage should suffice (and this imo whould be something that could be done automatically when a user installs a binary driver through the repos). For people experiencing this issue with open source drivers on a clean lucid install / live cd, they might want to give the fedora 12 / 13 live cds a try, just in case it were indeed a problem affecting only ubuntu. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
@mattrenfer The open-source driver has yet to mature especially in the 3D area, currently you won't get full performance. Since AMD decided to ditch support for older graphic-cards in their binary driver, you'll have to wait a while until the open driver gets optimized. -- Does not support current Lucid kernel (2.6.32) or xserver (1.7) https://bugs.launchpad.net/bugs/494699 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 494699] Re: Does not support current Lucid kernel (2.6.32) or xserver (1.7)
The drivers available from the official AMD/ATI website do not yet support the lucid kernel / xserver - use the packages that just got pushed to the lucid repositories (which basically is a unreleased catalyst) - you may have to wait a few hours until all mirrors are up- to-date, or you can take a look over at https://launchpad.net/ubuntu/lucid/+source/fglrx- installer/2:8.721-0ubuntu1 . -- Does not support current Lucid kernel (2.6.32) or xserver (1.7) https://bugs.launchpad.net/bugs/494699 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 406865] Re: [GM45] 3D applications fail to run in WINE
Go ahead and create one, quickly post back the link to the topic here. -- [GM45] 3D applications fail to run in WINE https://bugs.launchpad.net/bugs/406865 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 406865] Re: [GM45] 3D applications fail to run in WINE
Have you change or set some custom xorg parameters with previous attempts? Otherwise it can very well be that the build of the driver you got is indeed broken, which is not that unlikely to happen with daily builds. You can wait a few days for the next few builds to see if they fix the issue, but I'd really suggest that if you want to stick with ubuntu and have wine working to give lucid a try (alpha 2 is scheduled to be released tomorrow), which is likely to be considerably more stable than daily builds even if in alpha stage. Lastly I suggest we moved this discussion to the forum since launchpad isn't really the right place for such discussions. -- [GM45] 3D applications fail to run in WINE https://bugs.launchpad.net/bugs/406865 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 406865] Re: [GM45] 3D applications fail to run in WINE
Well concerning at least 9.04, it was in the middle of the EXA - UXA transition with new stuff coming in like KMS and GEM, therefore things were not really stable back then (and as far as I recall also fedora had plenty of problems at that stage). If you want to stick with ubuntu you'll need to add a PPA repository containing newer packages, especially the xserver video drivers and mesa, or take a look at lucid. For the thread: glxgears is not a benchmark, cfr. https://wiki.ubuntu.com/X/Troubleshooting/IntelPerformance Lastly, concerning this specific issue video size should not make too much of a difference, I'm actually not sure how wine uses this value, if only to report a size to applications asking for it or if it actually really matters internally. -- [GM45] 3D applications fail to run in WINE https://bugs.launchpad.net/bugs/406865 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 406865] Re: [GM45] 3D applications fail to run in WINE
Hi, it is not that fedora has figured out something that ubuntu has not, it is just that it is more a bleeding edge distribution than ubuntu is, which means that you often get upstream fixes faster than in ubuntu, but also that you might have to deal with upstream regressions in a more unplesant way because packages may get pushed to their repos with less testing. If you want bleeding edge with ubuntu, you can use a mainline ppa kernel and the X crack pushers repo and then you should also have the leatest and greatest of features and misfeatures, but keep in mind that those packages aren't tested at all against stability or even usability. But if you want newer packages with less effort and risk, you may also want to give fedora a try. -- [GM45] 3D applications fail to run in WINE https://bugs.launchpad.net/bugs/406865 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 406865] Re: [GM45] 3D applications fail to run in WINE
Concerning the X crash: this should have been fixed a while ago (see bug #401067), if you have this issue with an up-to-date system would you please collect a backtrace (see http://wiki.ubuntu.com/X/Backtracing) and open a new bug? For the rest from what I can see the problem is fixed in newer x and mesa packages (and maybe others?) - i.e. works well in fedora - but they aren't included in this release of ubuntu. -- [GM45] 3D applications fail to run in WINE https://bugs.launchpad.net/bugs/406865 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 406865] Re: [GM45] 3D applications fail to run in WINE
Concerning the X crash, yes - but it won't help much concerning the other issue (unless maybe you try bleeding edge packages from the X crack pushers PPA, but I haven't tried them myself and cannot guarantee they fix the issue - keep in mind that they also might make your system unusable). -- [GM45] 3D applications fail to run in WINE https://bugs.launchpad.net/bugs/406865 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455363] Re: Touchpad freezes when pressing a hotkey or keyboard key
I tested with a live cd of karmic release and still have this issue. As opposed with what I wrote in the description this actually seems to affect any keyboard key / hotkey: when pressing one of them about 2 times out of 3 the touchpad will freeze for about 1 second. This does not happen with an external mouse. ** Summary changed: - Touchpad lag when pressing keyboard shortcuts / hotkeys + Touchpad freezes when pressing a hotkey or keyboard key -- Touchpad freezes when pressing a hotkey or keyboard key https://bugs.launchpad.net/bugs/455363 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455363] Re: Touchpad freezes when pressing a hotkey or keyboard key
Okay, it was the disable keyboard while typing setting which seems to have been enabled by default in karmic. Just a notice: it makes many games totally unplayable which might confuse some users. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New = Invalid -- Touchpad freezes when pressing a hotkey or keyboard key https://bugs.launchpad.net/bugs/455363 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455235] Re: Incorrect monitor detection by Ubuntu in Karmic beta
*** This bug is a duplicate of bug 392544 *** https://bugs.launchpad.net/bugs/392544 Tried on the machine were I was seeing the issue and indeed the 2.6.32 mainline kernel from kernel ppa fixes the problem, as described in bug #392544. Marking as dupe. ** This bug has been marked a duplicate of bug 392544 [i945G] [intel KMS regression] wrong X resolution (fuzzy aspect match) -- Incorrect monitor detection by Ubuntu in Karmic beta https://bugs.launchpad.net/bugs/455235 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455235] Re: Incorrect monitor detection by Ubuntu in Karmic beta
Related with #392544 ? -- Incorrect monitor detection by Ubuntu in Karmic beta https://bugs.launchpad.net/bugs/455235 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455235] Re: Incorrect monitor detection by Ubuntu in Karmic beta
That would only be to disable KMS in which case the issue should not appear. But are you also seeing the issue with an intel graphicscard? -- Incorrect monitor detection by Ubuntu in Karmic beta https://bugs.launchpad.net/bugs/455235 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455235] Re: Incorrect monitor detection by Ubuntu in Karmic beta
Could be a good idea, if without KMS you do not have the issue then we could mark this bug a dup of the other one. As stated in the comments of the other report, also using newer mainline kernels (latest 2.6.32 rc) should fix the issue. (Unfortunately I don't currently have access to the pc I encountered the issue on, therefore cannot try myself...) -- Incorrect monitor detection by Ubuntu in Karmic beta https://bugs.launchpad.net/bugs/455235 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455235] Re: Incorrect monitor detection by Ubuntu in Karmic beta
Same problem here, only detecting up to 800x600 instead of 1024x768. Can sucessfully override as described here: http://ubuntuforums.org/showthread.php?t=945465 -- Incorrect monitor detection by Ubuntu in Karmic beta https://bugs.launchpad.net/bugs/455235 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455363] [NEW] Touchpad lag when pressing keyboard shortcuts / hotkeys
Public bug reported: Binary package hint: xserver-xorg-input-synaptics Using up-to-date karmic as of 19.10.09, hardware is a Lenovo T400. Problem: when pressing certain keyboard shortcuts / hotkeys, the mouse cursor hangs for about one second before resuming normal motion. I attached a video showing the problem when pressing the volume up / down hotkeys (the finger is always in motion on the touchpad), but the same happens for example when pressing ctrl+c in gedit. Not sure if xserver-xorg-input-synaptics is the right package, I first noticed the problem a few days ago, about when the following xserver-xorg-input packages were updated: 2009-10-14 xserver-xorg-input-synaptics 2009-10-15 xserver-xorg-input-wacom 2009-10-15 xserver-xorg-input-evdev Notes: - the problem does not appear when executing the hotkey function manually (i.e. choosing copy in gedit from the context menu). - it does not matter whether the laptop is on battery power or not (i.e. not a harddisk spinup delay problem) ProblemType: Bug Architecture: amd64 Date: Mon Oct 19 12:59:28 2009 DistroRelease: Ubuntu 9.10 MachineType: LENOVO 2767C99 Package: xserver-xorg-input-synaptics 1.1.2-1ubuntu7 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=3f3fd78c-6c8e-48e5-9129-d24d50ada2ee ro quiet splash acpi_osi=Linux ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: xserver-xorg-input-synaptics Uname: Linux 2.6.31-14-generic x86_64 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 04/17/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET70WW (3.00 ) dmi.board.name: 2767C99 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET70WW(3.00):bd04/17/2009:svnLENOVO:pn2767C99:pvrThinkPadT400:rvnLENOVO:rn2767C99:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2767C99 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-14-generic ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Touchpad lag when pressing keyboard shortcuts / hotkeys https://bugs.launchpad.net/bugs/455363 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 455363] Re: Touchpad lag when pressing keyboard shortcuts / hotkeys
** Attachment added: out.ogv http://launchpadlibrarian.net/33944329/out.ogv ** Attachment added: BootDmesg.gz http://launchpadlibrarian.net/33944337/BootDmesg.gz ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/33944339/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33944340/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/33944341/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/33944342/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/33944343/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/33944344/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/33944345/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/33944346/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/33944347/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/33944348/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/33944349/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/33944350/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/33944351/Xrandr.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/33944353/XsessionErrors.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/33944359/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/33944360/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/33944361/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/33944362/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/33944363/xkbcomp.txt -- Touchpad lag when pressing keyboard shortcuts / hotkeys https://bugs.launchpad.net/bugs/455363 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 282939] Re: gnusound crashes X session immediately on launch (Affects Intrepid, Jaunty, Karmic)
I am also experiencing this issue, backtrace of X crash attached. ** Attachment added: xcrash.log http://launchpadlibrarian.net/33973899/xcrash.log -- gnusound crashes X session immediately on launch (Affects Intrepid, Jaunty, Karmic) https://bugs.launchpad.net/bugs/282939 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 428783] Re: shadow remains on desktop after closing applet window
Just a side curiosity, why are shadows of those applets treated differently than the shadows of other objects in the first place? Note for instance that while windows / menus drop shadows on whatever is behind them, the clock applet seems to only drop a shadow if the desktop is behind it (but not if a window is behind it). -- shadow remains on desktop after closing applet window https://bugs.launchpad.net/bugs/428783 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
Just a notice: this bug is now also present with stock karmic packages, I suspect since the latest mesa update (7.6.0~git20090817.7c422387-0ubuntu2) -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
Okay! -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 414127] Re: Touchpad randomly fires incorrect events when scrolling
** Description changed: Using up-to-date karmic as of 15.08.2009 Problem: - When using the virtual scroll on the touchpad (i.e. only moving the finger on the right side of the pad, not pressing any button!), occasionally (apparently randomly) incorrect events are generated. + When using the virtual scroll on the touchpad (i.e. only moving the finger on the right side of the pad, not pressing any button!), occasionally (apparently randomly) incorrect events are generated. It also occurs with tap-to-click disabled. I can easily reproduce the issue by placing to fingers on the right side of the tab, i.e. _ | finger -| | | | finger -| || and tapping and slightly dragging with both fingers at a fast rate. Looking at the output from xev while doing this, between the events 4 and 5, occasionally some events of type 2 (center click) and 3 (rightclick) appear. This also happens when using the touchpad normally, i.e. browsing in firefox: quite often when scrolling through pages actions get perfomed that are either triggered by the center click or by a funciton of the contextmenu (which apparently hides again so quickly that one does not see it). To be noted is that this issue is NOT specific to any progam. I started noticing the problem since the last xserver-xorg-input- synaptics update, possibly related to the issues created with the patch that was introduced there, such as bug #405943. Hardware is a lenovo T400. -- Touchpad randomly fires incorrect events when scrolling https://bugs.launchpad.net/bugs/414127 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 414127] Re: Touchpad randomly fires incorrect events when scrolling
Uhm I never experienced the issue described there, the issue here is more general, i.e. the touchpad driver misreports events and then the program executes actions as if the reported button was pressed. -- Touchpad randomly fires incorrect events when scrolling https://bugs.launchpad.net/bugs/414127 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 414127] Re: Touchpad randomly fires incorrect events when scrolling
*** This bug is a duplicate of bug 386017 *** https://bugs.launchpad.net/bugs/386017 Indeed, now that you pointed it is exactely what I am experiencing. Marking as duplicate, thanks. ** This bug has been marked a duplicate of bug 386017 Brushing right-edge of trackpad causes clipboard to paste text -- Touchpad randomly fires incorrect events when scrolling https://bugs.launchpad.net/bugs/414127 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 414127] [NEW] Touchpad randomly fires incorrect events when scrolling
Public bug reported: Using up-to-date karmic as of 15.08.2009 Problem: When using the virtual scroll on the touchpad (i.e. only moving the finger on the right side of the pad, not pressing any button!), occasionally (apparently randomly) incorrect events are generated. I can easily reproduce the issue by placing to fingers on the right side of the tab, i.e. _ | finger -| | | | finger -| || and tapping and slightly dragging with both fingers at a fast rate. Looking at the output from xev while doing this, between the events 4 and 5, occasionally some events of type 2 (center click) and 3 (rightclick) appear. This also happens when using the touchpad normally, i.e. browsing in firefox: quite often when scrolling through pages actions get perfomed that are either triggered by the center click or by a funciton of the contextmenu (which apparently hides again so quickly that one does not see it). To be noted is that this issue is NOT specific to any progam. I started noticing the problem since the last xserver-xorg-input- synaptics update, possibly related to the issues created with the patch that was introduced there, such as bug #405943. Hardware is a lenovo T400. ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New -- Touchpad randomly fires incorrect events when scrolling https://bugs.launchpad.net/bugs/414127 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 405943] Re: [regression] rapid pointer movements with touchpad ignored
I suspect this issue could be related with the one I described in bug #414127. Is anyone who is experiencing this issue also experiencing issues like the one I described there? -- [regression] rapid pointer movements with touchpad ignored https://bugs.launchpad.net/bugs/405943 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
Just a short notice: as Bryce and often said above, this bug focuses on the occasional X crash. For the failure that only crashes / hangs wine (including GLXBadDrawable) I have opened a new bug #406865. -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
(The and often should not be there..) -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
Just an update from my part: I am still trying to get a backtrace via gdb, but as before, as soon as I attach gdb to X, X hangs until I terminate it, no matter if I start gdb from a VT, via ssh or within the gdm session itself. I also tried to launch gdm via gdb, but I had some difficulties to provide the correct arguments to gdm-binary ... Also, referring to http://wiki.ubuntu.com/X/Backtracing , no core file exists in /etx/X11 after the crash and also apport stays quiet. Was the gdm log attached in #11 of any use to you? Otherwise I'll keep trying. Just a note: issue still present with latest xserver 1.6.3 and all the other updated edgers packages. -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
I indeed forgot the cont via ssh... Anyway, backtrace attached. ** Attachment added: gdb-xorg.txt http://launchpadlibrarian.net/29826019/gdb-xorg.txt -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
Thanks for the background info! I tried to obtain some backtraces with the xorg edgers packages, at the moment the only one I managed to get was the one appended at the end of the gdm log of the crashed session, which is attached. Unfortunately gdb seems to hang X as soon as I attach it to the running instance of X, i.e. (but not the whole system, i.e. if I run sleep 30 kill -s KILL $(pidof gdb) and then run gdb, first X locks up, but restores as soon as gdb gets killed). Also, a new X from gdb from a VT also locks up screen and inputs. I'll try later this evening with a second computer via ssh. ** Attachment added: :0.log.1 http://launchpadlibrarian.net/29713443/%3A0.log.1 -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
Concerning the statement The problem is very likely caused by a problem with the intel graphics driver., I had a look at different setups and got the following results: - Both Jaunty and Karmic, GM45 (the Lenovo T400 I am experiencing the problem on): crash as described - Jaunty, proprietary ATI (HD3400) and proprietary NVIDIA: no problems of this kind (though I know nvidia has it's own driver framework) - Jaunty, opensource ATI (Lenovo T60, x1400, xserver-xorg-video-ati): Often GlxBadDrawable errors, but once in a while the applications started without any subsequent crashing. - Jaunty, older intel graphics (Intel GMA900): no problems of this kind The crashing itself as described in the initial description only appeared using the intel driver on the GM45 chipset, therefore I suspect that the problem lies there. On the other hand the GlxBadDrawable error seems to be a more widespread problem, though I didn't have the chance to test the newest packages on the T60 system as I do not own the laptop. I'll do some throughout testing according to http://wiki.ubuntu.com/X/Backtracing as soon as I get home this evening. -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [GM45] 3D application fail to run through Wine and often crash X
Okay, so I did some testing, and it looks like one of the updates in the past few days fixed the X crashing. Also, I did not experience any crashing or hanging anymore after testing some native Linux 3D applications. What however remains is wine failing on any attempt to run a non-native 3D application, with the following scenarios (in order of probabiltiy): 1) Immediate GLXBadDrawable, wine exits 2) The usual sequence of WINED3DFMT_A8R8G8B8 and similar error messages (as above) followed by a GLXBadDrawable + exit. 3) The usual WINED3DFMT_A8R8G8B8 plus wine displaying an empty window frame, the should-be 3D content missing, manual CTRL+C to exit. I also installed a separate karmic with the Xorg edgers PPA for testing, there X actually crashes like before. Now, out of the blue (I have no experience in graphics related stuff), isn't it that some color format is simply not implemented in the driver (at least concerning the WINED3DFMT_A8R8G8B8 errors)? And concerning the GLXBadDrawable which are observable also with xserver-xorg-video-ati and possibly other drivers, is there any way to get additional debug information? -- [GM45] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [Intel Graphics] 3D application fail to run through Wine and often crash X
Hello, Xorg.0.log is attached. Additionally I did some other testing, and I forgot to mention that the attempts often end with messages like X Error of failed request: GLXBadDrawable Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 505 Current serial number in output stream: 505 Also here, if I try repeatedly, occasionally one attempt wont end with GLXBadDrawable but will either crash X or terminate on it's own/hang shortly after the fixme:d3d_caps:IWineD3DImpl_FillGLCaps Received unrecognized GL_VENDOR Tungsten Graphics, Inc. Setting VENDOR_WINE. fixme:d3d:check_fbo_compat Format WINED3DFMT_R8G8B8 with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_A8R8G8B8 with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_X8R8G8B8 with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_R5G6B5 rtInternal format is not supported as FBO color attachment. fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM rtInternal format is not supported as FBO color attachment. fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16B16A16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. block. I have never found any (EE) entries after a crash in Xorg.0.log (or in any other log as I mentioned above...) ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/29317828/Xorg.0.log -- [Intel Graphics] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [Intel Graphics] 3D application fail to run through Wine and often crash X
Also native linux applications seem to have problems: I tried compiling and running vdrift, and X froze as soon as a track finished loading. Soundplayback did continue for a while though, which seems to indicate that only X froze and not the whole system... Again, I did not find any helpful information in any logs... -- [Intel Graphics] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 401067] Re: [Intel Graphics] 3D application fail to run through Wine and often crash X
** Description changed: - Running an up-to-date Ubuntu Karmik x86_64, hardware details attached. + Running an up-to-date Ubuntu Karmic x86_64, hardware details attached. Problem: 3D applications fail to run through wine without any exception. Furthermore, there is a 80% chance that the X server crashes after the attempt. The wine output reads: fixme:d3d_caps:IWineD3DImpl_FillGLCaps Received unrecognized GL_VENDOR Tungsten Graphics, Inc. Setting VENDOR_WINE. fixme:d3d:check_fbo_compat Format WINED3DFMT_R8G8B8 with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_A8R8G8B8 with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_X8R8G8B8 with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_R5G6B5 rtInternal format is not supported as FBO color attachment. fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM rtInternal format is not supported as FBO color attachment. fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16B16A16_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:win:EnumDisplayDevicesW ((null),0,0x32f7e0,0x), stub! Plus, in case of an X crash XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 after 56 requests (49 known processed) with 0 events remaining. Scanning through all the system logs, the only messages appearing at the time of the crash are Jul 18 14:02:16 PC4 bonobo-activation-server (sandro-20685): could not associate with desktop session: Failed to connect to socket /tmp/dbus-4wM2ONiot5: Connection refused Jul 18 14:02:17 PC4 console-kit-daemon[2928]: GLib-GObject-WARNING: instance of invalid non-instantiatable type `(null)' Jul 18 14:02:17 PC4 console-kit-daemon[2928]: GLib-GObject-CRITICAL: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Jul 18 14:02:17 PC4 console-kit-daemon[2928]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed Jul 18 14:02:17 PC4 acpid: client 16672[0:0] has disconnected Jul 18 14:02:17 PC4 acpid: client connected from 20695[0:0] It does not make any difference whether I run compiz or metacity. The problem is very likely caused by a problem with the intel graphics driver. -- [Intel Graphics] 3D application fail to run through Wine and often crash X https://bugs.launchpad.net/bugs/401067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
