[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
@Adrien I was happy until "You can easily fix that yourself". For every Launchpad reader that can, there's 100s who can't. And many thousands who don't even know Launchpad exists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
"It's not like you get hundreds of them each day." True. But even one such message puzzles and worries users. 360 users have marked this bug, but imagine how many thousands don't even know to look on Launchpad? This report was filed 18 months ago. I don't doubt it's hard to fix it for systems that have been upgraded. But this affects a fresh install of 16.04.2. Is it hard to make _apt the owner of .../package-data- downloads/partial/ when Ubuntu is freshly installed? I'm sure some of us reporting this bug come across as whiners, part of the problem, not part of the solution. Chippendale didn't send out furniture with splinters, he was passionate about quality. We're passionate about Linux. That's why we go to the trouble of reporting bugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Fresh install of 16.04.2, with latest updates. # apt-get install wine ttf-mscorefonts-installer: processing... ttf-mscorefonts-installer: downloading http://downloads.sourceforge.net/corefonts/andale32.exe Get:1 http://downloads.sourceforge.net/corefonts/andale32.exe [198 kB] Fetched 198 kB in 11s (16.8 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/andale32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) ... Similar messages for 10 more .exe files. Result is the user has no idea whether Wine has been fully installed correctly or not. /etc/passwd includes the line _apt:x:105:65534::/nonexistent:/bin/false # ll /var/lib/update-notifier/package-data-downloads/partial/ total 8 drwxr-xr-x 2 root root 4096 Jun 26 14:41 ./ drwxr-xr-x 3 root root 4096 Jun 26 14:41 ../ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 764414] Re: private master bugs are confusing and lead to more duplicate filings
@kfogel: really? Is that what tafthorne's suggestion was? Well, in that case, I agree, that's brilliant. @tafthorne: why did I not realise how brilliant your suggestion was? Simple. Because its length made me mutter 'tl;dr' and skip on to the next. Please, if you're going to make further brilliant suggestions for Ubuntu, MAKE THEM SHORT!!! ;) This bug report is approaching its 6th anniversary. Can we hope for progress? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/764414 Title: private master bugs are confusing and lead to more duplicate filings Status in apport package in Ubuntu: Triaged Bug description: Binary package hint: apport Apport currently tracks the master bug as a private bug visible only to Ubuntu developers (bugcontrol) and makes duplicate bugs public after stripping their data. This works well but has some downsides: - Launchpad cannot show the master bug to folk reporting bugs via apport (so they file new bugs always) - After users file a new bug apport detects its a duplicate and then they cannot see the master bug and get frustrated. It would be nice to have: - the master bug be public so that reporters of dups can see it in the dupe finder and can see if a dupe is detected post-filing. - Developers still have easy access to the raw crash data. - One way to do that that does not need much development would be to have a private bug exist, linked from the master bug (e.g. with a comment or in the description; something like 'Confidential crashdump for this bug is attached to bug 12345 - only visible to Ubuntu developers'). One way to achieve this is to have apport file a new public bug to be the master. This would have the necessary metadata and would include the link to the private bug + gather all the duplicates to itself. One downside is that Apport would appear to be the bug reporter for all crashdump based bug reports. That's not necessarily a bad thing, but it may confuse people. Another way would be to have apport file a new private bug, move the attachments over from the original bug, add explanation and metadata in the description, subscribe bugcontrol and then sanitise the original bug report the same way it sanitises public bugs today. This would make the original bug be the public master, preserving the date of filing and the reporter. OTOH large files would need to be shuffled around and this might be unreliable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/764414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 764414] Re: private master bugs are confusing and lead to more duplicate filings
Would 'Confirmed' be a more appropriate status than 'In progress'? Indeed, given that this bug was reported over 5 years ago, even mentioning the word 'progress' carries a touch of irony. :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/764414 Title: private master bugs are confusing and lead to more duplicate filings Status in apport package in Ubuntu: In Progress Bug description: Binary package hint: apport Apport currently tracks the master bug as a private bug visible only to Ubuntu developers (bugcontrol) and makes duplicate bugs public after stripping their data. This works well but has some downsides: - Launchpad cannot show the master bug to folk reporting bugs via apport (so they file new bugs always) - After users file a new bug apport detects its a duplicate and then they cannot see the master bug and get frustrated. It would be nice to have: - the master bug be public so that reporters of dups can see it in the dupe finder and can see if a dupe is detected post-filing. - Developers still have easy access to the raw crash data. - One way to do that that does not need much development would be to have a private bug exist, linked from the master bug (e.g. with a comment or in the description; something like 'Confidential crashdump for this bug is attached to bug 12345 - only visible to Ubuntu developers'). One way to achieve this is to have apport file a new public bug to be the master. This would have the necessary metadata and would include the link to the private bug + gather all the duplicates to itself. One downside is that Apport would appear to be the bug reporter for all crashdump based bug reports. That's not necessarily a bad thing, but it may confuse people. Another way would be to have apport file a new private bug, move the attachments over from the original bug, add explanation and metadata in the description, subscribe bugcontrol and then sanitise the original bug report the same way it sanitises public bugs today. This would make the original bug be the public master, preserving the date of filing and the reporter. OTOH large files would need to be shuffled around and this might be unreliable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/764414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Madbiologist: thanks for clarifying. So I agree filing it as a new bug would be good. I'm not an appropriate person to do that, since I'm using Unity less and less, and even in the past I've only used LTS releases. I hope someone will pick this up. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in emerald: New Status in One Hundred Papercuts: Fix Released Status in metacity: In Progress Status in ubuntu-mate: Opinion Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in unity-2d: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of "misses" when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an "invisible" region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System > Preferences > Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Madbiologist: you write "This bug is about the default resize grab handle at window borders being too small". Can I gently suggest you read the title of this problem report? "Resizing windows by grabbing window borders is difficult" Window borders. Nothing about a resize grab handle (which I assume is the region in the lower right of some desktop's windows, is that so?). And also read the substance of post #1. It's about window borders. I'm sorry, but if you think the solution to a request for set-ability of window borders is to provide a feature in one corner of the window, I feel you've misunderstood. No doubt that feature is indeed a useful fix for some bugs and feature requests, but not, I believe, this one. So I would request this bug's status be changed. Fixed is not correct. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in emerald: New Status in One Hundred Papercuts: Fix Released Status in metacity: In Progress Status in ubuntu-mate: Opinion Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in unity-2d: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of "misses" when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an "invisible" region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System > Preferences > Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Seth, when you say 'Fix Released', does this mean that in System Settings there is now a means (using GUI tools only) for the user to modify the border width? Anything less than that is, to my mind, not a 'fix'. And I suspect many others with hand/eye coordination problems would agree it's not a fix. Ubuntu has traditionally aimed at inclusiveness, it should be striving to meet the needs of many, not just young people who are fortunate to have full health. Making the border width easily modifiable would be a step towards making it more inclusive. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in emerald: New Status in One Hundred Papercuts: Fix Released Status in metacity: In Progress Status in ubuntu-mate: Opinion Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in unity-2d: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of "misses" when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an "invisible" region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System > Preferences > Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
I don't even accept that it's adequately fixed in Unity (unless there's been significant progress since 14.04, for I only use LTS releases). I teach elderly users with little or no experience of computers. Naturally many don't have good hand/eye coordination, so they need to be able to adjust settings easily to make the system fit their needs. One would expect this to be found under Settings / Universal Access, but there is nothing there that addresses this issue. If you look at Windows XP (I'm not familiar enough with later versions to speak from memory) you can go into the control panel and set window borders to whatever width you want. After adjustment the result may not be as pretty, but when you're over 70 and unlikely to have a career in Hollywood, 'pretty' isn't high on your wish list, accessibility IS. Please consider addressing this. It would be a boon if you can get it done before 16.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in emerald: New Status in One Hundred Papercuts: Fix Released Status in metacity: In Progress Status in ubuntu-mate: Opinion Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in unity-2d: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work
@Nathaniel: does http://packaging.ubuntu.com/html/fixing-a-bug.html help? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1267059 Title: Unattended-Upgrade::Remove-Unused-Dependencies does not work Status in unattended-upgrades package in Ubuntu: Triaged Bug description: I have a system that runs unattended-upgrades just fine. Now i want to automate removal of old kernels and kernel header packages that are accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused- Dependencies true;'. But it doesn't work. Details: Lots of stuff pending autoremoval: $ apt-get --assume-no autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic linux-image-3.2.0-51-generic linux- image-3.2.0-52-generic linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic 0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded. After this operation, 2,893 MB disk space will be freed. Do you want to continue [Y/n]? N Abort. Note that the majority of these packages have been installed by unattended-upgrades from precise-security. According to the comments within/etc/apt/apt.conf.d/50unattended- upgrades, this should automate autoremoval: // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) Unattended-Upgrade::Remove-Unused-Dependencies true; but nothing happens (note the line Packages that are auto removed: '' : $ unattended-upgrades --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=precise-security'] adjusting candidate version: 'Version: package:'accountsservice' version:'0.6.15-2ubuntu9.6.1'' adjusting candidate version: 'Version: package:'libaccountsservice0' version:'0.6.15-2ubuntu9.6.1'' adjusting candidate version: 'Version: package:'libdrm-intel1' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm-nouveau1a' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm-radeon1' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm2' version:'2.4.43-0ubuntu0.0.3'' Checking: bc ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-pc ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub2-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: iproute ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: landscape-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) blacklist: [] Packages that are auto removed: '' InstCount=0 DelCount=0 BrokenCout=0 No packages found that can be upgraded unattended I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS To manage
[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work
Apreche: you say it's a serious issue, and I agree with you. Allegedly, if I look at the stats at the top of the page, this affects me and 34 other users. Though I'm betting that's just the tip of the iceberg. Informal discussions reveal that bugs need to have thousands indicating it affects them before they're likely to get attention. So either don't hold your breath or find a way to get more visibility. :( Or find a developer you can get interested? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1267059 Title: Unattended-Upgrade::Remove-Unused-Dependencies does not work Status in unattended-upgrades package in Ubuntu: Triaged Bug description: I have a system that runs unattended-upgrades just fine. Now i want to automate removal of old kernels and kernel header packages that are accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused- Dependencies true;'. But it doesn't work. Details: Lots of stuff pending autoremoval: $ apt-get --assume-no autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic linux-image-3.2.0-51-generic linux- image-3.2.0-52-generic linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic 0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded. After this operation, 2,893 MB disk space will be freed. Do you want to continue [Y/n]? N Abort. Note that the majority of these packages have been installed by unattended-upgrades from precise-security. According to the comments within/etc/apt/apt.conf.d/50unattended- upgrades, this should automate autoremoval: // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) Unattended-Upgrade::Remove-Unused-Dependencies true; but nothing happens (note the line Packages that are auto removed: '' : $ unattended-upgrades --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=precise-security'] adjusting candidate version: 'Version: package:'accountsservice' version:'0.6.15-2ubuntu9.6.1'' adjusting candidate version: 'Version: package:'libaccountsservice0' version:'0.6.15-2ubuntu9.6.1'' adjusting candidate version: 'Version: package:'libdrm-intel1' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm-nouveau1a' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm-radeon1' version:'2.4.43-0ubuntu0.0.3'' adjusting candidate version: 'Version: package:'libdrm2' version:'2.4.43-0ubuntu0.0.3'' Checking: bc ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-pc ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: grub2-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: iproute ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) Checking: landscape-common ([Origin component:'main' archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0
[Touch-packages] [Bug 1372448] Re: HP Deskjet D1660 prints but no ink on paper!
I've changed the status back to incomplete because I still hope to move this forward. I'm unable to borrow the printer before January. ** Changed in: cups (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1372448 Title: HP Deskjet D1660 prints but no ink on paper! Status in “cups” package in Ubuntu: Incomplete Bug description: HP Deskjet D1660 moves the paper and the head exactly as if it's printing correctly, but there's no ink on the paper. However it does work as expected on Windows, so the hardware is ok. Reproduced on 12.04, 14.04, Linux Mint 17 (which is based on 14.04) and even Debian 7.5. I hope to borrow the printer from the owner to capture logs etc and investigate in more detail. It's strange that I can find no other reports of such behaviour with the D1660, though there are other reports of it not working at all and subsequent success. But bug #521429 describes an identical problem with the HP F370 printer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1372448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241972] Re: Drag and drop from Dash to Desktop doesn't work
If you don't have additional info, please just click on the This bug affects you and 93 other people exclamation mark (at the top of the bug report), so you add to the count. Adding comments like Me too just clutter reports and make it harder for developers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1241972 Title: Drag and drop from Dash to Desktop doesn't work Status in Chromium Browser: New Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in Unity 7.1 series: Won't Fix Status in Unity 7.2 series: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: When you try to drag and drop an app from Dash (both from app lens and home lens) to Desktop, system display an error and the shortcut isn't created. The error is: Error while copying - There was an error getting information about /. More details: The specified location is not supported Then there are four buttons: Cancel - Skip all - Skip - Retry. Way to reproduce: - Open the dash - Drag an app icon and drop on desktop What happend: - An error is raised What expected: - A shortcut is created With file, music and photo is all ok. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1241972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
Isn't this really a workaround, rather than a proper fix? Presumably when bi-directional comms are used there is useful info being returned by the printer, so now that it's prevented that will cause the printer to run slower or other problems will be ignored? Will this be taken up with Canon's engineers, or were they not the people who wrote the driver? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: Triaged Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372448] Re: HP Deskjet D1660 prints but no ink on paper!
Driver is whatever is installed by Ubuntu out of the box, a fresh install. I can't provide further info, but I hope to investigate fully when the owner lends me the printer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1372448 Title: HP Deskjet D1660 prints but no ink on paper! Status in “cups” package in Ubuntu: Incomplete Bug description: HP Deskjet D1660 moves the paper and the head exactly as if it's printing correctly, but there's no ink on the paper. However it does work as expected on Windows, so the hardware is ok. Reproduced on 12.04, 14.04, Linux Mint 17 (which is based on 14.04) and even Debian 7.5. I hope to borrow the printer from the owner to capture logs etc and investigate in more detail. It's strange that I can find no other reports of such behaviour with the D1660, though there are other reports of it not working at all and subsequent success. But bug #521429 describes an identical problem with the HP F370 printer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1372448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 521429] Re: HP Deskjet F370 produces nothing but blank outputs
Identical problem for the HP Deskjet D1660 printer reported in bug #1372448. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/521429 Title: HP Deskjet F370 produces nothing but blank outputs Status in “cups” package in Ubuntu: Expired Bug description: Binary package hint: cups HP Deskjet F370 just gives me blank outputs when printing. The printer works perfectly when connected to my Win 7 laptop but when connecting it to my Ubuntu desktop it fails. I can hear it working and the toner heads are moving but no ink is produced on the paper. The printer is connected via usb. It's similar to the bug described in report #313195 but as I have another os-version and another printer I file this report. System: Ubuntu Karmic 9.10 CUPS 1.4.1-5ubuntu2.2 Expected results: The printer should give me a printed copy of the desired document. Actual result: The printer just produces blank papers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/521429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
lpadmin -p MX310-series -o usb-unidir-default=true seems to fix the problem. Removing that (-R) and using instead lpadmin -p MX310-series -o usb-no-reattach-default=true the symptoms are as before. Does this help? Are there further tests I can run? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: Incomplete Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
I have the MX310 printer on loan again for a short time. I suspected that the behaviour, with the printer hanging up and requiring the power plug to be pulled to recover, while Ubuntu was fine, is perhaps due to a firmware error. After all, no matter what one throws at the printer, it shouldn't lock up, right? But I've downloaded the firmware update program (Windows and Mac only, grrr) using XP and found that the firmware is already at 1.040, Canon's latest version. On XP the printer prints the example doc (supplied above) without incident, again using Libre Office. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: Incomplete Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] [NEW] Canon MX310 printer hangs when printing LibreOffice Writer doc
Public bug reported: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: New Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
Example LO document used in above test. ** Attachment added: prints-but-hangs-printer.odt https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+attachment/4159903/+files/prints-but-hangs-printer.odt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: New Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
lsusb: Bus 001 Device 007: ID 04a9:1728 Canon, Inc. MX310 ser $ ls -l /dev/usb/lp* /dev/bus/usb/*/* crw-rw-r-- 1 root root 189, 0 Jul 21 19:49 /dev/bus/usb/001/001 crw-rw-r--+ 1 root lp 189, 6 Jul 21 19:49 /dev/bus/usb/001/007 crw-rw-r-- 1 root root 189, 128 Jul 21 19:49 /dev/bus/usb/002/001 crw-rw-r-- 1 root root 189, 132 Jul 21 19:49 /dev/bus/usb/002/005 crw-rw-r-- 1 root root 189, 256 Jul 21 19:49 /dev/bus/usb/003/001 crw-rw-r-- 1 root root 189, 384 Jul 21 19:49 /dev/bus/usb/004/001 crw-rw-r-- 1 root root 189, 512 Jul 21 19:49 /dev/bus/usb/005/001 crw-rw-r-- 1 root root 189, 513 Jul 21 19:49 /dev/bus/usb/005/002 crw-rw-r-- 1 root root 189, 514 Jul 21 19:49 /dev/bus/usb/005/003 crw-rw 1 root lp 180, 0 Jul 21 19:49 /dev/usb/lp0 crw-rw 1 root lp 180, 1 Jul 21 19:49 /dev/usb/lp1 $ sudo usb_printerid /dev/usb/lp0 GET_DEVICE_ID string: MFG:Canon;CMD:BJL,BJRaster3,BSCCe,PLI;SOJ:TXT01;MDL:MX310 series;CLS:PRINTER;DES:Canon MX310 series;VER:1.040;STA:10;HRI:EU;MSI:E3; $ sudo usb_printerid /dev/usb/lp1 GET_DEVICE_ID string: MFG:Canon;CMD:MultiPASS 2.1;MDL:MX310 series FAX;CLS:PRINTER;DES:Canon MX310 series FAX; $ lpinfo -v network https network http network ipp network ipps network socket network lpd network ipp14 direct usb://Canon/MX310%20series?serial=470CDEinterface=1 direct usb://Canon/MX310%20series%20FAX?serial=470CDEinterface=2 direct hp network smb direct hpfax $ Cups 1.7.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: New Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
Thanks for quick response. I did follow as much of that as seemed relevant to me. Can you be more specific? By the way, I had difficulty following the instructions to turn on the error log. The gear icon in 14.04 has no 'Printer' in its menu (and 12.04 has 'Printers', not 'Printer'). Though once I explored 12.04 and realised that the intent was to use the standard dialog in System Settings, I got past that. It's a wiki, but it's an immutable page, so someone needs to fix it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: Incomplete Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp