[Desktop-packages] [Bug 573006] Re: Touch screen driver clicks at wrong location
I've got the same problem with a MSI Wind Top AE1920, here is a xorg.conf with full support. It works on ubuntu 12.04 and 12.10. ** Attachment added: "xorg.conf for ubuntu 12.04 and up" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/573006/+attachment/3447847/+files/xorg.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/573006 Title: Touch screen driver clicks at wrong location Status in Open Input Framework: Invalid Status in “xserver-xorg-input-evdev” package in Ubuntu: Fix Released Bug description: Freeze Exception --- Some input devices provide information on proximity. For the X evdev module, X events are sent only while the device is in proximity. However, the kernel may send updates on the location of interaction while the device is not in proximity. One example is when a touch is lightly in contact with a resistive touchscreen. The kernel is sending coordinates, but X evdev doesn't pass them on until the kernel says the interaction has passed a pressure threshold and is now in good contact with the screen. When the device goes into proximity, the last X and Y values at any time must be used. These values may be sent in the same packet as the in proximity data, or the values may have been sent while out of proximity. The change here checks for each valuator value if it has been set in the current packet along with the proximity change. If not, then it checks if there was a value sent while out of proximity. This ensures that each value is correctly handled, whereas before the change only the values set along side the proximity change would be propagated through X. Without this change, a user may touch one location of a touchscreen, then touch a second location, and the X server will see the first touch and then a second touch which begins at the location of the first touch and is immediately dragged to the location of the second touch. With the change, the X events are set properly. The change fixes a logic error in the original masked valuators code that I wrote and landed upstream. I believe the risk of regression to be very low as the fix is self contained and easy to verify. Original Bug Report --- On Lucid, the touch screen of my Latitude 2100 is no longer handled by evtouch, but some other touchscreen driver having the following bug: When I press my finger agains the screen, the expected behaviour is that the cursor clicks at the location where my finger is. However, it clicks at the location where the pointer currently is and _afterwards_ moves to the location of my finger, what of course results in a selection between the original and the new position. How can I find out which touchscreen driver is currently active? I'd like to have a look at it. To manage notifications about this bug go to: https://bugs.launchpad.net/oif/+bug/573006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 573006] Re: Touch screen driver clicks at wrong location
I've got the same problem with a MSI Wind Top AE1920, here is a xorg.conf with full support. It works on ubuntu 12.04 and 12.10. ** Attachment added: "xorg.conf for ubuntu 12.04 and up" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/573006/+attachment/3447848/+files/xorg.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/573006 Title: Touch screen driver clicks at wrong location Status in Open Input Framework: Invalid Status in “xserver-xorg-input-evdev” package in Ubuntu: Fix Released Bug description: Freeze Exception --- Some input devices provide information on proximity. For the X evdev module, X events are sent only while the device is in proximity. However, the kernel may send updates on the location of interaction while the device is not in proximity. One example is when a touch is lightly in contact with a resistive touchscreen. The kernel is sending coordinates, but X evdev doesn't pass them on until the kernel says the interaction has passed a pressure threshold and is now in good contact with the screen. When the device goes into proximity, the last X and Y values at any time must be used. These values may be sent in the same packet as the in proximity data, or the values may have been sent while out of proximity. The change here checks for each valuator value if it has been set in the current packet along with the proximity change. If not, then it checks if there was a value sent while out of proximity. This ensures that each value is correctly handled, whereas before the change only the values set along side the proximity change would be propagated through X. Without this change, a user may touch one location of a touchscreen, then touch a second location, and the X server will see the first touch and then a second touch which begins at the location of the first touch and is immediately dragged to the location of the second touch. With the change, the X events are set properly. The change fixes a logic error in the original masked valuators code that I wrote and landed upstream. I believe the risk of regression to be very low as the fix is self contained and easy to verify. Original Bug Report --- On Lucid, the touch screen of my Latitude 2100 is no longer handled by evtouch, but some other touchscreen driver having the following bug: When I press my finger agains the screen, the expected behaviour is that the cursor clicks at the location where my finger is. However, it clicks at the location where the pointer currently is and _afterwards_ moves to the location of my finger, what of course results in a selection between the original and the new position. How can I find out which touchscreen driver is currently active? I'd like to have a look at it. To manage notifications about this bug go to: https://bugs.launchpad.net/oif/+bug/573006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 680628] Re: Unable to print a document with evince, works correctly with Adobe Acrobat Reader
Yes, what a pity ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/680628 Title: Unable to print a document with evince, works correctly with Adobe Acrobat Reader Status in Poppler: Fix Released Status in “cairo” package in Ubuntu: Fix Released Status in “poppler” package in Ubuntu: Fix Released Status in “cairo” package in Debian: New Bug description: Binary package hint: evince When I try to print this pdf with evince the first page take more than one hour for been printed. And when I use Adobe Acrobat Reader it take less than one minute. I've try on 2 others computer same behaviors. This is not the only pdf with this problems. I'm using Ubuntu 10.04 up to date. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evince 2.30.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: ath_hal Architecture: i386 Date: Tue Nov 23 20:59:11 2010 KernLog: ProcEnviron: LANGUAGE=fr_FR:fr:en_US:en PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: evince To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/680628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995054] Re: thunderbird loses langpacks after upgrade
Solution is: cd /usr/lib/thunderbird/extensions sudo ln -s /usr/lib/thunderbird-addons/extensions/langpack...@thunderbird.mozilla.org.xpi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/995054 Title: thunderbird loses langpacks after upgrade Status in “adblock-plus” package in Ubuntu: Invalid Status in “enigmail” package in Ubuntu: Invalid Status in “mozilla-devscripts” package in Ubuntu: Invalid Status in “mozvoikko” package in Ubuntu: Invalid Status in “thunderbird” package in Ubuntu: Confirmed Status in “adblock-plus” source package in Lucid: Triaged Status in “enigmail” source package in Lucid: Triaged Status in “mozilla-devscripts” source package in Lucid: Triaged Status in “mozvoikko” source package in Lucid: Triaged Status in “thunderbird” source package in Lucid: Triaged Bug description: Hi. After upgrading thunderbird to version 12.0.1+build1-0ubuntu0.10.04.1 on 10.04 I cannot see any system-wide langpack in the addons menu. The reason of it is that somehow (I think it's the order of package installation/configuring ) '/usr/lib/thunderbird/extensions' becomes a directory while upgrade (it should be symlink to '/usr/lib/thunderbird-addons/etenstions' normally). So, all langpacks stays in '/usr/lib/thunderbird-addons/extensions', but thunderbird doesn't detect them. I don't see this problem on 12.04, I think it's because it already had /usr/lib/thunderbird folder before upgrade, but ubuntu 10.04 used /usr/lib/thunderbird-a.b directories for storing thunderbird package data earlier, so it has this problem. A quick solution is: mv /usr/lib/thunderbird/extensions/* /usr/lib/thunderbird-addons/extensions rmdir /usr/lib/thunderbird/extensions ln -s /usr/lib/thunderbird-addons/extensions /usr/lib/thunderbird This bug has already affected many machines in our office. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adblock-plus/+bug/995054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 680628] Re: Unable to print a document with evince, works correctly with Adobe Acrobat Reader
Okay, i've got the same result here, so i think #24 is a dream ;-) So what could be the solution now ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/680628 Title: Unable to print a document with evince, works correctly with Adobe Acrobat Reader Status in Poppler: Fix Released Status in “cairo” package in Ubuntu: Fix Released Status in “poppler” package in Ubuntu: Fix Released Status in “cairo” package in Debian: New Bug description: Binary package hint: evince When I try to print this pdf with evince the first page take more than one hour for been printed. And when I use Adobe Acrobat Reader it take less than one minute. I've try on 2 others computer same behaviors. This is not the only pdf with this problems. I'm using Ubuntu 10.04 up to date. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evince 2.30.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: ath_hal Architecture: i386 Date: Tue Nov 23 20:59:11 2010 KernLog: ProcEnviron: LANGUAGE=fr_FR:fr:en_US:en PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: evince To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/680628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 680628] Re: Unable to print a document with evince, works correctly with Adobe Acrobat Reader
Hello Bruno, i only works on LTS versions ... but i'll put packages for maverick on ppa, upload in progress, so keep in touch. Éric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/680628 Title: Unable to print a document with evince, works correctly with Adobe Acrobat Reader Status in Poppler: Fix Released Status in “cairo” package in Ubuntu: Fix Released Status in “poppler” package in Ubuntu: Fix Released Status in “cairo” package in Debian: New Bug description: Binary package hint: evince When I try to print this pdf with evince the first page take more than one hour for been printed. And when I use Adobe Acrobat Reader it take less than one minute. I've try on 2 others computer same behaviors. This is not the only pdf with this problems. I'm using Ubuntu 10.04 up to date. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evince 2.30.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: ath_hal Architecture: i386 Date: Tue Nov 23 20:59:11 2010 KernLog: ProcEnviron: LANGUAGE=fr_FR:fr:en_US:en PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: evince To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/680628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 680628] Re: Unable to print a document with evince, works correctly with Adobe Acrobat Reader
Hello, this ppa is created, so could you please try it ? sudo apt-add-repository ppa:eric-seigne/lucid-poppler-cairo then try to print and ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/680628 Title: Unable to print a document with evince, works correctly with Adobe Acrobat Reader Status in Poppler: Fix Released Status in “cairo” package in Ubuntu: Fix Released Status in “poppler” package in Ubuntu: Fix Released Status in “cairo” package in Debian: New Bug description: Binary package hint: evince When I try to print this pdf with evince the first page take more than one hour for been printed. And when I use Adobe Acrobat Reader it take less than one minute. I've try on 2 others computer same behaviors. This is not the only pdf with this problems. I'm using Ubuntu 10.04 up to date. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evince 2.30.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: ath_hal Architecture: i386 Date: Tue Nov 23 20:59:11 2010 KernLog: ProcEnviron: LANGUAGE=fr_FR:fr:en_US:en PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: evince To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/680628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 680628] Re: Unable to print a document with evince, works correctly with Adobe Acrobat Reader
Hi all, here is a ppa : https://launchpad.net/~eric-seigne/+archive/lucid-poppler-cairo The "solution" is: * backport pixman 0.20 from natty * backport cairo from natty + changes on debian/control to break depends on specific versions of packages not available in lucid * backport poppler from natty + changes on debian/control to break depends on specific versions of packages not available in lucid Upload is in progress ... please test theses packages ! Éric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/680628 Title: Unable to print a document with evince, works correctly with Adobe Acrobat Reader Status in Poppler: Fix Released Status in “cairo” package in Ubuntu: Fix Released Status in “poppler” package in Ubuntu: Fix Released Status in “cairo” package in Debian: New Bug description: Binary package hint: evince When I try to print this pdf with evince the first page take more than one hour for been printed. And when I use Adobe Acrobat Reader it take less than one minute. I've try on 2 others computer same behaviors. This is not the only pdf with this problems. I'm using Ubuntu 10.04 up to date. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evince 2.30.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: ath_hal Architecture: i386 Date: Tue Nov 23 20:59:11 2010 KernLog: ProcEnviron: LANGUAGE=fr_FR:fr:en_US:en PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: evince To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/680628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 680628] Re: Unable to print a document with evince, works correctly with Adobe Acrobat Reader
i've got the same bug here, epdfview could print without any problem, it works with "lp command line" too but evince and f-spot (and others ?) takes a loong time to print. Éric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/680628 Title: Unable to print a document with evince, works correctly with Adobe Acrobat Reader Status in Poppler: Fix Released Status in “cairo” package in Ubuntu: Fix Released Status in “poppler” package in Ubuntu: Fix Released Status in “cairo” package in Debian: New Bug description: Binary package hint: evince When I try to print this pdf with evince the first page take more than one hour for been printed. And when I use Adobe Acrobat Reader it take less than one minute. I've try on 2 others computer same behaviors. This is not the only pdf with this problems. I'm using Ubuntu 10.04 up to date. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evince 2.30.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: ath_hal Architecture: i386 Date: Tue Nov 23 20:59:11 2010 KernLog: ProcEnviron: LANGUAGE=fr_FR:fr:en_US:en PATH=(custom, user) LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: evince To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/680628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 880490] [NEW] gvfs-mount sftp on non standard port does not work
Public bug reported: Please try this command on different versions of ubuntu, it works with lucid but not with natty gvfs-mount sftp://login@ip:port/home/user/login ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/880490 Title: gvfs-mount sftp on non standard port does not work Status in “gvfs” package in Ubuntu: New Bug description: Please try this command on different versions of ubuntu, it works with lucid but not with natty gvfs-mount sftp://login@ip:port/home/user/login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/880490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
