[Desktop-packages] [Bug 1894741] Re: texdoc does not work
Apologies, I just found I had a partial install of texdoc in my home directory! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1894741 Title: texdoc does not work Status in texlive-base package in Ubuntu: Invalid Bug description: $ texdoc /usr/bin/texdoc:42: Internal error: Texdoc is not installed properly. The line that fails is: local texdoc = require 'texdoclib' so there seems to be something wrong with texlua's path searching. A workaround is to cd to /usr/share/texlive/texmf-dist/scripts/texdoc and then run the texdoc command, as the required file is then found in the current directory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: texlive-base 2019.20200218-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 18:14:16 2020 InstallationDate: Installed on 2019-12-23 (259 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: Upgraded to focal on 2020-08-29 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1894741/+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 1894741] [NEW] texdoc does not work
Public bug reported: $ texdoc /usr/bin/texdoc:42: Internal error: Texdoc is not installed properly. The line that fails is: local texdoc = require 'texdoclib' so there seems to be something wrong with texlua's path searching. A workaround is to cd to /usr/share/texlive/texmf-dist/scripts/texdoc and then run the texdoc command, as the required file is then found in the current directory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: texlive-base 2019.20200218-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 18:14:16 2020 InstallationDate: Installed on 2019-12-23 (259 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: Upgraded to focal on 2020-08-29 (8 days ago) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal ** Changed in: texlive-base (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1894741 Title: texdoc does not work Status in texlive-base package in Ubuntu: Invalid Bug description: $ texdoc /usr/bin/texdoc:42: Internal error: Texdoc is not installed properly. The line that fails is: local texdoc = require 'texdoclib' so there seems to be something wrong with texlua's path searching. A workaround is to cd to /usr/share/texlive/texmf-dist/scripts/texdoc and then run the texdoc command, as the required file is then found in the current directory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: texlive-base 2019.20200218-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 18:14:16 2020 InstallationDate: Installed on 2019-12-23 (259 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: Upgraded to focal on 2020-08-29 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1894741/+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 1790608] Re: [snap] Libreoffice does not open files from thunderbird (more general: from /tmp)
@OlivierS 20.04 has .deb LibreOffice (6.4.5), so there's no need to worry just yet. You can install it directly with apt. No need to use an external PPA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1790608 Title: [snap] Libreoffice does not open files from thunderbird (more general: from /tmp) Status in libreoffice package in Ubuntu: Confirmed Bug description: I received a document via e-mail in Thunderbird. I have the Libreoffice snap package installed. When I want to open the document from Thunderbird, I see the Libreoffice splash screen, and then a dialog stating "/tmp/mozilla_0/.docx does not exist." The same dialog appears when I navigate to the folder in Files and want to open it. When I copy the file to my desktop, however, I can open it without problems. I guess the source of the issue is confinement, that the Libreoffice snap can only access files from $HOME. But this breaks the case where thunderbird creates a temporary copy in /tmp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1790608/+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 1842986] [NEW] [snap] libreoffice cannot open files in /tmp (e.g. opened by browser)
Public bug reported: With the libreoffice snap, I get an error trying to open a .docx file from Firefox, saying that the file cannot be found. This appears to be because Firefox puts the file under /tmp, but libreoffice has a different /tmp in its process. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1842986 Title: [snap] libreoffice cannot open files in /tmp (e.g. opened by browser) Status in libreoffice package in Ubuntu: New Bug description: With the libreoffice snap, I get an error trying to open a .docx file from Firefox, saying that the file cannot be found. This appears to be because Firefox puts the file under /tmp, but libreoffice has a different /tmp in its process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1842986/+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 310351]
The SimulateActivity interface is not actually specified in the fd.o spec: http://people.freedesktop.org/~hadess/idle-inhibition- spec/re01.html The only methods offered there are Inhibit and UnInhibit. SimulateActivity is not implemented in GNOME 3, so the patch will not work there. The route I suggest will work on any system implementing the fd.o spec. In general, I think that while one does have to be careful about dependencies in general. First, it is not unreasonable to assume that any system running one of the desktop environments that implement this DBus interface will have Perl installed. Of course, the Perl DBus implementation is not part of core Perl; I would be happy to make my patch emit a helpful error if it can't find the module. Secondly, for most users, xdg-utils will be installed from a system package, which can depend on the relevant Perl package (which is not large); as well, of course, as depending on Perl (since Perl is installed by default on many systems, e.g. Ubuntu and Mac OS X, the latter dependency will often not be needed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken Status in Xdg-utils: Unknown Status in xdg-utils package in Ubuntu: Confirmed Status in xdg-utils package in Debian: Confirmed Bug description: Binary package hint: kscreensaver xdg-screensaver returns "bad call" for all values tested. Looking at the script, I'd guess it is because it detects the KDE desktop and tries to use dcop when KDE4 has moved to dbus, but that's just a guess. For example: $ xdg-screensaver activate call failed lsb_release -rd -> Ubuntu 8.10 Flavor is kbuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+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 310351]
Thanks, Rex. I happen to be a GNOME user myself, but more importantly, I need an xdg-screensaver that works for users there. If you have any suggestions that you'd be happier with, I'm all ears. Note that we're talking about GNOME 3/gnome-shell, so gnome-screensaver can't be assumed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken Status in Xdg-utils: Unknown Status in xdg-utils package in Ubuntu: Confirmed Status in xdg-utils package in Debian: Confirmed Bug description: Binary package hint: kscreensaver xdg-screensaver returns "bad call" for all values tested. Looking at the script, I'd guess it is because it detects the KDE desktop and tries to use dcop when KDE4 has moved to dbus, but that's just a guess. For example: $ xdg-screensaver activate call failed lsb_release -rd -> Ubuntu 8.10 Flavor is kbuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+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 310351]
Created attachment 111737 Patch to fix this bug This patch fixes the bug. It necessitates a helper Perl script. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/310351 Title: Kubuntu screensaver xdg-screensaver broken Status in Xdg-utils: Unknown Status in xdg-utils package in Ubuntu: Confirmed Status in xdg-utils package in Debian: Confirmed Bug description: Binary package hint: kscreensaver xdg-screensaver returns "bad call" for all values tested. Looking at the script, I'd guess it is because it detects the KDE desktop and tries to use dcop when KDE4 has moved to dbus, but that's just a guess. For example: $ xdg-screensaver activate call failed lsb_release -rd -> Ubuntu 8.10 Flavor is kbuntu To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/310351/+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 1070823] Re: chromium-browser deletes modified autostart files
As far as I can tell, this is no longer a problem. In particular, I have a ~/.config/autostart/chromium-browser.desktop file with a timestamp from 2017, and it is set to run Chromium normally (without --no-startup- window). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1070823 Title: chromium-browser deletes modified autostart files Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium does not have X session support; see http://code.google.com/p/chromium/issues/detail?id=23001 However, if you configure it to run in the background, then it installs a ~/.config/autostart/ file. This combined with configuring to restore windows on startup would give effectively session management, but for one small problem: the autostart file is created with --no-startup-window. This makes sense, because the configuration item is to run Chromium in the background. However, if I then edit the command in gnome-session-properties, then on next startup, Chromium REMOVES the autostart file! This is bad behaviour: apps should not modify or remove configuration files once the user has edited them (for example, consider the management of configuration files under /etc when packages are upgraded). Hence, if Chromium were simply prevented from changing the autostart file if it is user-edited (i.e. has non-default contents), then it would be possible to get effective session management, even without explicit support for XSM. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Wed Oct 24 13:11:32 2012 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/home/rrt/local/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda1 ext4 451G 149G 280G 35% /\nudev devtmpfs 3.9G 4.0K 3.9G 1% /dev\ntmpfs tmpfs 1.6G 1.2M 1.6G 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 3.9G 3.0M 3.9G 1% /run/shm\nnone tmpfs 100M 0 100M 0% /run/user\ncgroup tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 29M 1.5M 28M6% /\nudev 984K 606 984K1% /dev\ntmpfs 987K 546 987K1% /run\nnone 987K 2 987K1% /run/lock\nnone 987K15 987K1% /run/shm\nnone 987K 1 987K1% /run/user\ncgroup 987K 9 987K1% /sys/fs/cgroup\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: chromium-browser UpgradeStatus: Upgraded to quantal on 2012-10-19 (4 days ago) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser --new-window %U\n'/desktop/gnome/url-handlers/https/enabled = b'false\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser --new-window %U\n'/desktop/gnome/url-handlers/http/enabled = b'false\n'/desktop/gnome/session/required_components/windowmanager = b'compiz\n'/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1070823/+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 1812373] Re: Desktop is not restored correctly after screen saver
Thanks for the explanation, and I agree that the bug is "Invalid" for Ubuntu. -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: Invalid Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Desktop is not restored correctly after screen saver
For anyone else having the same problem as me, a patched version of the Hamster time tracker extension is available; see https://github.com/projecthamster/hamster-shell-extension/issues/295 ** Bug watch added: github.com/projecthamster/hamster-shell-extension/issues #295 https://github.com/projecthamster/hamster-shell-extension/issues/295 -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: Incomplete Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Desktop is not restored correctly after screen saver
I had several of these extensions. I started by disabling them all. This fixed the problem (thanks!). I then re-enabled most of them one at a time (because they are all things I find extremely useful—I do not like to install extensions unless I have to!). In the end, I was able to reinstall all but one of the extensions I need, namely 'cont...@projecthamster.org' I had no problem with: 'nohotcor...@azuri.free.fr' 'switc...@landau.fi' 'topIcons@adel.gadl...@gmail.com' 'windowIsReady_Remover@nunofarr...@gmail.com' 'windowoverlay-ic...@sustmidown.centrum.cz' 'window-search-provi...@quelltexter.org' I am interested in how you made the list, @vanvugt; is there some reason to suspect the other extensions listed are problematic too? In any case, my immediate problem seems to be solved (thanks very much), and I now need to find a fix for using Project Hamster, as I rely on it to time work. -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: Incomplete Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Desktop is not restored correctly after screen saver
@vanvugt: I had a look at the other bug and its proposed fix. I do not have the package gnome-shell-extension-ubuntu-dock installed, and the recent update's changelog suggests that the update fixes a bug in that package, so I'm not sure how it could be the cause of this bug? -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: Incomplete Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Desktop is not restored correctly after screen saver
Thanks for the pointer; I've subscribed to that bug. -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: Incomplete Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Desktop is not restored correctly after screen saver
It's always been grey on Ubuntu GNOME as far as I'm aware. -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: Incomplete Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Desktop is not restored correctly after screen saver
I notice that if I use the mouse to deactivate the screen saver, I do still see the screen shield, so that appears to be working normally. When the shield lifts, I get the "login screen without login widget" described above. -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: New Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Desktop is not restored correctly after screen saver
I tried disabling the lock screen with $ gsettings set org.gnome.desktop.lockdown disable-lock-screen true and that makes no difference. -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: New Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Desktop is not restored correctly after screen saver
I have updated the bug to reflect that it's related to the screen saver (desktop idleness), not specifically the lock screen. ** Summary changed: - Lock screen stopped working + Desktop is not restored correctly after screen saver ** Description changed: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, - the lock screen stopped working properly. + the screen saver stopped working properly. - When I enter lock, either manually (by clicking the lock screen icon) or - automatically (by waiting for the lock screen timeout), the screen - either freezes with the desktop still showing, or shoes the same grey - background as the login screen; it does not show the normal lock screen - image. + When the screen is locked manually (by clicking the lock screen icon), + the screen either freezes with the desktop still showing, or shows the + same grey background as the login screen; it does not show the normal + lock screen image. - Pressing a key such as space, which would normally raise the screen - shield and reveal the login dialog, has no effect. + When the screen saver is activated automatically, the screen turns off + as normal, but when I press a key, the grey background as for the login + screen is shown (in fact, it's the same as the login screen, but without + the login widget; that is, the normal icons are shown at the top of the + screen). + Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) -- 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/1812373 Title: Desktop is not restored correctly after screen saver Status in gnome-shell package in Ubuntu: New Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the screen saver stopped working properly. When the screen is locked manually (by clicking the lock screen icon), the screen either freezes with the desktop still showing, or shows the same grey background as the login screen; it does not show the normal lock screen image. When the screen saver is activated automatically, the screen turns off as normal, but when I press a key, the grey background as for the login screen is shown (in fact, it's the same as the login screen, but without the login widget; that is, the normal icons are shown at the top of the screen). Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Lock screen stopped working
In case it was a kernel problem (I have also had a kernel update since I last rebooted, from 4.15.0-42 to -43), I installed the latest HWE 18.04 kernel, but that did not help. I should note that in fact the screen shield *does* sometimes activate; but when it does, pressing a key reveals only the grey background, not the login dialog. Another potential culprit might be gdm3, but of course there has been no update to that package recently. -- 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/1812373 Title: Lock screen stopped working Status in gnome-shell package in Ubuntu: New Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the lock screen stopped working properly. When I enter lock, either manually (by clicking the lock screen icon) or automatically (by waiting for the lock screen timeout), the screen either freezes with the desktop still showing, or shoes the same grey background as the login screen; it does not show the normal lock screen image. Pressing a key such as space, which would normally raise the screen shield and reveal the login dialog, has no effect. Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Lock screen stopped working
I tried building 3.28.3-0ubuntu0.18.04.3 and installing that, but that doesn't fix the problem, so it looks as though the cause may lie elsewhere, in some other update that has happened in the same period. -- 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/1812373 Title: Lock screen stopped working Status in gnome-shell package in Ubuntu: New Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the lock screen stopped working properly. When I enter lock, either manually (by clicking the lock screen icon) or automatically (by waiting for the lock screen timeout), the screen either freezes with the desktop still showing, or shoes the same grey background as the login screen; it does not show the normal lock screen image. Pressing a key such as space, which would normally raise the screen shield and reveal the login dialog, has no effect. Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1812373] Re: Lock screen stopped working
(The issue doesn't seem to me to be serious enough to warrant keeping the bug private.) ** Information type changed from Private Security to Public -- 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/1812373 Title: Lock screen stopped working Status in gnome-shell package in Ubuntu: New Bug description: With the update to 3.28.3-0ubuntu0.18.04.4, on two separate machines, the lock screen stopped working properly. When I enter lock, either manually (by clicking the lock screen icon) or automatically (by waiting for the lock screen timeout), the screen either freezes with the desktop still showing, or shoes the same grey background as the login screen; it does not show the normal lock screen image. Pressing a key such as space, which would normally raise the screen shield and reveal the login dialog, has no effect. Pressing Ctrl+Alt+F1 switches to the login dialog. I can then log in successfully, but all GNOME shell extensions are disabled. (A simple workaround is then to restart gnome-shell with the "r" command from the "Enter a command" dialog.) I am marking this bug as a security vulnerability because in the case that the screen simply freezes, confidential information may be displayed by the failure of the screen shield to activate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 18 10:28:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-11-26 (1514 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-16 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812373/+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 1087075] Re: Duplex options ignored for printing Postscript
I can confirm that this bug still exists in Ubuntu 16.04.5: specifically, I tried printing two pages of a PostScript file from Evince with Duplex set to "Long Edge (Standard)", and instead of a single sheet with both pages, the printer printed on two sheets. I also had the following error on the terminal from which I launched Evince: "fatal internal error -100" eight times, without a newline between the repetitions. It would be good to find a solution to this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1087075 Title: Duplex options ignored for printing Postscript Status in cups package in Ubuntu: Incomplete Bug description: Printing a Postscript file using lp -o Duplex=DuplexNoTumble foo.ps does not give duplex output. I have read other bug reports, turned collation off &c. and I can't see anything else that might be causing the problem. Printing from the gtk print dialog, the duplex setting I choose is respected, but because of a font-related bug with gtkprint, I'm using the lp command directly to print my Postscript file. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Dec 6 00:59:07 2012 InstallationDate: Installed on 2011-10-14 (418 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for bunyan: dnssd://Lexmark%20X543._ipp._tcp.local/ MachineType: Apple Inc. MacBookAir4,2 MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-10-20 (46 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1087075/+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 1159884] Re: References to ~/.xsession-errors in /etc/gdm/
The upstream bug has been migrated to the new GNOME bug-tracker at GitLab: https://gitlab.gnome.org/GNOME/gdm/issues/157 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1159884 Title: References to ~/.xsession-errors in /etc/gdm/ Status in gdm: Expired Status in gdm package in Ubuntu: Triaged Bug description: In several scripts shipped as part of gdm, e.g. /etc/gdm/PreSession/Default, and /etc/gdm/Xsession, there are comments referring to logging being done to .xsession-errors. However, these days, logging from gdm goes to .cache/gdm/session.log. This out-of-date information is also contained in many .po files, and some Debian patches. Time for a global search-and-replace? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gdm 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 16:21:41 2013 InstallationDate: Installed on 2011-05-24 (670 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: gdm UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1159884/+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 1159884] Re: References to ~/.xsession-errors in /etc/gdm/
I tried changing the remote bug watch, but Launchpad won't accept the GitLab URL. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1159884 Title: References to ~/.xsession-errors in /etc/gdm/ Status in gdm: Expired Status in gdm package in Ubuntu: Triaged Bug description: In several scripts shipped as part of gdm, e.g. /etc/gdm/PreSession/Default, and /etc/gdm/Xsession, there are comments referring to logging being done to .xsession-errors. However, these days, logging from gdm goes to .cache/gdm/session.log. This out-of-date information is also contained in many .po files, and some Debian patches. Time for a global search-and-replace? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gdm 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 16:21:41 2013 InstallationDate: Installed on 2011-05-24 (670 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: gdm UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1159884/+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 1159884] Re: References to ~/.xsession-errors in /etc/gdm/
This bug appears to be still present in package gdm3 (see /etc/gdm3/PreSession/Default). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1159884 Title: References to ~/.xsession-errors in /etc/gdm/ Status in gdm: Expired Status in gdm package in Ubuntu: Triaged Bug description: In several scripts shipped as part of gdm, e.g. /etc/gdm/PreSession/Default, and /etc/gdm/Xsession, there are comments referring to logging being done to .xsession-errors. However, these days, logging from gdm goes to .cache/gdm/session.log. This out-of-date information is also contained in many .po files, and some Debian patches. Time for a global search-and-replace? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gdm 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 16:21:41 2013 InstallationDate: Installed on 2011-05-24 (670 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: gdm UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1159884/+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 68924] Re: provide support for changing volume labels
I can find no evidence that this bug has ever been fixed, even in Ubuntu. Can anyone point me to evidence that it has been? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/68924 Title: provide support for changing volume labels Status in HAL: Won't Fix Status in One Hundred Papercuts: Invalid Status in Nautilus: New Status in hal package in Ubuntu: Won't Fix Status in nautilus package in Ubuntu: Fix Released Bug description: My old MP3MAN 1/2 gig mp3 player is able to be renamed in Windows but not in Ubuntu. I'm not sure if this is something that all players can do but it is something that could be well worth looking into (as I don't have a windows machine my mate renamed mine and I have a new samsung player now, for it's ogg support). Effectively in windows you right click on the player icon and hit rename and the player retains that name when you plug into any machine (I will send a screen shot) so mine now says DAVES MP3 rather than mp3man. This is not an urgent bug by any means but it is one thing I noticed that can't yet be done. I want to see bug 1 stripped out as soon as possible but it is always the little things that annoy people. * From duplicate bug #388207, I add emphasis that volumes should be re-namable using right-click. This may be obvious, but "let the record show" that volumes should act like all other files with respect to renaming. To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/68924/+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 708311] Re: Manually added startup application is deleted
It seems not. I think this bug can be closed, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708311 Title: Manually added startup application is deleted Status in chromium-browser package in Ubuntu: New Bug description: Binary package hint: gnome-session Since chromium-browser doesn't support X sessions, I tried adding a custom entry to Startup Applications. This works fine, but the .desktop file is regularly deleted. I am wondering if this happens whenever chromium is updated, because this happens once a day (I get it from the nightly build PPA). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-session-bin 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 Architecture: i386 Date: Wed Jan 26 21:12:46 2011 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 SourcePackage: gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708311/+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 815856] Re: On Lexmark X543dn, "All pages from feeder" only returns one page
Since the bug has been present for years, and there's nothing in the current Changelog about a fix, it doesn't seem worth just trying the latest version in the hope that it might have been fixed by accident. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Expired Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 1634490] Re: Pattern drawn over dialog title bars obscures title
I'm using gnome-shell, as shipped in Ubuntu 16.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1634490 Title: Pattern drawn over dialog title bars obscures title Status in libreoffice package in Ubuntu: New Bug description: Most dialogs in LibreOffice (but not the main document windows) have a pattern drawn over the title bar, which obscures the window title. I can't find any way to change this: changing the symbol style has no effect, and I can't find anything about this problem by googling. I attach a screenshot of the Format dialog from Calc to show the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 18 13:38:16 2016 InstallationDate: Installed on 2014-11-26 (692 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-07-25 (84 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1634490/+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 1634490] Re: Pattern drawn over dialog title bars obscures title
The effect occurs in no other application. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1634490 Title: Pattern drawn over dialog title bars obscures title Status in libreoffice package in Ubuntu: New Bug description: Most dialogs in LibreOffice (but not the main document windows) have a pattern drawn over the title bar, which obscures the window title. I can't find any way to change this: changing the symbol style has no effect, and I can't find anything about this problem by googling. I attach a screenshot of the Format dialog from Calc to show the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 18 13:38:16 2016 InstallationDate: Installed on 2014-11-26 (692 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-07-25 (84 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1634490/+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 624172] Re: Multiple copies of irexec started at login
Feel free to close it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/624172 Title: Multiple copies of irexec started at login Status in lirc package in Ubuntu: Incomplete Bug description: Binary package hint: lirc I use irexec to generate multimedia keystrokes from my Apple remote. Hence, I created a Startup Applications entry for irexec. Sometimes when I log in, multiple copies of irexec are run. It seems that this could be because irexec is not always killed when I log out: for example, in my current session, one of the copies of irexec has a PID just a little greater than my gnome-session, whereas the other has a lower PID, which seems to be similar to PIDs of other processes created when I first logged in after rebooting, e.g. mpd. I don't know whether this bug is properly considered to be in lirc or in some program related to GNOME session management, but as I cannot tell it seemed logical to start here (with the specific program that is causing problems), especially as I have not noticed this behaviour with any other program. I suppose there are multiple questions to answer: 1. Should irexec be killed (or die) when I log out? It seems that some programs started in my session, like mpd, persist when I log out. 2. When I log in, should irexec realise that it is already running and not start a second instance? If either 1 or 2 were happening, then I would not have a problem... Sorry if this is a bit vague, and let me know what other information I can provide to help track down the bug. (In case you're wondering, the reason this bug is a problem is because when there are multiple copies of irexec running, each IR control keypress is acted on once per copy of irexec, so when I press "play/pause", nothing seems to happen, because the music is first paused, then immediately unpaused, for example.) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: lirc 0.8.6-0ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Wed Aug 25 18:59:59 2010 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 SourcePackage: lirc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/624172/+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 567512] Re: uinput broken for at least Mac mini
Thanks; I don't have that machine any more. If I operate a Mac mini with uinput remote in future I'll look into it! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/567512 Title: uinput broken for at least Mac mini Status in lirc package in Ubuntu: Incomplete Status in lirc source package in Lucid: Won't Fix Status in lirc source package in Maverick: Won't Fix Bug description: I have patched and tested the latest lirc packages from lucid. I have uploaded a bzr branch to Launchpad and requested a merge to lucid- proposed. The debdiff is also attached. For the needs of the SRU: - Impact of this bug: This bug renders the "--uinput" of lirc useless. This options allows remote controls to input commands like key strokes (as you would with a multimedia keyboard with "play", "next/previous", "volume up/down", etc buttons). This is obviously a very simple and attractive way to use a remote control with Ubuntu, and is recommended in many tutorials (including on help.ubuntu.com). Currently, in lucid, the buttons pressed on the remote have no effect (until the lircd daemon is stopped or restarted). - Nominating for SRU, fulfills: (1) have an obviously safe patch (it only concerns the --uinput which is currently non-functional, and is tested by upstream and other distros) and (2) affect an application rather than critical infrastructure packages - My proposed patch simply includes a patch from upstream (git commit d987ce9c68239f637dddb9de9f9668f6e8f9fc1d) to fix this problem. It is included in the 0.8.7~pre3-0ubuntu1 version in maverick, which works fine. TEST CASE: A supported remote control and IR receiver are required. Install the lirc package. Configure /etc/lirc/lircd.conf for your remote, if not already done during package installation (or include a preset from /usr/share/lirc/remotes/). Ensure your remote button presses are detected when running irw. Edit /etc/lirc/hardware.conf and set these keys: REMOTE_MODULES="uinput" REMOTE_LIRCD_ARGS="--uinput" Restart lirc. Start rhythmbox and enable the "lirc" module. Restart rhythmbox and start playing a song. Press pause key on the remote and notice that rhythmbox doesn't take any notice. Stop lirc, and see that rhythmbox then pauses the song. I see no regression potential for this patch, as it only affects users running lirc with the --uinput option, which is currently non- functional with an up-to-date Ubuntu lucid. --- Architecture: i386 DistroRelease: Ubuntu 10.04 Package: lirc 0.8.6-0ubuntu4.2 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Tags: lucid Uname: Linux 2.6.32-25-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner src vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/567512/+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 1623512] Re: Fix for Play/Pause key on some MCE remotes
Thanks! I probably won't have time to do that, but I'll try to remember if I do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1623512 Title: Fix for Play/Pause key on some MCE remotes Status in lirc package in Ubuntu: New Bug description: The file /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb contains a section reading: #seen on HP Pavilion dv3t remote --Tim Mann, 3 Nov 2009 Media 0x7b7f PlayPause 0x7b91 I have a Compro VideoMate K300 remote, and I can't find a key corresponding to Media, but it does have a Play/Pause key generating the same code as above (0x7b91). However, using it with Kodi, for example, it does nothing useful, because Kodi does not recognise the "PlayPause" code. I suggest that for Kodi, XMBC & similar programs it's probably more useful to change the code output to KEY_PLAY. (I tried KEY_PLAYPAUSE, which is also mentioned in Kodi's Lircmap.xml, but that did not work in Kodi: nothing happened when I pressed the key.) With KEY_PLAY, the key works as expected: it plays or pauses the music. The change is to change "PlayPause" in the above line to "KEY_PLAY". Arguably, the correct fix is to change the keycode to "KEY_PLAYPAUSE", and then make Kodi correctly respond to "KEY_PLAYPAUSE". I attempted to do this by editing Kodi's Lircmap.xml, but failed. I looked at upstream lirc, but that has completely changed the organisation of remote config files since 0.9.0, so it seems most appropriate to make a fix in Ubuntu (and possibly Debian). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lirc 0.9.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 14 14:00:37 2016 InstallationDate: Installed on 2014-11-26 (658 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: lirc UpgradeStatus: Upgraded to xenial on 2016-07-25 (50 days ago) mtime.conffile..etc.lirc.hardware.conf: 2016-09-14T12:27:53.394843 mtime.conffile..etc.lirc.lircd.conf: 2016-09-14T13:55:14.416867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1623512/+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 1623512] Re: Fix for Play/Pause key on some MCE remotes
Thanks for the suggestion (and for your work upstream!). I had a look at lirc-remotes, and it already has what I consider the correct fix, namely, to change the key code to KEY_PLAYPAUSE. If when I get this version of lirc on my machine I still have my MCE remote, and it still doesn't work in Kodi, I suspect it will be time to chase the bug there instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1623512 Title: Fix for Play/Pause key on some MCE remotes Status in lirc package in Ubuntu: New Bug description: The file /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb contains a section reading: #seen on HP Pavilion dv3t remote --Tim Mann, 3 Nov 2009 Media 0x7b7f PlayPause 0x7b91 I have a Compro VideoMate K300 remote, and I can't find a key corresponding to Media, but it does have a Play/Pause key generating the same code as above (0x7b91). However, using it with Kodi, for example, it does nothing useful, because Kodi does not recognise the "PlayPause" code. I suggest that for Kodi, XMBC & similar programs it's probably more useful to change the code output to KEY_PLAY. (I tried KEY_PLAYPAUSE, which is also mentioned in Kodi's Lircmap.xml, but that did not work in Kodi: nothing happened when I pressed the key.) With KEY_PLAY, the key works as expected: it plays or pauses the music. The change is to change "PlayPause" in the above line to "KEY_PLAY". Arguably, the correct fix is to change the keycode to "KEY_PLAYPAUSE", and then make Kodi correctly respond to "KEY_PLAYPAUSE". I attempted to do this by editing Kodi's Lircmap.xml, but failed. I looked at upstream lirc, but that has completely changed the organisation of remote config files since 0.9.0, so it seems most appropriate to make a fix in Ubuntu (and possibly Debian). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lirc 0.9.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 14 14:00:37 2016 InstallationDate: Installed on 2014-11-26 (658 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: lirc UpgradeStatus: Upgraded to xenial on 2016-07-25 (50 days ago) mtime.conffile..etc.lirc.hardware.conf: 2016-09-14T12:27:53.394843 mtime.conffile..etc.lirc.lircd.conf: 2016-09-14T13:55:14.416867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1623512/+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 1623512] Re: Fix for Play/Pause key on some MCE remotes
I'm suggesting a fix for e.g. Xenial, as otherwise many users will have non working play/pause, a basic function, for a few years. The simple fix I suggest is safe, as it only affects MCE remotes, where the problem is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1623512 Title: Fix for Play/Pause key on some MCE remotes Status in lirc package in Ubuntu: New Bug description: The file /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb contains a section reading: #seen on HP Pavilion dv3t remote --Tim Mann, 3 Nov 2009 Media 0x7b7f PlayPause 0x7b91 I have a Compro VideoMate K300 remote, and I can't find a key corresponding to Media, but it does have a Play/Pause key generating the same code as above (0x7b91). However, using it with Kodi, for example, it does nothing useful, because Kodi does not recognise the "PlayPause" code. I suggest that for Kodi, XMBC & similar programs it's probably more useful to change the code output to KEY_PLAY. (I tried KEY_PLAYPAUSE, which is also mentioned in Kodi's Lircmap.xml, but that did not work in Kodi: nothing happened when I pressed the key.) With KEY_PLAY, the key works as expected: it plays or pauses the music. The change is to change "PlayPause" in the above line to "KEY_PLAY". Arguably, the correct fix is to change the keycode to "KEY_PLAYPAUSE", and then make Kodi correctly respond to "KEY_PLAYPAUSE". I attempted to do this by editing Kodi's Lircmap.xml, but failed. I looked at upstream lirc, but that has completely changed the organisation of remote config files since 0.9.0, so it seems most appropriate to make a fix in Ubuntu (and possibly Debian). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lirc 0.9.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 14 14:00:37 2016 InstallationDate: Installed on 2014-11-26 (658 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: lirc UpgradeStatus: Upgraded to xenial on 2016-07-25 (50 days ago) mtime.conffile..etc.lirc.hardware.conf: 2016-09-14T12:27:53.394843 mtime.conffile..etc.lirc.lircd.conf: 2016-09-14T13:55:14.416867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1623512/+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 1634490] Re: Pattern drawn over dialog title bars obscures title
I installed LibreOffice 5.2 from the libreoffice/ppa PPA, and that seems to fix the bug. However, I obviously can't tell whether the bug is fixed in Ubuntu proper, unless the packages from the PPA are adopted precisely as-is! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1634490 Title: Pattern drawn over dialog title bars obscures title Status in libreoffice package in Ubuntu: New Bug description: Most dialogs in LibreOffice (but not the main document windows) have a pattern drawn over the title bar, which obscures the window title. I can't find any way to change this: changing the symbol style has no effect, and I can't find anything about this problem by googling. I attach a screenshot of the Format dialog from Calc to show the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 18 13:38:16 2016 InstallationDate: Installed on 2014-11-26 (692 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-07-25 (84 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1634490/+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 1634490] [NEW] Pattern drawn over dialog title bars obscures title
Public bug reported: Most dialogs in LibreOffice (but not the main document windows) have a pattern drawn over the title bar, which obscures the window title. I can't find any way to change this: changing the symbol style has no effect, and I can't find anything about this problem by googling. I attach a screenshot of the Format dialog from Calc to show the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 18 13:38:16 2016 InstallationDate: Installed on 2014-11-26 (692 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-07-25 (84 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Screenshot of a dialog showing the problem" https://bugs.launchpad.net/bugs/1634490/+attachment/4763222/+files/Screenshot%20from%202016-10-18%2013-39-32.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1634490 Title: Pattern drawn over dialog title bars obscures title Status in libreoffice package in Ubuntu: New Bug description: Most dialogs in LibreOffice (but not the main document windows) have a pattern drawn over the title bar, which obscures the window title. I can't find any way to change this: changing the symbol style has no effect, and I can't find anything about this problem by googling. I attach a screenshot of the Format dialog from Calc to show the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice 1:5.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 18 13:38:16 2016 InstallationDate: Installed on 2014-11-26 (692 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: Upgraded to xenial on 2016-07-25 (84 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1634490/+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 1623512] [NEW] Fix for Play/Pause key on some MCE remotes
Public bug reported: The file /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb contains a section reading: #seen on HP Pavilion dv3t remote --Tim Mann, 3 Nov 2009 Media 0x7b7f PlayPause 0x7b91 I have a Compro VideoMate K300 remote, and I can't find a key corresponding to Media, but it does have a Play/Pause key generating the same code as above (0x7b91). However, using it with Kodi, for example, it does nothing useful, because Kodi does not recognise the "PlayPause" code. I suggest that for Kodi, XMBC & similar programs it's probably more useful to change the code output to KEY_PLAY. (I tried KEY_PLAYPAUSE, which is also mentioned in Kodi's Lircmap.xml, but that did not work in Kodi: nothing happened when I pressed the key.) With KEY_PLAY, the key works as expected: it plays or pauses the music. The change is to change "PlayPause" in the above line to "KEY_PLAY". Arguably, the correct fix is to change the keycode to "KEY_PLAYPAUSE", and then make Kodi correctly respond to "KEY_PLAYPAUSE". I attempted to do this by editing Kodi's Lircmap.xml, but failed. I looked at upstream lirc, but that has completely changed the organisation of remote config files since 0.9.0, so it seems most appropriate to make a fix in Ubuntu (and possibly Debian). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lirc 0.9.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 14 14:00:37 2016 InstallationDate: Installed on 2014-11-26 (658 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: lirc UpgradeStatus: Upgraded to xenial on 2016-07-25 (50 days ago) mtime.conffile..etc.lirc.hardware.conf: 2016-09-14T12:27:53.394843 mtime.conffile..etc.lirc.lircd.conf: 2016-09-14T13:55:14.416867 ** Affects: lirc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1623512 Title: Fix for Play/Pause key on some MCE remotes Status in lirc package in Ubuntu: New Bug description: The file /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb contains a section reading: #seen on HP Pavilion dv3t remote --Tim Mann, 3 Nov 2009 Media 0x7b7f PlayPause 0x7b91 I have a Compro VideoMate K300 remote, and I can't find a key corresponding to Media, but it does have a Play/Pause key generating the same code as above (0x7b91). However, using it with Kodi, for example, it does nothing useful, because Kodi does not recognise the "PlayPause" code. I suggest that for Kodi, XMBC & similar programs it's probably more useful to change the code output to KEY_PLAY. (I tried KEY_PLAYPAUSE, which is also mentioned in Kodi's Lircmap.xml, but that did not work in Kodi: nothing happened when I pressed the key.) With KEY_PLAY, the key works as expected: it plays or pauses the music. The change is to change "PlayPause" in the above line to "KEY_PLAY". Arguably, the correct fix is to change the keycode to "KEY_PLAYPAUSE", and then make Kodi correctly respond to "KEY_PLAYPAUSE". I attempted to do this by editing Kodi's Lircmap.xml, but failed. I looked at upstream lirc, but that has completely changed the organisation of remote config files since 0.9.0, so it seems most appropriate to make a fix in Ubuntu (and possibly Debian). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lirc 0.9.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 14 14:00:37 2016 InstallationDate: Installed on 2014-11-26 (658 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: lirc UpgradeStatus: Upgraded to xenial on 2016-07-25 (50 days ago) mtime.conffile..etc.lirc.hardware.conf: 2016-09-14T12:27:53.394843 mtime.conffile..etc.lirc.lircd.conf: 2016-09-14T13:55:14.416867 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1623512/+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 1620043] Re: All but one page sent by network scanner are discarded
Sorry, I don't have time to test dailies. If I can, I'll look into it upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1620043 Title: All but one page sent by network scanner are discarded Status in simple-scan package in Ubuntu: Incomplete Bug description: If I press Scan in simple-scan, then scan multiple pages on my scanner (in this case, a Lexmark X543dn), then only the first page appears in simple-scan. I can of course press Scan again to scan the next page, but with a network scanner this is tedious, as I have to enter a code on the scanner for every page, rather than just telling it to scan another page, or feeding a multi-page document into it. This has been reproducible since Maverick. WORKAROUND: Use XSane. See bug #717885 for original report against Maverick, detailed workflow and analysis. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 4 13:56:04 2016 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1620043/+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 1620043] Re: All but one page sent by network scanner are discarded
Unless there's evidence that the bug has been fixed (e.g. in the repository commit logs or release notes), it seems unlikely, given that it persists in the same form since I reported it 5 years ago. Also, it may have been intentional behavior (see bug #717885 for analysis). ** Description changed: If I press Scan in simple-scan, then scan multiple pages on my scanner (in this case, a Lexmark X543dn), then only the first page appears in simple-scan. I can of course press Scan again to scan the next page, but with a network scanner this is tedious, as I have to enter a code on the scanner for every page, rather than just telling it to scan another page, or feeding a multi-page document into it. This has been reproducible since Maverick. WORKAROUND: Use XSane. + + See bug #717885 for original report against Maverick, detailed workflow + and analysis. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 4 13:56:04 2016 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1620043 Title: All but one page sent by network scanner are discarded Status in simple-scan package in Ubuntu: Incomplete Bug description: If I press Scan in simple-scan, then scan multiple pages on my scanner (in this case, a Lexmark X543dn), then only the first page appears in simple-scan. I can of course press Scan again to scan the next page, but with a network scanner this is tedious, as I have to enter a code on the scanner for every page, rather than just telling it to scan another page, or feeding a multi-page document into it. This has been reproducible since Maverick. WORKAROUND: Use XSane. See bug #717885 for original report against Maverick, detailed workflow and analysis. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 4 13:56:04 2016 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1620043/+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 815856] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734367/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734368/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734363/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734364/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734365/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734361/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734366/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] Re: On Lexmark X543dn, "All pages from feeder" only returns one page
apport information ** Tags added: apport-collected xenial ** Description changed: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". + --- + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2014-11-26 (648 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + MachineType: TranquilPC IXL + Package: simple-scan 3.20.0-0ubuntu1 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 + Tags: xenial + Uname: Linux 4.4.0-34-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) + UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video + _MarkForUpload: True + dmi.bios.date: 01/14/2011 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: DH67CF + dmi.board.vendor: Intel Corporation + dmi.board.version: AAG10215-203 + dmi.chassis.type: 3 + dmi.chassis.vendor: TranquilPC + dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: + dmi.product.name: IXL + dmi.sys.vendor: TranquilPC ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734360/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] SimpleScanLog.txt
apport information ** Attachment added: "SimpleScanLog.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734370/+files/SimpleScanLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734371/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] DriverPackageVersions.txt
apport information ** Attachment added: "DriverPackageVersions.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734362/+files/DriverPackageVersions.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 815856] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/815856/+attachment/4734369/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/815856 Title: On Lexmark X543dn, "All pages from feeder" only returns one page Status in simple-scan package in Ubuntu: Incomplete Bug description: When I use simple-scan 2.32.0.1 with my Lexmark X543dn MFC, and tick "All pages from feeder", the scanner correctly scans all pages, and the Lexmark progress dialog shows the data for each page being received, but simple-scan malfunctions in two ways: 1. Only the first page is actually displayed. 2. After scanning all the pages, the Lexmark dialog that comes up at the start of a scan job is displayed again, which is unnecessary. So, there seems to be some slight communication problem: a case of "so near, and yet so far"! See bug 717885 for scanning with "Single Page". --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL Package: simple-scan 3.20.0-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare src sudo vboxusers video _MarkForUpload: True dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/815856/+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 1620043] [NEW] All but one page sent by network scanner are discarded
Public bug reported: If I press Scan in simple-scan, then scan multiple pages on my scanner (in this case, a Lexmark X543dn), then only the first page appears in simple-scan. I can of course press Scan again to scan the next page, but with a network scanner this is tedious, as I have to enter a code on the scanner for every page, rather than just telling it to scan another page, or feeding a multi-page document into it. See bug 815856 for scanning with "All pages from feeder."; see bug 717885 for the same bug in maverick, and for an elaboration of the workflow used. Also note that this works with XSane (again, more details in bug 717885). I am filing a new bug as requested by penalvch in comment #9 on that bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 4 13:56:04 2016 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1620043 Title: All but one page sent by network scanner are discarded Status in simple-scan package in Ubuntu: New Bug description: If I press Scan in simple-scan, then scan multiple pages on my scanner (in this case, a Lexmark X543dn), then only the first page appears in simple-scan. I can of course press Scan again to scan the next page, but with a network scanner this is tedious, as I have to enter a code on the scanner for every page, rather than just telling it to scan another page, or feeding a multi-page document into it. See bug 815856 for scanning with "All pages from feeder."; see bug 717885 for the same bug in maverick, and for an elaboration of the workflow used. Also note that this works with XSane (again, more details in bug 717885). I am filing a new bug as requested by penalvch in comment #9 on that bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: simple-scan 3.20.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 4 13:56:04 2016 InstallationDate: Installed on 2014-11-26 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: TranquilPC IXL ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to xenial on 2016-07-25 (40 days ago) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1620043/+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 1606959] Re: DPI setting is not correctly calculated on Ubuntu GNOME
Wow, fast fix, thanks Chad! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1606959 Title: DPI setting is not correctly calculated on Ubuntu GNOME Status in chromium-browser package in Ubuntu: Fix Committed Bug description: On Ubuntu GNOME 16.04 on my Retina MacBook Pro, chromium-browser, unlike any other app I've found, gets the wrong DPI, and starts up unscaled. On investigation, this appears to be because of a bug in desktop_screen_x11.cc (I checked this only in the sources for the currently shipped version of Chromium, against which I'm reporting this bug). The hardware is *correctly* queried via the GTK2 back-end in gtk2_ui.cc, and device_scale_factor is set to 2 in line 328 of desktop_screen_x11.cc. However, this is then unconditionally overridden lower down. In line 356, density_indicator is set to 8 (this corresponds to a scale factor of 1). The next few lines, guarded by #ifdef USE_GLIB, then try to read a value from the gsettings key /com/ubuntu/user-interface/scale- factor. Aside: Under Unity, I understand that this setting is populated with information about the connected displays (I did try to find where this happens, but I can only find references to the setting in unity- control-center, while presumably it must also be set whenever a new display is plugged or unplugged); under GNOME it seems not to be. The problem is that when the gsettings key /com/ubuntu/user-interface /scale-factor is empty, or absent, the default value of density_indicator is still used, overriding the hardware-provided value. The only circumstances in which the hardware-provided value will be used are when the key for the relevant display is explicitly set to 0. This means that scaling won't work on a GNOME system, which is ironic considering that the correct information has already been obtained from Gtk! As far as I can see, the fix is to change the setting of 8 in line 356 to 0, so that if no gsettings value can be obtained, then the hardware-supplied value, which has already been calculated, is used. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 51.0.2704.79-0ubuntu0.16.04.1.1242 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-eDP-1: edid-base64: AP///wAGEBigADAWAQSlHRJ4Am+xp1VMniUMUFQBAQEBAQEBAQEBAQEBAQEB4mgAoKBALmAwIDYAHrMQAAAa/ABDb2xvciBMQ0QKICAgEAAAEGM= dpms: On modes: 2560x1600 enabled: enabled status: connected Date: Wed Jul 27 15:14:57 2016 Desktop-Session: 'gnome' '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' Env: 'None' '/home/rrt/.local/lib/x86_64-linux-gnu' InstallationDate: Installed on 2015-12-28 (212 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Load-Avg-1min: 0.49 Load-Processes-Running-Percent: 0.1% MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to xenial on 2016-07-25 (2 days ago) dmi.bios.date: 09/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B16.1509081438 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" gconf-keys: /desktop/gnome/applications/browser/exec
[Desktop-packages] [Bug 1606959] Re: DPI setting is not correctly calculated on Ubuntu GNOME
I have traced this to an Ubuntu patch: debian/display-scaling-default- value The comment says: "Set default scaling to be 1:1, instead of using the hardware's reporting to define scaling by default. This is because hardware lies. Lots of it does." Unfortunately the solution, as far as I can tell, only works for Unity. Also, the use of com/ubuntu/user-interface/scale-factor poses the question: how does Unity get the right answer, and why is it worth trusting? Is it user-set? If it is user-set (which would explain why I couldn't find an automatic setting anywhere in the Unity code!), then it would be reasonable to look up non-Unity user settings too, such as GNOME's HiDPI "Window scaling" setting /org/gnome/desktop/interface/scaling-factor. In general, the relevant setting should be read depending on the desktop (sigh, sounds like another need for an xdg-util, e.g. a new setting for xdg-settings). An alternative would be to patch GNOME's control center to set the same property; then at least the code would also work for GNOME. Ubuntu's setting is clearly superior to GNOME's in that it is per-screen (or to be precise, per display adaptor), not a single number. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1606959 Title: DPI setting is not correctly calculated on Ubuntu GNOME Status in chromium-browser package in Ubuntu: New Bug description: On Ubuntu GNOME 16.04 on my Retina MacBook Pro, chromium-browser, unlike any other app I've found, gets the wrong DPI, and starts up unscaled. On investigation, this appears to be because of a bug in desktop_screen_x11.cc (I checked this only in the sources for the currently shipped version of Chromium, against which I'm reporting this bug). The hardware is *correctly* queried via the GTK2 back-end in gtk2_ui.cc, and device_scale_factor is set to 2 in line 328 of desktop_screen_x11.cc. However, this is then unconditionally overridden lower down. In line 356, density_indicator is set to 8 (this corresponds to a scale factor of 1). The next few lines, guarded by #ifdef USE_GLIB, then try to read a value from the gsettings key /com/ubuntu/user-interface/scale- factor. Aside: Under Unity, I understand that this setting is populated with information about the connected displays (I did try to find where this happens, but I can only find references to the setting in unity- control-center, while presumably it must also be set whenever a new display is plugged or unplugged); under GNOME it seems not to be. The problem is that when the gsettings key /com/ubuntu/user-interface /scale-factor is empty, or absent, the default value of density_indicator is still used, overriding the hardware-provided value. The only circumstances in which the hardware-provided value will be used are when the key for the relevant display is explicitly set to 0. This means that scaling won't work on a GNOME system, which is ironic considering that the correct information has already been obtained from Gtk! As far as I can see, the fix is to change the setting of 8 in line 356 to 0, so that if no gsettings value can be obtained, then the hardware-supplied value, which has already been calculated, is used. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 51.0.2704.79-0ubuntu0.16.04.1.1242 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-eDP-1: edid-base64: AP///wAGEBigADAWAQSlHRJ4Am+xp1VMniUMUFQBAQEBAQEBAQEBAQEBAQEB4mgAoKBALmAwIDYAHrMQAAAa/ABDb2xvciBMQ0QKICAgEAAAEGM= dpms: On modes: 2560x1600 enabled: enabled status: connected Date: Wed Jul 27 15:14:57 2016 Desktop-Session: 'gnome' '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' Env: 'None' '/home/rrt/.local/lib/x86_64-linux-gnu' InstallationDate: Installed on 2015-12-28 (212 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Load-Avg-1min: 0.49 Load-Processes-Running-Percent: 0.1% MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro qui
[Desktop-packages] [Bug 1606959] Re: DPI setting is not correctly calculated on Ubuntu GNOME
Note to any users affected by this bug: a workaround is to manually
populate the /com/ubuntu/user-interface/scale-factor key. For example,
on my MacBook Pro, I set it using dconf-editor to:
{'eDP1': 16, 'DP1': 8, 'DP2': 8, 'HDMI1': 8, 'HDMI2': 8}
It is a fairly safe assumption that the internal display (eDP1) will
always be the same DPI, and that I will only use non-Retina external
displays. Most users should be in the same situation, unless they're
lucky enough to use secondary Retina displays sometimes, but not lucky
enough to use them always.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1606959
Title:
DPI setting is not correctly calculated on Ubuntu GNOME
Status in chromium-browser package in Ubuntu:
New
Bug description:
On Ubuntu GNOME 16.04 on my Retina MacBook Pro, chromium-browser,
unlike any other app I've found, gets the wrong DPI, and starts up
unscaled.
On investigation, this appears to be because of a bug in
desktop_screen_x11.cc (I checked this only in the sources for the
currently shipped version of Chromium, against which I'm reporting
this bug).
The hardware is *correctly* queried via the GTK2 back-end in
gtk2_ui.cc, and device_scale_factor is set to 2 in line 328 of
desktop_screen_x11.cc.
However, this is then unconditionally overridden lower down. In line
356, density_indicator is set to 8 (this corresponds to a scale factor
of 1). The next few lines, guarded by #ifdef USE_GLIB, then try to
read a value from the gsettings key /com/ubuntu/user-interface/scale-
factor.
Aside: Under Unity, I understand that this setting is populated with
information about the connected displays (I did try to find where this
happens, but I can only find references to the setting in unity-
control-center, while presumably it must also be set whenever a new
display is plugged or unplugged); under GNOME it seems not to be.
The problem is that when the gsettings key /com/ubuntu/user-interface
/scale-factor is empty, or absent, the default value of
density_indicator is still used, overriding the hardware-provided
value. The only circumstances in which the hardware-provided value
will be used are when the key for the relevant display is explicitly
set to 0.
This means that scaling won't work on a GNOME system, which is ironic
considering that the correct information has already been obtained
from Gtk!
As far as I can see, the fix is to change the setting of 8 in line 356
to 0, so that if no gsettings value can be obtained, then the
hardware-supplied value, which has already been calculated, is used.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 51.0.2704.79-0ubuntu0.16.04.1.1242
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
DRM.card0-DP-1:
edid-base64:
dpms: Off
modes:
enabled: disabled
status: disconnected
DRM.card0-DP-2:
edid-base64:
dpms: Off
modes:
enabled: disabled
status: disconnected
DRM.card0-HDMI-A-1:
edid-base64:
dpms: Off
modes:
enabled: disabled
status: disconnected
DRM.card0-HDMI-A-2:
edid-base64:
dpms: Off
modes:
enabled: disabled
status: disconnected
DRM.card0-eDP-1:
edid-base64:
AP///wAGEBigADAWAQSlHRJ4Am+xp1VMniUMUFQBAQEBAQEBAQEBAQEBAQEB4mgAoKBALmAwIDYAHrMQAAAa/ABDb2xvciBMQ0QKICAgEAAAEGM=
dpms: On
modes: 2560x1600
enabled: enabled
status: connected
Date: Wed Jul 27 15:14:57 2016
Desktop-Session:
'gnome'
'/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg'
'/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
Env:
'None'
'/home/rrt/.local/lib/x86_64-linux-gnu'
InstallationDate: Installed on 2015-12-28 (212 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Load-Avg-1min: 0.49
Load-Processes-Running-Percent: 0.1%
MachineType: Apple Inc. MacBookPro11,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to xenial on 2016-07-25 (2 days ago)
dmi.bios.date: 09/08/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B16.1509081438
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5
[Desktop-packages] [Bug 1606959] [NEW] DPI setting is not correctly calculated on Ubuntu GNOME
Public bug reported: On Ubuntu GNOME 16.04 on my Retina MacBook Pro, chromium-browser, unlike any other app I've found, gets the wrong DPI, and starts up unscaled. On investigation, this appears to be because of a bug in desktop_screen_x11.cc (I checked this only in the sources for the currently shipped version of Chromium, against which I'm reporting this bug). The hardware is *correctly* queried via the GTK2 back-end in gtk2_ui.cc, and device_scale_factor is set to 2 in line 328 of desktop_screen_x11.cc. However, this is then unconditionally overridden lower down. In line 356, density_indicator is set to 8 (this corresponds to a scale factor of 1). The next few lines, guarded by #ifdef USE_GLIB, then try to read a value from the gsettings key /com/ubuntu/user-interface/scale-factor. Aside: Under Unity, I understand that this setting is populated with information about the connected displays (I did try to find where this happens, but I can only find references to the setting in unity-control- center, while presumably it must also be set whenever a new display is plugged or unplugged); under GNOME it seems not to be. The problem is that when the gsettings key /com/ubuntu/user-interface /scale-factor is empty, or absent, the default value of density_indicator is still used, overriding the hardware-provided value. The only circumstances in which the hardware-provided value will be used are when the key for the relevant display is explicitly set to 0. This means that scaling won't work on a GNOME system, which is ironic considering that the correct information has already been obtained from Gtk! As far as I can see, the fix is to change the setting of 8 in line 356 to 0, so that if no gsettings value can be obtained, then the hardware- supplied value, which has already been calculated, is used. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 51.0.2704.79-0ubuntu0.16.04.1.1242 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-eDP-1: edid-base64: AP///wAGEBigADAWAQSlHRJ4Am+xp1VMniUMUFQBAQEBAQEBAQEBAQEBAQEB4mgAoKBALmAwIDYAHrMQAAAa/ABDb2xvciBMQ0QKICAgEAAAEGM= dpms: On modes: 2560x1600 enabled: enabled status: connected Date: Wed Jul 27 15:14:57 2016 Desktop-Session: 'gnome' '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' Env: 'None' '/home/rrt/.local/lib/x86_64-linux-gnu' InstallationDate: Installed on 2015-12-28 (212 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Load-Avg-1min: 0.49 Load-Processes-Running-Percent: 0.1% MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to xenial on 2016-07-25 (2 days ago) dmi.bios.date: 09/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B16.1509081438 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser --new-window %U\n'/desktop/gnome/url-handlers/https/enabled = b'false\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'false\n'/desktop/gnome/session/required_components/windowmanager = b'compiz\n'/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'Tangerine\n'/desktop/gnome/interface/gtk_theme = b'Human-Clearlooks\n' modified
[Desktop-packages] [Bug 1026869] Re: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this be
In fact, the situation appears to be more complicated, and points to a race condition of some sort. Having fixed the problem, I thought I'd try a theory about what causes it. So, I removed the dictionary and restarted Firefox. However, my spelling language was still correctly set to en-GB. Further, I can no longer reproduce the problem in a fresh profile, which of course does not have the dictionary installed. I should stress that the only thing I changed in any of this was my Firefox profile; I did not add, remove or otherwise alter any Ubuntu package. Hence, I really can't see what could have fixed the problem (since it has gone from being reproducible with a fresh profile to not being reproducible with a fresh profile), and I wonder whether there may be a race condition; not least, because the code that scans for dictionaries runs asynchronously. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1026869 Title: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this behavior Status in Mozilla Firefox: New Status in Hunspell: New Status in myspell: New Status in firefox package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Bug description: I've been searching for the solution to this bug for a long time. Firefox's spell-check, despite my locale being en-US, sets itself to en-GB, en-ZA or something en_US, which isn't even correct. The problem, it seems, is that Firefox uses whatever spell-checking backends you have installed - aspell, myspell, and hunspell. The result is that Firefox chooses, en-GB as the default spell checker more-often than not. So I uninstalled myspell, hunspell, and a package called firefox-locale-en and now everything is correct - only one spell checker is installed in Firefox. The language selector, however, always prompts to reinstall these backends whenever it is loaded. This Firefox add-on can assist, it gives you a list of dictionaries installed: https://addons.mozilla.org/en-US/firefox/addon/dictionary- switcher/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1026869/+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 1026869] Re: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this be
This bug continues to affect Firefox 40 in Ubuntu. I can confirm the workaround of installing a dictionary *in Firefox* for the desired default language. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1026869 Title: Firefox accepts dictionaries and spell check entries from every which spell check backend, leaving problems with defaults and the language selector enables this behavior Status in Mozilla Firefox: New Status in Hunspell: New Status in myspell: New Status in firefox package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Bug description: I've been searching for the solution to this bug for a long time. Firefox's spell-check, despite my locale being en-US, sets itself to en-GB, en-ZA or something en_US, which isn't even correct. The problem, it seems, is that Firefox uses whatever spell-checking backends you have installed - aspell, myspell, and hunspell. The result is that Firefox chooses, en-GB as the default spell checker more-often than not. So I uninstalled myspell, hunspell, and a package called firefox-locale-en and now everything is correct - only one spell checker is installed in Firefox. The language selector, however, always prompts to reinstall these backends whenever it is loaded. This Firefox add-on can assist, it gives you a list of dictionaries installed: https://addons.mozilla.org/en-US/firefox/addon/dictionary- switcher/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1026869/+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 1411621] Re: British English "-ize" endings not in dictionary
Works fine for me; did you have a particular example? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/1411621 Title: British English "-ize" endings not in dictionary Status in libreoffice-dictionaries package in Ubuntu: New Status in openoffice.org-dictionaries package in Ubuntu: New Bug description: The myspell-en-gb dictionary does not contain acceptable British English "-ize" endings. See http://www.oxforddictionaries.com/words/ize-ise-or-yse for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1411621/+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 1340722] Re: Screen order cannot be configured correctly
This bug is still a problem on an up-to-date 14.04 system. I'm sorry, I don't have time to test this with a development release (being a hardware problem, I presume it would not be interesting to try it with a VM installation). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1340722 Title: Screen order cannot be configured correctly Status in xorg package in Ubuntu: Incomplete Bug description: I have two screens driven by different graphics cards. I configure them in "Screen Display" settings to have the radeon-driven secondary screen on the left, and the intel-driven primary screen on the right. Every time I start up my computer and log in, they are the other way around (primary on the left, secondary on the right). This problem does not occur when I drive both monitors from the same graphics adaptor (but unfortunately I then get other problems!). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:29:34 2014 InstallationDate: Installed on 2011-05-24 (1143 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-16 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340722/+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 1340719] Re: Mouse droppings on radeon-controlled screen
Because of this bug I changed to an nvidia graphics card, so I don't have any further information on it, positive or negative. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1340719 Title: Mouse droppings on radeon-controlled screen Status in xorg package in Ubuntu: Incomplete Bug description: I have a two-monitor setup, one driven by the onboard Intel graphics, and the other by an ATI HD 5450-powered card, using the radeon driver. When I move the mouse pointer over the second, radeon-driven screen, I get mouse droppings. I tried to take a screenshot showing this, but the process of taking the screenshot (by pressing PrtSc) clears up the droppings. So does clicking on a window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:21:46 2014 InstallationDate: Installed on 2011-05-24 (1143 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-16 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340719/+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 771896] Re: No way to save current session
This is still working for me in GNOME 3 on Trusty. See https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1037616 comment #4 for a succinct summary of the rather involved way to activate the session saving/restoring workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/771896 Title: No way to save current session Status in Release Notes for Ubuntu: Invalid Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Precise: Fix Released Status in gnome-session source package in Quantal: Fix Released Bug description: Binary package hint: gnome-session There is no way I can find to set up a session the way you'd like to have Unity start up and then save that setup. This also affects the Classic session. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-session 2.32.1-0ubuntu19 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Wed Apr 27 09:27:01 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413) PackageArchitecture: all ProcEnviron: LANGUAGE=en PATH=(custom, user) LANG=C LC_MESSAGES=en_US.UTF-8 SHELL=/bin/csh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/771896/+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 1409978] [NEW] "guile-2.0 --version" runs without output and 100% CPU forever
Public bug reported:
This happens on one machine and not on another. It seems to be nothing
to do with the user's environment, since if I run "sudo guile-2.0
--version" I get the same problem.
strace shows:
strace guile --version
execve("/usr/bin/guile", ["guile", "--version"], [/* 121 vars */]) = 0
brk(0) = 0x16d8000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7eff80557000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/home/rrt/.local/lib/x86_64-linux-gnu/tls/x86_64/libguile-2.0.so.22",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/home/rrt/.local/lib/x86_64-linux-gnu/tls/x86_64", 0x7fff3f90b9e0) = -1
ENOENT (No such file or directory)
open("/home/rrt/.local/lib/x86_64-linux-gnu/tls/libguile-2.0.so.22",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/home/rrt/.local/lib/x86_64-linux-gnu/tls", 0x7fff3f90b9e0) = -1 ENOENT
(No such file or directory)
open("/home/rrt/.local/lib/x86_64-linux-gnu/x86_64/libguile-2.0.so.22",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/home/rrt/.local/lib/x86_64-linux-gnu/x86_64", 0x7fff3f90b9e0) = -1
ENOENT (No such file or directory)
open("/home/rrt/.local/lib/x86_64-linux-gnu/libguile-2.0.so.22",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/home/rrt/.local/lib/x86_64-linux-gnu", {st_mode=S_IFDIR|0750,
st_size=4096, ...}) = 0
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=188131, ...}) = 0
mmap(NULL, 188131, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7eff80529000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/usr/lib/libguile-2.0.so.22", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0 \225\4\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=1543432, ...}) = 0
mmap(NULL, 3693024, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7eff7ffb1000
mprotect(0x7eff800fb000, 2093056, PROT_NONE) = 0
mmap(0x7eff802fa000, 196608, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x149000) = 0x7eff802fa000
mmap(0x7eff8032a000, 51680, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7eff8032a000
close(3)= 0
open("/home/rrt/.local/lib/x86_64-linux-gnu/libpthread.so.0",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0po\0\0\0\0\0\0"..., 832)
= 832
fstat(3, {st_mode=S_IFREG|0755, st_size=141574, ...}) = 0
mmap(NULL, 2217264, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7eff7fd93000
mprotect(0x7eff7fdac000, 2093056, PROT_NONE) = 0
mmap(0x7eff7ffab000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x18000) = 0x7eff7ffab000
mmap(0x7eff7ffad000, 13616, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7eff7ffad000
close(3)= 0
open("/home/rrt/.local/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\37\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1845024, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7eff80528000
mmap(NULL, 3953344, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7eff7f9cd000
mprotect(0x7eff7fb88000, 2097152, PROT_NONE) = 0
mmap(0x7eff7fd88000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bb000) = 0x7eff7fd88000
mmap(0x7eff7fd8e000, 17088, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7eff7fd8e000
close(3)= 0
open("/home/rrt/.local/lib/x86_64-linux-gnu/libgc.so.1", O_RDONLY|O_CLOEXEC) =
-1 ENOENT (No such file or directory)
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/libgc.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\20\335\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=719995, ...}) = 0
mmap(NULL, 2573952, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7eff7f758000
mprotect(0x7eff7f789000, 2093056, PROT_NONE) = 0
mmap(0x7eff7f988000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3) = 0x7eff7f988000
mmap(0x7eff7f98b000, 267904, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7eff7f
[Desktop-packages] [Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
As I posted on the upstream bug, this bug would be a lot less annoying if: 1. The key short were listed in the Keyboard configuration applet, with appropriate greying out/some sort of explanatory message that comes up if you try to change it. 2. The workaround were only applied on machines that need it. -- 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/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings Status in Gnome Settings Daemon: Won't Fix Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-settings-daemon The current patch to bug 539477 breaks the super+p keybinding for all user applications when running gnone-settings-daemon. This behavior is hard-coded, not discoverable, and not configurable. The "workaround" is to disable parts of xrandr such that screen switching is no longer possible. The patch has been checked in and released as a bugfix to Ubuntu 10.10, causing regressions in several applications. For more details, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/ particularly https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/comments/68 and immediately above. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/694910/+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 1340733] [NEW] Mouse pointer disappears when switching users
Public bug reported: When I switch users from the GNOME Shell main menu, the GDM screen comes up without the mouse pointer. The keyboard still works, but even if I log in to another user using just the keyboard, the mouse pointer does not appear in the new user session. This problem is machine-specific: it doesn't happen on my desktop PC. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdm 3.10.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:45:06 2014 InstallationDate: Installed on 2014-04-24 (77 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1340733 Title: Mouse pointer disappears when switching users Status in “gdm” package in Ubuntu: New Bug description: When I switch users from the GNOME Shell main menu, the GDM screen comes up without the mouse pointer. The keyboard still works, but even if I log in to another user using just the keyboard, the mouse pointer does not appear in the new user session. This problem is machine-specific: it doesn't happen on my desktop PC. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdm 3.10.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:45:06 2014 InstallationDate: Installed on 2014-04-24 (77 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1340733/+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 1340722] [NEW] Screen order cannot be configured correctly
Public bug reported: I have two screens driven by different graphics cards. I configure them in "Screen Display" settings to have the radeon-driven secondary screen on the left, and the intel-driven primary screen on the right. Every time I start up my computer and log in, they are the other way around (primary on the left, secondary on the right). This problem does not occur when I drive both monitors from the same graphics adaptor (but unfortunately I then get other problems!). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:29:34 2014 InstallationDate: Installed on 2011-05-24 (1143 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-16 (85 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1340722 Title: Screen order cannot be configured correctly Status in “xorg” package in Ubuntu: New Bug description: I have two screens driven by different graphics cards. I configure them in "Screen Display" settings to have the radeon-driven secondary screen on the left, and the intel-driven primary screen on the right. Every time I start up my computer and log in, they are the other way around (primary on the left, secondary on the right). This problem does not occur when I drive both monitors from the same graphics adaptor (but unfortunately I then get other problems!). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:29:34 2014 InstallationDate: Installed on 2011-05-24 (1143 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-16 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340722/+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 1340719] [NEW] Mouse droppings on radeon-controlled screen
Public bug reported: I have a two-monitor setup, one driven by the onboard Intel graphics, and the other by an ATI HD 5450-powered card, using the radeon driver. When I move the mouse pointer over the second, radeon-driven screen, I get mouse droppings. I tried to take a screenshot showing this, but the process of taking the screenshot (by pressing PrtSc) clears up the droppings. So does clicking on a window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:21:46 2014 InstallationDate: Installed on 2011-05-24 (1143 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-16 (85 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1340719 Title: Mouse droppings on radeon-controlled screen Status in “xorg” package in Ubuntu: New Bug description: I have a two-monitor setup, one driven by the onboard Intel graphics, and the other by an ATI HD 5450-powered card, using the radeon driver. When I move the mouse pointer over the second, radeon-driven screen, I get mouse droppings. I tried to take a screenshot showing this, but the process of taking the screenshot (by pressing PrtSc) clears up the droppings. So does clicking on a window. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 11 13:21:46 2014 InstallationDate: Installed on 2011-05-24 (1143 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-16 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1340719/+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 564613] Re: Samsung NC10 internal mic always hissing
Closing this bug owing to age (not least, age of the hardware; also, the
kernel will have moved on) and lack of interest.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/564613
Title:
Samsung NC10 internal mic always hissing
Status in “alsa-driver” package in Ubuntu:
Invalid
Bug description:
On my Samsung NC10, with RealTek ALC272 sound card, recording from the
internal mic always comes with a substantial hiss, however I fiddle
with the settings. Under Windows, there is no problem. This bug is
similar to #448859, but it is not the same: I have no trouble making
audible recordings, and I do not have to turn up the input gain (I
have the input set in PulseAudio to "unamplified"). The problem is
simply that there is always hiss on the input.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-source (not installed)
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rrt2362 F mpd
rrt5828 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 22'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,144dca00,0011'
Controls : 18
Simple ctrls : 11
Date: Fri Apr 16 12:24:26 2010
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_GB.UTF-8
SourcePackage: alsa-driver
dmi.bios.date: 09/08/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 11CA.M015.20090908.RHU
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr11CA.M015.20090908.RHU:bd09/08/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/564613/+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 567519] Re: lircd(8) mentions non-existent /dev/input/uinput
This bug is still present in trusty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/567519 Title: lircd(8) mentions non-existent /dev/input/uinput Status in “lirc” package in Ubuntu: New Bug description: Binary package hint: lirc As far as I can see, this file is now called /dev/uinput. Please could you update the man page? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: lirc 0.8.6-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Tue Apr 20 21:39:42 2010 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 SourcePackage: lirc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/567519/+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 343407] Re: Please make it possible to send a report directly from the command line
I don't mind this any more, and apparently no-one else does either, so closing. ** Changed in: apport (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/343407 Title: Please make it possible to send a report directly from the command line Status in “apport” package in Ubuntu: Invalid Bug description: Binary package hint: apport apport now prompts before opening the web form. Please could a command-line flag be added to go directly to the web? You could have an option for each item in the interactive menu, e.g. --view --send --keep, and they need not even be mutually exclusive. The extra stage is useful if one is offline, if one is paranoid, or merely concerned about what will go in a particular bug report (e.g. I could imagine checking for certain packages), but most of the time the extra prompt is an annoyance. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: apport 0.145 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 SourcePackage: apport Uname: Linux 2.6.28-9-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/343407/+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 960392] Re: Please use xdg-mime and xdg-settings from xdg-utils
This bug is fixed in trusty. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/960392 Title: Please use xdg-mime and xdg-settings from xdg-utils Status in “chromium-browser” package in Ubuntu: Fix Released Bug description: chromium-browser has its own, out-of-date, versions of xdg-mime and xdg-settings. Apparently this is not necessary, as the Debian package simply depends on xdg-utils. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 17.0.963.79~r125985-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 20 16:52:19 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/home/rrt/local/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2012-03-06 (14 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/960392/+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 841371] Re: Shortcut for Ssharp doesn't work
This bug has since been fixed in the way I suggested. It is fixed at least in saucy. ** Changed in: libx11 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/841371 Title: Shortcut for Ssharp doesn't work Status in “libx11” package in Ubuntu: Fix Released Bug description: /usr/share/X11/locale/en_US.UTF-8/Compose contains the line: : "ẞ" Ssharp # LATIN CAPITAL LETTER SHARP S Unfortunately, this doesn't work, as the system doesn't seem to recognise the symbolic name "Ssharp". Replacing it with the unicode code makes it work: : "ẞ" U1E9E # (Ssharp) LATIN CAPITAL LETTER SHARP S ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libx11-data 2:1.4.2-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,imgjpeg,decor,text,scale,titleinfo,mousepoll,move,imgsvg,compiztoolbox,snap,regex,place,kde,imgpng,workarounds,grid,gnomecompat,dbus,resize,staticswitcher,session] CompositorRunning: compiz Date: Sun Sep 4 22:12:19 2011 Dependencies: DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.1.2, 2.6.38-11-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2000] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: TranquilPC IXL PackageArchitecture: all ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=b14299ce-70d0-4b10-ab62-aff152625f36 ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 version.ia32-libs: ia32-libs 20090808ubuntu13 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/841371/+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 1271238] [NEW] Typo in comment
Public bug reported: In the file /usr/share/X11/xkb/types/extra the word "captial" should be "capital" (occurs once, in line 116). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xkb-data 2.5.1-3ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Jan 21 16:50:24 2014 Dependencies: InstallationDate: Installed on 2011-05-24 (972 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True PackageArchitecture: all SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to saucy on 2013-10-10 (102 days ago) ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1271238 Title: Typo in comment Status in “xkeyboard-config” package in Ubuntu: New Bug description: In the file /usr/share/X11/xkb/types/extra the word "captial" should be "capital" (occurs once, in line 116). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xkb-data 2.5.1-3ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Jan 21 16:50:24 2014 Dependencies: InstallationDate: Installed on 2011-05-24 (972 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True PackageArchitecture: all SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to saucy on 2013-10-10 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1271238/+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 1018962] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1018962/+attachment/3945366/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1018962 Title: After login mouse pointer does not work Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: My display manager (as you should be able to see) is gdm, and my desktop is GNOME 3. When I log in, the mouse pointer is working; after I have pressed Enter to enter my password, and the screen refreshes (i.e. my session is starting up) the mouse pointer does not work: moving on the touchpad does not move the pointer. If I switch to another virtual terminal and back, the pointer starts to work again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.0-0ubuntu1~precise1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jun 28 19:18:57 2012 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Apple Inc. MacBookAir4,2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-25-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to precise on 2012-02-12 (136 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2011-10-14 (818 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True NonfreeKernelModules: ksplice_ag89wjej_vmlinux_new ksplice_ag89wjej ksplice_yffha1k4 ksplice_m3cri4fc ksplice_caeey7wk_vmlinux_new ksplice_caeey7wk ksplice_fgvotmio ksplice_8gzutgft ksplice_h80sediq_vmlinux_new ksplice_h80sediq ksplice_tnswy3vd ksplice_ioqpd5q7_vmlinux_new ksplice_ioqpd5q7 ksplice_zv0mstyh_vmlinux_new ksplice_zv0mstyh ksplice_oabb1i2u_vmlinux_new ksplice_oabb1i2u ksplice_cj7704vj_drm_new ksplice_cj7704vj ksplice_ilphyd4k_vmlinux_new ksplice_ilphyd4k ksplice_ktqcup59 ksplice_nhqzpgos ksplice_jenu4t7x ksplice_noyrwldn ksplice_gg497h90_vmlinux_new ksplice_gg497h90 ksplice_7z0ky6ly_jfs_new ksplice_7z0ky6ly ksplice_q2aucb73_mac80211_new ksplice_q2aucb73 ksplice_v81n4j7f_vmlinux_new ksplice_v81n4j7f ksplice_kd9blj1q ksplice_2laff7vz_vmlinux_new ksplice_2laff7vz ksplice_s5qb6lrf_vmlinux_new ksplice_s5qb6lrf Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-12 (89 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare src To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1018962/+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 1018962] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1018962/+attachment/3945367/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1018962 Title: After login mouse pointer does not work Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: My display manager (as you should be able to see) is gdm, and my desktop is GNOME 3. When I log in, the mouse pointer is working; after I have pressed Enter to enter my password, and the screen refreshes (i.e. my session is starting up) the mouse pointer does not work: moving on the touchpad does not move the pointer. If I switch to another virtual terminal and back, the pointer starts to work again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.0-0ubuntu1~precise1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jun 28 19:18:57 2012 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Apple Inc. MacBookAir4,2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-25-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to precise on 2012-02-12 (136 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2011-10-14 (818 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True NonfreeKernelModules: ksplice_ag89wjej_vmlinux_new ksplice_ag89wjej ksplice_yffha1k4 ksplice_m3cri4fc ksplice_caeey7wk_vmlinux_new ksplice_caeey7wk ksplice_fgvotmio ksplice_8gzutgft ksplice_h80sediq_vmlinux_new ksplice_h80sediq ksplice_tnswy3vd ksplice_ioqpd5q7_vmlinux_new ksplice_ioqpd5q7 ksplice_zv0mstyh_vmlinux_new ksplice_zv0mstyh ksplice_oabb1i2u_vmlinux_new ksplice_oabb1i2u ksplice_cj7704vj_drm_new ksplice_cj7704vj ksplice_ilphyd4k_vmlinux_new ksplice_ilphyd4k ksplice_ktqcup59 ksplice_nhqzpgos ksplice_jenu4t7x ksplice_noyrwldn ksplice_gg497h90_vmlinux_new ksplice_gg497h90 ksplice_7z0ky6ly_jfs_new ksplice_7z0ky6ly ksplice_q2aucb73_mac80211_new ksplice_q2aucb73 ksplice_v81n4j7f_vmlinux_new ksplice_v81n4j7f ksplice_kd9blj1q ksplice_2laff7vz_vmlinux_new ksplice_2laff7vz ksplice_s5qb6lrf_vmlinux_new ksplice_s5qb6lrf Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-12 (89 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare src To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1018962/+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 1018962] Re: After login mouse pointer does not work
I still get this bug in Saucy, but not in an easily-reproducible form: after login, the touch pad works fine, but if I leave the machine unattended, then when I come back, and the screen saver has activated, then sometimes either a) the button does not work (on my Macbook Air, this is pressing the touchpad down), but the pointer still moves when I move my finger on the pad; or b) the touchpad does not work at all (moving my finger on it does not move the pointer). In both cases, I can make the touchpad work again by switching to a text virtual terminal and then back to the X virtual terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1018962 Title: After login mouse pointer does not work Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: My display manager (as you should be able to see) is gdm, and my desktop is GNOME 3. When I log in, the mouse pointer is working; after I have pressed Enter to enter my password, and the screen refreshes (i.e. my session is starting up) the mouse pointer does not work: moving on the touchpad does not move the pointer. If I switch to another virtual terminal and back, the pointer starts to work again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.0-0ubuntu1~precise1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jun 28 19:18:57 2012 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Apple Inc. MacBookAir4,2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-25-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to precise on 2012-02-12 (136 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2011-10-14 (818 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True NonfreeKernelModules: ksplice_ag89wjej_vmlinux_new ksplice_ag89wjej ksplice_yffha1k4 ksplice_m3cri4fc ksplice_caeey7wk_vmlinux_new ksplice_caeey7wk ksplice_fgvotmio ksplice_8gzutgft ksplice_h80sediq_vmlinux_new ksplice_h80sediq ksplice_tnswy3vd ksplice_ioqpd5q7_vmlinux_new ksplice_ioqpd5q7 ksplice_zv0mstyh_vmlinux_new ksplice_zv0mstyh ksplice_oabb1i2u_vmlinux_new ksplice_oabb1i2u ksplice_cj7704vj_drm_new ksplice_cj7704vj ksplice_ilphyd4k_vmlinux_new ksplice_ilphyd4k ksplice_ktqcup59 ksplice_nhqzpgos ksplice_jenu4t7x ksplice_noyrwldn ksplice_gg497h90_vmlinux_new ksplice_gg497h90 ksplice_7z0ky6ly_jfs_new ksplice_7z0ky6ly ksplice_q2aucb73_mac80211_new ksplice_q2aucb73 ksplice_v81n4j7f_vmlinux_new ksplice_v81n4j7f ksplice_kd9blj1q ksplice_2laff7vz_vmlinux_new ksplice_2laff7vz ksplice_s5qb6lrf_vmlinux_new ksplice_s5qb6lrf Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-12 (89 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare src To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1018962/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1018962] Re: After login mouse pointer does not work
By the way, this statement in message #2 does not make sense: "Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful." I originally reported this bug against Ubuntu 12.04. There is no information on this bug for a release since then, so the assertion that "information from the prior release is already available" is false. (Although, this statement is not very clear, as it only implies that it means the release prior to the development release; it does not actually say so.) In any case, I've now supplied information about the 13.10 release, i.e. 3 releases more recent, which, even though it's not the development release (which I do not have the capability easily to test on this machine) does suggest that the problem is likely to persist there too. ** Tags added: apport-collected saucy ** Description changed: My display manager (as you should be able to see) is gdm, and my desktop is GNOME 3. When I log in, the mouse pointer is working; after I have pressed Enter to enter my password, and the screen refreshes (i.e. my session is starting up) the mouse pointer does not work: moving on the touchpad does not move the pointer. If I switch to another virtual terminal and back, the pointer starts to work again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.0-0ubuntu1~precise1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jun 28 19:18:57 2012 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Apple Inc. MacBookAir4,2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-25-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to precise on 2012-02-12 (136 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A + --- + ApportVersion: 2.12.5-0ubuntu2.2 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2011-10-14 (818 days ago) + InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) + MarkForUpload: True + NonfreeKernelModules: ksplice_ag89wjej_vmlinux_new ksplice_ag89wjej ksplice_yffha1k4 ksplice_m3cri4fc ksplice_caeey7wk_vmlinux_new ksplice_caeey7wk ksplice_fgvotmio ksplice_8gzutgft ksplice_h80sediq_vmlinux_new ksplice_h80sediq ksplice_tnswy3vd ksplice_ioqpd5q7_vmlinux_new ksplice_ioqpd5q7 ksplice_zv0mstyh_vmlinux_new ksplice_zv0mstyh ksplice_oabb1i2u_vmlinux_new ksplice_oabb1i2u ksplice_cj7704vj_drm_new ksplice_cj7704vj ksplice_ilphyd4k_vmlinux_new ksplice_ilphyd4k ksplice_ktqcup59 ksplice_nhqzpgos ksplice_jenu4t7x ksplice_noyrwldn ksplice_gg497h90_vmlinux_new ksplice_gg497h90 ksplice_7z0ky6ly_jfs_new ksplice_7z0ky6ly ksplice_q2aucb73_mac80211_new ksplice_q2aucb73 ksplice_v81n4j7f_vmlinux_new ksplice_v81n4j7f ksplice_kd9blj1q ksplice_2laff7vz_vmlinux_new ksplice_2laff7vz ksplice_s5qb6lrf_vmlinux_new ksplice_s5qb6lrf + Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 + Tags: saucy + Uname: Linux 3.11.0-14-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-10-12 (89 days ago) + UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare src -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.
[Desktop-packages] [Bug 1129679] Re: Server hangs preceded by "EQ overflowing."
Is #26 an automated message? The bug has been confirmed for the current release, 13.10 (see #25). Also, the wording of the message is a bit odd. It gives "there hasn't been any activity in [the bug] recently" as a justification for re- checking whether the bug still exists. I don't see why this might be an indication the bug is fixed: it just as likely indicates that the reporter believes they have supplied all requested information, and is now waiting for a fix. It's reasonable to ask whether a bug still exists in a new release, but it has already been confirmed that it does. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1129679 Title: Server hangs preceded by "EQ overflowing." Status in X.org xf86-video-intel: New Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: After upgrading to raring, my Lenovo Twist has begun to freeze and crash. Sometimes I am able to switch to vt1 to restart X, sometimes it just hangs hard. In all instances the behavior coincides with the "EQ overflowing" messages in Xorg.log. One saved X log contains: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fd5882eaef6] (EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x7fd5882cc21b] (EE) 2: /usr/bin/X (0x7fd58813b000+0x6d362) [0x7fd5881a8362] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fd582ee2000+0x5f34) [0x7fd582ee7f34] (EE) 4: /usr/bin/X (0x7fd58813b000+0x96597) [0x7fd5881d1597] (EE) 5: /usr/bin/X (0x7fd58813b000+0xbfd58) [0x7fd5881fad58] (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fd587242000+0xfbd0) [0x7fd587251bd0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7fd585f5f747] (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7fd58703a338] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm_intel.so.1 (0x7fd5847c9000+0x5a37) [0x7fd5847cea37] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x12f54) [0x7fd5849fbf54] (EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x29857) [0x7fd584a12857] (EE) 12: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x124b5) [0x7fd5849fb4b5] (EE) 13: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0xf9b48) [0x7fd584ae2b48] (EE) 14: /usr/bin/X (0x7fd58813b000+0x139679) [0x7fd588274679] (EE) 15: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0xfac15) [0x7fd584ae3c15] (EE) 16: /usr/bin/X (0x7fd58813b000+0x1331be) [0x7fd58826e1be] (EE) 17: /usr/bin/X (0x7fd58813b000+0x58a41) [0x7fd588193a41] (EE) 18: /usr/bin/X (0x7fd58813b000+0x4754a) [0x7fd58818254a] (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fd585e8fea5] (EE) 20: /usr/bin/X (0x7fd58813b000+0x47891) [0x7fd588182891] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Mon Feb 18 17:47:38 2013 DistUpgraded: 2013-02-17 01:06:25,336 DEBUG The following packages are marked for removal: libcogl9 python-pyatspi2 libcaribou0 libcaribou-common linux-image-extra-3.5.0-23-generic python3.2-minimal python-pyatspi libsdl-mixer1.2 libtelepathy-logger2 libpython3.2 libcec1 linux-headers-3.5.0-22-generic linux-headers-3.5.0-17-generic libdns81 gir1.2-caribou-1.0 python3.2 caribou libisccc80 linux-image-3.5.0-23-generic liblwres80 libnux-3.0-0 libmikmod2 libdrm-nouveau1a linux-headers-3.5.0-23-generic libbind9-80 linux-headers-3.5.0-21 linux-headers-3.5.0-22 linux-headers-3.5.0-17 linux-headers-3.5.0-23 linux-headers-3.5.0-19 libisccfg82 libgrail5 linux-tools-3.5.0-17 linux-tools-3.5.0-22 google-earth-stable fuse-utils linux-headers-3.5.0-21-generic libisc83 libnux-3.0-common linux-headers-3.5.0-19-generic DistroCodename: raring DistroVariant: ubuntu InstallationDate: Installed on 2012-11-23 (87 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 33474HU MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=5bc29b22-60c8-4ab8-84ad-cd9d988a01d4 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to raring on 2013-02-17 (1 days ago) dmi.bios.date: 08/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GDET33WW (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 33474HU dmi.board.
[Desktop-packages] [Bug 960174] Re: Keyboard modifiers spontaneously reset
I no longer have this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/960174 Title: Keyboard modifiers spontaneously reset Status in “xorg-server” package in Ubuntu: Incomplete Bug description: For the last few days, I've found that some keyboard settings (for example, changing Caps Lock to be a Ctrl key), which I have set under "Keyboard Settings→Options…", spontaneously reset on one 12.04 machine; and always reset after suspend/resume on another. This seems to be accompanied by a message such as: [219372.505] (II) XKB: reuse xkmfile /var/lib/xkb/server- E9EA10154E11AFEF2F1D0F18AF3DCD3D803A1FF6.xkm in the X logs. The file thus reused is not the latest one in the directory. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: x11-xkb-utils 7.6+4 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 20 13:01:10 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: x11-xkb-utils UpgradeStatus: Upgraded to precise on 2012-03-06 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/960174/+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 1173073] Re: Broken sounds in Skype
I don't understand why this bug wasn't fixed by renaming /usr/bin/skype to /usr/bin/skype.real, and having a script /usr/bin/skype which simply runs: #!/bin/bash PULSE_LATENCY_MSEC=60 exec -a /usr/bin/skype /usr/bin/skype.real "$@" ? (I fixed this bug for myself with a similar script in ~/bin.) But anyway, only fixing the desktop file doesn't really count as a fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1173073 Title: Broken sounds in Skype Status in “pulseaudio” package in Ubuntu: Incomplete Status in “skype” package in Ubuntu: Fix Released Bug description: When skype notify something and play sound (for i.e., contact became online or send me message, or calling), it sounds with wheezing. In another programs all OK. If I playing this wav files all is OK too. robotex@robotex-laptop:~$ lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1173073/+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 1208485] Re: [Thinkpad T520] Skype audio in Saucy broken
I am getting exactly this problem. I don't have SkypeTab. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1208485 Title: [Thinkpad T520] Skype audio in Saucy broken Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: In the last week or so Skype audio in Saucy has broken. I mostly don't hear anything but occassionally when I try to make a test call a get loud distortion until I kill Skype (and in some cases I need to reboot to get rid of it). I am running Intel, Skype 4.2.0.11 (the multiarch binary for 12.04 from the skype.com). Skype is a core requirement for many of us to work, so this is a pretty critical bug. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.12-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1591 F pulseaudio /dev/snd/pcmC0D0c: jono 1591 F...m pulseaudio Date: Mon Aug 5 07:25:53 2013 InstallationDate: Installed on 2013-05-05 (92 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130504) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1208485/+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 708311] Re: Manually added startup application is deleted
It is precisely the version in ~/.local/share/applications that is overwritten. (That is where gnome-session-properties aka Startup Applications stores its desktop files.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708311 Title: Manually added startup application is deleted Status in “chromium-browser” package in Ubuntu: New Bug description: Binary package hint: gnome-session Since chromium-browser doesn't support X sessions, I tried adding a custom entry to Startup Applications. This works fine, but the .desktop file is regularly deleted. I am wondering if this happens whenever chromium is updated, because this happens once a day (I get it from the nightly build PPA). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-session-bin 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 Architecture: i386 Date: Wed Jan 26 21:12:46 2011 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 SourcePackage: gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708311/+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 1129679] Re: Server hangs preceded by "EQ overflowing."
No, Alt+Ctrl+F1 &c. were unresponsive: I could not switch to another VT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1129679 Title: Server hangs preceded by "EQ overflowing." Status in X.org xf86-video-intel: New Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: After upgrading to raring, my Lenovo Twist has begun to freeze and crash. Sometimes I am able to switch to vt1 to restart X, sometimes it just hangs hard. In all instances the behavior coincides with the "EQ overflowing" messages in Xorg.log. One saved X log contains: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fd5882eaef6] (EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x7fd5882cc21b] (EE) 2: /usr/bin/X (0x7fd58813b000+0x6d362) [0x7fd5881a8362] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fd582ee2000+0x5f34) [0x7fd582ee7f34] (EE) 4: /usr/bin/X (0x7fd58813b000+0x96597) [0x7fd5881d1597] (EE) 5: /usr/bin/X (0x7fd58813b000+0xbfd58) [0x7fd5881fad58] (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fd587242000+0xfbd0) [0x7fd587251bd0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7fd585f5f747] (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7fd58703a338] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm_intel.so.1 (0x7fd5847c9000+0x5a37) [0x7fd5847cea37] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x12f54) [0x7fd5849fbf54] (EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x29857) [0x7fd584a12857] (EE) 12: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x124b5) [0x7fd5849fb4b5] (EE) 13: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0xf9b48) [0x7fd584ae2b48] (EE) 14: /usr/bin/X (0x7fd58813b000+0x139679) [0x7fd588274679] (EE) 15: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0xfac15) [0x7fd584ae3c15] (EE) 16: /usr/bin/X (0x7fd58813b000+0x1331be) [0x7fd58826e1be] (EE) 17: /usr/bin/X (0x7fd58813b000+0x58a41) [0x7fd588193a41] (EE) 18: /usr/bin/X (0x7fd58813b000+0x4754a) [0x7fd58818254a] (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fd585e8fea5] (EE) 20: /usr/bin/X (0x7fd58813b000+0x47891) [0x7fd588182891] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Mon Feb 18 17:47:38 2013 DistUpgraded: 2013-02-17 01:06:25,336 DEBUG The following packages are marked for removal: libcogl9 python-pyatspi2 libcaribou0 libcaribou-common linux-image-extra-3.5.0-23-generic python3.2-minimal python-pyatspi libsdl-mixer1.2 libtelepathy-logger2 libpython3.2 libcec1 linux-headers-3.5.0-22-generic linux-headers-3.5.0-17-generic libdns81 gir1.2-caribou-1.0 python3.2 caribou libisccc80 linux-image-3.5.0-23-generic liblwres80 libnux-3.0-0 libmikmod2 libdrm-nouveau1a linux-headers-3.5.0-23-generic libbind9-80 linux-headers-3.5.0-21 linux-headers-3.5.0-22 linux-headers-3.5.0-17 linux-headers-3.5.0-23 linux-headers-3.5.0-19 libisccfg82 libgrail5 linux-tools-3.5.0-17 linux-tools-3.5.0-22 google-earth-stable fuse-utils linux-headers-3.5.0-21-generic libisc83 libnux-3.0-common linux-headers-3.5.0-19-generic DistroCodename: raring DistroVariant: ubuntu InstallationDate: Installed on 2012-11-23 (87 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 33474HU MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=5bc29b22-60c8-4ab8-84ad-cd9d988a01d4 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to raring on 2013-02-17 (1 days ago) dmi.bios.date: 08/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GDET33WW (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 33474HU dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGDET33WW(1.03):bd08/30/2012:svnLENOVO:pn33474HU:pvrThinkPadTwist:rvnLENOVO:rn33474HU:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33474HU dmi.product.version: ThinkPad Twist dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.
[Desktop-packages] [Bug 1129679] Re: Server hangs preceded by "EQ overflowing."
I had this bug in an un-upgraded 12.10 system: my X server froze, the X server log shows a backtrace identical with that in the bug report. However, nothing crashes (I had to log in remotely and kill the X server manually to get control back). If I can provide any more information from system logs &c., do ask. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1129679 Title: Server hangs preceded by "EQ overflowing." Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: After upgrading to raring, my Lenovo Twist has begun to freeze and crash. Sometimes I am able to switch to vt1 to restart X, sometimes it just hangs hard. In all instances the behavior coincides with the "EQ overflowing" messages in Xorg.log. One saved X log contains: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fd5882eaef6] (EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x7fd5882cc21b] (EE) 2: /usr/bin/X (0x7fd58813b000+0x6d362) [0x7fd5881a8362] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fd582ee2000+0x5f34) [0x7fd582ee7f34] (EE) 4: /usr/bin/X (0x7fd58813b000+0x96597) [0x7fd5881d1597] (EE) 5: /usr/bin/X (0x7fd58813b000+0xbfd58) [0x7fd5881fad58] (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fd587242000+0xfbd0) [0x7fd587251bd0] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7fd585f5f747] (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7fd58703a338] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm_intel.so.1 (0x7fd5847c9000+0x5a37) [0x7fd5847cea37] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x12f54) [0x7fd5849fbf54] (EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x29857) [0x7fd584a12857] (EE) 12: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0x124b5) [0x7fd5849fb4b5] (EE) 13: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0xf9b48) [0x7fd584ae2b48] (EE) 14: /usr/bin/X (0x7fd58813b000+0x139679) [0x7fd588274679] (EE) 15: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fd5849e9000+0xfac15) [0x7fd584ae3c15] (EE) 16: /usr/bin/X (0x7fd58813b000+0x1331be) [0x7fd58826e1be] (EE) 17: /usr/bin/X (0x7fd58813b000+0x58a41) [0x7fd588193a41] (EE) 18: /usr/bin/X (0x7fd58813b000+0x4754a) [0x7fd58818254a] (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fd585e8fea5] (EE) 20: /usr/bin/X (0x7fd58813b000+0x47891) [0x7fd588182891] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Mon Feb 18 17:47:38 2013 DistUpgraded: 2013-02-17 01:06:25,336 DEBUG The following packages are marked for removal: libcogl9 python-pyatspi2 libcaribou0 libcaribou-common linux-image-extra-3.5.0-23-generic python3.2-minimal python-pyatspi libsdl-mixer1.2 libtelepathy-logger2 libpython3.2 libcec1 linux-headers-3.5.0-22-generic linux-headers-3.5.0-17-generic libdns81 gir1.2-caribou-1.0 python3.2 caribou libisccc80 linux-image-3.5.0-23-generic liblwres80 libnux-3.0-0 libmikmod2 libdrm-nouveau1a linux-headers-3.5.0-23-generic libbind9-80 linux-headers-3.5.0-21 linux-headers-3.5.0-22 linux-headers-3.5.0-17 linux-headers-3.5.0-23 linux-headers-3.5.0-19 libisccfg82 libgrail5 linux-tools-3.5.0-17 linux-tools-3.5.0-22 google-earth-stable fuse-utils linux-headers-3.5.0-21-generic libisc83 libnux-3.0-common linux-headers-3.5.0-19-generic DistroCodename: raring DistroVariant: ubuntu InstallationDate: Installed on 2012-11-23 (87 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 33474HU MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=5bc29b22-60c8-4ab8-84ad-cd9d988a01d4 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to raring on 2013-02-17 (1 days ago) dmi.bios.date: 08/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GDET33WW (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 33474HU dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGDET33WW(1.03):bd08/30/2012:svnLENOVO:pn33474HU:pvrThinkPadTwist:rvnLENOVO:rn33474HU:rvrWin8
[Desktop-packages] [Bug 1160073] [NEW] Typo in 70gconfd_path-on-session
Public bug reported: "additionnal" should be "additional" ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gconf2-common 3.2.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 22:30:47 2013 InstallationDate: Installed on 2011-05-24 (671 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gconf UpgradeStatus: Upgraded to quantal on 2012-10-19 (157 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1160073 Title: Typo in 70gconfd_path-on-session Status in “gconf” package in Ubuntu: New Bug description: "additionnal" should be "additional" ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gconf2-common 3.2.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 22:30:47 2013 InstallationDate: Installed on 2011-05-24 (671 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gconf UpgradeStatus: Upgraded to quantal on 2012-10-19 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1160073/+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 1159884] [NEW] References to wrong error file location in comments & doc strings
Public bug reported: In several scripts shipped as part of gdm, e.g. /etc/gdm/PreSession/Default, and /etc/gdm/Xsession, there are comments referring to logging being done to .xsession-errors. However, these days, logging from gdm goes to .cache/gdm/session.log. This out-of-date information is also contained in many .po files, and some Debian patches. Time for a global search-and-replace? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gdm 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 16:21:41 2013 InstallationDate: Installed on 2011-05-24 (670 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: gdm UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1159884 Title: References to wrong error file location in comments & doc strings Status in “gdm” package in Ubuntu: New Bug description: In several scripts shipped as part of gdm, e.g. /etc/gdm/PreSession/Default, and /etc/gdm/Xsession, there are comments referring to logging being done to .xsession-errors. However, these days, logging from gdm goes to .cache/gdm/session.log. This out-of-date information is also contained in many .po files, and some Debian patches. Time for a global search-and-replace? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gdm 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 16:21:41 2013 InstallationDate: Installed on 2011-05-24 (670 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: gdm UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1159884/+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 1159825] [NEW] Man page package patch needs updating
Public bug reported: In debian/patches/2002_gs_man_fix_debian.patch, occurrences of "gs-gpl" need to be replaced with "ghostscript" to give the correct paths in gs(1). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ghostscript 9.06~dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: ksplice_ll1dijxu_vmlinux_new ksplice_ll1dijxu ksplice_yd5h3vnq ksplice_vols3dds_vmlinux_new ksplice_vols3dds ksplice_69ryzznb ksplice_4h7n6pni_vmlinux_new ksplice_4h7n6pni ksplice_5ppx2n2l_vmlinux_new ksplice_5ppx2n2l ksplice_xms4wva9 ksplice_n8ksvevz_vmlinux_new ksplice_n8ksvevz ksplice_f6k5622a ksplice_zcc72zja_vmlinux_new ksplice_zcc72zja ksplice_2qld5jl4_bluetooth_new ksplice_2qld5jl4 ksplice_lti9cj5k_vmlinux_new ksplice_lti9cj5k ksplice_tyd4tmxo ksplice_sn48rf1u_vmlinux_new ksplice_sn48rf1u ksplice_kyjwccfl_xfs_new ksplice_kyjwccfl ksplice_5ep6irac ksplice_c2np3oe8 ksplice_pnbhxo6y ksplice_8qmwktvm ksplice_v7uc7vby_vmlinux_new ksplice_v7uc7vby ksplice_i1j4rzj0_vmlinux_new ksplice_i1j4rzj0 ksplice_c1cjlr9a_vmlinux_new ksplice_c1cjlr9a ksplice_znq141tz_vmlinux_new ksplice_znq141tz ksplice_5u9ktqmj_vmlinux_new ksplice_5u9ktqmj ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 14:52:35 2013 InstallationDate: Installed on 2011-05-24 (670 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) Lpstat: device for bunyan: ipp://192.168.1.77:631/ipp MachineType: TranquilPC IXL MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 , Postscript-Lexmark 20130226 (OpenPrinting LSB 3.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=b14299ce-70d0-4b10-ab62-aff152625f36 ro quiet splash vt.handoff=7 SourcePackage: ghostscript UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1159825 Title: Man page package patch needs updating Status in “ghostscript” package in Ubuntu: New Bug description: In debian/patches/2002_gs_man_fix_debian.patch, occurrences of "gs- gpl" need to be replaced with "ghostscript" to give the correct paths in gs(1). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ghostscript 9.06~dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: ksplice_ll1dijxu_vmlinux_new ksplice_ll1dijxu ksplice_yd5h3vnq ksplice_vols3dds_vmlinux_new ksplice_vols3dds ksplice_69ryzznb ksplice_4h7n6pni_vmlinux_new ksplice_4h7n6pni ksplice_5ppx2n2l_vmlinux_new ksplice_5ppx2n2l ksplice_xms4wva9 ksplice_n8ksvevz_vmlinux_new ksplice_n8ksvevz ksplice_f6k5622a ksplice_zcc72zja_vmlinux_new ksplice_zcc72zja ksplice_2qld5jl4_bluetooth_new ksplice_2qld5jl4 ksplice_lti9cj5k_vmlinux_new ksplice_lti9cj5k ksplice_tyd4tmxo ksplice_sn48rf1u_vmlinux_new ksplice_sn48rf1u ksplice_kyjwccfl_xfs_new ksplice_kyjwccfl ksplice_5ep6irac ksplice_c2np3oe8 ksplice_pnbhxo6y ksplice_8qmwktvm ksplice_v7uc7vby_vmlinux_new ksplice_v7uc7vby ksplice_i1j4rzj0_vmlinux_new ksplice_i1j4rzj0 ksplice_c1cjlr9a_vmlinux_new ksplice_c1cjlr9a ksplice_znq141tz_vmlinux_new ksplice_znq141tz ksplice_5u9ktqmj_vmlinux_new ksplice_5u9ktqmj ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 14:52:35 2013 InstallationDate: Installed on 2011-05-24 (670 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) Lpstat: device for bunyan: ipp://192.168.1.77:631/ipp MachineType: TranquilPC IXL MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 , Postscript-Lexmark 20130226 (OpenPrinting LSB 3.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=b14299ce-70d0-4b10-ab62-aff152625f36 ro quiet splash vt.handoff=7 SourcePackage: ghostscript UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.m
[Desktop-packages] [Bug 1159825] Re: Man page package patch needs updating
(This bug should probably be forwarded to Debian, but I reported it against Ubuntu as the version of ghostscript in Ubuntu is newer than that in Debian.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1159825 Title: Man page package patch needs updating Status in “ghostscript” package in Ubuntu: New Bug description: In debian/patches/2002_gs_man_fix_debian.patch, occurrences of "gs- gpl" need to be replaced with "ghostscript" to give the correct paths in gs(1). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ghostscript 9.06~dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: ksplice_ll1dijxu_vmlinux_new ksplice_ll1dijxu ksplice_yd5h3vnq ksplice_vols3dds_vmlinux_new ksplice_vols3dds ksplice_69ryzznb ksplice_4h7n6pni_vmlinux_new ksplice_4h7n6pni ksplice_5ppx2n2l_vmlinux_new ksplice_5ppx2n2l ksplice_xms4wva9 ksplice_n8ksvevz_vmlinux_new ksplice_n8ksvevz ksplice_f6k5622a ksplice_zcc72zja_vmlinux_new ksplice_zcc72zja ksplice_2qld5jl4_bluetooth_new ksplice_2qld5jl4 ksplice_lti9cj5k_vmlinux_new ksplice_lti9cj5k ksplice_tyd4tmxo ksplice_sn48rf1u_vmlinux_new ksplice_sn48rf1u ksplice_kyjwccfl_xfs_new ksplice_kyjwccfl ksplice_5ep6irac ksplice_c2np3oe8 ksplice_pnbhxo6y ksplice_8qmwktvm ksplice_v7uc7vby_vmlinux_new ksplice_v7uc7vby ksplice_i1j4rzj0_vmlinux_new ksplice_i1j4rzj0 ksplice_c1cjlr9a_vmlinux_new ksplice_c1cjlr9a ksplice_znq141tz_vmlinux_new ksplice_znq141tz ksplice_5u9ktqmj_vmlinux_new ksplice_5u9ktqmj ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 14:52:35 2013 InstallationDate: Installed on 2011-05-24 (670 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) Lpstat: device for bunyan: ipp://192.168.1.77:631/ipp MachineType: TranquilPC IXL MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 , Postscript-Lexmark 20130226 (OpenPrinting LSB 3.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=b14299ce-70d0-4b10-ab62-aff152625f36 ro quiet splash vt.handoff=7 SourcePackage: ghostscript UpgradeStatus: Upgraded to quantal on 2012-10-19 (156 days ago) dmi.bios.date: 01/14/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0098.2011.0114.1739 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-203 dmi.chassis.type: 3 dmi.chassis.vendor: TranquilPC dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0098.2011.0114.1739:bd01/14/2011:svnTranquilPC:pnIXL:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-203:cvnTranquilPC:ct3:cvr: dmi.product.name: IXL dmi.sys.vendor: TranquilPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1159825/+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 844103] Re: GDM 3.0 and higher ignores /etc/environment
@sefs, see fix in comment #6, which involves rebuilding gdm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/844103 Title: GDM 3.0 and higher ignores /etc/environment Status in GDM: The Gnome Display Manager: Fix Released Status in “gdm” package in Ubuntu: Fix Released Bug description: When I login in via gdm /sbin is not in my $PATH. 10:07:37 - flash:[~] echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/games:/home/bdmurray/bin/:/home/bdmurray/bin/ However, if I ssh to my system it is set: 10:13:38 - flash:[~] ssh localhost bdmurray@localhost's password: bdmurray@flash:[~] echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/home/bdmurray/bin/ ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gdm 3.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 CheckboxSubmission: fee5e196cb921cbd36888f428b38b488 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Wed Sep 7 10:06:24 2011 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: gdm UpgradeStatus: Upgraded to oneiric on 2011-09-06 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/844103/+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 689593] Re: 2x100% CPU and memory usage growth when setting bootable flag in palimpsest
By the way, not even a comment from an Ubuntu maintainer for 2 years, and yet using Startup Disk Creator is the official way to create install media. Imagine the scenario which must've happened more than once: Ubuntu Enthusiast: Here, I'll make you a USB stick so you can try it…wait…oh, my computer's frozen! Potential Ubuntu user: Thanks, I'll stick with Windows/Mac OS. [optional: Ubuntu Enthusiast: Yeah, I think I might switch back.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/689593 Title: 2x100% CPU and memory usage growth when setting bootable flag in palimpsest Status in abstraction for enumerating and managing block devices: New Status in “gnome-disk-utility” package in Ubuntu: Confirmed Bug description: When unsetting the bootable flag on a partition using palimpsest, the following things happen: - udisks-helper-modify-partition and udisks-daemon processes use 100% CPU each - udisks-daemon chews about 18MiB of memory each second This problem exists regardless of whether the partition is mounted or not. natty gnome-disk-utility 2.32.1-0ubuntu3 udisks 1.0.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/689593/+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 689593] Re: 2x100% CPU and memory usage growth when setting bootable flag in palimpsest
Same here in 12.10, when using Startup Disk Creator. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/689593 Title: 2x100% CPU and memory usage growth when setting bootable flag in palimpsest Status in abstraction for enumerating and managing block devices: New Status in “gnome-disk-utility” package in Ubuntu: Confirmed Bug description: When unsetting the bootable flag on a partition using palimpsest, the following things happen: - udisks-helper-modify-partition and udisks-daemon processes use 100% CPU each - udisks-daemon chews about 18MiB of memory each second This problem exists regardless of whether the partition is mounted or not. natty gnome-disk-utility 2.32.1-0ubuntu3 udisks 1.0.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/689593/+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 1087075] Re: Duplex options ignored for printing Postscript
To clarify: I can print PDF duplex fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1087075 Title: Duplex options ignored for printing Postscript Status in “cups” package in Ubuntu: New Bug description: Printing a Postscript file using lp -o Duplex=DuplexNoTumble foo.ps does not give duplex output. I have read other bug reports, turned collation off &c. and I can't see anything else that might be causing the problem. Printing from the gtk print dialog, the duplex setting I choose is respected, but because of a font-related bug with gtkprint, I'm using the lp command directly to print my Postscript file. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Dec 6 00:59:07 2012 InstallationDate: Installed on 2011-10-14 (418 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for bunyan: dnssd://Lexmark%20X543._ipp._tcp.local/ MachineType: Apple Inc. MacBookAir4,2 MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-10-20 (46 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1087075/+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 1087075] Re: Duplex options ignored for printing Postscript
On further investigation, I cannot print a Postscript file duplex at all, either using lp or from Evince, so the problem appears to be with CUPS's Postscript backend. ** Summary changed: - Command-line duplex option to lp is ignored + Duplex options ignored for printing Postscript -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1087075 Title: Duplex options ignored for printing Postscript Status in “cups” package in Ubuntu: New Bug description: Printing a Postscript file using lp -o Duplex=DuplexNoTumble foo.ps does not give duplex output. I have read other bug reports, turned collation off &c. and I can't see anything else that might be causing the problem. Printing from the gtk print dialog, the duplex setting I choose is respected, but because of a font-related bug with gtkprint, I'm using the lp command directly to print my Postscript file. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Dec 6 00:59:07 2012 InstallationDate: Installed on 2011-10-14 (418 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for bunyan: dnssd://Lexmark%20X543._ipp._tcp.local/ MachineType: Apple Inc. MacBookAir4,2 MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-10-20 (46 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1087075/+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 1010909] Re: permission denied: /usr/bin/{mktexpk, mktextfm}
This bug appears to be the problem reported here:
http://ubuntuforums.org/showthread.php?p=8690020
In short, the problem is that the apparmor profile for evince does not
allow the font files to be written.
Unfortunately, the algorithm used by the TeXLive scripts to decide where
to write generated font files is complicated. For example, in my case,
they seem to be written under
$HOME/texmf/fonts
but I also have files generated in the recent past (perhaps with a
previous version of TeXLive?) under $HOME/.texmf-var/fonts
and there are other possibilities, I believe. Hence, finding a solution
that is both secure and reliable requires input from a TeXpert.
For the moment I have simply disabled Evince's apparmor profile.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-bin in Ubuntu.
https://bugs.launchpad.net/bugs/1010909
Title:
permission denied: /usr/bin/{mktexpk,mktextfm}
Status in “texlive-bin” package in Ubuntu:
Confirmed
Bug description:
I think there's a bug with mktexpk and mktextfm:
I get the following:
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 cmtt7
mktexpk: don't know how to create bitmap font for cmtt7.
kpathsea: Appending font creation commands to missfont.log.
page: Warning: font `cmtt7' at 600x600 not found, trying `cmr10' instead
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600
cmcsc14
/usr/bin/mktexpk: 1: /usr/bin/mktexpk: /usr/share/texmf/web2c/mktexnam:
Permission denied
mktexpk: / already exists.
/usr/bin/mktexpk: 210: /usr/bin/mktexpk: /usr/share/texmf/web2c/mktexupd:
Permission denied
[...]
and later on:
kpathsea: Running mktextfm cmssbx20
/usr/bin/mktextfm: 1: /usr/bin/mktextfm: /usr/share/texmf/web2c/mktexnam:
Permission denied
/usr/bin/mktextfm: 75: /usr/bin/mktextfm: /usr/share/texmf/web2c/mktexdir:
Permission denied
mktextfm: mktexdir failed.
System is:
Description: Ubuntu 12.04 LTS
Release: 12.04
Package is:
texlive-binaries:
Installiert: 2009-11ubuntu2
Kandidat:2009-11ubuntu2
Versionstabelle:
*** 2009-11ubuntu2 0
500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: texlive-binaries 2009-11ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 9 17:05:03 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/zsh
SourcePackage: texlive-bin
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1010909/+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 1010909] Re: permission denied: /usr/bin/{mktexpk, mktextfm}
(The suggestion of running the commands with sudo is a workaround, but
it's not a fix; meanwhile, the bug continues to exist in at least
quantal.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-bin in Ubuntu.
https://bugs.launchpad.net/bugs/1010909
Title:
permission denied: /usr/bin/{mktexpk,mktextfm}
Status in “texlive-bin” package in Ubuntu:
Confirmed
Bug description:
I think there's a bug with mktexpk and mktextfm:
I get the following:
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 cmtt7
mktexpk: don't know how to create bitmap font for cmtt7.
kpathsea: Appending font creation commands to missfont.log.
page: Warning: font `cmtt7' at 600x600 not found, trying `cmr10' instead
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600
cmcsc14
/usr/bin/mktexpk: 1: /usr/bin/mktexpk: /usr/share/texmf/web2c/mktexnam:
Permission denied
mktexpk: / already exists.
/usr/bin/mktexpk: 210: /usr/bin/mktexpk: /usr/share/texmf/web2c/mktexupd:
Permission denied
[...]
and later on:
kpathsea: Running mktextfm cmssbx20
/usr/bin/mktextfm: 1: /usr/bin/mktextfm: /usr/share/texmf/web2c/mktexnam:
Permission denied
/usr/bin/mktextfm: 75: /usr/bin/mktextfm: /usr/share/texmf/web2c/mktexdir:
Permission denied
mktextfm: mktexdir failed.
System is:
Description: Ubuntu 12.04 LTS
Release: 12.04
Package is:
texlive-binaries:
Installiert: 2009-11ubuntu2
Kandidat:2009-11ubuntu2
Versionstabelle:
*** 2009-11ubuntu2 0
500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: texlive-binaries 2009-11ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 9 17:05:03 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/zsh
SourcePackage: texlive-bin
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1010909/+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 1087075] [NEW] Command-line duplex option to lp is ignored
Public bug reported: Printing a Postscript file using lp -o Duplex=DuplexNoTumble foo.ps does not give duplex output. I have read other bug reports, turned collation off &c. and I can't see anything else that might be causing the problem. Printing from the gtk print dialog, the duplex setting I choose is respected, but because of a font-related bug with gtkprint, I'm using the lp command directly to print my Postscript file. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Dec 6 00:59:07 2012 InstallationDate: Installed on 2011-10-14 (418 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for bunyan: dnssd://Lexmark%20X543._ipp._tcp.local/ MachineType: Apple Inc. MacBookAir4,2 MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-10-20 (46 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1087075 Title: Command-line duplex option to lp is ignored Status in “cups” package in Ubuntu: New Bug description: Printing a Postscript file using lp -o Duplex=DuplexNoTumble foo.ps does not give duplex output. I have read other bug reports, turned collation off &c. and I can't see anything else that might be causing the problem. Printing from the gtk print dialog, the duplex setting I choose is respected, but because of a font-related bug with gtkprint, I'm using the lp command directly to print my Postscript file. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Dec 6 00:59:07 2012 InstallationDate: Installed on 2011-10-14 (418 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for bunyan: dnssd://Lexmark%20X543._ipp._tcp.local/ MachineType: Apple Inc. MacBookAir4,2 MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-10-20 (46 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1087075/+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 891642] Re: gnome-power-statistics shows bogus "Energy when full" value
This bug still occurs intermittently in quantal with kernel 3.5.0-17-generic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/891642 Title: gnome-power-statistics shows bogus "Energy when full" value Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: gnome-power-statistics sometimes gets the wrong value for Energy when full, causing the battery indicator to show nearly empty when it's nowhere near empty. For example: slice 14:29:01 ~$ cat /sys/class/power_supply/BAT0/energy_full 6741 slice 14:31:52 ~$ cat /sys/class/power_supply/BAT0/energy_full_design 6700 slice 14:31:57 ~$ cat /sys/class/power_supply/BAT0/energy_now 2831 Meanwhile, gnome-power-statistics is correctly showing Energy (design) as 67.0Wh, but Energy when full as 633.7Wh, roughly a factor of 10 too high. Interestingly, although it then calculates that the battery has about 6.1% left, it still shows the time remaining correctly (about 2 hours). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Thu Nov 17 14:28:44 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/891642/+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 966005] Re: [media-keys] gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() while pushing brightness keys
*** This bug is a duplicate of bug 959874 *** https://bugs.launchpad.net/bugs/959874 The bug as originally reported is a duplicate of a fixed bug (good news for the original reporter, I hope!). The last report is a new bug which I'm also seeing, but with unofficial packages. If you see it with official packages, Pedro, please report it as a new bug. -- 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/966005 Title: [media-keys] gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() while pushing brightness keys Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Settings daemon died on pressing keyboard backlight brightness buttons on MacBook Air. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu2 Uname: Linux 3.3.0-030300-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 27 01:02:56 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/966005/+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 968431] Re: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete()
*** This bug is a duplicate of bug 959874 *** https://bugs.launchpad.net/bugs/959874 ** This bug is no longer a duplicate of bug 966005 [media-keys] gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() while pushing brightness keys ** This bug has been marked a duplicate of bug 959874 gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() -- 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/968431 Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete() Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Bug occured when computer start on Ubuntu 12.04 beta 1 ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Mar 29 19:05:30 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/968431/+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 966005] Re: [media-keys] gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() while pushing brightness keys
*** This bug is a duplicate of bug 959874 *** https://bugs.launchpad.net/bugs/959874 ** This bug has been marked a duplicate of bug 959874 gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() -- 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/966005 Title: [media-keys] gnome-settings-daemon crashed with SIGSEGV in ubuntu_osd_do_notification() while pushing brightness keys Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Settings daemon died on pressing keyboard backlight brightness buttons on MacBook Air. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.92-0ubuntu2 Uname: Linux 3.3.0-030300-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 27 01:02:56 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/966005/+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
