[Desktop-packages] [Bug 1551599] Re: Remove button missing after package installation
This bug is still present in Ubuntu Gnome 17.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1551599 Title: Remove button missing after package installation Status in One Hundred Papercuts: Confirmed Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Confirmed Bug description: [What Happens] == Installing -- 1. Open the Software app (GNOME Software). Search for clocks. 2. Click Install next to Clocks. 3. The Install button becomes insensitive and changes to Installing... 4. The Install button becomes sensitive again and changes back to Install (it should have changed to Remove) 5. If you click the Clocks row (still in the All page), the Clocks info page opens with an Install button (it should have a Launch button and a Remove button). 6. If you switch to the Installed page, Clocks correctly shows up with a Remove button. 7. If you click the Clocks row in the Installed page, the Clocks info page correctly opens with a Launch button and a Remove button. 8. Close the Software app then reopen it. Same results as #4-7 above. 9. $ pkill gnome-software 10. Open the Software app. Now Clocks shows up correctly in the All page with a Remove button and the Clocks info page correctly includes the Launch and Remove buttons but not the Install button. Removing 11. Click the Remove button to uninstall Clocks. 12. The Remove button becomes insensitive again and changes to Removing... 12. We basically get the same broken results as before. In the All page, the Clocks row shows Remove still. Clicking the Clocks row shows the Info page with Launch and Remove. One change is that in the Installed page, Clocks shows up twice, once with an Install button, once with a Remove button. Completely stopping the gnome-software process (via logging out or the pkill trick mentioned in #9) is necessary for the Software app to correctly register Clocks as being removed. I was unable to reproduce this bug with Fedora 24. See also bug 1582959 which is similar but a bit different. [Original bug report] = Used gnome-software to install a package. Once it was installed I expected to see an option to remove it. As can be seen all I see is the option to Install the package. If you click Install you are then given the option to remove the package. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 1 08:05:06 2016 InstallationDate: Installed on 2015-10-29 (123 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1551599/+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 1676918] Re: Kernel 4.10+ regression: blackscreen when trying to resume from suspend
** Summary changed: - blackscreen when trying to resume from suspend + Kernel 4.10+ regression: blackscreen when trying to resume from suspend ** Description changed: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 + + Update: So far I did not encounter any issues with suspend/resume with + Kernel 4.8 and 4.9. This seems to be a regression in 4.10. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1676918 Title: Kernel 4.10+ regression: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 Update: So far I did not encounter any issues with suspend/resume with Kernel 4.8 and 4.9. This seems to be a regression in 4.10. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1678436] [NEW] Gnome-Software does not install local .deb-files
Public bug reported: When trying to install a downloaded .deb-file through double clicking in Nautilus Gnome Software is started and offers an "Install"-Button, but when it is pressed nothing happens. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.7-0ubuntu2 Uname: Linux 4.8.17-040817-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 1 11:39:49 2017 InstallationDate: Installed on 2017-03-24 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1678436 Title: Gnome-Software does not install local .deb-files Status in gnome-software package in Ubuntu: New Bug description: When trying to install a downloaded .deb-file through double clicking in Nautilus Gnome Software is started and offers an "Install"-Button, but when it is pressed nothing happens. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.7-0ubuntu2 Uname: Linux 4.8.17-040817-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 1 11:39:49 2017 InstallationDate: Installed on 2017-03-24 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1678436/+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 1678432] [NEW] Gnome-Software shows an "Install"-Button for already installed software
Public bug reported: Sometimes The Gnome Software Center shows an "Install"-Button for Software that is already installed. Pressing it will cause a password prompt and after that the "Start"- and "Remove"-Buttons will appear. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.7-0ubuntu2 Uname: Linux 4.8.17-040817-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 1 11:33:45 2017 InstallationDate: Installed on 2017-03-24 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1678432 Title: Gnome-Software shows an "Install"-Button for already installed software Status in gnome-software package in Ubuntu: New Bug description: Sometimes The Gnome Software Center shows an "Install"-Button for Software that is already installed. Pressing it will cause a password prompt and after that the "Start"- and "Remove"-Buttons will appear. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.7-0ubuntu2 Uname: Linux 4.8.17-040817-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 1 11:33:45 2017 InstallationDate: Installed on 2017-03-24 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1678432/+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 1676918] Re: blackscreen when trying to resume from suspend
Got a blackscreen with Kernel 4.11. Unfortunately kern.log and syslog don't have any entries about it. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] Re: blackscreen when trying to resume from suspend
Trying Kernel 4.11 since yesterday. So far no blackscreens but I think I should test it for a longer duration. Unfortunately Kernel 4.11 is no real solution for me because of another suspend/resume bug that as far as I can tell at the moment might exist since Kernel 4.9. -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] Re: blackscreen when trying to resume from suspend
** Description changed: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. - --- + + I'm currently testing Kernel 4.8 from the mainline ppa because of this + other suspend resume bug, that appeared only with 17.04: + + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 + + --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1676918/+attachment/4849418/+files/JournalErrors.txt -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] Re: blackscreen when trying to resume from suspend
apport information ** Tags added: apport-collected wayland-session zesty ** Description changed: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. + --- + ApportVersion: 2.20.4-0ubuntu2 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 17.04 + InstallationDate: Installed on 2017-03-24 (4 days ago) + InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) + Package: systemd 232-19 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + Tags: zesty wayland-session + Uname: Linux 4.8.17-040817-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1676918/+attachment/4849417/+files/Dependencies.txt -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] Re: blackscreen when trying to resume from suspend
** Package changed: ubuntu => linux (Ubuntu) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 390989] Re: [SecurityRoadmap] Locked screen shows the desktop
The problem still occurs with 16.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/390989 Title: [SecurityRoadmap] Locked screen shows the desktop Status in GNOME Screensaver: Expired Status in gnome-screensaver package in Ubuntu: Fix Released Bug description: Ubuntu 9.04 When I lock the screen and arrives the next day, when I touch the keyboard and wakes the screen to enter my password an image of the desktop is shown under a very short period of time before the password prompt is shown. If someone has a camera it's possible to take a photo of the screen of how it looked just before it was locked. I'm using dual screen and a Nvidia built in driver. The image is shown in the laptop monitor, maybe on the extra screen that's cloned (hard to see because it's syncing to long to see). Please let me know if you need more information. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/390989/+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 1511735] Re: libnl: fail to bind() netlink sockets
This update broke Network-Manager on my system. Used these steps to manually downgrade libnl to get network connections working again. http://askubuntu.com/questions/727127/last-upgrade-crashes-network- manager-no-internet-connection-no-applet -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Fix Released Status in libnl3 package in Debian: Fix Released Bug description: [Triage Notes] The proposed fix for this bug in libnl3 caused a regression in trusty- proposed, tracked in bug 1539634. The regression is caused by a latent bug in Network Manager. We expect to fix this by landing a fix for the bug in Network Manager in trusty-updates at the same time as this fix. [Impact] * Applications in Trusty using libnl-3-200 which frequently open and close netlink sockets can easily fail when attempting to bind the local socket. The problem happens when libnl choose a port id already used by another application and subsequently libnl fails instead of trying another port id. The original bug was discovered when attempting to start a virtual machine under libvirt, which is a user of this library. * Backporting fixes from upstream release fixes a real bug in the current version of the library in Trusty. The alternative is for all applications to manually manage their local port allocation, or as upstream has accepted allowing libnl to attempt to try for other local ports. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. [Test Case] * On a Trusty 14.04 system 1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \ libnl-genl-3-dev libnl-route-3-200 \ make gcc build-essential libnl1 2. download and unpack attachment: lp_1511735_test.tar 3. Run testcases: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 6975 (pid: 6974) local port has been set by the libnl to 6975 (pid: 6975) ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975) libnl FAILED % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=6978 TEST (a)... Traceback (most recent call last): File "libnl3-test-rh1249158.py", line 226, in locals()["TEST_" + arg]() File "libnl3-test-rh1249158.py", line 140, in TEST_a sk = nl_get_socket() File "libnl3-test-rh1249158.py", line 115, in nl_get_socket raise IOError(-err, _nl_geterror()) OSError: [Errno 6] b'Unspecific failure' 4. After applying the updated packages: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 11295 (pid: 11294) local port has been set by the libnl to 2894081055 (pid: 11295) libnl OK % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=11296 TEST (a)... ...done TEST (b)... ...done TEST (c)... ...done TEST (d)... ...done [Regression Potential] * There are quite a few high profile packages that depend on this package, notably libvirt and network-manager. The complete list is here: # on Trusty % apt-rdepends -r libnl-3-200 | head -n 33 libnl-3-200 Reverse Depends: batctl (>= 2013.4.0-2) Reverse Depends: bmon (>= 1:3.1-1) Reverse Depends: crda (>= 1.1.2-1ubuntu2) Reverse Depends: hostapd (>= 1:2.1-0ubuntu1) Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1) Reverse Depends: iw (>= 3.4-1) Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1) Reverse Depends: kismet (>= 2013.03.R1b-3) Reverse Depends: knemo (>= 0.7.6-2) Reverse Depends: libfsobasics3 (>= 0.12.0-4) Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1) Reverse Depends: libnl-3-200-dbg (= 3.2.21-1) Reverse Depends: libnl-3-dev (= 3.2.21-1) Reverse Depends: libnl-cli-3-200 (= 3.2.21-1) Reverse Depends: libnl-genl-3-200 (= 3.2.21-1) Reverse Depends: libnl-nf-3-200 (= 3.2.21-1) Reverse Depends: libnl-route-3-200 (= 3.2.21-1) Reverse Depends: libnl-utils (>= 3.2.21-1) Reverse Depends: libnss-gw-name (>= 0.3-2) Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13) Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13) Reverse Depends: lowpan-test-tools (>= 0.3-1)
[Desktop-packages] [Bug 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design
Almost two years later now this "temporary" fallback is still present in the Xenial beta. Any chance that this behavior will get fixed or do we have to wait for Unity 8? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design Status in Onboard: Invalid Status in Unity: Invalid Status in onboard package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140413) Package: unity PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+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 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design
Any update on this? Lockscreen still falls back to gnome-screensaver after enabling accessibility. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design Status in Onboard on-screen keyboard: Invalid Status in Unity: Invalid Status in “onboard” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) Package: unity PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+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 1310404] [NEW] Enabling the onscreen keyboard in the accessibility menu changes lockscreen design
Public bug reported: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: onboard Importance: Undecided Status: New ** Affects: unity Importance: Undecided Status: New ** Affects: onboard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Also affects: onboard Importance: Undecided Status: New ** Also affects: unity Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design Status in Onboard on-screen keyboard: New Status in Unity: New Status in “onboard” package in Ubuntu: New Bug description: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+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 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design
Confirmed on askubuntu http://askubuntu.com/questions/449623/howto- restore-the-new-14-04-lockscreen/451451?noredirect=1#451451 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design Status in Onboard on-screen keyboard: New Status in Unity: New Status in “onboard” package in Ubuntu: New Bug description: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+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 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design
** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design Status in Onboard on-screen keyboard: New Status in Unity: New Status in “onboard” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) Package: unity PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+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 1310404] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1310404/+attachment/4090482/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design Status in Onboard on-screen keyboard: New Status in Unity: New Status in “onboard” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) Package: unity PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+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 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design
apport information ** Tags added: apport-collected ** Description changed: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.1-0ubuntu3 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2014-04-14 (6 days ago) + InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) + Package: unity + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 + Tags: trusty + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm lpadmin sambashare sudo + _MarkForUpload: True ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1310404/+attachment/4090481/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design Status in Onboard on-screen keyboard: New Status in Unity: New Status in “onboard” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: After enabling the onscreen keyboard in the accessibility menu the design of the lockscreen is changed to the old design of Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu4 [modified: usr/share/onboard/onboard-defaults.conf] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 21 00:16:10 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140413) Package: unity PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+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 1041935] Re: Simulated Secondary Click does not work
Still not working with eGalax touchscreen on 14.04 though it works correct with a mouse. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mousetweaks in Ubuntu. https://bugs.launchpad.net/bugs/1041935 Title: Simulated Secondary Click does not work Status in “mousetweaks” package in Ubuntu: Confirmed Bug description: I have activated the Simulated Secondary Click in System Settings - Universal Acces, but it does not work with any input device (1) convential mouse (2) egalax touchscreen (3) wacom ISDv4 90 Pen. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Sun Aug 26 15:11:51 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120821) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=de_DE:de LANG=de_DE.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mousetweaks/+bug/1041935/+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 1176567] Re: Firefox v20 startup is slow
Some additional information: apt-cache policy firefox firefox: Installiert: 25.0.1+build1-0ubuntu0.13.10.1 Installationskandidat: 25.0.1+build1-0ubuntu0.13.10.1 Versionstabelle: *** 25.0.1+build1-0ubuntu0.13.10.1 0 500 http://de.archive.ubuntu.com/ubuntu/ saucy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main i386 Packages 100 /var/lib/dpkg/status 24.0+build1-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages -- 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/1176567 Title: Firefox v20 startup is slow Status in “firefox” package in Ubuntu: Confirmed Bug description: lsb_release: Description: Ubuntu 13.04 Release: 13.04 apt-cache policy firefox: firefox: Installed: 20.0+build1-0ubuntu2 Candidate: 20.0+build1-0ubuntu2 Version table: *** 20.0+build1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status Even without addons on a fresh system and Firefox install, Firefox takes a while to start up. Once Firefox is running, a few seconds are needed before I can start typing a URL. The start up processes needs to be sped up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1176567/+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 1176567] Re: Firefox v20 startup is slow
Firefox needs endless time for starting or sometimes freezes while starting. This problem occured to me with 13.04 and 13.10 but only on my Wetab (a.k.a Exo-PC, a tablet with netbook hardware) not on any of my other computers. According to users of the wetab-community-forum this problem occured to them too with Ubuntu. Other distributions/operating system don't have this problem. -- 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/1176567 Title: Firefox v20 startup is slow Status in “firefox” package in Ubuntu: Confirmed Bug description: lsb_release: Description: Ubuntu 13.04 Release: 13.04 apt-cache policy firefox: firefox: Installed: 20.0+build1-0ubuntu2 Candidate: 20.0+build1-0ubuntu2 Version table: *** 20.0+build1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status Even without addons on a fresh system and Firefox install, Firefox takes a while to start up. Once Firefox is running, a few seconds are needed before I can start typing a URL. The start up processes needs to be sped up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1176567/+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
