[Desktop-packages] [Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
For info. The bug also means that the systemd journal is growing at an extremely fast rate. Double whammy. All these files by default reside in the root file system. Which is usually created quite small. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Try https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/comments/18 It worked for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+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 1939746] [NEW] Leaves open window marker on icon in gdm3 favourites sidebar after program has exited
Public bug reported: Frequently leaves an open window marker on the Thunderbird icon in Gnome Desktop favourites sidebar. This is especially prevalent when the program has been launched as the default email client by some other process. Right clicking on the icon brings up the "New window/Compose New Message/Contacts/Remove from favourites/Quit". This menu is unresponsive and cannot be dismissed. This makes Thunderbird unusable. Ubuntu version is Hirsute. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: gdm3 thunderbird ** Description changed: Frequently leaves an open window marker on the Thunderbird icon in Gnome Desktop favourites sidebar. This is especially prevalent when the program has been launched as the default email client by some other process. Right clicking on the icon brings up the "New window/Compose New Message/Contacts/Remove from favourites/Quit". This menu is unresponsive and cannot be dismissed. This makes Thunderbird unusable. + + Ubuntu version is Hirsute. -- 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/1939746 Title: Leaves open window marker on icon in gdm3 favourites sidebar after program has exited Status in thunderbird package in Ubuntu: New Bug description: Frequently leaves an open window marker on the Thunderbird icon in Gnome Desktop favourites sidebar. This is especially prevalent when the program has been launched as the default email client by some other process. Right clicking on the icon brings up the "New window/Compose New Message/Contacts/Remove from favourites/Quit". This menu is unresponsive and cannot be dismissed. This makes Thunderbird unusable. Ubuntu version is Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1939746/+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 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
Daniel, I apologise. We have been talking about different apps. I have been referring to the browser plugin that talks to https://extensions.gnome.org/. This is because it was the first thing I spotted when I searched on the net. I realise that what you have been talking about the is a standalone app that is accessible via the applications panel or the activities search box. Yes, the standalone app works perfectly and is packaged with the shell. The browser plugin does not. I have only tested the Firefox version though. The Chrome one might be better. Thank you for being patient Roger -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+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 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
I am running Ubuntu Focal 20.04. The gnome-shell version is 3.36.2-1ubuntu1-20.04.1. The desktop icons version is 20.04.0-2-1ubuntu1-20.04.1. The app does not work. I believe the app is designed to work on per user extensions only. The desktop icon extension is installed as a system extension in /usr/share/gnome-shell/extensions. See the review by akram87 on the page https://extensions.gnome.org/extension/1465/desktop-icons/ But that is not the point. All I am trying to achieve is to gather information about the impact the ubuntu version of the extension has on the desktop rendering. The easiest way for the user to do this is by issuing one simple command. sudo mv /usr/share/gnome-shell/extensions/desktop-icons@csoriano something-else If I am missing something here please accept my apologies. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+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 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
The Extensions app does not appear to work fro the csoriano version of desktop icons. It thinks that it is the rastersoft fork. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+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 1867585] Re: CPU spikes caused by saving PDF to Desktop
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1867585 Title: CPU spikes caused by saving PDF to Desktop Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: ### Affected version - Ubuntu 19.10 - GNOME 3.34.1 - X11 ### Bug summary Downloading a large (60MB) PDF to the desktop causes CPU spikes at regular intervals. Was not able to reproduce when saving it elsewhere (such as `~/Documents`) ### Steps to reproduce [PDF](https://openstax.org/details/books/psychology?Book%20details) This is the PDF I downloaded that presented the issue (it's a free textbook published by OpenStax). 1. Click "Download PDF" 2. Save to the Desktop 3. Verify degraded system performance (see notes below) 4. Delete PDF 5. Verify system performance is no longer degraded ### Relevant logs, screenshots, screencasts etc. The culprit appears to be `createThumbnail.js`. It appears to be stuck in an infinite loop of starting and stopping a new process. This makes it a bit difficult to monitor. The method that worked for me was to run `top -o %CPU`, press `d`, and set the delay to something short like `0.1`. You should see `createThumbnail` continuously flash on and off the top of the list. I tested saving and deleting the PDF repeatedly and there were a couple times when it wouldn't cause the issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.10.2-1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 03:02:52 2020 InstallationDate: Installed on 2020-03-04 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1867585/+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 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+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 1832812] Re: Locking and unlocking the screen is slow and stuttery
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes
This bug is still present in Focal. It seems to have lost focus in upstream. In Focal it is much harder to remove the extension as it is even more tightly linked in as a mandatory dependency for a number of major system components. The only way to remove it is by deleting or renaming its files. It seems to me that this extension is responsible for numerous performance issues. A number of bugs have been raised on different symptoms, but all have a common factor of impacting performance and involving this extension. May I suggest that an umbrella bug is created and named something like "Unacceptable Gnome shell perfomance" and marked as critical. The first priority is to make this extension optional and disabled by default. The process of enabling should warn of potential performance issues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1812883 Title: Desktop view flashes every time ~/Desktop changes Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: All of the icons on my desktop visibly flash every time I change anything in the folder ~/Desktop, even if the change is not something that is visible on my desktop. For example, "touch ~/Desktop/.#foo". I mean, the icons that haven't changed should never flash at all, even if a change is made that _does_ affect the visible display -- only the things that are actually new or different should change their appearance, and everything else should remain the same and not flash. But at the very least, there should be no flash when there are no visible changes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 11:38:30 2019 InstallationDate: Installed on 2019-01-02 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1448351] Re: Preserve job files (allow reprinting) causes UI freeze
I am seeing a version of this bug in 19.04. However, this also causes a corruption of the of the cupsd.conf file and subsequent failure of the cups service to start/restart. The cupsd.conf filer is overwritten with the single line. PreserveJobFiles Yes I think this deserves more urgency than medium. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1448351 Title: Preserve job files (allow reprinting) causes UI freeze Status in One Hundred Papercuts: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: I can set this via dconf and I have no issues, but when I use the GUI to change this setting and press OK, the application freezes up and I have to force it to close. Happens on Ubuntu 15.04 currently, and it happened on 14.10 as well after some updates. I'm assuming it's an issue in this application and not CUPS because I can change it via dconf without issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: system-config-printer-gnome 1.5.6+20150318-0ubuntu2 Uname: Linux 4.0.0-04-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CupsErrorLog: E [24/Apr/2015:12:24:19 -0400] [Client 18] Local authentication certificate not found. E [24/Apr/2015:19:32:49 -0400] [Client 14] Local authentication certificate not found. E [24/Apr/2015:19:45:05 -0400] [Client 29] Local authentication certificate not found. CurrentDesktop: Unity Date: Fri Apr 24 19:58:36 2015 InstallationDate: Installed on 2015-04-23 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire X1430 PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-04-generic root=UUID=68234429-c890-4e23-b852-c4a62ff3282d ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aspire X1430 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svnAcer:pnAspireX1430:pvr:rvnAcer:rnAspireX1430:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire X1430 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1448351/+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 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon
I have now reinstalled the extension and having been running for a day without problems. This leads me to think that this a persistent data, rather than code related problem. I can only assume that the purge reinstall cycle removed whatever was causing the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1825623 Title: [AppIndicatorSupport-FATAL] unable to update overlay icon Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: After startup or login, An error occurs that just states cancel or report... but does not open a detail dialog Error messages in the syslog: ... Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon ... It seems that the update notifier cannot register its icon in the top bar. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 10:49:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (354 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825623/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes
The extension is only fully removed if you purge it and reboot your system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1812883 Title: Desktop view flashes every time ~/Desktop changes Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: All of the icons on my desktop visibly flash every time I change anything in the folder ~/Desktop, even if the change is not something that is visible on my desktop. For example, "touch ~/Desktop/.#foo". I mean, the icons that haven't changed should never flash at all, even if a change is made that _does_ affect the visible display -- only the things that are actually new or different should change their appearance, and everything else should remain the same and not flash. But at the very least, there should be no flash when there are no visible changes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 11:38:30 2019 InstallationDate: Installed on 2019-01-02 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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
Re: [Desktop-packages] [Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes
Hi Jonathon, Sorry, I wasn't clear. I really only meant the uninstall as a temporary test, to provide more information on what issues this extension was causing. For me it also solved a number of seemingly unrelated issues mostly to do with excessive cpu usage. Roger On 19 August 2019 20:35:40 Jonathan Kamens wrote: > I hardly think enough research into this has been done for it to be > obvious that this is a duplicate. > > > There are literally eight app indicator icons in my system tray right > now that disappear when I uninstall gnome-shell-extension-appindicator > (Synology Drive, Google Hangouts, Google Chrome, Dropbox, Yubico > Authenticator, Slack, Zoom, Flameshot), and I use them all the time. > Uninstalling that extension simply is not an option. > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1812883 > > > Title: > Desktop view flashes every time ~/Desktop changes > > > Status in gnome-shell-extension-desktop-icons: > New > Status in gnome-shell-extension-desktop-icons package in Ubuntu: > Triaged > > > Bug description: > All of the icons on my desktop visibly flash every time I change > anything in the folder ~/Desktop, even if the change is not something > that is visible on my desktop. > > > For example, "touch ~/Desktop/.#foo". > > > I mean, the icons that haven't changed should never flash at all, even > if a change is made that _does_ affect the visible display -- only the > things that are actually new or different should change their > appearance, and everything else should remain the same and not flash. > But at the very least, there should be no flash when there are no > visible changes. > > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: nautilus 1:3.30.5-1ubuntu1 > ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 > Uname: Linux 4.18.0-13-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.10-0ubuntu19 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Jan 22 11:38:30 2019 > InstallationDate: Installed on 2019-01-02 (20 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > SourcePackage: nautilus > UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) > > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1812883 Title: Desktop view flashes every time ~/Desktop changes Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: All of the icons on my desktop visibly flash every time I change anything in the folder ~/Desktop, even if the change is not something that is visible on my desktop. For example, "touch ~/Desktop/.#foo". I mean, the icons that haven't changed should never flash at all, even if a change is made that _does_ affect the visible display -- only the things that are actually new or different should change their appearance, and everything else should remain the same and not flash. But at the very least, there should be no flash when there are no visible changes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 11:38:30 2019 InstallationDate: Installed on 2019-01-02 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1532431] Re: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces
** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1532431 Title: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces Status in network-manager package in Ubuntu: Invalid Bug description: If a virtual 802.11 interface of type monitor is created on a 802.11 physical interface that already has a virtual interface of type managed created on it, then the managed interface is deleted. NetworkManager sets the type of the monitor interface to managed. This can be illustrated by the following commands. All the interface names have been listed in /etc/network/interfaces as follows so NetworkManager should not be managing them in any way. # Disable network manager on interface names I want to use for monitoring # related purposes iface eth1 inet manual iface BigTenda inet manual iface LittleBelkin inet manual iface LittleTenda inet manual iface Sinmax inet manual iface mon0 inet manual iface phy0.mon manual iface phy1.mon manual iface phy2.mon manual iface phy3.mon manual iface phy4.mon manual iface phy5.mon manual iface phy6.mon manual iface phy7.mon manual iface phy8.mon manual iface phy9.mon manual root@dragon:/home/roger# systemctl start NetworkManager root@dragon:/home/roger# iw dev phy#3 Interface Sinmax ifindex 11 wdev 0x30001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor flags otherbss root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type monitor Interface Sinmax ifindex 11 wdev 0x30001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw dev Sinmax del root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# systemctl stop NetworkManager root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds root@dragon:/home/roger# iw dev phy#4 Interface Sinmax ifindex 13 wdev 0x40001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor flags otherbss root@dragon:/home/roger# iw dev phy#4 Interface phy2.mon ifindex 14 wdev 0x40002 addr 00:0f:11:92:06:b2 type monitor Interface Sinmax ifindex 13 wdev 0x40001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw dev Sinmax del root@dragon:/home/roger# iw dev phy#4 Interface phy2.mon ifindex 14 wdev 0x40002 addr 00:0f:11:92:06:b2 type monitor This stops any running or future network traces on this interface working. This is another example of network manager interfering with interfaces it is not supposed to be managing. See bug #1314848 which is still unresolved. The above test was carried out on Ubuntu 15.10 network-manager: Installed: 1.0.4-0ubuntu5.2 Candidate: 1.0.4-0ubuntu5.2 Version table: *** 1.0.4-0ubuntu5.2 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu5 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+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 1746232] Re: driver looping then crashing
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing Status in linux package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Bug description: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. The above message is repeated once a second for a while. This usually but not always terminates with a page load fault in the driver. System can run for a few days without this happening. But on average it is once or twice a day. Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 30 11:40:08 2018 DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-07-01 (577 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/wd-root ro SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Dec 9 13:32:35 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 892918] Re: Cannot start jack using qjackctrl via dbus when playback only option is needed
** Changed in: jackd2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/892918 Title: Cannot start jack using qjackctrl via dbus when playback only option is needed Status in jackd2 package in Ubuntu: Invalid Bug description: My audio hardware requires the playback only option to be specified to successfully start jackd. However I cannot start jackd with this option via qjackctrl unless dbus startup option is disabled. I am guessing that qjacktrl causes a dbus jackd with default parameters to be started (and stopped) before it tries to start the one with the playback only parameter. Starting a jackd without the playback only parameter always results in a server that hang and doe not respond to any client requests. Catch 22. Ubuntu 11.10 jackd2 1.9.7~dsfg-1ubuntu2 qjackctl 0.3.8-1 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: jackd2 1.9.7~dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Nov 21 01:32:38 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: Upgraded to oneiric on 2011-10-15 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/892918/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes
I think this bug may well be a duplicate of #1825623. Would anyone object if I marked it as such. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1812883 Title: Desktop view flashes every time ~/Desktop changes Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: All of the icons on my desktop visibly flash every time I change anything in the folder ~/Desktop, even if the change is not something that is visible on my desktop. For example, "touch ~/Desktop/.#foo". I mean, the icons that haven't changed should never flash at all, even if a change is made that _does_ affect the visible display -- only the things that are actually new or different should change their appearance, and everything else should remain the same and not flash. But at the very least, there should be no flash when there are no visible changes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 11:38:30 2019 InstallationDate: Installed on 2019-01-02 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes
I worked round this issue by uninstalling gnome-shell-extension- appindicator. This fixed this issue and also a number of high cpu usage issues I was seeing. The cpu issues were sometimes severe enough to also expose weaknesses in the compositor. I suggest that anyone who is getting problems with gnome shell tries this work around and reports the results back here along with the a quick summary of the problem they were seeing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1812883 Title: Desktop view flashes every time ~/Desktop changes Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: All of the icons on my desktop visibly flash every time I change anything in the folder ~/Desktop, even if the change is not something that is visible on my desktop. For example, "touch ~/Desktop/.#foo". I mean, the icons that haven't changed should never flash at all, even if a change is made that _does_ affect the visible display -- only the things that are actually new or different should change their appearance, and everything else should remain the same and not flash. But at the very least, there should be no flash when there are no visible changes. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 11:38:30 2019 InstallationDate: Installed on 2019-01-02 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1835295] Re: Closing a window on the desktop freezes the desktop for a minute or more.
Closed bug to reduce confusion. ** This bug is no longer a duplicate of bug 1812883 Desktop view flashes every time ~/Desktop changes ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1835295 Title: Closing a window on the desktop freezes the desktop for a minute or more. Status in gnome-shell package in Ubuntu: Invalid Bug description: When I close a window on the gnome desktop. The desktop often freezes for anything between 30 seconds and a number of minutes. I notice this most often when closing a terminal window with ctrl+d. When look at the syslog and cpu usage (top) from a terminal logged in via ssh I see gnome-shell running at 100% and various gnome-shell error messages being reports. On the longer freezes the display often corrupts and the compositor can take a number of minutes to recover. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 3 20:04:23 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-07-01 (1097 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835295/+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 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon
I have seen a number of issues related to this error message. Including slow wake up from sleeps. Long pauses in screen repaint. Long launch times for applications. The only sure fix I found was to completely purge the gnome-shell-extension-appindicator package and reboot. The system them becomes properly responsive again. I have no idea what visual flim flam this extension provides so I can certainly do without it. It is a shame that it is installed by default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1825623 Title: [AppIndicatorSupport-FATAL] unable to update overlay icon Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: After startup or login, An error occurs that just states cancel or report... but does not open a detail dialog Error messages in the syslog: ... Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon ... It seems that the update notifier cannot register its icon in the top bar. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 10:49:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (354 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825623/+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 1835295] Re: Closing a window on the desktop freezes the desktop for a minute or more.
*** This bug is a duplicate of bug 1826604 *** https://bugs.launchpad.net/bugs/1826604 Hi Daniel, Sorry about the incomplete bug report. I had forgotten that I had turned apport. I have now found a fix for the first part of my report. This has reduced the noise level so that I can see the next part is definitely not the same bug. For the fist bug the relevant line from syslog is Jul 3 21:25:06 dragon gnome-shell[8816]: JS ERROR: TypeError: fileItem is null#012_updateDesktopIfChanged@/usr/share/gnome-shell/extensions /desktop- icons@csoriano/desktopManager.js:339:17#012_monitorDesktopFolder/<@/usr/share /gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89 This means that this bug is a duplicate of #1826604. The other bug seems to be related to gdm-x-session so I raise it over there. (After I have fixed apport!) Roger ** This bug has been marked a duplicate of bug 1826604 Extension causes saving files to desktop to be slow -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1835295 Title: Closing a window on the desktop freezes the desktop for a minute or more. Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I close a window on the gnome desktop. The desktop often freezes for anything between 30 seconds and a number of minutes. I notice this most often when closing a terminal window with ctrl+d. When look at the syslog and cpu usage (top) from a terminal logged in via ssh I see gnome-shell running at 100% and various gnome-shell error messages being reports. On the longer freezes the display often corrupts and the compositor can take a number of minutes to recover. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 3 20:04:23 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-07-01 (1097 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835295/+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 1835295] [NEW] Closing a window on the desktop freezes the desktop for a minute or more.
Public bug reported: When I close a window on the gnome desktop. The desktop often freezes for anything between 30 seconds and a number of minutes. I notice this most often when closing a terminal window with ctrl+d. When look at the syslog and cpu usage (top) from a terminal logged in via ssh I see gnome-shell running at 100% and various gnome-shell error messages being reports. On the longer freezes the display often corrupts and the compositor can take a number of minutes to recover. I see that there a number of bug reports with similar problems. Returning to the computer after a period of activity also can cause a long delay when wakoen up by a key press (similsr to #1830255).. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 3 20:04:23 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-07-01 (1097 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1835295 Title: Closing a window on the desktop freezes the desktop for a minute or more. Status in gnome-shell package in Ubuntu: New Bug description: When I close a window on the gnome desktop. The desktop often freezes for anything between 30 seconds and a number of minutes. I notice this most often when closing a terminal window with ctrl+d. When look at the syslog and cpu usage (top) from a terminal logged in via ssh I see gnome-shell running at 100% and various gnome-shell error messages being reports. On the longer freezes the display often corrupts and the compositor can take a number of minutes to recover. I see that there a number of bug reports with similar problems. Returning to the computer after a period of activity also can cause a long delay when wakoen up by a key press (similsr to #1830255).. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 3 20:04:23 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-07-01 (1097 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-24 (70 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-01-09T14:52:27.643509 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835295/+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 1769231] Re: wpa_cli -i flag and p2p_disabled=1 config broken
The p2p-disabled flag is not supported until wpa-supplicant 2.5+. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1769231 Title: wpa_cli -i flag and p2p_disabled=1 config broken Status in wpa package in Ubuntu: Confirmed Bug description: When connecting to wpa_supplicant with wpa_cli -i interface command, the connection hangs and never completes. This breaks various ifupdown integrations. Also, when p2p_disable=1 is set in wpa_supplicant.conf, the directive is not honored. I pulled the latest upstream hostap 2.6 source from git and built it using the same config file pulled from the deb source and tested to verify. Oddly the bug is actually in the wpa_supplicant binary as starting 2.6 with the right flags allows both the 2.4 and the 2.6 client to work correctly. However, starting the 2.4 daemon provided by artful causes both wpa_cli -i connection flags to fail. Starting the packaged wpa_supplicant throws an odd warning as well, not the double prefix on the p2p-dev. /sbin/wpa_supplicant -B -P /run/wpa_supplicant.wlp4s0.pid -i wlp4s0 -W -D nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf Successfully initialized wpa_supplicant Could not read interface p2p-dev-wlp4s0 flags: No such device Failed to create interface p2p-dev-p2p-dev-wlp4s0: -22 (Invalid argument) nl80211: Failed to create a P2P Device interface p2p-dev-p2p-dev-wlp4s0 P2P: Failed to enable P2P Device interface Also, in the presence of the p2p_disabled=1 flag, the 2.6 daemon provides the expected behavior of simply not creating the addition /run/wpa_supplicant/p2p-dev-wlp4s0 socket and unnamed device as seen by iw dev. However, the packaged version still creates both, apparently leaving p2p enabled. root@mendota:~/code/hostap/wpa_supplicant# iw dev phy#0 Unnamed/non-netdev interface wdev 0x5e addr e0:9d:31:d6:45:f3 type P2P-device txpower 0.00 dBm Interface wlp4s0 ifindex 3 wdev 0x1 addr e0:9d:31:d6:45:f2 type managed txpower 22.00 dBm root@mendota:~/code/hostap/wpa_supplicant# ls -l /run/wpa_supplicant total 0 srwxrwx--- 1 root dialout 0 May 4 12:49 p2p-dev-wlp4s0 srwxrwx--- 1 root dialout 0 May 4 12:49 wlp4s0 root@mendota:~/code/hostap/wpa_supplicant# wpa_cli -p /run/wpa_supplicant -i wlp4s0 wpa_cli v2.4 Copyright (c) 2004-2015, Jouni Malinen and contributors This software may be distributed under the terms of the BSD license. See README for more details. Interactive mode Warning: Failed to attach to wpa_supplicant. Could not connect to wpa_supplicant: wlp4s0 - re-trying ... Note that 2.6 still allows a connection even when p2p_disabled is not set and the unnammed p2p dev and socket is created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: wpasupplicant 2.4-0ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Fri May 4 12:49:50 2018 ProcEnviron: LANGUAGE=en_US TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1769231/+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 1746232] Re: driver looping then crashing
I have raised this bug at https://bugzilla.kernel.org/show_bug.cgi?id=198669 ** Bug watch added: Linux Kernel Bug Tracker #198669 https://bugzilla.kernel.org/show_bug.cgi?id=198669 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. The above message is repeated once a second for a while. This usually but not always terminates with a page load fault in the driver. System can run for a few days without this happening. But on average it is once or twice a day. Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 30 11:40:08 2018 DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-07-01 (577 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/wd-root ro SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Dec 9 13:32:35 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746232] Re: driver looping then crashing
The file name above should read radeon_ring.c. I thought you used to be able to edit comments on here! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. The above message is repeated once a second for a while. This usually but not always terminates with a page load fault in the driver. System can run for a few days without this happening. But on average it is once or twice a day. Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 30 11:40:08 2018 DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-07-01 (577 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/wd-root ro SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Dec 9 13:32:35 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746232] Re: driver looping then crashing
This crash looks very similar to #1301649. However is does not require the system to go into power save. The crash is in radeon_ring_backup which is in linux/drivers/gpu/drm/radeon/radeon_device.c and part of the linux (kernel) package. I have added that package to this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. The above message is repeated once a second for a while. This usually but not always terminates with a page load fault in the driver. System can run for a few days without this happening. But on average it is once or twice a day. Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 30 11:40:08 2018 DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-07-01 (577 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/wd-root ro SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Dec 9 13:32:35 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746232] Re: driver looping then crashing
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1746232 Title: driver looping then crashing Status in linux package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. The above message is repeated once a second for a while. This usually but not always terminates with a page load fault in the driver. System can run for a few days without this happening. But on average it is once or twice a day. Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 30 11:40:08 2018 DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-07-01 (577 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/wd-root ro SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Dec 9 13:32:35 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746232/+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 1746232] [NEW] driver looping then crashing
Public bug reported: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. The above message is repeated once a second for a while. This usually but not always terminates with a page load fault in the driver. System can run for a few days without this happening. But on average it is once or twice a day. Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jan 30 11:40:08 2018 DistUpgraded: 2017-11-06 18:26:08,552 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.10.0, 4.13.0-21-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-25-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-31-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-07-01 (577 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/wd-root ro SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to artful on 2017-11-06 (84 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0403:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Dec 9 13:32:35 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu ** Description changed: Running driver on Artful with the xwayland compositor. At random times the GPU stalls with. Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0 stalled for more than 29200msec Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU lockup (current fence id 0x1bdb last fence id 0x1bdc on ring 0) Usually when the system is idle. - The above message is repeated once a second for a while. The usually but - not always terminates with a page load fault in the driver. + The above message is repeated once a second for a while. This usually + but not always terminates with a page load fault in the driver. + + System can run for a few days without this happening. But on average it + is once or twice a day. + + Jan 30 11:22:30 dragon kernel: [ 488.507091] BUG: unable to handle kernel paging request at b406c1891ffc Jan 30 11:22:30 dragon kernel: [ 488.507176] IP: radeon_ring_backup+0xd3/0x140 [radeon] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-video-radeon 1:7.10.0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname:
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
I am changing the name of this bug and reopening it because the problem with the invalid ppd file still exists. The make-duplex-page-sizes-default.sh generates causes bad ppd files to be generated for the following printers. hp-officejet_6800.ppd: FAIL hp-officejet_pro_6830.ppd: FAIL hp-photosmart_5510d_series.ppd: FAIL hp-officejet_pro_6230.ppd: FAIL hp-photosmart_6510_series.ppd: FAIL hp-envy_7640_series.ppd: FAIL hp-officejet_5740_series.ppd: FAIL hp-envy_5640_series.ppd: FAIL hp-envy_5660_series.ppd: FAIL hp-officejet_8040_series.ppd: FAIL hp-officejet_6700.ppd: FAIL hp-officejet_pro_3610.ppd: FAIL hp-photosmart_7520_series.ppd: FAIL hp-officejet_7610_series.ppd: FAIL hp-officejet_7110_series.ppd: FAIL hp-officejet_pro_8500_a909a.ppd: FAIL hp-officejet_pro_8500_a909g.ppd: FAIL hp-officejet_pro_8500_a910.ppd: FAIL hp-photosmart_c309a_series.ppd: FAIL hp-officejet_pro_3620.ppd: FAIL hp-photosmart_7510_series.ppd: FAIL hp-officejet_pro_8500_a909n.ppd: FAIL hp-officejet_6000_e609n.ppd: FAIL hp-deskjet_3540_series.ppd: FAIL hp-photosmart_premium_c309g-m.ppd: FAIL hp-photosmart_prem-web_c309n-s.ppd: FAIL hp-officejet_6500_e709n.ppd: FAIL hp-envy_4500_series.ppd: FAIL hp-photosmart_prem_c310_series.ppd: FAIL hp-officejet_6500_e710n-z.ppd: FAIL hp-deskjet_4510_series.ppd: FAIL hp-officejet_4630_series.ppd: FAIL hp-officejet_pro_8000_a809.ppd: FAIL hp-deskjet_4640_series.ppd: FAIL hp-photosmart_estn_c510_series.ppd: FAIL hp-photosmart_prem_c410_series.ppd: FAIL hp-envy_5530_series.ppd: FAIL hp-laserjet_professional_p1609dn.ppd: FAIL hp-laserjet_professional_p1606dn.ppd: FAIL hp-laserjet_professional_p1607dn.ppd: FAIL hp-laserjet_professional_p1608dn.ppd: FAIL ** Changed in: hplip (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: New Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100]
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
I have upgraded to Xenial and I can no longer reproduce the original bug. I can only assume it was something in gtk+ this has been fixed in Xenial. The fact that when it happened the jobs stuck in the queue unless deleted with the only evidence that anything was amiss being the lack of print output and a message in the error log that was only available if debug mode was switched on. Running the xenial printer- driver-hpcups source on my Wily system still showed showed the bug. I am happy to run a local patched version on Xenial. So as far as I am concerned you can either let this bug time out or mark it as invalid. If anyone wants to raise an SRU it is up to them. That is a learning curve I do not want to experience. Thanks for your time. Roger -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
I thought I had posted a reply but i obviously had not. I had already tried the the test you suggested. I built a 3.15.7 version the hplip package with the make-duplex-page- sizes-default.sh script disabled and reinstalled with that. The hpcups.drv work fine for duplex printing with A4.duplex selected. I have also tried printing duplex with the PaperSize set to plain A4. This did not crash with the setPageDevice error as was happening before. Loolking at the logs the PageSize being sent to gs was just A4 not Custom.A4 as before. so something was happening differently I will have to revert to the original installation to check that I was running an identical test, but I am fairly certain I am. I not sure what the meaning is of these Custom.XXX pagesizes, or what is setting them. I will have another look at what is happening with cupsUIConstraints stuff over the next few days. But as far as I am concerned removing the script is good to go. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course
Re: [Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just about every rule in the "bug laws". I offer no excuse:-) Comments please. Roger ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: printer-driver-hpcups 3.15.7-0ubuntu4
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
I spelt constraints correctly in the next version and it still does seem to be doing anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just about every rule in the "bug laws". I offer no excuse:-) Comments please. Roger
Re: [Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
On 18/04/16 04:41, Till Kamppeter wrote: > Perhaps we need to remove the script to return to upstream reality with > the original awkwardness (perhaps this could be the SRU for Xenial) and > for a more sophisticated solution pre-build all PPDs, edit them with a > script to rename the paper sizes, and then either compress the PPDs with > pyppd for shipping or look whther CUPS has a tool to reverse-compile > PPDs to a .drv file, to generate the new .drv file this way. > > WDYT? > Hi Till, My gut response is remove the script. However this may bring into play problems with jobs sticking in the queue for no apparent reason that I mentioned in the original bug post. This definitely occurs when printing from applications using gtk+ and is caused by cups not picking up that GS has terminated with an error, in this case "rangecheck in SetPageDevice. This error is only reported in the error_log if debug logging is enabled. I think it would be a good idea to fix this anyway! I have been looking at a solution using cupsUIConstraint and cupsUIResolver to forbid the use of non duplex page sizes when duplex printing is selected and a .duplex page size is available. I have not got it to work yet. The idea is to insert lines like these after each .Duplex CustomMedia found. Attribute cupsUIContraints A4Pagesize "*Duplex *PageSize A4" Attribute cupsUIResolver A4PageSize "*Duplex *PageSize A4.Duplex" Attribute cupsUIContraints A4PageRegion "*Duplex *PageRegion A4" Attribute cupsUIResolver A4PageRegion "*Duplex *PageRegion A4.Duplex" Attribute cupsUIContraints A4ImageableArea "*Duplex *ImageableArea A4" Attribute cupsUIResolver A4ImageableArea "*Duplex *ImageableArea A4.Duplex" Attribute cupsUIContraints A4PaperDimension "*Duplex *PaperDimension A4" Attribute cupsUIResolver A4PaperDimension "*Duplex *PaperDimension A4.Duplex" Comments? Roger -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
Ok. I understand the need for the {0,4} now!
Unfortunately in the 6510 ppd definition in the drv file the .Duplex
defintion is 102 lines further down the file.
I will test with a value to compensate for that. But I still think that
this is just sticking a bandage on a bandage.
I found a note somewhere on the apple site about setting PageSize and
MediaSize constriants which looked interesting (you need to set both). I
wonder if we could set up constraints such that selecting a *Duplex
option needed a .Duplex paper size. At quick glance though this looks
difficult if not impossible.
Roger
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1568996
Title:
Duplex printing does not work properly for HP printers
Status in hplip package in Ubuntu:
Incomplete
Bug description:
I am reporting this as a new bug because I want to avoid adding
further to the mish mash of half fixed bugs that is duplex printing on
hp printers via cups.
I will warn readers that this will sound like a bit of a rant. But
these issues have been outstanding for years
1. Take the hpcups.drv driver information from the upstream part of
the current source package and run it throught the cups ppd compiler
in test mode, anbd filter the output for failures.
roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL
roger@dragon:~/ppd-testing$
Result a nice clean file.
2. Take this file and run it through the script debian/local/make-
duplex-page-sizes-default.sh that is run when this file is installed
on a system. Then repeat the above test.
roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL
--- Other FAILS removed
hp-photosmart_6510_series.ppd: FAIL
**FAIL** Multiple occurrences of option PageRegion choice name Card4x6.
**FAIL** Multiple occurrences of option PageRegion choice name Hagaki.
**FAIL** Multiple occurrences of option PageRegion choice name Card5x8.
**FAIL** Multiple occurrences of option PageRegion choice name Oufuku.
**FAIL** Multiple occurrences of option PageRegion choice name
Executive.
**FAIL** Multiple occurrences of option PageRegion choice name A4.
**FAIL** Multiple occurrences of option PageSize choice name Card4x6.
**FAIL** Multiple occurrences of option PageSize choice name Hagaki.
**FAIL** Multiple occurrences of option PageSize choice name Card5x8.
**FAIL** Multiple occurrences of option PageSize choice name Oufuku.
**FAIL** Multiple occurrences of option PageSize choice name Executive.
**FAIL** Multiple occurrences of option PageSize choice name A4.
--Other FAILS removed
I have removed the many other printer types that fail for clarity. It
is a feature of the cups ppdc compiler that if you do not specify the
-t option it will blithely go on and produce the compiled ppds errors
and all. I personally think that this is a bug and the compiler should
refuse to produce erroneous ppds, but putting that to one side. Taking
A4 as an exmaple the hp6510 ppd file now has two definitions for
PageSize A4.
*PageSize A4/A4 210x297mm: "<>setpagedevice"
and
*PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice"
Same name but different page dimensions. Only the first one will ever
be seen by the cups system.
3. This above often does not matter when printing from the command
line. Because PageSize options are not often specified. However,
taking as an example a gnome desktop application such as Evince
printing a pdf using the gtk+ print options with duplex printing
selected. In this case a PageSize option will be passed to Cups and it
will look like this.
D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper
number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal
ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed-
e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date-
time-at-creation= date-time-at-processing= time-at-creation=1460393994
time-at-processing=1460393994"
So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so
what is passed down for matching is "A4" which matches the first
occurrence of A4. Depending on what other defaults are set in the pdd
it might print something, but it will most likely be clipped. In the
case of the 6510 it results in this.
D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error:
rangecheck in setpagedevice
Of course the above line only appears in the error_log if you have
debugging turned on. So the job just appears to stuck in the print
queue for no reason at all. This is probably another bug.
The work around. This has been mentioned many times in various bug
reports. You need page sizes, page regions, imageable areas, and paper
dimensions with names ending
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
** Attachment added: "Script to replace the original" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4638301/+files/mds-rfj.sh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just about every rule in the "bug laws".
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
The attached script is a work in progress. The CustomMedia stuff is working but the UIConstraints is not. I have tried to make it as simple and clear as posible but I have more work to do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
Well I found one problem in the script. But unfortunately it does not fix the problem. the line duplexsizes=`grep -v '^//' $f | grep CustomMedia | grep '\.Duplex' | cut -d " " -f 4 | cut -d "/" -f 1 | cut -d '"' -f 2 | perl -p -e "s/\.Duplex//" | sort | uniq` does not match all of the CustomMedia .Duplex lines in the file. It misses the ones which do no begin with 3 spaces. Some of these have tabs, a mixture of tabs and spaces, or a different number of spaces. As far as I can see this does not matter as any ones it misses are picked up elsewhere in the file. I only picked this up using my cut down version of the drv file which was small enough not to have alternative findbale lines. I will now retry a the tests I did with the cut down file to see if this has caused me to draw bad conclusions. But I think this needs to fixed anyway for hygienes sake. This appears to work. duplexsizes=`grep -v '^//' $f | grep CustomMedia | grep '\.Duplex' | cut -d '"' -f 2 | cut -d '/' -f 1 | perl -p -e "s/\.Duplex//" | sort | uniq` I don't know if this assumption that all the relevant lines start with 3 spaces affects any of the perl code lower down in the script. I struggle to read perl !!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
"{0,100}?". No change same failures.
"*?" Lots more failures.
Not done any tests with bigger than 100, the request is too open ended!
Is it time to reassess this approach? I suggest we ensure that the DRV
file is correct at package build time and push the required changes
upstream. Running a script at install time to try to correct the file
seems like asking for trouble to me. Is their any way to use
UIConstraints to ensure that any printer that requires special duplex
page sizes does not allow the option to be set without a duplex page
size being selected. I we have to run a script then do it at package
build time and error the build process if this results in an invalid DRV
file.
My procedure for running these tests is as follows.
Starting with the source package installed.
1. Run configure to generate the DRV file from the templates.
2. Copy the generated file to my testing directory.
3. For each test I do.
4. Make another temporary copy of the file I copied from the source.
5. Run ppdc -t tempfile | grep " FAIL" > fails.orig to get a baseline.
6. Run the script or a modified version of the script.
7. Run ppdc -t tempfile | grep " FAIL" >fails.new
This should ensure that I am testing the in the states before and after
the script had modified the file at install time.
The space in front of the FAIL in the grep is to filter out all the individual
fails and leave the ones that just contain the printer model name. It should be
removed to catch all fails.
Cheers,
Roger
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1568996
Title:
Duplex printing does not work properly for HP printers
Status in hplip package in Ubuntu:
Incomplete
Bug description:
I am reporting this as a new bug because I want to avoid adding
further to the mish mash of half fixed bugs that is duplex printing on
hp printers via cups.
I will warn readers that this will sound like a bit of a rant. But
these issues have been outstanding for years
1. Take the hpcups.drv driver information from the upstream part of
the current source package and run it throught the cups ppd compiler
in test mode, anbd filter the output for failures.
roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL
roger@dragon:~/ppd-testing$
Result a nice clean file.
2. Take this file and run it through the script debian/local/make-
duplex-page-sizes-default.sh that is run when this file is installed
on a system. Then repeat the above test.
roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL
--- Other FAILS removed
hp-photosmart_6510_series.ppd: FAIL
**FAIL** Multiple occurrences of option PageRegion choice name Card4x6.
**FAIL** Multiple occurrences of option PageRegion choice name Hagaki.
**FAIL** Multiple occurrences of option PageRegion choice name Card5x8.
**FAIL** Multiple occurrences of option PageRegion choice name Oufuku.
**FAIL** Multiple occurrences of option PageRegion choice name
Executive.
**FAIL** Multiple occurrences of option PageRegion choice name A4.
**FAIL** Multiple occurrences of option PageSize choice name Card4x6.
**FAIL** Multiple occurrences of option PageSize choice name Hagaki.
**FAIL** Multiple occurrences of option PageSize choice name Card5x8.
**FAIL** Multiple occurrences of option PageSize choice name Oufuku.
**FAIL** Multiple occurrences of option PageSize choice name Executive.
**FAIL** Multiple occurrences of option PageSize choice name A4.
--Other FAILS removed
I have removed the many other printer types that fail for clarity. It
is a feature of the cups ppdc compiler that if you do not specify the
-t option it will blithely go on and produce the compiled ppds errors
and all. I personally think that this is a bug and the compiler should
refuse to produce erroneous ppds, but putting that to one side. Taking
A4 as an exmaple the hp6510 ppd file now has two definitions for
PageSize A4.
*PageSize A4/A4 210x297mm: "<>setpagedevice"
and
*PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice"
Same name but different page dimensions. Only the first one will ever
be seen by the cups system.
3. This above often does not matter when printing from the command
line. Because PageSize options are not often specified. However,
taking as an example a gnome desktop application such as Evince
printing a pdf using the gtk+ print options with duplex printing
selected. In this case a PageSize option will be passed to Cups and it
will look like this.
D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper
number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal
ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed-
e47e-3817-4972-b4bfad8ef5d8
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
** Attachment removed: "The cut own version of the original hpcups.drv file" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635423/+files/6510.drv.orig -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just about
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
** Attachment added: "The script form Xenial source (looks unchanged since 2010)" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635428/+files/make-duplex-page-sizes-default.sh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
** Attachment added: "The cut down version after running script" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635424/+files/6510.drv.munged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just about every rule
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
The version on Xenial is hplip-3.16.3+repack0 I have cut out the bits of the Xenial hpcup.drv file that generate the ppds for the 6510 and other Copperhead printers, and used them to run some tests. These show that the make-duplex-page-sizes-default.sh (from Xenial) fails to rename the original A4 definitions to A4.SM for these printers. I have attached before and after version of this cut down file and the script from the Xenial source for anyone to try this for themselves. I even pulled out my O'Reilly Perl book, but I still could not any sense of the script! Roger ** Attachment added: "The cut own version of the original hpcups.drv file" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635423/+files/6510.drv.orig -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
** Attachment added: "The cut own version of the original hpcups.drv file" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635427/+files/6510.drv.orig -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just about every
Re: [Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just about every rule in the "bug laws". I offer no excuse:-) Comments please. Roger ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: printer-driver-hpcups 3.15.7-0ubuntu4
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
Just realised that I still have not got the wording right in the description regarding the workaround. I think a simpler workaround given the current layout of the hpcups.drv file is just to remove the first occurence of each the duplicated pagesize and PageSize and PageRegion lines in the ppd and make sure the second one is picked up by default. I will hold off modifying the description until others have verified this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to
Re: [Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
Hi Till, Just tested with a Xenial live dvdrom. Yes the problem is still there. Looks like the same list of printers. Roger On 12/04/16 17:48, Till Kamppeter wrote: > Can you please test (with a live CD or USB stick) whether the problem > persists in Xenial (Ubuntu 16.04 LTS)? Thanks. > > > ** Changed in: hplip (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: Incomplete Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well. You might make the
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
So... after looking at that debian/local/make-duplex-page-sizes- default.sh again and remembering why I hate perl. I decided that this bug should probably be changed to: The make-duplex-page-sizes-default.sh generates causes bad ppd files to be generated for the following printers. hp-officejet_6800.ppd: FAIL hp-officejet_pro_6830.ppd: FAIL hp-photosmart_5510d_series.ppd: FAIL hp-officejet_pro_6230.ppd: FAIL hp-photosmart_6510_series.ppd: FAIL hp-envy_7640_series.ppd: FAIL hp-officejet_5740_series.ppd: FAIL hp-envy_5640_series.ppd: FAIL hp-envy_5660_series.ppd: FAIL hp-officejet_8040_series.ppd: FAIL hp-officejet_6700.ppd: FAIL hp-officejet_pro_3610.ppd: FAIL hp-photosmart_7520_series.ppd: FAIL hp-officejet_7610_series.ppd: FAIL hp-officejet_7110_series.ppd: FAIL hp-officejet_pro_8500_a909a.ppd: FAIL hp-officejet_pro_8500_a909g.ppd: FAIL hp-officejet_pro_8500_a910.ppd: FAIL hp-photosmart_c309a_series.ppd: FAIL hp-officejet_pro_3620.ppd: FAIL hp-photosmart_7510_series.ppd: FAIL hp-officejet_pro_8500_a909n.ppd: FAIL hp-officejet_6000_e609n.ppd: FAIL hp-deskjet_3540_series.ppd: FAIL hp-photosmart_premium_c309g-m.ppd: FAIL hp-photosmart_prem-web_c309n-s.ppd: FAIL hp-officejet_6500_e709n.ppd: FAIL hp-envy_4500_series.ppd: FAIL hp-photosmart_prem_c310_series.ppd: FAIL hp-officejet_6500_e710n-z.ppd: FAIL hp-deskjet_4510_series.ppd: FAIL hp-officejet_4630_series.ppd: FAIL hp-officejet_pro_8000_a809.ppd: FAIL hp-deskjet_4640_series.ppd: FAIL hp-photosmart_estn_c510_series.ppd: FAIL hp-photosmart_prem_c410_series.ppd: FAIL hp-envy_5530_series.ppd: FAIL hp-laserjet_professional_p1609dn.ppd: FAIL hp-laserjet_professional_p1606dn.ppd: FAIL hp-laserjet_professional_p1607dn.ppd: FAIL hp-laserjet_professional_p1608dn.ppd: FAIL -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: New Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100]
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
I have changed the original bug text slightly. After spending some time grepping the cups and gtk source to find what was adding the .Duplex suffix I realised it was probably coming from my own changes and I had copied the wrong bit of log into the bug. The problem is still that it is the second A4 occurrence that has the correct bounding box for duplex printing and of this is never found. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1568996 Title: Duplex printing does not work properly for HP printers Status in hplip package in Ubuntu: New Bug description: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so what is passed down for matching is "A4" which matches the first occurrence of A4. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped. In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. It is probably best to make these entries default as well.
[Desktop-packages] [Bug 1568996] Re: Duplex printing does not work properly for HP printers
** Description changed: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL - roger@dragon:~/ppd-testing$ + roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL - **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. - **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. - **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. - **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. - **FAIL** Multiple occurrences of option PageRegion choice name Executive. - **FAIL** Multiple occurrences of option PageRegion choice name A4. - **FAIL** Multiple occurrences of option PageSize choice name Card4x6. - **FAIL** Multiple occurrences of option PageSize choice name Hagaki. - **FAIL** Multiple occurrences of option PageSize choice name Card5x8. - **FAIL** Multiple occurrences of option PageSize choice name Oufuku. - **FAIL** Multiple occurrences of option PageSize choice name Executive. - **FAIL** Multiple occurrences of option PageSize choice name A4. + **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. + **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. + **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. + **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. + **FAIL** Multiple occurrences of option PageRegion choice name Executive. + **FAIL** Multiple occurrences of option PageRegion choice name A4. + **FAIL** Multiple occurrences of option PageSize choice name Card4x6. + **FAIL** Multiple occurrences of option PageSize choice name Hagaki. + **FAIL** Multiple occurrences of option PageSize choice name Card5x8. + **FAIL** Multiple occurrences of option PageSize choice name Oufuku. + **FAIL** Multiple occurrences of option PageSize choice name Executive. + **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper - number-up=1 MediaType=Plain PageSize=Custom.A4.Duplex OutputMode=Normal + number-up=1 MediaType=Plain PageSize=Custom.A4 OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" - So the PageSize is "Custom.A4.Duplex". The "Custom" bit gets stripped - off so what is passed down for matching is "A4.Duplex" which in our 6510 - example does not match anything in the ppd. Depending on what other - defaults are set in the pdd it might print something, but it will most - likely be clipped (source of numerous duplex margins bugs). In the case + So the PageSize is "Custom.A4". The "Custom" bit gets stripped off so + what is passed down for matching is "A4" which matches the first + occurrence of A4. Depending on what other defaults are set in the pdd it
[Desktop-packages] [Bug 1568996] [NEW] Duplex printing does not work properly for HP printers
Public bug reported: I am reporting this as a new bug because I want to avoid adding further to the mish mash of half fixed bugs that is duplex printing on hp printers via cups. I will warn readers that this will sound like a bit of a rant. But these issues have been outstanding for years 1. Take the hpcups.drv driver information from the upstream part of the current source package and run it throught the cups ppd compiler in test mode, anbd filter the output for failures. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.upstream | grep FAIL roger@dragon:~/ppd-testing$ Result a nice clean file. 2. Take this file and run it through the script debian/local/make- duplex-page-sizes-default.sh that is run when this file is installed on a system. Then repeat the above test. roger@dragon:~/ppd-testing$ ppdc -t hpcups.drv.munged | grep FAIL --- Other FAILS removed hp-photosmart_6510_series.ppd: FAIL **FAIL** Multiple occurrences of option PageRegion choice name Card4x6. **FAIL** Multiple occurrences of option PageRegion choice name Hagaki. **FAIL** Multiple occurrences of option PageRegion choice name Card5x8. **FAIL** Multiple occurrences of option PageRegion choice name Oufuku. **FAIL** Multiple occurrences of option PageRegion choice name Executive. **FAIL** Multiple occurrences of option PageRegion choice name A4. **FAIL** Multiple occurrences of option PageSize choice name Card4x6. **FAIL** Multiple occurrences of option PageSize choice name Hagaki. **FAIL** Multiple occurrences of option PageSize choice name Card5x8. **FAIL** Multiple occurrences of option PageSize choice name Oufuku. **FAIL** Multiple occurrences of option PageSize choice name Executive. **FAIL** Multiple occurrences of option PageSize choice name A4. --Other FAILS removed I have removed the many other printer types that fail for clarity. It is a feature of the cups ppdc compiler that if you do not specify the -t option it will blithely go on and produce the compiled ppds errors and all. I personally think that this is a bug and the compiler should refuse to produce erroneous ppds, but putting that to one side. Taking A4 as an exmaple the hp6510 ppd file now has two definitions for PageSize A4. *PageSize A4/A4 210x297mm: "<>setpagedevice" and *PageSize A4/A4 AutoDuplex 210x297mm: "<>setpagedevice" Same name but different page dimensions. Only the first one will ever be seen by the cups system. 3. This above often does not matter when printing from the command line. Because PageSize options are not often specified. However, taking as an example a gnome desktop application such as Evince printing a pdf using the gtk+ print options with duplex printing selected. In this case a PageSize option will be passed to Cups and it will look like this. D [11/Apr/2016:17:59:54 +0100] [Job 288] argv[5]="InputSlot=Upper number-up=1 MediaType=Plain PageSize=Custom.A4.Duplex OutputMode=Normal ColorModel=KGray Duplex=DuplexNoTumble job-uuid=urn:uuid:4ef4d5ed- e47e-3817-4972-b4bfad8ef5d8 job-originating-host-name=localhost date- time-at-creation= date-time-at-processing= time-at-creation=1460393994 time-at-processing=1460393994" So the PageSize is "Custom.A4.Duplex". The "Custom" bit gets stripped off so what is passed down for matching is "A4.Duplex" which in our 6510 example does not match anything in the ppd. Depending on what other defaults are set in the pdd it might print something, but it will most likely be clipped (source of numerous duplex margins bugs). In the case of the 6510 it results in this. D [11/Apr/2016:17:59:55 +0100] [Job 288] Unrecoverable error: rangecheck in setpagedevice Of course the above line only appears in the error_log if you have debugging turned on. So the job just appears to stuck in the print queue for no reason at all. This is probably another bug. The work around. This has been mentioned many times in various bug reports. You need page sizes, page regions, imageable areas, and paper dimensions with names ending in .Duplex in your ppd. Rename the duplicate which has the biggest bottom margin, hopefully this is the one with AutoDuplex in the descriptive text. You might make the corresponding changes in the drv file if you wish. That will save you having to reapply them every time the ppd file is regenerated. I realise that I have broken just about every rule in the "bug laws". I offer no excuse:-) Comments please. Roger ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: printer-driver-hpcups 3.15.7-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 18:10:41 2016 InstallationDate: Installed on 2014-05-04 (707 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lpstat: device for HP-Photosmart-6510-series:
[Desktop-packages] [Bug 1532431] Re: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces
Attached a NetworkManager log showing what happens when the interface is deleted. ** Attachment added: "Network Manager log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+attachment/4547334/+files/test.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1532431 Title: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces Status in network-manager package in Ubuntu: New Bug description: If a virtual 802.11 interface of type monitor is created on a 802.11 physical interface that already has a virtual interface of type managed created on it, then the managed interface is deleted. NetworkManager sets the type of the monitor interface to managed. This can be illustrated by the following commands. All the interface names have been listed in /etc/network/interfaces as follows so NetworkManager should not be managing them in any way. # Disable network manager on interface names I want to use for monitoring # related purposes iface eth1 inet manual iface BigTenda inet manual iface LittleBelkin inet manual iface LittleTenda inet manual iface Sinmax inet manual iface mon0 inet manual iface phy0.mon manual iface phy1.mon manual iface phy2.mon manual iface phy3.mon manual iface phy4.mon manual iface phy5.mon manual iface phy6.mon manual iface phy7.mon manual iface phy8.mon manual iface phy9.mon manual root@dragon:/home/roger# systemctl start NetworkManager root@dragon:/home/roger# iw dev phy#3 Interface Sinmax ifindex 11 wdev 0x30001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor flags otherbss root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type monitor Interface Sinmax ifindex 11 wdev 0x30001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw dev Sinmax del root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# systemctl stop NetworkManager root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds root@dragon:/home/roger# iw dev phy#4 Interface Sinmax ifindex 13 wdev 0x40001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor flags otherbss root@dragon:/home/roger# iw dev phy#4 Interface phy2.mon ifindex 14 wdev 0x40002 addr 00:0f:11:92:06:b2 type monitor Interface Sinmax ifindex 13 wdev 0x40001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw dev Sinmax del root@dragon:/home/roger# iw dev phy#4 Interface phy2.mon ifindex 14 wdev 0x40002 addr 00:0f:11:92:06:b2 type monitor This stops any running or future network traces on this interface working. This is another example of network manager interfering with interfaces it is not supposed to be managing. See bug #1314848 which is still unresolved. The above test was carried out on Ubuntu 15.10 network-manager: Installed: 1.0.4-0ubuntu5.2 Candidate: 1.0.4-0ubuntu5.2 Version table: *** 1.0.4-0ubuntu5.2 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu5 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+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 1532431] [NEW] NetworkManager interferes with unmanaged 802.11 monitor mode interfaces
Public bug reported: If a virtual 802.11 interface of type monitor is created on a 802.11 physical interface that already has a virtual interface of type managed created on it, then the managed interface is deleted. NetworkManager sets the type of the monitor interface to managed. This can be illustrated by the following commands. All the interface names have been listed in /etc/network/interfaces as follows so NetworkManager should not be managing them in any way. # Disable network manager on interface names I want to use for monitoring # related purposes iface eth1 inet manual iface BigTenda inet manual iface LittleBelkin inet manual iface LittleTenda inet manual iface Sinmax inet manual iface mon0 inet manual iface phy0.mon manual iface phy1.mon manual iface phy2.mon manual iface phy3.mon manual iface phy4.mon manual iface phy5.mon manual iface phy6.mon manual iface phy7.mon manual iface phy8.mon manual iface phy9.mon manual root@dragon:/home/roger# systemctl start NetworkManager root@dragon:/home/roger# iw dev phy#3 Interface Sinmax ifindex 11 wdev 0x30001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor flags otherbss root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type monitor Interface Sinmax ifindex 11 wdev 0x30001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw dev Sinmax del root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# systemctl stop NetworkManager root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds root@dragon:/home/roger# iw dev phy#4 Interface Sinmax ifindex 13 wdev 0x40001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor flags otherbss root@dragon:/home/roger# iw dev phy#4 Interface phy2.mon ifindex 14 wdev 0x40002 addr 00:0f:11:92:06:b2 type monitor Interface Sinmax ifindex 13 wdev 0x40001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw dev Sinmax del root@dragon:/home/roger# iw dev phy#4 Interface phy2.mon ifindex 14 wdev 0x40002 addr 00:0f:11:92:06:b2 type monitor This stops any running or future network traces on this interface working. This is another example of network manager interfering with interfaces it is not supposed to be managing. See bug #1314848 which is still unresolved. The above test was carried out on Ubuntu 15.10 network-manager: Installed: 1.0.4-0ubuntu5.2 Candidate: 1.0.4-0ubuntu5.2 Version table: *** 1.0.4-0ubuntu5.2 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu5 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: iw mac80211 monitor networkmanager wifi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1532431 Title: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces Status in network-manager package in Ubuntu: New Bug description: If a virtual 802.11 interface of type monitor is created on a 802.11 physical interface that already has a virtual interface of type managed created on it, then the managed interface is deleted. NetworkManager sets the type of the monitor interface to managed. This can be illustrated by the following commands. All the interface names have been listed in /etc/network/interfaces as follows so NetworkManager should not be managing them in any way. # Disable network manager on interface names I want to use for monitoring # related purposes iface eth1 inet manual iface BigTenda inet manual iface LittleBelkin inet manual iface LittleTenda inet manual iface Sinmax inet manual iface mon0 inet manual iface phy0.mon manual iface phy1.mon manual iface phy2.mon manual iface phy3.mon manual iface phy4.mon manual iface phy5.mon manual
[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device
Just a quick comment. I know this was mentioned before (#46) but it would be a good idea if everyone checked this behaviour with phone in both locked and unlocked states _before_ it is plugged into the USB. -- 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/1314556 Title: Unable to mount Android MTP device Status in gvfs package in Ubuntu: Confirmed Bug description: I have the same problem on 3 computers with 14.04: So I tried, mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): Resource temporarily unavailable outep: usb_get_endpoint_status(): Device or resource busy ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 11:18:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor InstallationDate: Installed on 2013-02-12 (441 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+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 1453479] Re: Unable to mount Android Phone since upgrade from 14.10 to 15.04
Jon, Do you have a screen lock (pin etc.) active on your phone? If so do you see any difference in behaviour between connecting your phone when it is unlocked and connecting it when it is locked? Roger -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1453479 Title: Unable to mount Android Phone since upgrade from 14.10 to 15.04 Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10 on my Dell Inspiron 14R I was able to mount my HTC One M7 (Android 5.0.2) out-of-the-box. I could browse the phone's content via Nautilus as if it were a flash drive. Now, since upgrading to Ubuntu 15.04, I am not able to mount the phone. When I plug it in via USB, I receive a pop-up window saying "Unable to mount Android Phone" (see attached screenshot). Nautilus will open and will display "Android Phone" in the navigation panel, but it does not display any content on the phone. I also tried creating a live DVD of 15.04 and launched Ubuntu that way. I was still unable to mount my Android phone. Nothing on the phone changed since I was able to mount it on 14.10, and USB Debugging is enabled. Please let me know if there are any logs or other information that will be useful in investigating this. I am submitting this as a bug because it was working in 14.10 but is no longer working in 15.04. -Jon ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-settings-daemon 15.04.1+15.04.20150408-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 9 21:24:18 2015 ExecutablePath: /usr/lib/unity-settings-daemon/unity-fallback-mount-helper InstallationDate: Installed on 2013-04-28 (741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to vivid on 2015-04-25 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1453479/+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 1314556] Re: Unable to mount Android MTP device
Same problem on 15.04 with an HTC Desire 820. Unable to mount android phone message and then an empty nautilus browser window. Is this something to do with the transient usb mass storage device that phones with this chipset reports on the usb bus for a while after first connection. This is formatted as a windows file system and contains a windows installer for the phone. -- 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/1314556 Title: Unable to mount Android MTP device Status in gvfs package in Ubuntu: Confirmed Bug description: I have the same problem on 3 computers with 14.04: So I tried, mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): Resource temporarily unavailable outep: usb_get_endpoint_status(): Device or resource busy ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 11:18:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor InstallationDate: Installed on 2013-02-12 (441 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+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 1453479] Re: Unable to mount Android Phone since upgrade from 14.10 to 15.04
I am also seeing this problem with my HTC Desire 820. I think this is a duplicate of #1314556 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1453479 Title: Unable to mount Android Phone since upgrade from 14.10 to 15.04 Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10 on my Dell Inspiron 14R I was able to mount my HTC One M7 (Android 5.0.2) out-of-the-box. I could browse the phone's content via Nautilus as if it were a flash drive. Now, since upgrading to Ubuntu 15.04, I am not able to mount the phone. When I plug it in via USB, I receive a pop-up window saying "Unable to mount Android Phone" (see attached screenshot). Nautilus will open and will display "Android Phone" in the navigation panel, but it does not display any content on the phone. I also tried creating a live DVD of 15.04 and launched Ubuntu that way. I was still unable to mount my Android phone. Nothing on the phone changed since I was able to mount it on 14.10, and USB Debugging is enabled. Please let me know if there are any logs or other information that will be useful in investigating this. I am submitting this as a bug because it was working in 14.10 but is no longer working in 15.04. -Jon ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-settings-daemon 15.04.1+15.04.20150408-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 9 21:24:18 2015 ExecutablePath: /usr/lib/unity-settings-daemon/unity-fallback-mount-helper InstallationDate: Installed on 2013-04-28 (741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to vivid on 2015-04-25 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1453479/+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 1422007] Re: Photosmart_6510.ppd A4.Duplex PageSize shifts Postscript userspace 3mm up page
** Changed in: hplip (Ubuntu) Status: New = Incomplete ** Changed in: hplip (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1422007 Title: Photosmart_6510.ppd A4.Duplex PageSize shifts Postscript userspace 3mm up page Status in hplip package in Ubuntu: Invalid Bug description: The default hpcups driver ppd for HP Photosmart 6510 printers when used with the A4.Duplex PageSize (or any other related PageSize) shifts the Postscript userspace coordinate system 3mm up the page on all pages of single sided prints and on odd numbered pages of duplex prints. Even numbered pages of duplex prints are correctly positioned on the paper. This can be seen by printing that attached test file a4test.pdf using lpr on an HP 6510 printer and probably on other similar printers using the same basic driver and ppd layout. lpr -P Photosmart_6510 -o PageSize=A4.Duplex -o Duplex=None a4test.pdf and lpr -P Photosmart_6510 -o PageSize=A4.Duplex -o Duplex=DuplexNoTumble a4test.pdf This is making it very difficult to diagnose/resolve the other (possibly gtk related) clipping problems when duplex printing using this driver. Ubuntu 14.04 printer-driver-hpcups 3.14.3-0ubuntu3.2 hplip 3.14.3-0ubuntu3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1422007/+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 1422007] Re: Photosmart_6510.ppd A4.Duplex PageSize shifts Postscript userspace 3mm up page
I have closed this as invalid while I do more work investigating. Using the latest version of hplip improves things. Then only a very small amount is clipped off the bottom. This may be a local printer hardware related problem. However the main reason I raised this bug was to clean away some of the uncertainity in investigating duplex printing related problems with gui applications such as Evince and Adobe reader. Both of these do not shrink pages properly when asked to in the print options, but the clipping is different in each case. Setting LogLevel debug in cupsd.conf shows that the fit-to-page option is not being passed on to the filters in these cases. For information more detailed logging can be enabled by setting hpLogLevel 1 in cupsd.conf this logging is directed to the systen logging daemon (rsyslogd in later ubuntu versions). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1422007 Title: Photosmart_6510.ppd A4.Duplex PageSize shifts Postscript userspace 3mm up page Status in hplip package in Ubuntu: Invalid Bug description: The default hpcups driver ppd for HP Photosmart 6510 printers when used with the A4.Duplex PageSize (or any other related PageSize) shifts the Postscript userspace coordinate system 3mm up the page on all pages of single sided prints and on odd numbered pages of duplex prints. Even numbered pages of duplex prints are correctly positioned on the paper. This can be seen by printing that attached test file a4test.pdf using lpr on an HP 6510 printer and probably on other similar printers using the same basic driver and ppd layout. lpr -P Photosmart_6510 -o PageSize=A4.Duplex -o Duplex=None a4test.pdf and lpr -P Photosmart_6510 -o PageSize=A4.Duplex -o Duplex=DuplexNoTumble a4test.pdf This is making it very difficult to diagnose/resolve the other (possibly gtk related) clipping problems when duplex printing using this driver. Ubuntu 14.04 printer-driver-hpcups 3.14.3-0ubuntu3.2 hplip 3.14.3-0ubuntu3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1422007/+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 1422007] [NEW] Photosmart_6510.ppd A4.Duplex PageSize shifts Postscript userspace 3mm up page
Public bug reported: The default hpcups driver ppd for HP Photosmart 6510 printers when used with the A4.Duplex PageSize (or any other related PageSize) shifts the Postscript userspace coordinate system 3mm up the page on all pages of single sided prints and on odd numbered pages of duplex prints. Even numbered pages of duplex prints are correctly positioned on the paper. This can be seen by printing that attached test file a4test.pdf using lpr on an HP 6510 printer and probably on other similar printers using the same basic driver and ppd layout. lpr -P Photosmart_6510 -o PageSize=A4.Duplex -o Duplex=None a4test.pdf and lpr -P Photosmart_6510 -o PageSize=A4.Duplex -o Duplex=DuplexNoTumble a4test.pdf This is making it very difficult to diagnose/resolve the other (possibly gtk related) clipping problems when duplex printing using this driver. Ubuntu 14.04 printer-driver-hpcups 3.14.3-0ubuntu3.2 hplip 3.14.3-0ubuntu3.2 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: duplex hpcups hplip margins ** Attachment added: 2 page vector graphic a4 margin test print https://bugs.launchpad.net/bugs/1422007/+attachment/4319465/+files/a4test.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1422007 Title: Photosmart_6510.ppd A4.Duplex PageSize shifts Postscript userspace 3mm up page Status in hplip package in Ubuntu: New Bug description: The default hpcups driver ppd for HP Photosmart 6510 printers when used with the A4.Duplex PageSize (or any other related PageSize) shifts the Postscript userspace coordinate system 3mm up the page on all pages of single sided prints and on odd numbered pages of duplex prints. Even numbered pages of duplex prints are correctly positioned on the paper. This can be seen by printing that attached test file a4test.pdf using lpr on an HP 6510 printer and probably on other similar printers using the same basic driver and ppd layout. lpr -P Photosmart_6510 -o PageSize=A4.Duplex -o Duplex=None a4test.pdf and lpr -P Photosmart_6510 -o PageSize=A4.Duplex -o Duplex=DuplexNoTumble a4test.pdf This is making it very difficult to diagnose/resolve the other (possibly gtk related) clipping problems when duplex printing using this driver. Ubuntu 14.04 printer-driver-hpcups 3.14.3-0ubuntu3.2 hplip 3.14.3-0ubuntu3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1422007/+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 405116] Re: hpcups driver of HPLIP has broken margins
Aarrg. Even hpijs is broken now as well. But it is broken in exactly the same way. Does it mean the problem is somewhere upstream from cups? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/405116 Title: hpcups driver of HPLIP has broken margins Status in HP Linux Imaging and Printing: Fix Released Status in cups package in Ubuntu: Fix Released Status in hplip package in Ubuntu: Fix Released Status in hplip package in Debian: Fix Released Bug description: Binary package hint: hplip Hi. I have an HP DeskJet D2600 connected via USB. When I turned the printer on, a default configuration named Deskjet-D2600-series (using the HP Deskjet d2600 Series [en] driver) was generated that I can see in the gnome printer configuration window. When I print a test page the contents has a big margin at the top and the bottom is cut off. In the printer configuration if I change the driver to HP Deksjet d2600 Series hpijs [en] or HP Deksjet d2600 Series hpijs 3.9.6b.4 [en] the margin problem is corrected, but now black contents is printed in what looks like a combination of colors that appears black but looks more like dark brown. What I'm hoping for is that the margins for the default driver are corrected. I can provide any information that might be needed. Thanks. ProblemType: Bug Architecture: amd64 Date: Sun Jul 26 23:03:14 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Deskjet-D2600-series: hp:/usb/Deskjet_D2600_series?serial=TH94M140BG05C9 Package: hpijs-ppds 3.9.6b-1ubuntu4 PackageArchitecture: all Papersize: letter PpdFiles: Deskjet-D2600-series: HP Deskjet d2600 Series, hpcups 3.9.6b ProcCmdLine: root=UUID=06e1c48d-56bd-443b-8324-1975f908d414 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-4.22-generic SourcePackage: hplip Uname: Linux 2.6.31-4-generic x86_64 dmi.bios.date: 05/17/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: AV8 (VIA K8T800P-8237) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/17/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAV8(VIAK8T800P-8237):rvr1.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/405116/+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 405116] Re: hpcups driver of HPLIP has broken margins
Can someone please reopen this bug! I have just tried the test file I attached 18 months ago again. The margins are even more broken now! Printing the test with shrink to fit enabled shows a 15mm clip at the top and bottom and 4mm each side in both single sided and duplex modes on A4. This driver has been broken for 6 years now Or at least someone tell me what is wrong with my test :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/405116 Title: hpcups driver of HPLIP has broken margins Status in HP Linux Imaging and Printing: Fix Released Status in cups package in Ubuntu: Fix Released Status in hplip package in Ubuntu: Fix Released Status in hplip package in Debian: Fix Released Bug description: Binary package hint: hplip Hi. I have an HP DeskJet D2600 connected via USB. When I turned the printer on, a default configuration named Deskjet-D2600-series (using the HP Deskjet d2600 Series [en] driver) was generated that I can see in the gnome printer configuration window. When I print a test page the contents has a big margin at the top and the bottom is cut off. In the printer configuration if I change the driver to HP Deksjet d2600 Series hpijs [en] or HP Deksjet d2600 Series hpijs 3.9.6b.4 [en] the margin problem is corrected, but now black contents is printed in what looks like a combination of colors that appears black but looks more like dark brown. What I'm hoping for is that the margins for the default driver are corrected. I can provide any information that might be needed. Thanks. ProblemType: Bug Architecture: amd64 Date: Sun Jul 26 23:03:14 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Deskjet-D2600-series: hp:/usb/Deskjet_D2600_series?serial=TH94M140BG05C9 Package: hpijs-ppds 3.9.6b-1ubuntu4 PackageArchitecture: all Papersize: letter PpdFiles: Deskjet-D2600-series: HP Deskjet d2600 Series, hpcups 3.9.6b ProcCmdLine: root=UUID=06e1c48d-56bd-443b-8324-1975f908d414 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-4.22-generic SourcePackage: hplip Uname: Linux 2.6.31-4-generic x86_64 dmi.bios.date: 05/17/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: AV8 (VIA K8T800P-8237) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/17/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAV8(VIAK8T800P-8237):rvr1.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/405116/+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 1314848] Re: not possible to create connection with no IP addresses
This bug also affects me. I just want an interface that nothing is sent out on and with no addresses, for my switch's monitor port. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1314848 Title: not possible to create connection with no IP addresses Status in “network-manager” package in Ubuntu: Confirmed Bug description: It does not seem to be possible to create network connections with no IP addresses., for example for passive monitoring of existing link. To reproduce: (1) In nm-connection-editor, create a new connection of type 'Ethernet'. (2) In IPv4 settings, set Method to Disabled (3) In IPv6 settings, set Method to Ignore. (4) Hit Save (5) Click on newly-created connection and hit Edit. Look at the IPv6 tab What I expected to happen: The Method is set to Ignore. What happened instead: The Method is set to Automatic. Follow up: (6) set Method to Ignore (7) Hit Save. Observe error message: The property 'NMSettingIP6Config' / 'method' is invalid: 1 (8) Try to repeat same operation with kde-nm-connection-editor. This editor will silently ignore any errors which disable both connections. Other info: $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu7 Candidate: 0.9.8.8-0ubuntu7 Version table: *** 0.9.8.8-0ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1314848/+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 860680] Re: systray.py crashed with SIGSEGV
For a more comprehensive fix that catches all the cases where warning
are generated when the global intrepreter lock has been released and
_PyThreadState_Current set to NULL, you can try the following patch to
pygobject-2.
--- pygobject-2-2.28.6.orig/gobject/gobjectmodule.c
+++ pygobject-2-2.28.6/gobject/gobjectmodule.c
@@ -2307,7 +2307,7 @@ _log_func(const gchar *log_domain,
const gchar *message,
gpointer user_data)
{
-if (G_LIKELY(Py_IsInitialized()))
+if (G_LIKELY(Py_IsInitialized()) (NULL != _PyThreadState_Current))
{
PyGILState_STATE state;
PyObject* warning = user_data;
This seems a bit like wallpapering over the cracks, but it was the
simplest fix I could come up with.
Roger
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject-2 in Ubuntu.
https://bugs.launchpad.net/bugs/860680
Title:
systray.py crashed with SIGSEGV
Status in HP Linux Imaging and Printing:
Invalid
Status in “hplip” package in Ubuntu:
Invalid
Status in “pango” package in Ubuntu:
New
Status in “pygobject-2” package in Ubuntu:
New
Status in “python-defaults” package in Ubuntu:
New
Bug description:
system reboot and after loading the desktop the error happened.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: hplip-data 3.11.7-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 27 11:33:43 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/hplip/systray.py
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110922)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for Officejet6500: hp:/net/Officejet_6500_E709n?ip=10.80.0.11
MachineType: Dell Inc. Inspiron N7010
PackageArchitecture: all
Papersize: letter
PpdFiles: Officejet6500: HP Officejet 6500 e709n hpijs, 3.11.7
ProcCmdline: python /usr/bin/hp-systray
ProcCwd: /home/rbrown
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic
root=UUID=e545f842-1c5b-4880-b81d-75cfaeef4f0c ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x49c60b: mov0x10(%rax),%rdi
PC (0x0049c60b) ok
source 0x10(%rax) (0x0010) not located in a known VMA region (needed
readable region)!
destination %rdi ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
Title: systray.py crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/20/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 08VFX1
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A09
dmi.modalias:
dmi:bvnDellInc.:bvrA09:bd10/20/2010:svnDellInc.:pnInspironN7010:pvrA09:rvnDellInc.:rn08VFX1:rvrA09:cvnDellInc.:ct8:cvrA09:
dmi.product.name: Inspiron N7010
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/860680/+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 860680] Re: systray.py crashed with SIGSEGV
I switched to trying to resolve my case of the bug by fixing the cause of the warning. In my case this is a warning from pango that it could not find a loadable module. /usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory' The directory /usr/lib/i386-linux-gnu/pango does not even exist on my installation. However in /etc/pango/pango.modules there is a long list of modules supposedly in that directory including an entry for pango- basic-fc.so. I found some comments on the web that pango-basic-fc.so is now statically linked in recent revisions of pango. So I just renamed the pango.modules file to pango.modules.old. Everything now works fine. This would seem to prove that this is a bug in the python infrastructure. It is definitely not a bug in hplip. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/860680 Title: systray.py crashed with SIGSEGV Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Confirmed Status in “pygobject-2” package in Ubuntu: New Status in “python-defaults” package in Ubuntu: New Bug description: system reboot and after loading the desktop the error happened. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: hplip-data 3.11.7-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 27 11:33:43 2011 EcryptfsInUse: Yes ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110922) InterpreterPath: /usr/bin/python2.7 Lpstat: device for Officejet6500: hp:/net/Officejet_6500_E709n?ip=10.80.0.11 MachineType: Dell Inc. Inspiron N7010 PackageArchitecture: all Papersize: letter PpdFiles: Officejet6500: HP Officejet 6500 e709n hpijs, 3.11.7 ProcCmdline: python /usr/bin/hp-systray ProcCwd: /home/rbrown ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=e545f842-1c5b-4880-b81d-75cfaeef4f0c ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x49c60b: mov0x10(%rax),%rdi PC (0x0049c60b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 10/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd10/20/2010:svnDellInc.:pnInspironN7010:pvrA09:rvnDellInc.:rn08VFX1:rvrA09:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron N7010 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/860680/+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 860680] Re: systray.py crashed with SIGSEGV
Here is a slighlty more informative gdb run with the python-qt4 debug symbols loaded. You can see from this that the crash occurs because the qt4 sip code calls Py_BEGIN_ALLOW_THREADS This sets _PyThreadState_Current to NULL, and then sipCpp = new sipQApplication(nargc, argv); Somewhere in the setup of this object a call to the Python warning mechansim occurs with the trhead state still NULL. (gdb) ignore 1 1149 Will ignore next 1149 crossings of breakpoint 1. (gdb) run Starting program: /usr/bin/python /usr/bin/hp-systray -g -x [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. HP Linux Imaging and Printing System (ver. 3.14.3) System Tray Status Service ver. 2.0 Copyright (c) 2001-13 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. hp-systray[3194]: debug: Locking: /home/roger/.hplip/hp-systray.lock hp-systray[3194]: debug: Creating pipe: hpssd (5) == systemtray (4) hp-systray[3194]: debug: Creating pipe: hpssd (6) == hpdio (4) hp-systray[3194]: debug: Creating pipe: hpdio (8) == hpssd (7) hp-systray(hpdio)[3196]: debug: PID=3196 hp-systray(hpssd)[3195]: debug: PID=3195 hp-systray(hpssd)[3195]: debug: Entering main dbus loop... [New Thread 0xb40a9b40 (LWP 3197)] [New Thread 0xb36ffb40 (LWP 3198)] /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) hp-systray(qt4)[3194]: debug: PID=3194 hp-systray(qt4)[3194]: debug: Go to here 1! Hardware watchpoint 1: _PyThreadState_Current Old value = (PyThreadState *) 0x835d050 New value = (PyThreadState *) 0x0 PyEval_SaveThread () at ../Python/ceval.c:340 340 if (tstate == NULL) (gdb) finish Run till exit from #0 PyEval_SaveThread () at ../Python/ceval.c:340 init_type_QApplication (sipSelf=0xb7a664f4, sipArgs= (['/usr/bin/hp-systray', '-g', '-x'],), sipKwds=0x0, sipUnused=0xbfffe880, sipParseErr=0xbfffe88c) at /build/buildd/python-qt4-4.10.4+dfsg/sip/QtGui/qapplication.sip:886 886 sipCpp = new sipQApplication(nargc, argv); Value returned is $2 = (PyThreadState *) 0x835d050 (gdb) next 885 Py_BEGIN_ALLOW_THREADS (gdb) next 886 sipCpp = new sipQApplication(nargc, argv); (gdb) next Program received signal SIGSEGV, Segmentation fault. do_warn.29441 ( message=message@entry='/usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory', category=category@entry=type at remote 0xb43a878c, stack_level=stack_level@entry=1) at ../Python/_warnings.c:594 594 if (!setup_context(stack_level, filename, lineno, module, registry)) (gdb) bt #0 do_warn.29441 ( message=message@entry='/usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory', category=category@entry=type at remote 0xb43a878c, stack_level=stack_level@entry=1) at ../Python/_warnings.c:594 #1 0x081f34cf in PyErr_WarnEx (category=type at remote 0xb43a878c, text=0x8726768 /usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory, stack_level=1) at ../Python/_warnings.c:720 #2 0xb4e5aaec in ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so #3 0xb67152f7 in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6715523 in g_log () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb45637d6 in ?? () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 #6 0xb535fdfe in g_type_module_use () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #7 0xb456389b in ?? () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 #8 0xb4563967 in ?? () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 #9 0xb4567e8c in ?? () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 #10 0xb456818c in ?? () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 #11 0xb45691f7 in pango_itemize_with_base_dir () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 #12 0xb4570d5f in ?? () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 ---Type return to continue, or q return to quit--- #13 0xb4572116 in pango_layout_get_unknown_glyphs_count () from /usr/lib/i386-linux-gnu/libpango-1.0.so.0 #14 0xb481c130 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 #15 0xb481fc03 in ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 #16 0xb535cb43 in g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #17 0xb533f8fe in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #18 0xb53418f1 in g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #19 0xb5342010 in g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #20 0xb48219f4 in gtk_entry_new () from
[Desktop-packages] [Bug 860680] Re: systray.py crashed with SIGSEGV
I suspect that this is happening because python has hooked itself if into the GTK logging system. So it looks like _PyErr_WarnEx should really check whether _PyThreadState_Current is non NULL before proceding. This rreally looks like a horrible can of worms. Can the python guys please look at this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject-2 in Ubuntu. https://bugs.launchpad.net/bugs/860680 Title: systray.py crashed with SIGSEGV Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Confirmed Status in “pygobject-2” package in Ubuntu: New Status in “python-defaults” package in Ubuntu: New Bug description: system reboot and after loading the desktop the error happened. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: hplip-data 3.11.7-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 27 11:33:43 2011 EcryptfsInUse: Yes ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110922) InterpreterPath: /usr/bin/python2.7 Lpstat: device for Officejet6500: hp:/net/Officejet_6500_E709n?ip=10.80.0.11 MachineType: Dell Inc. Inspiron N7010 PackageArchitecture: all Papersize: letter PpdFiles: Officejet6500: HP Officejet 6500 e709n hpijs, 3.11.7 ProcCmdline: python /usr/bin/hp-systray ProcCwd: /home/rbrown ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=e545f842-1c5b-4880-b81d-75cfaeef4f0c ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x49c60b: mov0x10(%rax),%rdi PC (0x0049c60b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 10/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd10/20/2010:svnDellInc.:pnInspironN7010:pvrA09:rvnDellInc.:rn08VFX1:rvrA09:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron N7010 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/860680/+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 860680] Re: systray.py crashed with SIGSEGV
I had a quick try with python-dbg but got some error messages very early one in the initialisation process. I have not looked into them any further. However I have no do a run with a hardware break point on _PyThreadState_Current. This show that it is the /usr/lib/python2.7 /dist-packages/PyQt4/QtGui.so module that is causing the problem by calling PyEval_SaveThread () just before the crash. This has the affect of setting the current thread state to NULL. So this no looks like it could be a problem with the Qt4 support in Python not handling multithreading correctly. I think this is a far as I can go diagnosing this. I was hoping I could find some way of hacking a work around into hp-systray but this seems unlikely. (gdb) ignore 1 1147 Will ignore next 1147 crossings of breakpoint 1. (gdb) run Starting program: /usr/bin/python /usr/bin/hp-systray -g -x [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. HP Linux Imaging and Printing System (ver. 3.14.3) System Tray Status Service ver. 2.0 Copyright (c) 2001-13 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. hp-systray[3456]: debug: Locking: /home/roger/.hplip/hp-systray.lock hp-systray[3456]: debug: Creating pipe: hpssd (5) == systemtray (4) hp-systray[3456]: debug: Creating pipe: hpssd (6) == hpdio (4) hp-systray[3456]: debug: Creating pipe: hpdio (8) == hpssd (7) hp-systray(hpdio)[3458]: debug: PID=3458 hp-systray(hpssd)[3457]: debug: PID=3457 hp-systray(hpssd)[3457]: debug: Entering main dbus loop... [New Thread 0xb40a9b40 (LWP 3459)] [New Thread 0xb36ffb40 (LWP 3460)] /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) hp-systray(qt4)[3456]: debug: PID=3456 hp-systray(qt4)[3456]: debug: Go to here 1! Hardware watchpoint 1: _PyThreadState_Current Old value = (PyThreadState *) 0x835d050 New value = (PyThreadState *) 0x0 PyEval_SaveThread () at ../Python/ceval.c:340 340 if (tstate == NULL) (gdb) bt #0 PyEval_SaveThread () at ../Python/ceval.c:340 #1 0xb6413d58 in ?? () from /usr/lib/python2.7/dist-packages/PyQt4/QtGui.so #2 0xb723fd86 in ?? () from /usr/lib/python2.7/dist-packages/sip.so #3 0x08144c11 in wrap_init.25210 (self=SystemTrayApp at remote 0xb7a664f4, args=(['/usr/bin/hp-systray', '-g', '-x'],), wrapped=0xb723faa0, kwds=0x0) at ../Objects/typeobject.c:4748 #4 0x0814481c in wrapper_call.11136 (wp=wp@entry=0xb7285eac, args=args@entry=(['/usr/bin/hp-systray', '-g', '-x'],), kwds=kwds@entry=0x0) at ../Objects/descrobject.c:1035 #5 0x081045a9 in PyObject_Call (kw=0x0, arg=(['/usr/bin/hp-systray', '-g', '-x'],), func=method-wrapper at remote 0xb7285eac) at ../Objects/abstract.c:2529 #6 PyEval_CallObjectWithKeywords ( func=func@entry=method-wrapper at remote 0xb7285eac, arg=arg@entry=(['/usr/bin/hp-systray', '-g', '-x'],), kw=kw@entry=0x0) at ../Python/ceval.c:3889 #7 0x0817c6ed in wrapperdescr_call.11249 (descr=0xb72922ac, args=optimised out, kwds=0x0) at ../Objects/descrobject.c:343 #8 0x081572f5 in PyObject_Call (kw=0x0, arg=(SystemTrayApp at remote 0xb7a664f4, ['/usr/bin/hp-systray', '-g', '-x']), func=wrapper_descriptor at remote 0xb72922ac) at ../Objects/abstract.c:2529 #9 do_call (nk=optimised out, na=optimised out, pp_stack=0xbfffea1c, ---Type return to continue, or q return to quit--- func=wrapper_descriptor at remote 0xb72922ac) at ../Python/ceval.c:4238 #10 call_function (oparg=optimised out, pp_stack=0xbfffea1c) at ../Python/ceval.c:4043 #11 PyEval_EvalFrameEx ( f=f@entry=Frame 0xb421731c, for file /usr/share/hplip/ui4/systemtray.py, line 301, in __init__ (self=SystemTrayApp at remote 0xb7a664f4, args=['/usr/bin/hp-systray', '-g', '-x'], read_pipe=4), throwflag=throwflag@entry=0) at ../Python/ceval.c:2666 #12 0x080c7212 in PyEval_EvalCodeEx (closure=optimised out, defcount=0, defs=0x0, kwcount=optimised out, kws=optimised out, argcount=optimised out, args=optimised out, locals=0x0, globals=optimised out, co=optimised out) at ../Python/ceval.c:3252 #13 function_call.15346 (func=func@entry=function at remote 0xb421841c, arg=arg@entry=(SystemTrayApp at remote 0xb7a664f4, ['/usr/bin/hp-systray', '-g', '-x'], 4), kw=kw@entry=0x0) at ../Objects/funcobject.c:526 #14 0x08114a22 in PyObject_Call (kw=0x0, arg=(SystemTrayApp at remote 0xb7a664f4, ['/usr/bin/hp-systray', '-g', '-x'], 4), func=function at remote 0xb421841c) at ../Objects/abstract.c:2529 #15 instancemethod_call.8775 (func=function at remote 0xb421841c, func@entry=instancemethod at remote 0xb76e2824, arg=(SystemTrayApp at remote 0xb7a664f4, ['/usr/bin/hp-systray', '-g', '-x'], 4), arg@entry=(['/usr/bin/hp-systray',
[Desktop-packages] [Bug 860680] Re: systray.py crashed with SIGSEGV
This looks like a bug in the python interpreter.
The routine setup_context in Python/_warnings.c looks like this.
setup_context(Py_ssize_t stack_level, PyObject **filename, int *lineno,
PyObject **module, PyObject **registry)
{
PyObject *globals;
/* Setup globals and lineno. */
PyFrameObject *f = PyThreadState_GET()-frame;
PyThreadState_GET is a macro defined in Include/pystate.h
#ifdef Py_DEBUG
#define PyThreadState_GET() PyThreadState_Get()
#else
#define PyThreadState_GET() (_PyThreadState_Current)
#endif
Py_DEBUG does not appear to have been defined when this version of
python was compiled. So the contents of _PyThreadState_Current are used
as a pointer. Unfortunately it looks like this routine can be called
when it is set to NULL. I put a break on the do_warn function in the
interpreter and ran hp-systray -g -x. The first time it triggers
(_PyThreadState_Current is non NULL and all is OK. The second time it is
NULL and the crash occurs. This may be because this warning is being
triggered deep in the initialisation code of a python object.
I do not know whether this is a python bug or an hplip bug. Maybe a
python expert can comment on this.
P.S. the python assembly code is heavily inline optimised by gcc so is
very hard to relate to real line numbers.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/860680
Title:
systray.py crashed with SIGSEGV
Status in HP Linux Imaging and Printing:
New
Status in “hplip” package in Ubuntu:
Confirmed
Bug description:
system reboot and after loading the desktop the error happened.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: hplip-data 3.11.7-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 27 11:33:43 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/hplip/systray.py
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110922)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for Officejet6500: hp:/net/Officejet_6500_E709n?ip=10.80.0.11
MachineType: Dell Inc. Inspiron N7010
PackageArchitecture: all
Papersize: letter
PpdFiles: Officejet6500: HP Officejet 6500 e709n hpijs, 3.11.7
ProcCmdline: python /usr/bin/hp-systray
ProcCwd: /home/rbrown
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic
root=UUID=e545f842-1c5b-4880-b81d-75cfaeef4f0c ro quiet splash vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x49c60b: mov0x10(%rax),%rdi
PC (0x0049c60b) ok
source 0x10(%rax) (0x0010) not located in a known VMA region (needed
readable region)!
destination %rdi ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hplip
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
Title: systray.py crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/20/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 08VFX1
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A09
dmi.modalias:
dmi:bvnDellInc.:bvrA09:bd10/20/2010:svnDellInc.:pnInspironN7010:pvrA09:rvnDellInc.:rn08VFX1:rvrA09:cvnDellInc.:ct8:cvrA09:
dmi.product.name: Inspiron N7010
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/860680/+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 1046635] Re: systray.py crashed with SIGSEGV in setup_context()
This bug is still affecting me in 14.04. Have looked at this further using gdb. It seems that there is a generic problem in do_warn when called from systray.py. A number of other bugs have reported this with different warning messages cuasing the crash. So anything that causes a warning message wlll cause a crash. In my case the message is related to pango. When I first saw this bug on a previous distribution it was caused by a different warning message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1046635 Title: systray.py crashed with SIGSEGV in setup_context() Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Confirmed Bug description: I went to settings, when I clicked ok, the applet hung for a couple of seconds then crashed. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: hplip-data 3.12.6-3ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Wed Sep 5 22:04:07 2012 ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) InterpreterPath: /usr/bin/python2.7 Lpstat: p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so device for Photosmart-C4600-series: hp:/usb/Photosmart_C4600_series?serial=CN978MG0DT05BQ MachineType: Apple Inc. MacBookPro8,1 PackageArchitecture: all Papersize: letter PpdFiles: Photosmart-C4600-series: HP Photosmart c4600 Series, hpcups 3.12.6 ProcCmdline: /usr/bin/python /usr/share/hplip/systray.py --force-startup ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=763c5bc8-6479-4726-b801-ef603ad83e22 ro quiet i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.i915_enable_rc6=7 drm.vblankoffdelay=1 usbcore.autosuspend=1 hpet=force SegvAnalysis: Segfault happened at: 0x54ba0b: mov0x10(%rax),%rax PC (0x0054ba0b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: gtk_widget_get_direction () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QGtkStyle::drawPrimitive(QStyle::PrimitiveElement, QStyleOption const*, QPainter*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 Title: systray.py crashed with SIGSEGV in gtk_widget_get_direction() UpgradeStatus: Upgraded to quantal on 2012-07-12 (55 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81: dmi.product.name: MacBookPro8,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1046635/+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 860680] Re: systray.py crashed with SIGSEGV
This bug has many duplicates. It appears that systray.py will crash whenever a warning message is generated. The oither bugs report a number of different warning messages. The following bugs are definite duplicates. #862779 #1046036 #1046635 #1157504 #1287596 #1299676 #1299764 The following are potential duplicates #917727 #923137 #963315 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/860680 Title: systray.py crashed with SIGSEGV Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Confirmed Bug description: system reboot and after loading the desktop the error happened. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: hplip-data 3.11.7-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 27 11:33:43 2011 EcryptfsInUse: Yes ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110922) InterpreterPath: /usr/bin/python2.7 Lpstat: device for Officejet6500: hp:/net/Officejet_6500_E709n?ip=10.80.0.11 MachineType: Dell Inc. Inspiron N7010 PackageArchitecture: all Papersize: letter PpdFiles: Officejet6500: HP Officejet 6500 e709n hpijs, 3.11.7 ProcCmdline: python /usr/bin/hp-systray ProcCwd: /home/rbrown ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=e545f842-1c5b-4880-b81d-75cfaeef4f0c ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x49c60b: mov0x10(%rax),%rdi PC (0x0049c60b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 10/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd10/20/2010:svnDellInc.:pnInspironN7010:pvrA09:rvnDellInc.:rn08VFX1:rvrA09:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron N7010 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/860680/+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 916336] Re: systray.py crashed with SIGSEGV in gdk_xsettings_watch_cb()
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug is no longer a duplicate of bug 862779 systray.py crashed with SIGSEGV ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/916336 Title: systray.py crashed with SIGSEGV in gdk_xsettings_watch_cb() Status in “hplip” package in Ubuntu: New Bug description: Add a fax/printer using hplip (not CUPS directly). ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: hplip-data 3.11.7-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CheckboxSubmission: 070ee660fbfb538b46e658849fd5bd28 CheckboxSystem: d00f84de8a555815fa1c4660280da308 CupsErrorLog: W [13/Jan/2012:09:27:47 +0100] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/HP_Color_LaserJet_2840_Gray__' has already been added W [13/Jan/2012:09:27:47 +0100] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/HP_Color_LaserJet_2840_RGB__' has already been added W [13/Jan/2012:09:27:47 +0100] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/HP_Color_LaserJet_2840_fax_Gray__' has already been added W [13/Jan/2012:09:27:47 +0100] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/HP_Color_LaserJet_2840_fax_RGB__' has already been added Date: Sat Jan 14 02:24:46 2012 ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) InterpreterPath: /usr/bin/python2.7 Lpstat: device for HP_Color_LaserJet_2840: hp:/net/HP_Color_LaserJet_2840?ip=192.168.2.10 device for HP_Color_LaserJet_2840_fax: hpfax:/net/HP_Color_LaserJet_2840?ip=192.168.2.10 MachineType: Dell Inc. Studio XPS 1645 PackageArchitecture: all Papersize: a4 PpdFiles: HP_Color_LaserJet_2840: HP Color LaserJet 2800 Foomatic/Postscript HP_Color_LaserJet_2840_fax: HP Fax hpcups ProcCmdline: python /usr/bin/hp-systray ProcEnviron: LANGUAGE=es:en PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=0d50f363-a0d5-45f4-9eac-96376aa6c85b ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x49c51b do_warn+27: mov0x10(%rax),%rdi PC (0x0049c51b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: gdk_xsettings_watch_cb (window=optimized out, is_start=optimized out, mask=optimized out, cb_data=optimized out) at /build/buildd/gtk+2.0-2.24.6/gdk/x11/gdkevents-x11.c:3110 gdk_xsettings_watch_cb (window=10485770, is_start=0, mask=optimized out, cb_data=0x2e48250) at /build/buildd/gtk+2.0-2.24.6/gdk/x11/gdkevents-x11.c:3074 check_manager_window (client=0x2b48aa0) at /build/buildd/gtk+2.0-2.24.6/gdk/x11/xsettings-client.c:423 _gdk_xsettings_client_process_event (client=optimized out, xev=optimized out) at /build/buildd/gtk+2.0-2.24.6/gdk/x11/xsettings-client.c:589 gdk_xsettings_client_event_filter (xevent=optimized out, event=optimized out, data=optimized out) at /build/buildd/gtk+2.0-2.24.6/gdk/x11/gdkevents-x11.c:3067 Title: systray.py crashed with SIGSEGV in gdk_xsettings_watch_cb() UdevDb: Error: [Errno 2] No existe el archivo o el directorio UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare src dmi.bios.date: 04/01/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0Y517R dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd04/01/2011:svnDellInc.:pnStudioXPS1645:pvrA13:rvnDellInc.:rn0Y517R:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Studio XPS 1645 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/916336/+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 892973] Re: systray.py crashed with SIGSEGV
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug is no longer a duplicate of bug 862779 systray.py crashed with SIGSEGV ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/892973 Title: systray.py crashed with SIGSEGV Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Confirmed Bug description: The service crashed on system shutdown ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: hplip-data 3.11.7-1ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 CrashCounter: 1 Date: Mon Nov 21 07:31:30 2011 ExecutablePath: /usr/share/hplip/systray.py InterpreterPath: /usr/bin/python2.7 Lpstat: device for Officejet_4500_G510n-z: hp:/net/Officejet_4500_G510n-z?zc=HPOccam device for Officejet_4500_G510n-z_fax: hpfax:/net/Officejet_4500_G510n-z?zc=HPOccam MachineType: System manufacturer System Product Name PackageArchitecture: all Papersize: a4 PpdFiles: Officejet_4500_G510n-z_fax: HP Fax hpcups Officejet_4500_G510n-z: HP Officejet 4500 g510n-z, hpcups 3.11.1 ProcCmdline: python /usr/bin/hp-systray ProcEnviron: LANGUAGE=it_IT:it:en_GB:en PATH=(custom, user) LANG=it_IT.utf8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=abb7c194-733c-4d92-8c17-d48683aaf5b3 ro quiet vga=795 splash SegvAnalysis: Segfault happened at: 0x80dce94 do_warn+20:mov0x8(%eax),%eax PC (0x080dce94) ok source 0x8(%eax) (0x0008) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV UpgradeStatus: Upgraded to oneiric on 2011-10-28 (23 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse lp lpadmin mythtv plugdev sambashare vboxusers video dmi.bios.date: 08/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1804:bd08/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/892973/+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 862779] Re: systray.py crashed with SIGSEGV
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/862779 Title: systray.py crashed with SIGSEGV Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Confirmed Bug description: I think I filed this bug before... strange I'm not being prompted for duplicates. Anyway, as always, after resuming from suspend - something crashed. This time a few 'bamfdaemon' crashes and now this one. Just mark it as a dup if it is. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: hplip-data 3.11.7-1ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 29 22:16:41 2011 ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110803.1) InterpreterPath: /usr/bin/python2.7 Lpstat: device for HP-Officejet-6500a: hp:/net/Officejet_6500_E710a-f?zc=HP2E0437 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all Papersize: letter PpdFiles: HP-Officejet-6500a: HP Officejet 6500 e710a-f, hpcups 3.11.7 ProcCmdline: python /usr/bin/hp-systray ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=24ee2295-58ad-4d06-a4eb-c0c7359e2bb6 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x49c60b: mov0x10(%rax),%rdi PC (0x0049c60b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV UpgradeStatus: Upgraded to oneiric on 2011-09-28 (1 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare dmi.bios.date: 01/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: H67M-GE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd01/17/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/862779/+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 1046036] Re: systray.py crashed with SIGSEGV in setup_context()
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1046036 Title: systray.py crashed with SIGSEGV in setup_context() Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: New Bug description: HPLIP is very unstable after upgrade from 12.04 to 12.10. Previous instances compiz completely crashed and gave no opportunity for reporting. This time only systray crashed. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: hplip-data 3.12.6-3ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Tue Sep 4 09:38:10 2012 ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) InterpreterPath: /usr/bin/python2.7 Lpstat: p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so device for Deskjet-F300-series: hp:/usb/Deskjet_F300_series?serial=CN726GM1JW04KH device for Officejet_Pro_8500_A910: hp:/net/Officejet_Pro_8500_A910?zc=HPOccam device for Officejet_Pro_8500_A910_fax: hpfax:/net/Officejet_Pro_8500_A910?zc=HPOccam MachineType: Gigabyte Technology Co., Ltd. GA-MA785GMT-USB3 PackageArchitecture: all Papersize: a4 PpdFiles: Officejet_Pro_8500_A910: HP Officejet Pro 8500 a910, hpcups 3.12.6 Officejet_Pro_8500_A910_fax: HP Fax4 hpcups Deskjet-F300-series: HP Deskjet f300 Series, hpcups 3.12.6 ProcCmdline: /usr/bin/python /usr/bin/hp-systray ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-13-generic root=UUID=d5fb4124-9549-4ae0-bce9-49e9debd9838 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x54ba0b: mov0x10(%rax),%rax PC (0x0054ba0b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: gtk_widget_style_get () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 QGtkStyle::pixelMetric(QStyle::PixelMetric, QStyleOption const*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QScrollBar::sizeHint() const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QAbstractScrollAreaPrivate::layoutChildren() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QAbstractScrollAreaPrivate::init() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 Title: systray.py crashed with SIGSEGV in gtk_widget_style_get() UpgradeStatus: Upgraded to quantal on 2012-09-04 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/04/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-785GMT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd01/04/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785GMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-785GMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA785GMT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1046036/+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 1299764] Re: systray.py crashed with SIGSEGV in setup_context()
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1299764 Title: systray.py crashed with SIGSEGV in setup_context() Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: New Bug description: unable to install or update sftware ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hplip-data 3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Sun Mar 30 09:40:13 2014 ExecutablePath: /usr/share/hplip/systray.py InstallationDate: Installed on 2014-03-28 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140328) InterpreterPath: /usr/bin/python2.7 Lpstat: device for HP-Officejet-Pro-8500-a910: https://198.168.1.109 device for PDF: cups-pdf:/ MachineType: Dell Inc. Studio XPS 1640 PackageArchitecture: all Papersize: letter PpdFiles: HP-Officejet-Pro-8500-a910: HP Officejet Pro 8500 a910, hpcups 3.14.3 PDF: Generic CUPS-PDF Printer ProcCmdline: /usr/bin/python /usr/bin/hp-systray -x ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=b665dffe-0167-4bfb-826a-a92d40861cde ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x5ac13d: mov0x10(%rax),%rdi PC (0x005ac13d) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_type_module_use () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_theme_engine_get () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV in g_type_module_use() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 03/29/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0U785D dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/29/2010:svnDellInc.:pnStudioXPS1640:pvrA143:rvnDellInc.:rn0U785D:rvrA14:cvnDellInc.:ct8:cvrA14: dmi.product.name: Studio XPS 1640 dmi.product.version: A143 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1299764/+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 1287596] Re: systray.py crashed with SIGSEGV in setup_context()
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1287596 Title: systray.py crashed with SIGSEGV in setup_context() Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: New Bug description: Was checking a setting in hplip using the systray icon when it crashed. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hplip-data 3.14.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CupsErrorLog: CurrentDesktop: XFCE Date: Tue Mar 4 21:23:12 2014 ExecutablePath: /usr/share/hplip/systray.py InterpreterPath: /usr/bin/python2.7 Lpstat: device for Officejet_5600: hp:/usb/Officejet_5600_series?serial=CN66NDF84304B2 device for Officejet_5600_fax: hpfax:/usb/Officejet_5600_series?serial=CN66NDF84304B2 device for PDF: cups-pdf:/ MachineType: System manufacturer System Product Name PackageArchitecture: all Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer Officejet_5600: HP Officejet 5600 Series, hpcups 3.13.11 Officejet_5600_fax: HP Fax hpcups ProcCmdline: /usr/bin/python /usr/bin/hp-systray -x ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=ba8659f4-635e-4ad7-9ad7-8e66a90395d0 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x81f2cb4: mov0x8(%eax),%ebp PC (0x081f2cb4) ok source 0x8(%eax) (0x0008) not located in a known VMA region (needed readable region)! destination %ebp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0 gtk_widget_get_direction () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so gtk_paint_focus () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV in g_return_if_fail_warning() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lp lpadmin sudo dmi.bios.date: 03/25/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5VD2-VM ACPI BIOS Revision 1302 dmi.board.name: P5VD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5VD2-VMACPIBIOSRevision1302:bd03/25/2008:svnSystemmanufacturer:pnSystemProductName:pvr:rvnASUSTeKComputerINC.:rnP5VD2-VM:rvr1.XX:cvnChassisManufacture:ct3:cvr: dmi.product.name: System Product Name dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1287596/+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 1157504] Re: systray.py crashed with SIGSEGV
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1157504 Title: systray.py crashed with SIGSEGV Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: New Bug description: hplip icon sis not appear on the top bar. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: hplip-data 3.13.3-1 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 Date: Tue Mar 19 21:15:00 2013 ExecutablePath: /usr/share/hplip/systray.py InstallationDate: Installed on 2013-03-14 (5 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130313) InterpreterPath: /usr/bin/python2.7 Lpstat: device for Photosmart_C4700: hp:/net/Photosmart_C4700_series?zc=HPBBD932 MachineType: Gigabyte Technology Co., Ltd. GA-A55M-DS2 MarkForUpload: True PackageArchitecture: all Papersize: letter PpdFiles: Photosmart_C4700: HP Photosmart c4700 Series, hpcups 3.13.3 ProcCmdline: /usr/bin/python /usr/bin/hp-systray -x ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=341e6244-731a-4c81-ba51-d0361140b232 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x52ddad: mov0x10(%rax),%rdi PC (0x0052ddad) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 02/29/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-A55M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd02/29/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-A55M-DS2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A55M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A55M-DS2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1157504/+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 1299676] Re: systray.py crashed with SIGSEGV in setup_context()
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1299676 Title: systray.py crashed with SIGSEGV in setup_context() Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: New Bug description: I got the crash when i opened the COLOR option in the SYSTEM SETTING window. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hplip-data 3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 23:14:16 2014 ExecutablePath: /usr/share/hplip/systray.py InstallationDate: Installed on 2014-03-23 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140322) InterpreterPath: /usr/bin/python2.7 Lpstat: device for HP-LaserJet-1020: usb://HP/LaserJet%201020?serial=FN0JLTF device for HP_LaserJet_1020: hp:/usb/HP_LaserJet_1020?serial=FN0JLTF MachineType: Dell Inc. XPS L521X PackageArchitecture: all Papersize: letter PpdFiles: HP_LaserJet_1020: HP LaserJet 1020, hpcups 3.14.3, requires proprietary plugin HP-LaserJet-1020: HP LaserJet 1020 Foomatic/foo2zjs-z1 (recommended) ProcCmdline: /usr/bin/python /usr/bin/hp-systray -x ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=25d1fad0-78c2-4384-a69f-933bc6185a3a ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x5ac13d: mov0x10(%rax),%rdi PC (0x005ac13d) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_type_module_use () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_theme_engine_get () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV in g_type_module_use() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/17/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 029M77 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.name: XPS L521X dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1299676/+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 1046635] Re: systray.py crashed with SIGSEGV in setup_context()
*** This bug is a duplicate of bug 860680 *** https://bugs.launchpad.net/bugs/860680 ** This bug has been marked a duplicate of bug 860680 systray.py crashed with SIGSEGV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1046635 Title: systray.py crashed with SIGSEGV in setup_context() Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Confirmed Bug description: I went to settings, when I clicked ok, the applet hung for a couple of seconds then crashed. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: hplip-data 3.12.6-3ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Wed Sep 5 22:04:07 2012 ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) InterpreterPath: /usr/bin/python2.7 Lpstat: p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so device for Photosmart-C4600-series: hp:/usb/Photosmart_C4600_series?serial=CN978MG0DT05BQ MachineType: Apple Inc. MacBookPro8,1 PackageArchitecture: all Papersize: letter PpdFiles: Photosmart-C4600-series: HP Photosmart c4600 Series, hpcups 3.12.6 ProcCmdline: /usr/bin/python /usr/share/hplip/systray.py --force-startup ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=763c5bc8-6479-4726-b801-ef603ad83e22 ro quiet i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.i915_enable_rc6=7 drm.vblankoffdelay=1 usbcore.autosuspend=1 hpet=force SegvAnalysis: Segfault happened at: 0x54ba0b: mov0x10(%rax),%rax PC (0x0054ba0b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: gtk_widget_get_direction () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libpixmap.so ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 QGtkStyle::drawPrimitive(QStyle::PrimitiveElement, QStyleOption const*, QPainter*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 Title: systray.py crashed with SIGSEGV in gtk_widget_get_direction() UpgradeStatus: Upgraded to quantal on 2012-07-12 (55 days ago) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81: dmi.product.name: MacBookPro8,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1046635/+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 860680] Re: systray.py crashed with SIGSEGV
This bug still exists on 14.04 Trusty Tahr. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/860680 Title: systray.py crashed with SIGSEGV Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Confirmed Bug description: system reboot and after loading the desktop the error happened. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: hplip-data 3.11.7-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 27 11:33:43 2011 EcryptfsInUse: Yes ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110922) InterpreterPath: /usr/bin/python2.7 Lpstat: device for Officejet6500: hp:/net/Officejet_6500_E709n?ip=10.80.0.11 MachineType: Dell Inc. Inspiron N7010 PackageArchitecture: all Papersize: letter PpdFiles: Officejet6500: HP Officejet 6500 e709n hpijs, 3.11.7 ProcCmdline: python /usr/bin/hp-systray ProcCwd: /home/rbrown ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=e545f842-1c5b-4880-b81d-75cfaeef4f0c ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x49c60b: mov0x10(%rax),%rdi PC (0x0049c60b) ok source 0x10(%rax) (0x0010) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 10/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd10/20/2010:svnDellInc.:pnInspironN7010:pvrA09:rvnDellInc.:rn08VFX1:rvrA09:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron N7010 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/860680/+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 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Still happening at 14.04. Managed to do apport-retrace and run gdb. This is what the stack trace looks like now. It may be another bug is hiding the first one. info (gdb)Auto-loading safe path done. warning: core file may not match specified executable file. [New LWP 6922] [New LWP 7063] [New LWP 7064] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Traceback (most recent call last): File /tmp/apport_sandbox_XIhMcU/usr/lib/debug/usr/lib/i386-linux-gnu/libstdc++.so.6.0.19-gdb.py, line 63, in module from libstdcxx.v6.printers import register_libstdcxx_printers ImportError: No module named 'libstdcxx' Core was generated by `/usr/bin/python /usr/bin/hp-systray -x'. Program terminated with signal SIGSEGV, Segmentation fault. #0 setup_context (registry=synthetic pointer, module=synthetic pointer, lineno=synthetic pointer, filename=synthetic pointer, stack_level=1, stack_level@entry=16) at ../Python/_warnings.c:449 449 ../Python/_warnings.c: No such file or directory. (gdb) bt #0 setup_context (registry=synthetic pointer, module=synthetic pointer, lineno=synthetic pointer, filename=synthetic pointer, stack_level=1, stack_level@entry=16) at ../Python/_warnings.c:449 #1 do_warn.29441 (message=message@entry=0xb6a40020, category=category@entry=0xb3b5f78c, stack_level=stack_level@entry=1) at ../Python/_warnings.c:594 #2 0x081f34cf in PyErr_WarnEx (category=category@entry=0xb3b5f78c, text=text@entry=0x97516e0 /usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory, stack_level=stack_level@entry=1) at ../Python/_warnings.c:720 #3 0xb4612aec in _log_func (log_domain=log_domain@entry=0xb3d35a56 Pango, log_level=log_level@entry=G_LOG_LEVEL_WARNING, message=message@entry=0x97516e0 /usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory, user_data=user_data@entry=0xb3b5f78c) at /build/buildd/pygobject-2-2.28.6/gobject/gobjectmodule.c:2316 #4 0xb5f6f2f7 in g_logv (log_domain=log_domain@entry=0xb3d35a56 Pango, log_level=log_level@entry=G_LOG_LEVEL_WARNING, format=format@entry=0xb3d40925 %s, args=args@entry=0xbff769ec \300\027u\t) at /build/buildd/glib2.0-2.40.0/./glib/gmessages.c:1012 #5 0xb5f6f523 in g_log (log_domain=log_domain@entry=0xb3d35a56 Pango, log_level=log_level@entry=G_LOG_LEVEL_WARNING, ---Type return to continue, or q return to quit--- format=format@entry=0xb3d40925 %s) at /build/buildd/glib2.0-2.40.0/./glib/gmessages.c:1071 #6 0xb3d1b7d6 in pango_module_load (module=0x9747ce0) at /build/buildd/pango1.0-1.36.3/./pango/modules.c:225 #7 0xb4b1bdfe in g_type_module_use (module=0x9747ce0) at /build/buildd/glib2.0-2.40.0/./gobject/gtypemodule.c:244 #8 0xb3d1b89b in pango_engine_pair_get_engine (pair=0x973da60) at /build/buildd/pango1.0-1.36.3/./pango/modules.c:321 #9 0xb3d1b967 in append_engines (engine_list=engine_list@entry=0xbff7704c, pair_list=optimised out) at /build/buildd/pango1.0-1.36.3/./pango/modules.c:810 #10 0xb3d1c013 in pango_map_get_engines (map=0x974f408, script=script@entry=PANGO_SCRIPT_COMMON, exact_engines=exact_engines@entry=0xbff77048, fallback_engines=fallback_engines@entry=0xbff7704c) at /build/buildd/pango1.0-1.36.3/./pango/modules.c:862 #11 0xb3d1fe8c in get_engines (fallback_engines=0xbff7704c, exact_engines=0xbff77048, script=optimised out, lang=optimised out, context=optimised out) at /build/buildd/pango1.0-1.36.3/./pango/pango-context.c:1161 #12 get_shaper_and_font (state=state@entry=0xbff76b9c, wc=wc@entry=9679, shape_engine=shape_engine@entry=0xbff76b48, font=font@entry=0xbff76b4c) at /build/buildd/pango1.0-1.36.3/./pango/pango-context.c:1250 ---Type return to continue, or q return to quit--- #13 0xb3d2018c in itemize_state_process_run (state=state@entry=0xbff76b9c) at /build/buildd/pango1.0-1.36.3/./pango/pango-context.c:1485 #14 0xb3d211f7 in pango_itemize_with_base_dir (context=0x97479a0, base_dir=base_dir@entry=PANGO_DIRECTION_LTR, text=0x9748148 ●, start_index=0, length=length@entry=3, attrs=attrs@entry=0x973a1a0, cached_iter=cached_iter@entry=0x973ccc0) at /build/buildd/pango1.0-1.36.3/./pango/pango-context.c:1590 #15 0xb3d28d5f in pango_layout_check_lines (layout=optimised out) at /build/buildd/pango1.0-1.36.3/./pango/pango-layout.c:3998 #16 0xb3d2a116 in pango_layout_get_unknown_glyphs_count ( layout=layout@entry=0xb2f056a8) at /build/buildd/pango1.0-1.36.3/./pango/pango-layout.c:1281 #17 0xb3fd4130 in find_invisible_char (widget=widget@entry=0x973a968) at /build/buildd/gtk+2.0-2.24.23/gtk/gtkentry.c:2259 #18 0xb3fd7c03 in gtk_entry_init (entry=0x973a968) at /build/buildd/gtk+2.0-2.24.23/gtk/gtkentry.c:2282 #19 0xb4b18b43 in g_type_create_instance
[Desktop-packages] [Bug 1232454] Re: Computer will suspend very soon because of inactivity. dialog when resuming from suspend
I think there are a number of bugs here. The version I see is. With Turn screen off when inactive set to 30 minutes and Suspend when inactive for set to 1 hour. If I come back after an hour the screen has turned off, but the computer has not suspended. When I wake up the screen the dekstop has locked as expected, when I type in my password the dekstop unlocks and shows the Computer will suspend very soon because of inactivity. dialog. This bug should probably be more like Computer will suspend very soon because of inactivity. dialog prevents system from suspending. I will call the the Type A version of this bug. I think it the same as Bug #1243174 which is marked as a duplicate of this. Does any one who sees them want to define types B,C, and D! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1232454 Title: Computer will suspend very soon because of inactivity. dialog when resuming from suspend Status in Gnome Settings Daemon: Unknown Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10 today, every time I unlock my computer after leaving it for a long time I get this prompt: -- Power Automatic suspend Computer will suspend very soon because of inactivity. -- However, the computer doesn't actually suspend. And even if I do this manually (which works) and then resume, the prompt is still there (and in that case, not true at all). This is ugly and seems broken! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-desktop 1.304 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sat Sep 28 15:32:42 2013 InstallationDate: Installed on 2012-08-03 (420 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1232454/+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 632066] Re: systray.py crashed with SIGSEGV in g_type_module_use()
Just upgraded to 13.10 and am getting this on every login. It was working fine on 13.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/632066 Title: systray.py crashed with SIGSEGV in g_type_module_use() Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: Incomplete Status in “qt4-x11” package in Ubuntu: Incomplete Bug description: Binary package hint: hplip apport reported ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: hplip-data 3.10.6-1ubuntu5 [modified: usr/share/hplip/base/__init__.pyc usr/share/hplip/base/codes.pyc usr/share/hplip/base/g.pyc usr/share/hplip/base/logger.pyc] ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 CupsErrorLog: E [06/Sep/2010:17:33:06 +0530] [cups-driverd] Bad driver information file /usr/share/cups/drv/sample.drv! E [06/Sep/2010:17:33:34 +0530] [cups-driverd] Bad driver information file /usr/share/cups/drv/sample.drv! Date: Sun Sep 5 18:11:23 2010 ExecutablePath: /usr/share/hplip/systray.py InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100215) InterpreterPath: /usr/bin/python2.6 Lpstat: device for Deskjet_D1500: hp:/usb/Deskjet_D1500_series?serial=TH96O5D3SF058V Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Kobian KN6100M PackageArchitecture: all Papersize: a4 PpdFiles: Deskjet_D1500: HP Deskjet d1500 Series hpijs, 3.10.6 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=32eb576a-bffd-44df-90ce-526c0652eb1c ro spUser Nameh quiet spUser Nameh ProcCmdline: python /usr/bin/hp-systray ProcEnviron: LANGUAGE=en_GB:en LANG=en_US.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x80d1c48: mov0x8(%edx),%edx PC (0x080d1c48) ok source 0x8(%edx) (0x0008) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: ?? () from /usr/lib/libgtk-x11-2.0.so.0 g_type_module_use () from /usr/lib/libgobject-2.0.so.0 gtk_theme_engine_get () from /usr/lib/libgtk-x11-2.0.so.0 ?? () from /usr/lib/libgtk-x11-2.0.so.0 ?? () from /usr/lib/libgtk-x11-2.0.so.0 Title: systray.py crashed with SIGSEGV in g_type_module_use() UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access sambashare tape vboxusers video dmi.bios.date: 06/01/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: KN6100M dmi.board.vendor: Kobian dmi.chassis.type: 3 dmi.chassis.vendor: Kobian dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/01/2007:svnKobian:pnKN6100M:pvr:rvnKobian:rnKN6100M:rvr:cvnKobian:ct3:cvr: dmi.product.name: KN6100M dmi.sys.vendor: Kobian To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/632066/+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 405116] Re: hpcups driver of HPLIP has broken margins
Some additional info. I ran some more tests using the hpijs driver and duplex printing on a Photosmart 6510, and there is still a 5mm clip of the top margin on when duplex printing a test pdf file using evince. This occurs irrespective of whether Shrink to printable area or Fit to printable area is set in the page handling options. I have attached the test file for info. ** Attachment added: Two page margin/printbale area test https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/405116/+attachment/3720238/+files/a4test.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/405116 Title: hpcups driver of HPLIP has broken margins Status in HP Linux Imaging and Printing: Fix Released Status in “cups” package in Ubuntu: Fix Released Status in “hplip” package in Ubuntu: Fix Released Status in “hplip” package in Debian: Fix Released Bug description: Binary package hint: hplip Hi. I have an HP DeskJet D2600 connected via USB. When I turned the printer on, a default configuration named Deskjet-D2600-series (using the HP Deskjet d2600 Series [en] driver) was generated that I can see in the gnome printer configuration window. When I print a test page the contents has a big margin at the top and the bottom is cut off. In the printer configuration if I change the driver to HP Deksjet d2600 Series hpijs [en] or HP Deksjet d2600 Series hpijs 3.9.6b.4 [en] the margin problem is corrected, but now black contents is printed in what looks like a combination of colors that appears black but looks more like dark brown. What I'm hoping for is that the margins for the default driver are corrected. I can provide any information that might be needed. Thanks. ProblemType: Bug Architecture: amd64 Date: Sun Jul 26 23:03:14 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Deskjet-D2600-series: hp:/usb/Deskjet_D2600_series?serial=TH94M140BG05C9 Package: hpijs-ppds 3.9.6b-1ubuntu4 PackageArchitecture: all Papersize: letter PpdFiles: Deskjet-D2600-series: HP Deskjet d2600 Series, hpcups 3.9.6b ProcCmdLine: root=UUID=06e1c48d-56bd-443b-8324-1975f908d414 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-4.22-generic SourcePackage: hplip Uname: Linux 2.6.31-4-generic x86_64 dmi.bios.date: 05/17/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: AV8 (VIA K8T800P-8237) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/17/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAV8(VIAK8T800P-8237):rvr1.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/405116/+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 405116] Re: hpcups driver of HPLIP has broken margins
I can confirm that this bug is still present in 13.04. Using the add printer function from the desktop gui to find a network connected HP Photosmart 6510 and accepting all the defaults, results in a configuration which clips at the top and bottom margins. The simple fix is to go into the printer's properties in the desktop gui and change the Make and Model: to refer to hpijs rather than hpcups. On my system the working Make and Model is HP Photosmart 6510 Series hpijs, 3.13.3. When the gui asks you about the ppd tell it to use a new (default) one and the reapply any of your required changes (e.g. duplex printing). Roger -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/405116 Title: hpcups driver of HPLIP has broken margins Status in HP Linux Imaging and Printing: Fix Released Status in “cups” package in Ubuntu: Fix Released Status in “hplip” package in Ubuntu: Fix Released Status in “hplip” package in Debian: Fix Released Bug description: Binary package hint: hplip Hi. I have an HP DeskJet D2600 connected via USB. When I turned the printer on, a default configuration named Deskjet-D2600-series (using the HP Deskjet d2600 Series [en] driver) was generated that I can see in the gnome printer configuration window. When I print a test page the contents has a big margin at the top and the bottom is cut off. In the printer configuration if I change the driver to HP Deksjet d2600 Series hpijs [en] or HP Deksjet d2600 Series hpijs 3.9.6b.4 [en] the margin problem is corrected, but now black contents is printed in what looks like a combination of colors that appears black but looks more like dark brown. What I'm hoping for is that the margins for the default driver are corrected. I can provide any information that might be needed. Thanks. ProblemType: Bug Architecture: amd64 Date: Sun Jul 26 23:03:14 2009 DistroRelease: Ubuntu 9.10 Lpstat: device for Deskjet-D2600-series: hp:/usb/Deskjet_D2600_series?serial=TH94M140BG05C9 Package: hpijs-ppds 3.9.6b-1ubuntu4 PackageArchitecture: all Papersize: letter PpdFiles: Deskjet-D2600-series: HP Deskjet d2600 Series, hpcups 3.9.6b ProcCmdLine: root=UUID=06e1c48d-56bd-443b-8324-1975f908d414 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-4.22-generic SourcePackage: hplip Uname: Linux 2.6.31-4-generic x86_64 dmi.bios.date: 05/17/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: AV8 (VIA K8T800P-8237) dmi.board.vendor: http://www.abit.com.tw/ dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/17/2006:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnAV8(VIAK8T800P-8237):rvr1.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/405116/+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
