[Bug 1267648] Re: Copying large amount of files to USB stick makes system laggy or even freeze/hang (temporary)
*** This bug is a duplicate of bug 1208993 *** https://bugs.launchpad.net/bugs/1208993 Part of the problem could be that that Nautilus eats up a lot of memory (even up to the point where it may crash) and may slow down or freeze when copying many files. This is due to issues with gvfs: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1133477 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267648 Title: Copying large amount of files to USB stick makes system laggy or even freeze/hang (temporary) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 388595] Re: Nautilus very slow copying huge amount of data
*** This bug is a duplicate of bug 1133477 *** https://bugs.launchpad.net/bugs/1133477 ** This bug has been marked a duplicate of bug 1133477 [SRU] cut-n-paste move files got stuck forever -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/388595 Title: Nautilus very slow copying huge amount of data To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/388595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
Could this, at least in part, be a duplicate of this bug? https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1133477 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133477] Re: cut-n-paste move files got stuck forever
This is most probably caused by this upstream issue: https://bugzilla.gnome.org/show_bug.cgi?id=757747 These patches to gvfs should greatly reduce the problem: https://git.gnome.org/browse/gvfs/commit/?id=0e001c9 https://git.gnome.org/browse/gvfs/commit/?id=fe33512 https://git.gnome.org/browse/gvfs/commit/?id=1224147 https://git.gnome.org/browse/gvfs/commit/?id=57acc80 As I understand, gvfs >1.30.3 should include these patches, so Ubuntu Zesty 17.04 should suffer much less from this issue. Can someone verify this? There are several similar bug reports that may be duplicates: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/388595 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993 ** Bug watch added: GNOME Bug Tracker #757747 https://bugzilla.gnome.org/show_bug.cgi?id=757747 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133477 Title: cut-n-paste move files got stuck forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1133477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133477] Re: cut-n-paste move files got stuck forever
** Also affects: caja (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133477 Title: cut-n-paste move files got stuck forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1133477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574211] Re: The "nolapic" boot option causes a kernel panic
I tested the mainline kernel 4.6.0-040600rc7, and the problem does not occur with this version. I also tested 4.4.10-040410, in which the problem did occur. It seems that the problem is indeed fixed in the upstream 4.6 kernel series, but not in 4.4. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: The kernel parameter "nolapic" causes an unrecoverable kernel panic with the 4.4.0-21 kernel in Xenial (16.04). I've verified this on two different machines. The 4.2.0-36 kernel from 15.10 boots without problems, with the same options. The kernel-logs contain no information on the failed boot attempts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: levien 2391 F pulseaudio - /dev/snd/controlC0: levien 2391 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: levien 2391 F pulseaudio + /dev/snd/controlC0: levien 2391 F pulseaudio CurrentDesktop: MATE Date: Sun Apr 24 11:54:14 2016 HibernationDevice: RESUME=UUID=df18bec1-dd4a-4c76-bb15-065133e0ffd0 InstallationDate: Installed on 2016-02-11 (72 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: - lono wireless extensions. - - enp0s10 no wireless extensions. + lono wireless extensions. + + enp0s10 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic root=UUID=c0232677-d281-4213-a6ec-682260728775 ro nolapic quiet splash RelatedPackageVersions: - linux-restricted-modules-4.2.0-36-generic N/A - linux-backports-modules-4.2.0-36-generic N/A - linux-firmware1.157 + linux-restricted-modules-4.2.0-36-generic N/A + linux-backports-modules-4.2.0-36-generic N/A + linux-firmware1.157 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) dmi.bios.date: 09/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574211 Title: The "nolapic" boot option causes a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574211] [NEW] The "nolapic" boot option causes a kernel panic
Public bug reported: The kernel parameter "nolapic" causes an unrecoverable kernel panic with the 4.4.0-21 kernel in Xenial (16.04). I've verified this on two different machines. The 4.2.0-36 kernel from 15.10 boots without problems, with the same options. The kernel-logs contain no information on the failed boot attempts. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: levien 2391 F pulseaudio /dev/snd/controlC0: levien 2391 F pulseaudio CurrentDesktop: MATE Date: Sun Apr 24 11:54:14 2016 HibernationDevice: RESUME=UUID=df18bec1-dd4a-4c76-bb15-065133e0ffd0 InstallationDate: Installed on 2016-02-11 (72 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp0s10 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic root=UUID=c0232677-d281-4213-a6ec-682260728775 ro nolapic quiet splash RelatedPackageVersions: linux-restricted-modules-4.2.0-36-generic N/A linux-backports-modules-4.2.0-36-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) dmi.bios.date: 09/10/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574211 Title: The "nolapic" boot option causes a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965281] Re: no dropbox indicator in gnome-classic panel
I had the same problem. It turned out that Dropbox requires the Notification Area applet, which isn't installed by default. Hold ALT + Win, right-click in the Gnome panel and add the applet. See if that solves the problem... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965281 Title: no dropbox indicator in gnome-classic panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/965281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112310] Re: Setting Wacom pen button to double click doesn't work
This seems to be fixed in 12.04, albeit with a new syntax. To assign a double-click to a button, either run something like: xsetwacom --set "Wacom Graphire2 4x5 stylus" Button 3 "button 1 button 1" (source: https://gist.github.com/i-e-b/2894651) or better, create a file /usr/lib/X11/xorg.conf.d/10-wacom.conf with the following line: Option "Button 3" "button 1 button 1" This fixes the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/112310 Title: Setting Wacom pen button to double click doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/112310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581663] Re: Wacom stylus buttons no longer emit double click events in Xorg
In 12.04, it will also work to create /usr/lib/X11/xorg.conf.d/10-wacom.conf with the following line: Option "Button 3" "button 1 button 1" This fixes the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581663 Title: Wacom stylus buttons no longer emit double click events in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/581663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581663] Re: Wacom stylus buttons no longer emit double click events in Xorg
I've just updated to 12.04 and tested it. The original syntax no longer works, but this does work: xsetwacom --set "Wacom Graphire2 4x5 stylus" Button 3 "button 1 button 1" (from: https://gist.github.com/i-e-b/2894651) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581663 Title: Wacom stylus buttons no longer emit double click events in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/581663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 519577] Re: package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build
I've just tested Jason's packages on an i386 system as well. On amd64 there is no libflashsupport-oss4 package, and the Flash-plugin just hangs on sound-output. On i386 I installed the libflashsupport-oss4 package, and the Flash-plugin does not hang, but there is no sound from Flash. I tried the solutions suggested in http://ubuntuforums.org/showthread.php?t=873749 without avail. I haven't tried compiling my own version of libflashsupport yet... -- package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build https://bugs.launchpad.net/bugs/519577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52857] Re: ERROR: cpu exception in dosemu code outside of VM86()!
The issue I experienced seems to have been fixed in the version of dosemu (dosemu-1.4.0.1) that is in the Lucid repositories. I haven't tested Maverick yet, but I suppose it should work there as well. -- ERROR: cpu exception in dosemu code outside of VM86()! https://bugs.launchpad.net/bugs/52857 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 519577] Re: package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build
Nice work, Jason! However, on amd64 the problems with the Flash-plugin still persist. Is there a reason why the libflashsupport-oss4 package was only built for i386? -- package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build https://bugs.launchpad.net/bugs/519577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 380860] Re: kile spell checker not aware of latex
As a reasonable temporary workaround in Lucid, I downloaded the latest version of latex.xml from svn (http://websvn.kde.org/trunk/KDE/kdelibs/kate/syntax/data/latex.xml?view=markup) and copied it into ~/.kde/share/apps/katepart/syntax/ It still has trouble with macro-parameters and backward quotes, but at least most LaTeX commands will be properly recognised as such. Especially if you only use on-the-fly spellchecking, it is quite usable this way... -- kile spell checker not aware of latex https://bugs.launchpad.net/bugs/380860 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdelibs in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 519577] Re: package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build
Currently the best way around this is not to use the oss4-dkms package from the repository, but to install OSS4 using one of the other methods (ie. install the prebuilt package from the opensound.com website or compile and install it yourself). I've put some instructions on my site: http://levien.zonnetjes.net/?q=oss4 -L. -- package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build https://bugs.launchpad.net/bugs/519577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112310] Re: Setting Wacom pen button to double click doesn't work
As I am not the original reporter, I've submitted a new bug report for Lucid as Bug #581663 I also found a workaround that was submitted a few months ago to one of the Ubuntu forums. It uses the X key-bindings to produce double click events. I did not test it yet: http://www.uluga.ubuntuforums.org/showthread.php?t=1366998 -- Setting Wacom pen button to double click doesn't work https://bugs.launchpad.net/bugs/112310 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581663] Re: Wacom stylus buttons no longer emit double click events in Xorg
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/48595880/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/48595881/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/48595883/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/48595884/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/48595885/Lsusb.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/48595886/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/48595887/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/48595888/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/48595889/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/48595890/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/48595891/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/48595892/UdevLog.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/48595893/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/48595894/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/48595895/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/48595896/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/48595897/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/48595898/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/48595899/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/48595900/xkbcomp.txt -- Wacom stylus buttons no longer emit double click events in Xorg https://bugs.launchpad.net/bugs/581663 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581663] [NEW] Wacom stylus buttons no longer emit double click events in Xorg
Public bug reported: Binary package hint: xorg This issue has already been reported for Jaunty in bug #112310, but as requested I'm submitting a new bug report for Lucid. According to the documentation from the Linux Wacom Project, you should be able to set a Wacom stylus button to double click using either a command like: xsetwacom set "Wacom Graphire2 4x5" button3 "dblclick 1" or by adding a line to the appropriate section of xorg.conf (or in Lucid: /usr/lib/X11/xorg.conf.d/10-wacom.conf): Option "Button3" "dblclick 1" The latter method stopped working in Ubuntu 7.04, and the former method stopped working in Ubuntu 9.04. Both methods still do not work in 10.04. The first method will not produce any errors, but seems to have no effect when using a "dblclick" setting. The second method will produce a warning in the Xorg log and also has no effect for "dblclick" settings: (**) Option "Device" "/dev/input/event6" (**) Wacom Graphire2 4x5 cursor: always reports core events (**) Option "Button2" "3" (**) Option "Button3" "dblclick 1" (WW) Option "Button3" requires an integer value (II) XINPUT: Adding extended input device "Wacom Graphire2 4x5 cursor" (type: CURSOR) Numeric button values (17, 196609) that used to generate double click events on older Wacom driver versions do not generate an error, but also do not work. A workaround to get double click events working has been reported, but it bypasses the Wacom problem (by changing the X key bindings) and I have not tested it yet: http://www.uluga.ubuntuforums.org/showthread.php?t=1366998 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon May 17 12:14:37 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-22-generic, x86_64: installed MachineType: System manufacturer System Product Name ProcCmdLine: root=UUID=8b1363d2-71fe-429a-87a8-51803bb29e60 ro usbcore.autosuspend=1 quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 04/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd04/06/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-22-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Wacom stylus buttons no longer emit double click events in Xorg https://bugs.launchpad.net/bugs/581663 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 519577] Re: package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build
Good work, the patched package from the PPA seems to install without problems now on my system (Lucid Lynx amd64). It works for the most part, however it did indeed seemed to cause the Flash-plugin to hang on sound output (as was already mentioned by Jason). This would probably need to be fixed for the package to be really usable... -- package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build https://bugs.launchpad.net/bugs/519577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112310] Re: Setting Wacom pen button to double click doesn't work
As suggested in bug #446943 I added the following two lines to the first section of /usr/lib/X11/xorg.conf.d/10-wacom.conf in Lucid: Option "Button2" "3" Option "Button3" "dblclick 1" Button 2 now works as expected, but for button 3 Xorg still complains that the value should be an integer and refuses to work. When using the values 196609 or 17 Xorg does not complain, but double click events also don't work. When using xsetwacom no errors are logged, but again the double click event is not emitted. I also tested the xsetwacom method without compiz, but the result was the same. Also with Metacity I could not get double click events to work... -- Setting Wacom pen button to double click doesn't work https://bugs.launchpad.net/bugs/112310 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112310] Re: Setting Wacom pen button to double click doesn't work
The problem still persists in Lucid when using xsetwacom. Also, I'm unsure as to where the wacom configuration settings should go now in the Xorg configuration files... The HAL fdi-stuff is deprecated as I understand, and wacom configuration now seems to be located in /usr/lib/X11/xorg.conf.d/10-wacom.conf. However, it contains InputClass sections rather than the old InputDevice sections. I have trouble finding any documentation on this new configuration, and don't want to break Xorg by messing around with it unknowlingly. Can anyone enlighten me? :-) -- Setting Wacom pen button to double click doesn't work https://bugs.launchpad.net/bugs/112310 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112310] Re: Setting Wacom pen button to double click doesn't work
I can confirm this on Jaunty. In Intrepid, this at least used to work: xsetwacom set "Wacom Graphire2 4x5" button3 "dblclick 1" But as of Jaunty, setting a button to "dblclick 1" or "17" seems to be broken, which is rather annoying. I haven't tried setting it in xorg.conf, as that already stopped working in Hardy. Moreover, Wacom tablets are now recognised through hald anyway (making them hotpluggable, which is nice). -L. -- Setting Wacom pen button to double click doesn't work https://bugs.launchpad.net/bugs/112310 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52857] Re: ERROR: cpu exception in dosemu code outside of VM86()!
I had the same problem on my AMD Phenom X4 (cpu family 16): dosemu crashes on boot, and the last time I tried it, it took the entire X-session with it (which I found a bit odd). Anyway, it seems that the "Division by zero" bug with new CPU-types has been fixed upstream, in SVN rev 1869: http://sourceforge.net/tracker/?func=detail&aid=2760088&group_id=49784&atid=457447 The current Ubuntu source-package seems to be at SVN rev 1828, let's hope it gets updated soon... ** Bug watch added: SourceForge.net Tracker #2760088 http://sourceforge.net/support/tracker.php?aid=2760088 ** Also affects: dosemu via http://sourceforge.net/support/tracker.php?aid=2760088 Importance: Unknown Status: Unknown -- ERROR: cpu exception in dosemu code outside of VM86()! https://bugs.launchpad.net/bugs/52857 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335405] Re: Screen refresh problems with nvidia on Jaunty
*** This bug is a duplicate of bug 269904 *** https://bugs.launchpad.net/bugs/269904 Not exactly, as explained by nVidia developer Aaron Plattner in https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/269904/comments/33 it is a design problem in X itself. More precisely, the problem is in the XDamage extension, which notifies applications and other parts of X when the screen needs to be redrawn. It was apparently never designed to handle asynchronous rendering (as Compiz does with the nvidia driver). This can result in redraw requests being sent/received in the wrong order. The Damage extension needs to be extended to fix this, which is not exactly trivial. That's why this is all taking so long... -- Screen refresh problems with nvidia on Jaunty https://bugs.launchpad.net/bugs/335405 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269904] Re: Screen refresh problems with nvidia on intrepid
Oops, sorry for posting duplicate information about the race condition and the loose binding thing. I guess I should've read the entire thread before pasting the comment. Still, apparently this bug is hard to find through Google or the search option in Launchpad, because it has so many manifestations (and "solutions"). So I hope it's still helpful for people like me, who get directed here from one of the 15 duplicates and don't scroll all the way up... :-P -- Screen refresh problems with nvidia on intrepid https://bugs.launchpad.net/bugs/269904 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269904] Re: Screen refresh problems with nvidia on intrepid
I've been trying to track down the cause of this problem for ages, and I think the comment from another user at bug #270377 has just helped me find it. Apparently the redraw problems described here and in the other bug reports are caused by a race condition, that can occur with compiz in combination with nvidia driver versions above 177.76. According to nvidia developers at the nvnews forums: "[the cause of the problem] is a race condition between the X server and compiz that's the result of a fundamental design problem in the way the Damage extension works." and "[fixing it] will require more changes to the Damage and GLX extensions, the X server, Compiz, and the NVIDIA X driver." Because it is apparently caused by a design problem, it will probably take some time before the problem is fixed. The only real way to ensure it doesn't happen at the moment is not to use compiz. But on some systems it helps to change settings that affect the timing of pixmap uploads to the GPU. That's why it may help to disable the compiz "--loose-binding" option, or to play with the powermizer settings. The fact that the occurrence of race-conditions may be affected by timing also explains the fact that everyone seems to experience this bug (and its many duplicates) differently, depending on hardware- configuration, which programs are running, the number of open windows, X.org and driver settings, etc. For me, restarting compiz without loose binding immediately solved the refresh problems, albeit at the cost of compiz rendering performance. I just had a look at the wrapper script that launches compiz in Ubuntu. It enables --loose-binding on nvidia hardware (which in turn works around a performance issue with texture binding on nVidia cards), but it only seems to do this when indirect rendering is disabled (the default setting). So in theory this should disable --loose-binding without having to edit the wrapper script or (re)start compiz by hand every time: mkdir -p ~/.config/compiz; echo INDIRECT=0 >> ~/.config/compiz/compiz- manager It just adds "INDIRECT=0" to the configuration file ~/.config/compiz /compiz-manager, to force indirect rendering. This will of course degrade performance (e.g. with desktop cube) and will also disable some effect plugins (e.g. water). But I much prefer it to having the current redraw problems or disabling desktop effects all together. I do hope this issue gets properly fixed though... See also: http://www.nvnews.net/vbulletin/showthread.php?t=120892 http://www.nvnews.net/vbulletin/showthread.php?t=124470 -- Screen refresh problems with nvidia on intrepid https://bugs.launchpad.net/bugs/269904 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225858] Re: compiz refreshes infrequently and doesn't redraw window contents after suspend/resume, screensaver or full-screen applications.
*** This bug is a duplicate of bug 269904 *** https://bugs.launchpad.net/bugs/269904 ** This bug has been marked a duplicate of bug 269904 Screen refresh problems with nvidia on intrepid -- compiz refreshes infrequently and doesn't redraw window contents after suspend/resume, screensaver or full-screen applications. https://bugs.launchpad.net/bugs/225858 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270377] Re: content of window do not redraw automatically (intrepid)
*** This bug is a duplicate of bug 269904 *** https://bugs.launchpad.net/bugs/269904 Anakin, you're brilliant! I've been trying to track down the cause of this problem for ages, and your suggestion has just helped me find it. Apparently the redraw problems are caused by a race condition, which occurs with compiz in combination with nvidia driver versions above 177.76. According to nvidia developers at the nvnews forums: "[the cause of the problem] is a race condition between the X server and compiz that's the result of a fundamental design problem in the way the Damage extension works." and "[fixing it] will require more changes to the Damage and GLX extensions, the X server, Compiz, and the NVIDIA X driver." Because it is apparently caused by a design problem, it will probably take some time before the problem is fixed. The only real way to ensure it doesn't happen is not to use compiz. But on some systems it helps to change settings that affect the timing of pixmap uploads to the GPU. You can for instance try to disable the compiz "--loose-binding" option, or play with the powermizer settings. I just had a look at the wrapper script that launches compiz in Ubuntu. It enables --loose-binding on nvidia hardware (which in turn works around a performance issue with texture binding on nVidia cards), but it only seems to do this when indirect rendering is disabled (the default setting). So in theory this should disable --loose-binding without having to edit the wrapper script or (re)start compiz by hand every time: mkdir -p ~/.config/compiz; echo INDIRECT=0 >> ~/.config/compiz/compiz- manager It just adds "INDIRECT=0" to the configuration file ~/.config/compiz /compiz-manager, to force indirect rendering. This will of course degrade performance and disable some effect plugins, but if it works I would much prefer it to having the current redraw problems... See also: http://www.nvnews.net/vbulletin/showthread.php?t=120892 http://www.nvnews.net/vbulletin/showthread.php?t=124470 ** This bug has been marked a duplicate of bug 269904 Screen refresh problems with nvidia on intrepid -- content of window do not redraw automatically (intrepid) https://bugs.launchpad.net/bugs/270377 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270377] Re: content of window do not redraw automatically (intrepid)
I just tried the 180.27 nvidia driver as well, but this version still locks up my system after an hour or so. When this happens the Xorg process goes to 100% CPU use, and I need to log in remotely to either kill X or restart the system, because other methods (CTRL-ALT-DEL, CTRL- ALT-Backspace or switching to a text terminal) don't work anymore... Unfortunately the system logs don't give any indication of errors when this happens. I've switched back to 177.82 again, because at least this version is stable (for me). Also, the 180.27 driver still gave redraw issues. Here's slightly more detailed description: With compiz 0.7.8 all window updates would cease at the moment any application tries to go fullscreen (screensaver, image viewers, etc.). After I upgraded to compiz 0.7.9, at least this problem was gone and the redraw-issues were relatively minor and infrequent (or unpredictable if you will), and mostly occured in Firefox (haven't tried LastFM). However, when I open a lot of (I think more than 32) windows, the contents of the most recently opened windows isn't drawn or updated at all until I manually resize the window. My system has an Asus M3N 78 motherboard with a GeForce 8200 mGPU and a quad-core Phenom CPU. When I turn off desktop effects, everything works just fine. (To be able to switch easily I installed Compiz-Switch: http://forlong.blogage.de/article/pages/Compiz-Switch). I guess I'll just have to keep trying new versions of the nvidia driver as they are released... -- content of window do not redraw automatically (intrepid) https://bugs.launchpad.net/bugs/270377 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325665] Re: hda-intel: no codecs initialised
This is the kernel output when the sound is working normally: [ 13.717726] HDA Intel :00:07.0: power state changed by ACPI to D0 [ 13.717737] HDA Intel :00:07.0: PCI INT A -> Link[LAZA] -> GSI 21 (level, low) -> IRQ 21 [ 13.717794] HDA Intel :00:07.0: setting latency timer to 64 [ 13.875499] hda_codec: num_steps = 0 for NID=0x27 (ctl = Surround Playback Volume) [ 13.875743] hda_codec: num_steps = 0 for NID=0x26 (ctl = Center Playback Volume) [ 13.876036] hda_codec: num_steps = 0 for NID=0x18 (ctl = Side Playback Volume) [ 13.876622] hda_codec: num_steps = 0 for NID=0x14 (ctl = Capture Volume) Sometimes I need to reboot (one or several times) to get this. This is the alsa-info output when everything is working: http://www .alsa-project.org/db/?f=80ce5ae4037468e9afd7506d6f8dd9cb09e1b8fc -- hda-intel: no codecs initialised https://bugs.launchpad.net/bugs/325665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325665] Re: hda-intel: no codecs initialised
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/22008887/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/2200/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/22008890/Dependencies.txt ** Attachment added: "HalComputerInfo.txt" http://launchpadlibrarian.net/22008891/HalComputerInfo.txt ** Attachment added: "LsUsb.txt" http://launchpadlibrarian.net/22008893/LsUsb.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/22008894/Lspci.txt ** Attachment added: "ProcCpuInfo.txt" http://launchpadlibrarian.net/22008895/ProcCpuInfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/22008896/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/22008897/ProcModules.txt -- hda-intel: no codecs initialised https://bugs.launchpad.net/bugs/325665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 325665] [NEW] hda-intel: no codecs initialised
Public bug reported: Sometimes when booting, the sound hardware isn't detected (or not properly initialised?), and I don't have any audio. Usually rebooting helps, but not always. I'm running an up-to-date Intrepid Ibex amd64 on a board with an nVidia chipset and a Realtek ALC1200 audio controller. This is what the kernel says on booting when the sound doesn't work: [ 12.777106] HDA Intel :00:07.0: power state changed by ACPI to D0 [ 12.777117] HDA Intel :00:07.0: PCI INT A -> Link[LAZA] -> GSI 21 (level, low) -> IRQ 21 [ 12.777171] HDA Intel :00:07.0: setting latency timer to 64 [ 12.809774] hda-intel: no codecs initialized [ 12.809832] HDA Intel :00:07.0: PCI INT A disabled Here is the output from alsa-info in these cases: http://www.alsa- project.org/db/?f=ae306fb3e6a0bfb28b51ca505a0f06e594de0544 ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: linux-image-2.6.27-11-generic 2.6.27-11.27 ProcCmdLine: root=UUID=8b1363d2-71fe-429a-87a8-51803bb29e60 ro pci=routeirq quiet splash ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-11.27-generic SourcePackage: linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- hda-intel: no codecs initialised https://bugs.launchpad.net/bugs/325665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270377] Re: content of window do not redraw automatically (intrepid)
** Bug watch added: Compiz Plugins / Config Bugs #964 http://bugs.opencompositing.org/show_bug.cgi?id=964 ** Also affects: compiz via http://bugs.opencompositing.org/show_bug.cgi?id=964 Importance: Unknown Status: Unknown -- content of window do not redraw automatically (intrepid) https://bugs.launchpad.net/bugs/270377 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270377] Re: content of window do not redraw automatically (intrepid)
I experienced more or less the same redraw issues, on an up-to-date Intrepid AMD64 install with a GeForce 8200. The failures to redraw window contents occur only with desktop-effects turned on, and mostly in Firefox but sometimes also in other applications. I tried both the standard 177.82 and the new 180.22 nvidia drivers, but both experienced redraw problems. Additionally, the 180.22 driver destabilised USB and X.org on my system (interrupt issues?), so I had to switch back to 177. Next I tried updating compiz to 0.7.9-git20080918. This seems to have helped a bit, I now only get redraw issues after opening a lot of windows (>32). If I keep the number of open windows below 32, everything seems to be OK. Strange... -- content of window do not redraw automatically (intrepid) https://bugs.launchpad.net/bugs/270377 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225858] Re: compiz refreshes infrequently and doesn't redraw window contents after suspend/resume, screensaver or full-screen applications.
** Summary changed: - compiz refreshes infrequently and doesn't redraw window contents after suspend/resume. + compiz refreshes infrequently and doesn't redraw window contents after suspend/resume, screensaver or full-screen applications. -- compiz refreshes infrequently and doesn't redraw window contents after suspend/resume, screensaver or full-screen applications. https://bugs.launchpad.net/bugs/225858 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225858] Re: compiz refreshes infrequently and doesn't redraw window contents after suspend/resume.
The compiz redraw-problems seem to pop up every time an application tries to use the full screen. That's why the screensaver triggered it in my case, but I also get the same issues when I try to view a full-screen image. So it seems to be the same problem that is described here: http://www.nvnews.net/vbulletin/showthread.php?t=122336 Reverting to version 173 of the nvidia driver seemed to resolve this particular issue for me, although I didn't test very well because this driver messed up scrolling in most applications, making it impossible to work. Updating the nvidia driver to the current stable release (180.22, taken from https://launchpad.net/%7Emythbuntu-trunk-0.22/+archive/ppa) also seemed to solve the problem, but caused stability issues on my system. (These were possibly interrupt-related, after a while my USB devices tended to lock up, or the entire X.org just crashed or hung for no apparent reason.) So I switched back to the default 177.82 nvidia driver and upgraded compiz to the latest git-snapshot (0.7.9-git20080918, following http://ubuntuforums.org/showthread.php?t=971379). This seems to cause the least problems so far. There are still some annoying window-update issues when I open a lot of windows, but other than that everything works as it should with desktop-effects switched on. I guess this bug is a combined problem of the current compiz-fusion (0.7.8) and the nvidia 177.82 driver in Intrepid, as updating either seems to make it go away... -- compiz refreshes infrequently and doesn't redraw window contents after suspend/resume, screensaver or full-screen applications. https://bugs.launchpad.net/bugs/225858 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225858] Re: compiz refreshes infrequently and doesn't redraw window contents after suspend/resume.
I get the same problems on my system, a quad-core AMD Phenom with an nVidia GeForce 8200 (rev a2) chipset, running Intrepid Ibex 8.10 amd64 and version 177 of the nvidia driver. Additional information: The problems also seem to occur after the screen has just been blanked by the (default) screensaver, without going to standby or suspend (also the monitor stays on). After coming back from the screensaver, redraws and effects are slow as hell, and window contents is no longer updated properly. Events such as mouseclicks and keyboard input continue to be registered by applications, but because nothing is updated it appears as though the system hangs. Switching off desktop effects or restarting compiz.real restores behaviour back to normal. At first I thought it was caused by the Wobbly Windows plugin, because after disabling the plugin everything seemed to work fine again. However, this was only temporary because after the next screensaver blank the problems returned, though in a slightly different way (redraws only failed for newly opened windows this time). Changing other plugin settings did not seem to help. There were no errors reported in the Xorg logfile or in /var/log/messages. I haven't tried reverting to version 173 of the nvidia driver yet. -- compiz refreshes infrequently and doesn't redraw window contents after suspend/resume. https://bugs.launchpad.net/bugs/225858 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24630] Re: Evince crashes when zooming PDF-File to 400%
I have been experiencing possibly the same problem with evince and any PDF-file which has scanned pages (e.g. any scientific article from before 1995 or so, such as this one: http://www.pubmedcentral.nih.gov/picrender.fcgi?artid=1215979&blobtype=pdf ) These documents seem to open just fine at first, but then the system just locks up swapping and eventually evince is killed due to lack of resources. Zooming to 400% is not even needed. Monitoring with top shows that the evince process fills up all available memory, followed by all available swap space, until it is killed. I'm using evince on an up-to-date 8.04 Hardy Heron system with 512 Mb memory and 512 Mb swapspace. The same documents open fine with KPDF and acroread on the same system, and with evince on a Feisty system. PDF documents without scanned pages seem to open just fine in evince as well. -- Evince crashes when zooming PDF-File to 400% https://bugs.launchpad.net/bugs/24630 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112310] Re: Setting Wacom pen button to double click doesn't work
Sorry for the delay, I only just installed Hardy due to lack of time (and disk-space for the update). The wacom-tools method seems to work correctly now. However, adding Option "Button3" "dblclick 1" or Option "Button3" "17" to xorg.conf still does not work. When using the first form, X complains that the parameter value has to be numeric. However, the old numeric value 17 also does not work anymore. Seems as if the driver and the bit that parses the Xorg values are out of sync somehow, one expecting a numeric value while the other expects a string... As a workaround, I've added the following command to my Session: xsetwacom set stylus button3 "dblclick 1" Where should I report the xorg.conf issue? -L. -- Setting Wacom pen button to double click doesn't work https://bugs.launchpad.net/bugs/112310 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211962] [NEW] keyjnote exits with OpenGL error
Public bug reported:
Binary package hint: keyjnote
I'm trying to run keyjnote on the most current Ubuntu server 8.04 beta.
Xorg is running fine, Xpdf works fine, glxinfo reports a working GL
environment (albeit software rendering), glxgears runs fine, yet
keyjnote always gives me the following error:
Welcome to KeyJnote version 0.10.2
Traceback (most recent call last):
File "/usr/bin/keyjnote", line 160, in
from OpenGL.GL import *
File "/usr/lib/python2.5/site-packages/OpenGL/GL/__init__.py", line 2, in
from OpenGL.raw.GL import *
File "/usr/lib/python2.5/site-packages/OpenGL/raw/GL/__init__.py", line 6, in
from OpenGL.raw.GL.constants import *
File "/usr/lib/python2.5/site-packages/OpenGL/raw/GL/constants.py", line 7,
in
from OpenGL import platform, arrays
File "/usr/lib/python2.5/site-packages/OpenGL/platform/__init__.py", line 57,
in
_load()
File "/usr/lib/python2.5/site-packages/OpenGL/platform/__init__.py", line 40,
in _load
plugin_class = _findPlatform( platform )
File "/usr/lib/python2.5/site-packages/OpenGL/platform/__init__.py", line 28,
in _findPlatform
return entrypoint.load()
File "/usr/lib/python2.5/site-packages/pkg_resources.py", line 1912, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File "/usr/lib/python2.5/site-packages/OpenGL/platform/glx.py", line 8, in
class GLXPlatform( baseplatform.BasePlatform ):
File "/usr/lib/python2.5/site-packages/OpenGL/platform/glx.py", line 16, in
GLXPlatform
mode=ctypes.RTLD_GLOBAL
File "/usr/lib/python2.5/site-packages/OpenGL/platform/ctypesloader.py", line
42, in loadLibrary
return dllType( name, mode )
File "/usr/lib/python2.5/ctypes/__init__.py", line 348, in __init__
self._handle = _dlopen(self._name, mode)
OSError: ('GL: cannot open shared object file: No such file or directory',
'GL', None)
It seems that python cannot find the OpenGL library, but I don't know
anything about Python so I'm having a hard time figuring out what's
causing this...
** Affects: keyjnote (Ubuntu)
Importance: Undecided
Status: New
--
keyjnote exits with OpenGL error
https://bugs.launchpad.net/bugs/211962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112310] Re: Setting pen button to double click doesn't work
I have the same problem, but with a Graphire tablet. I tried both: xsetwacom set stylus button3 "dblclick 1" and setting it in xorg.conf: Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device""/dev/input/wacom" Option "Type" "stylus" Option "Button2" "3" Option "Button3" "dblclick 1" EndSection So it seems that this bug is not related to xsetwacom but to the wacom- driver that is shipped with Xorg... -Levien ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Setting pen button to double click doesn't work + Setting Wacom pen button to double click doesn't work ** Description changed: Binary package hint: wacom-tools I have a Wacom Volito 2 and am using Ubuntu 7.04. In both 6.06 en 6.10 I was able to set the second button of my Wacom pen to doubleclick using the following code in xorg.conf: Option"Button2""17" However, this code doesn't work anymore in Ubuntu 7.04. Using 'xsetwacom list param" I found out that I had to use the following code in the console to set my stylus to doubleclick: - xsetwacom stylus Button2 "dblclick 1" + xsetwacom set stylus Button2 "dblclick 1" But that doens't work... also the following codes don't work: - xsetwacom stylus Button2 "dblclick 0" - xsetwacom stylus Button2 "dblclick 1" - xsetwacom stylus Button2 "dblclick 2" - xsetwacom stylus Button2 "2" - xsetwacom stylus Button2 "17" + xsetwacom set stylus Button2 "dblclick 0" + xsetwacom set stylus Button2 "dblclick 1" + xsetwacom set stylus Button2 "dblclick 2" + xsetwacom set stylus Button2 "2" + xsetwacom set stylus Button2 "17" I hope this can be fixed, since a single button for doubleclicking is way easier than tapping twice or tapping once and using the return button. -- Setting Wacom pen button to double click doesn't work https://bugs.launchpad.net/bugs/112310 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 15093] Re: gksudo fails if using libpam-krb5 for password auth
Hi Eddie, Well, I'm no expert on this I'm afraid. But as far as I understand it the problem is as follows: gksudo is basically a graphical front-end for sudo, and therefore it needs to know when sudo asks for a password. PAM modules however present their own prompt, which may be quite different from the standard "Password:" one. If that happens, gksudo will not recognise the custom password prompt and will just keep waiting. The first patch just tells sudo to override the PAM prompt in such cases, so that gksudo will recognise it. The problem is that this breaks certain kinds of authentication (which of course is not a problem if you don't need those, as in my case). The second patch adds an option to sudo allowing for a postfix-string to be appended to the password prompt. gksudo can then simply wait for this string, and then pass its password to sudo. However, this patch is still waiting to be included in sudo. As it has been submitted in two years ago, it seems that the sudo developers do not consider it to be a priority feature. So in short, the problem with gksudo and pam is not really a bug, it is just a result of the way gksudo is implemented as a front-end to sudo. The best way to get it fixed would be to let the sudo maintainers know that this is really a feature that people do need, and to help them test it. Here is sudo bugzilla link again: http://www.sudo.ws/bugs/show_bug.cgi?id=180 As for your problem, the patched version of sudo may or may not solve it. It probably depends on what kind of prompt the bioapi module presents, if any. I wouldn't be too worried about patching sudo though. You can easily see what the patch does just by looking at the code. Furthermore, you can always go back to the original sudo if it doesn't work. The only problem is that the link to the patched version will probably get overwritten if sudo is updated... Best regards, Levien -- gksudo fails if using libpam-krb5 for password auth https://bugs.launchpad.net/bugs/15093 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 15093] Re: gksudo fails if using libpam-krb5 for password auth
Have you tried a patched version of sudo? You can get Jeff's patch from
http://www.sudo.ws/bugs/attachment.cgi?id=37
Get the source-package for sudo ("apt-get source sudo" or the latest tarball
from http://www.sudo.ws/sudo/download.html), apply the patch, recompile and
install (e.g. in /usr/local). You can rename the original sudo (in /usr/bin) to
something like /usr/bin/sudo_original and then do "ln -s /usr/local/bin/sudo
/usr/bin/sudo". That might solve your problem for the time being.. Of course
this issue really needs to be addressed by Ubuntu / gksudo / sudo if more
people are to use PAM authentication with Ubuntu.
-L.
--
gksudo fails if using libpam-krb5 for password auth
https://bugs.launchpad.net/bugs/15093
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 15093] Re: gksudo fails if using libpam-krb5 for password auth
I agree with brettatoms, it is important to fix this issue if Ubuntu is to be usable in anything other than a stand-alone desktop environment. I am currently working with a small NGO to try and replace their ancient Windows 98 installations with Ubuntu 7.04. We authenticate the Ubuntu machines against a windows domain server. I now work around this bug by installing a patched copy of sudo in /usr/local/bin, and replacing /usr/bin/sudo with a symlink to the patched version. But anyone will agree that this is hardly an elegant solution... -L. -- gksudo fails if using libpam-krb5 for password auth https://bugs.launchpad.net/bugs/15093 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
