[Desktop-packages] [Bug 2075334] Re: After upgrade to 24.04 the system now has audio problems.
I have also encountered a problem where the audio quits working. To correct the problem - I open sound settings and change "Configuration" to "Digital Stereo ..." and then back to "Digital Surround 5.1 ...". Thanks! -- 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/2075334 Title: After upgrade to 24.04 the system now has audio problems. Status in alsa-driver package in Ubuntu: New Bug description: I had no problems with Ubuntu 23.10 but upgraded to 24.04 as recommended by the "update-manager" options. The audio problem seemed to improve with the kernel 6.8.0.38. (I updated via update-manager interface.) (Previous update attempt via USB boot had much worse audio problems.) (I have another older PC running Ubuntu 24.04 that has no audio issues.) Please advise. Thanks! ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 31 08:04:58 2024 InstallationDate: Installed on 2024-06-01 (60 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: Dell Inc. OptiPlex 9020 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to noble on 2024-07-24 (7 days ago) dmi.bios.date: 12/27/2017 dmi.bios.release: 65.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 00V62H dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd12/27/2017:br65.21:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn00V62H:rvrA01:cvnDellInc.:ct15:cvr:sku05A4: dmi.product.name: OptiPlex 9020 dmi.product.sku: 05A4 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2075334/+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 2037004] Re: warnings in terminal with software-properties-gtk
Initially, the warning/error "udevadm hwdb is deprecated. Use systemd- hwdb instead." repeats 6 times (either as described above, or when running "ubuntu-drivers devices"). After adding ppa:graphics- drivers/ppa, the warning/error repeats 8 times. The number of repeats seems to correspond to the number of driver options (not counting nouveau). Also, nvidia-driver-545 appears after adding the ppa, but 550 does not. $ ubuntu-drivers devices udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. ... driver : nvidia-driver-545 - third-party non-free recommended driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-545-open - third-party non-free driver : nvidia-driver-535-server-open - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-535-server - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-535 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2037004 Title: warnings in terminal with software-properties-gtk Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: When running software-properties-gtk and switching to the "Additional Drivers" tab I saw the following warnings in my terminal: $ software-properties-gtk udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. udevadm hwdb is deprecated. Use systemd-hwdb instead. ... ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 11:49:24 2023 InstallationDate: Installed on 2018-08-10 (1868 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2037004/+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 2007742] Re: Can't update stage views actor
I can consistently trigger this issue by installing the Google Chrome deb (Version 110.0.5481.177) and resizing the window. journalctl will get filled with these errors while resizing. I am unsure if this is a Google Chrome issue or a Gnome issue? -- 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/2007742 Title: Can't update stage views actor Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: These messages repeat: [ 105.711276] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bba91da500] is on because it needs an allocation. [ 105.711772] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bbac95c330] is on because it needs an allocation. [ 105.711903] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bbae726860] is on because it needs an allocation. --- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 Uname: Linux 6.1.11-060111-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 21:54:39 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-22 (179 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-02-08 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+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 2007742] Re: Can't update stage views actor
Same issue w/ my system locking up for about 30 seconds to 1 minute each time it happens: Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e06fa94310] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e075f10b10] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e06fce46c0] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e07281faf0] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e072823850] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e07281e740] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e0728226d0] is on because it needs an allocation. My system is running Pop! OS 22.04 - it's not Ubuntu, but it is based on it and I figured this would be useful. jacob@jacob-hp-dev-one -- OS: Pop!_OS 22.04 LTS x86_64 Host: Dev One Notebook PC Kernel: 6.1.11-76060111-generic Uptime: 23 hours, 26 mins Packages: 2289 (dpkg), 16 (flatpak), 6 (snap) Shell: bash 5.1.16 Resolution: 1920x1080, 1920x1080 DE: GNOME 42.5 WM: Mutter WM Theme: Pop Theme: Pop-dark [GTK2/3] Icons: Pop [GTK2/3] Terminal: gnome-terminal CPU: AMD Ryzen 7 PRO 5850U with Radeon Graphics (16) @ 1.900GHz GPU: AMD ATI 03:00.0 Cezanne Memory: 17926MiB / 63630MiB -- 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/2007742 Title: Can't update stage views actor Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: These messages repeat: [ 105.711276] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bba91da500] is on because it needs an allocation. [ 105.711772] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bbac95c330] is on because it needs an allocation. [ 105.711903] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bbae726860] is on because it needs an allocation. --- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 Uname: Linux 6.1.11-060111-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 21:54:39 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-22 (179 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-02-08 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+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 1988333] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613357/+files/monitors.xml.txt -- 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/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613354/+files/ProcCpuinfoMinimal.txt -- 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/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613356/+files/ShellJournal.txt -- 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/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613355/+files/ProcEnviron.txt -- 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/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613353/+files/GsettingsChanges.txt -- 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/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] Re: Ubuntu Gnome Dock Randomly Dies
apport information ** Tags added: apport-collected ** Description changed: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 42.4-0ubuntu0.22.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 + RebootRequiredPkgs: Error: path contained symlinks. + RelatedPackageVersions: mutter-common 42.2-0ubuntu1 + Tags: jammy + Uname: Linux 5.15.0-46-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1988333/+attachment/5613352/+files/Dependencies.txt -- 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/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 42.4-0ubuntu0.22.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] [NEW] Ubuntu Gnome Dock Randomly Dies
Public bug reported: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1988333 Title: Ubuntu Gnome Dock Randomly Dies Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I have at the bottom) will randomly die. When this happens: * The dock is reduced to just the "Show Applications" icon * One or more open applications will no longer accept events (mouse or keyboard) * Ctrl-` (and sometimes Ctrl-TAB) cease working I can restore it by hitting Alt-F2 and then "r" in the dialog. When this happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The extra icons go away after the screensaver kicks in and is then unlocked. $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.1 Candidate: 72~ubuntu5.22.04.1 Version table: *** 72~ubuntu5.22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1988333/+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 1307109] Re: Alcor Micro AU9540 keeps powering down when card is present
I personally couldn't waste anymore time troubleshooting this problem. Ensure you are using a Smartcard Reader that is compatible with the CCID (Chip/Smart Card Interface Devices) and ICCD (Integrated Circuit(s) Card Devices) driver. Supported CCID readers/ICCD tokens: https://ccid.apdu.fr/ccid/supported.html Here are some Smart Card Readers that were intermittently working in Linux: [ray@ThinkPad ~]$ lsusb Bus 005 Device 021: ID 0bda:0165 Realtek Semiconductor Corp. Smart Card Reader Interface Bus 003 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader The Realtek Semiconductor Corp. Smart Card Reader Interface (0bda:0165) is actually a Stanley Global SGT111 Smart Card Reader. The Alcor Micro Corp. AU9540 Smartcard Reader (058f:9540) is a smart card reader that I added when I bought my Lenovo ThinkPad T14 (not knowing that it had compatibility issues with Linux). After running pcsc_scan, I could see the both of the above card readers fluctuate between: Card state: Card removed AND Card state: Card inserted. This would cause my VMware Horizon Client to randomly disconnect from Desktop Anywhere (very annoying). Here are the Smart Card Readers that I ended up buying on Amazon and eBay because they are fully supported by the CCID driver: SCM Microsystems Inc. SCR 3310 USB Smart Card Reader: https://ccid.apdu.fr/ccid/supported.html#0x04E60x5116 CHERRY SmartTerminal ST-1144: https://ccid.apdu.fr/ccid/supported.html#0x046A0x002D (Features: “One-hand operation“ possible due to heavy weight and stable base.) [ray@ThinkPad ~]$ lsusb Bus 005 Device 020: ID 04e6:5116 SCM Microsystems, Inc. SCR331-LC1 / SCR3310 SmartCard Reader Bus 005 Device 022: ID 046a:002d Cherry GmbH SmartTerminal XX44 I haven't had any issues with the using the above supported Card Readers. I use the CHERRY SmartTerminal ST-1144 when I'm at my desk, and the Identiv SCR3310v2.0 USB Smart Card Reader when I have to travel for work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1307109 Title: Alcor Micro AU9540 keeps powering down when card is present Status in pcsc-lite package in Ubuntu: Confirmed Bug description: I have smart card reader built-into this laptop, however, whenever I insert a card - it'll read it for a few seconds, then the USB connection to the reader gets powered down and thus the card disappears in the systems eyes. After a few seconds, it comes back and everything's happy. Then the cycle repeats again and again and again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-23-generic 3.13.0-23.45 [modified: boot/vmlinuz-3.13.0-23-generic] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpds 3933 F pulseaudio /dev/snd/controlC0: jpds 3933 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 6 18:37:24 2014 HibernationDevice: RESUME=UUID=05490d4c-6800-46a1-b5ba-8b32bdc57e89 InstallationDate: Installed on 2014-04-06 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406) MachineType: Hewlett-Packard HP EliteBook Folio 1040 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-23-generic N/A linux-backports-modules-3.13.0-23-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L83 Ver. 01.05 dmi.board.name: 213E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.2A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL83Ver.01.05:bd02/09/2014:svnHewlett-Packard:pnHPEliteBookFolio1040G1:pvrA3009DD18303:rvnHewlett-Packard:rn213E:rvrKBCVersion24.2A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook Folio 1040 G1 dmi.product.version: A3009DD18303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1307109/+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 1892559] Re: [MIR] ccid opensc pcsc-lite
** Changed in: ccid (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => Ray Veldkamp (rayveldkamp) ** Changed in: ccid (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: In Progress Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subs
[Desktop-packages] [Bug 1932990] Re: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied
I am investigating whether I can fix the error by using an option, '--user-data-dir=/tmp', when I launch the chromiumdriver. First, snap has made the use of this simple tool, chromiumdriver, much more complex. Second, I have tried to uninstall the snap version of the tool and I cannot now install a non-snap version. Somehow snap has soured the soup. If it is going to cause these kinds of problems, I am certainly not going to be trying to use snap for other tools unless I have to. If the install requirements are very complex, such as with installing certificates, snap is a good thing. But when the install process is simple, one should not use snap? Is that the solution? -- 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/1932990 Title: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Status in chromium-browser package in Ubuntu: New Bug description: All I am getting is: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Jun 18, 2021 9:11:36 PM org.openqa.selenium.os.OsProcess checkForError But: # ls -ld /opt/appserver/snap/chromium/1646 drwxr-xr-x 2 appserver appserveradm 4096 Jun 18 20:46 /opt/appserver/snap/chromium/1646 The application (a java app) that is making the call to selenium is owned by appserver. So what could the problem be? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1932990/+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 1932990] [NEW] cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied
Public bug reported: All I am getting is: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Jun 18, 2021 9:11:36 PM org.openqa.selenium.os.OsProcess checkForError But: # ls -ld /opt/appserver/snap/chromium/1646 drwxr-xr-x 2 appserver appserveradm 4096 Jun 18 20:46 /opt/appserver/snap/chromium/1646 The application (a java app) that is making the call to selenium is owned by appserver. So what could the problem be? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1932990 Title: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Status in chromium-browser package in Ubuntu: New Bug description: All I am getting is: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Jun 18, 2021 9:11:36 PM org.openqa.selenium.os.OsProcess checkForError But: # ls -ld /opt/appserver/snap/chromium/1646 drwxr-xr-x 2 appserver appserveradm 4096 Jun 18 20:46 /opt/appserver/snap/chromium/1646 The application (a java app) that is making the call to selenium is owned by appserver. So what could the problem be? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1932990/+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 1932990] Re: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied
Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-73-generic x86_64) -- 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/1932990 Title: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Status in chromium-browser package in Ubuntu: New Bug description: All I am getting is: cannot create user data directory: /opt/appserver/snap/chromium/1646: Permission denied Jun 18, 2021 9:11:36 PM org.openqa.selenium.os.OsProcess checkForError But: # ls -ld /opt/appserver/snap/chromium/1646 drwxr-xr-x 2 appserver appserveradm 4096 Jun 18 20:46 /opt/appserver/snap/chromium/1646 The application (a java app) that is making the call to selenium is owned by appserver. So what could the problem be? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1932990/+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 115153]
Created attachment 8811577 Date thread ordering.PNG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird -> Go to the inbox, set your view to threaded and your sorting to order received -> Receive an email to an older thread The thread will remain in the same spot in the list, even though of its children is my most current email and should be on top. The correct way to do this would be to have the entire thread move up to the top, based on the received status of the children in the thread view. ProblemType: Bug Architecture: i386 Date: Wed May 16 19:02:39 2007 DistroRelease: Ubuntu 7.04 Package: mozilla-thunderbird 1.5.0.10-0ubuntu3 PackageArchitecture: i386 SourcePackage: mozilla-thunderbird Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 2006 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+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 115153]
Created attachment 8811578 Order received thread ordering.PNG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird -> Go to the inbox, set your view to threaded and your sorting to order received -> Receive an email to an older thread The thread will remain in the same spot in the list, even though of its children is my most current email and should be on top. The correct way to do this would be to have the entire thread move up to the top, based on the received status of the children in the thread view. ProblemType: Bug Architecture: i386 Date: Wed May 16 19:02:39 2007 DistroRelease: Ubuntu 7.04 Package: mozilla-thunderbird 1.5.0.10-0ubuntu3 PackageArchitecture: i386 SourcePackage: mozilla-thunderbird Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 2006 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+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 115153]
I'm not sure if I have the same problem but I'll explain it. Messages I received in Thunderbird did not actually have the right 'Received' date. So I added mailnews.customDBHeaders = " Received" and now the received column shows the date when my mail was actually received. But sorting by 'Received' is still no different from supporting by date. So I tried 'Order Received' and that seems to work except with threaded messages. For example ascending threaded: foo 100 bar 102 -re:bar 105 qux 103 So I would expect that the 'bar' thread would come after qux but it doesn't. This is actually a big problem sometimes because I have a lot of messages in my inbox and sometimes when they don't arrive for several days they end up way back earlier in the list and I don't even notice them. I will upload two screenshots. In fairness that happens rarely but I'm surprised this bug has been open for a decade. How do we get it handed off to someone? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/115153 Title: Counter intuitive ordering for threaded Email ordered by "order received' Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird -> Go to the inbox, set your view to threaded and your sorting to order received -> Receive an email to an older thread The thread will remain in the same spot in the list, even though of its children is my most current email and should be on top. The correct way to do this would be to have the entire thread move up to the top, based on the received status of the children in the thread view. ProblemType: Bug Architecture: i386 Date: Wed May 16 19:02:39 2007 DistroRelease: Ubuntu 7.04 Package: mozilla-thunderbird 1.5.0.10-0ubuntu3 PackageArchitecture: i386 SourcePackage: mozilla-thunderbird Uname: Linux dennis03 2.6.15-25-686 #1 SMP PREEMPT Wed Jun 14 11:34:19 UTC 2006 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/115153/+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 1860002] [NEW] Airport Extreme not given working option
Public bug reported: Description:Ubuntu 18.04.3 LTS Release:18.04 ubuntu-drivers-common: Installed: 1:0.5.2.5 Candidate: 1:0.5.2.5 Version table: *** 1:0.5.2.5 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.5.2 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Recently repurposed Macbook Pro (7,1) as ubuntu station. Wireless wasn't working. ubuntu-drivers recommended bcmwl-kernel-source. Installed as recommended. Not reliable on boot. Mostly wlp2s0 Scan_results error (-22). After some research discovered that firmware-b43-installer supports chipset on this Mac. from apt-cache show firmware-b43-installer Supported chipsets: * BCM4306/3; * BCM4311; * BCM4318; * BCM4321; * BCM4322 (only 14e4:432b); * BCM4312 (with Low-Power a.k.a. LP-PHY). After purging bcmwl-kernel-source, installing firmware-b43-installer, wireless works fine. suggest that firmware-b43-installer be a listed option for bcm4322 (14e4:432b) in ubuntu-drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-drivers-common 1:0.5.2.5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 07:18:07 2020 InstallationDate: Installed on 2020-01-14 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1860002 Title: Airport Extreme not given working option Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Description: Ubuntu 18.04.3 LTS Release: 18.04 ubuntu-drivers-common: Installed: 1:0.5.2.5 Candidate: 1:0.5.2.5 Version table: *** 1:0.5.2.5 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.5.2 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Recently repurposed Macbook Pro (7,1) as ubuntu station. Wireless wasn't working. ubuntu-drivers recommended bcmwl-kernel-source. Installed as recommended. Not reliable on boot. Mostly wlp2s0 Scan_results error (-22). After some research discovered that firmware-b43-installer supports chipset on this Mac. from apt-cache show firmware-b43-installer Supported chipsets: * BCM4306/3; * BCM4311; * BCM4318; * BCM4321; * BCM4322 (only 14e4:432b); * BCM4312 (with Low-Power a.k.a. LP-PHY). After purging bcmwl-kernel-source, installing firmware-b43-installer, wireless works fine. suggest that firmware-b43-installer be a listed option for bcm4322 (14e4:432b) in ubuntu-drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-drivers-common 1:0.5.2.5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 07:18:07 2020 InstallationDate: Installed on 2020-01-14 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1860002/+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 1771880] Re: Seahorse unable to import pkcs12 certificates
It's been over a year.. Is anyone going to fix this? Like pls -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in gnome-keyring package in Ubuntu: Confirmed Status in seahorse package in Ubuntu: Confirmed Status in gnome-keyring package in Fedora: New Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1771880/+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 1827823] Re: Text lags on input and displays incorrectly on Seek website on Firefox browser
This is now a near-constant issue and occurs on multiple apps: https://youtu.be/B1CYcDVZlrA https://www.youtube.com/watch?v=EdF7EnLthxc The zoom is too far in, while large-text is off in universal access and there is only one resolution for the monitor. The dock would often not pop up when hovering over it with auto-hide on. I am going to move back to Manjaro or another OS. -- 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/1827823 Title: Text lags on input and displays incorrectly on Seek website on Firefox browser Status in firefox package in Ubuntu: New Bug description: This is a video that demonstrates the problem: https://youtu.be/9ukXfcfszeY. After refreshing the page the problem did not continue to occur. I just installed Ubuntu yesterday on a new high-end, custom-built desktop, after having issues with using a couple of Manjaro desktop environments. Just now, while typing in this field, there were a few lags, but the text still displays correctly. ``` jray@fm:~$ inxi -Fxz System:Host: fm Kernel: 4.15.0-48-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.28.3 (Gtk 3.22.30-1ubuntu3) Distro: Ubuntu 18.04.2 LTS Machine: Device: desktop Mobo: ASUSTeK model: TUF B450M-PLUS GAMING v: Rev X.0x serial: N/A UEFI: American Megatrends v: 1002 date: 03/07/2019 CPU: 8 core AMD Ryzen 7 2700X Eight-Core (-MT-MCP-) arch: Zen rev.2 cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 59085 clock speeds: max: 3700 MHz 1: 1890 MHz 2: 1886 MHz 3: 1887 MHz 4: 1889 MHz 5: 1888 MHz 6: 2037 MHz 7: 1883 MHz 8: 2185 MHz 9: 1890 MHz 10: 1886 MHz 11: 1880 MHz 12: 1884 MHz 13: 1890 MHz 14: 2176 MHz 15: 2042 MHz 16: 2194 MHz Graphics: Card: NVIDIA Device 1e82 bus-ID: 07:00.0 Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev,nouveau (unloaded: modesetting,vesa) Resolution: 1024x768@76.00hz OpenGL: renderer: llvmpipe (LLVM 7.0, 128 bits) version: 3.3 Mesa 18.2.8 Direct Render: Yes Audio: Card-1 Advanced Micro Devices [AMD] Family 17h (Models 00h-0fh) HD Audio Controller driver: snd_hda_intel bus-ID: 09:00.3 Card-2 NVIDIA Device 10f8 driver: snd_hda_intel bus-ID: 07:00.1 Sound: Advanced Linux Sound Architecture v: k4.15.0-48-generic Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: f000 bus-ID: 05:00.0 IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: Drives:HDD Total Size: 500.1GB (14.3% used) ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_Plus_500GB size: 500.1GB Partition: ID-1: / size: 395G used: 5.7G (2%) fs: ext4 dev: /dev/dm-0 ID-2: swap-1 size: 68.65GB used: 0.00GB (0%) fs: swap dev: /dev/dm-1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 27.8C mobo: N/A Fan Speeds (in rpm): cpu: 0 Info: Processes: 380 Uptime: 1:01 Memory: 3488.5/64419.5MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.191) inxi: 2.3.56 ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 66.0.3+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jray 1819 F pulseaudio /dev/snd/controlC1: jray 1819 F pulseaudio BuildID: 20190410105841 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon May 6 11:32:46 2019 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-05-05 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IpRoute: default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.3 metric 100 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410105841 (In use) RunningInc
[Desktop-packages] [Bug 1827823] [NEW] Text lags on input and displays incorrectly on Seek website on Firefox browser
Public bug reported: This is a video that demonstrates the problem: https://youtu.be/9ukXfcfszeY. After refreshing the page the problem did not continue to occur. I just installed Ubuntu yesterday on a new high-end, custom-built desktop, after having issues with using a couple of Manjaro desktop environments. Just now, while typing in this field, there were a few lags, but the text still displays correctly. ``` jray@fm:~$ inxi -Fxz System:Host: fm Kernel: 4.15.0-48-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.28.3 (Gtk 3.22.30-1ubuntu3) Distro: Ubuntu 18.04.2 LTS Machine: Device: desktop Mobo: ASUSTeK model: TUF B450M-PLUS GAMING v: Rev X.0x serial: N/A UEFI: American Megatrends v: 1002 date: 03/07/2019 CPU: 8 core AMD Ryzen 7 2700X Eight-Core (-MT-MCP-) arch: Zen rev.2 cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 59085 clock speeds: max: 3700 MHz 1: 1890 MHz 2: 1886 MHz 3: 1887 MHz 4: 1889 MHz 5: 1888 MHz 6: 2037 MHz 7: 1883 MHz 8: 2185 MHz 9: 1890 MHz 10: 1886 MHz 11: 1880 MHz 12: 1884 MHz 13: 1890 MHz 14: 2176 MHz 15: 2042 MHz 16: 2194 MHz Graphics: Card: NVIDIA Device 1e82 bus-ID: 07:00.0 Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev,nouveau (unloaded: modesetting,vesa) Resolution: 1024x768@76.00hz OpenGL: renderer: llvmpipe (LLVM 7.0, 128 bits) version: 3.3 Mesa 18.2.8 Direct Render: Yes Audio: Card-1 Advanced Micro Devices [AMD] Family 17h (Models 00h-0fh) HD Audio Controller driver: snd_hda_intel bus-ID: 09:00.3 Card-2 NVIDIA Device 10f8 driver: snd_hda_intel bus-ID: 07:00.1 Sound: Advanced Linux Sound Architecture v: k4.15.0-48-generic Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: f000 bus-ID: 05:00.0 IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: Drives:HDD Total Size: 500.1GB (14.3% used) ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_Plus_500GB size: 500.1GB Partition: ID-1: / size: 395G used: 5.7G (2%) fs: ext4 dev: /dev/dm-0 ID-2: swap-1 size: 68.65GB used: 0.00GB (0%) fs: swap dev: /dev/dm-1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 27.8C mobo: N/A Fan Speeds (in rpm): cpu: 0 Info: Processes: 380 Uptime: 1:01 Memory: 3488.5/64419.5MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.191) inxi: 2.3.56 ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 66.0.3+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jray 1819 F pulseaudio /dev/snd/controlC1: jray 1819 F pulseaudio BuildID: 20190410105841 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon May 6 11:32:46 2019 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-05-05 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IpRoute: default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.3 metric 100 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0.3/20190410105841 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2019-05-06 (0 days ago) dmi.bios.date: 03/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1002:bd03/07/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.s
[Desktop-packages] [Bug 1822642] [NEW] Suspend with pm-suspend (or any other way) stops working after a few cycles
Public bug reported: I had a fresh installation of Ubuntu-18.04. From the beginning suspend was failing spuriously. When I looked up in Google, I was suggested to upgrade my kernel as the provided kernel 4.15 was buggy. So I compiled the kernel from source and upgraded to 5.04. The problem still persisted. Having GRUB_CMDLINE_LINUX_DEFAULT="acpi_sleep=nonvs" in the file /etc/default/grub and running sudo update-grub does not change anything. Finally I have narrowed down the problem to calling sudo pm- suspend directly. The command works perfectly fine until a few suspend- wakeup cycles have passed. After a few cycle, the screen blanks out and the system does not go to sleep. Nothing responds and I have to do a hard reboot after which everything works the same. Release: Description: Ubuntu 18.04.2 LTS Release:18.04 pm-utils: Installed: 1.4.1-17 Candidate: 1.4.1-17 Version table: *** 1.4.1-17 500 500 http://in.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status Expected pm-suspend to work every time. Instead, pm-suspend fails to put the system to sleep after a few cycles. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pm-utils 1.4.1-17 Uname: Linux 5.0.4 x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 21:20:39 2019 InstallationDate: Installed on 2019-02-13 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1822642 Title: Suspend with pm-suspend (or any other way) stops working after a few cycles Status in pm-utils package in Ubuntu: New Bug description: I had a fresh installation of Ubuntu-18.04. From the beginning suspend was failing spuriously. When I looked up in Google, I was suggested to upgrade my kernel as the provided kernel 4.15 was buggy. So I compiled the kernel from source and upgraded to 5.04. The problem still persisted. Having GRUB_CMDLINE_LINUX_DEFAULT="acpi_sleep=nonvs" in the file /etc/default/grub and running sudo update-grub does not change anything. Finally I have narrowed down the problem to calling sudo pm- suspend directly. The command works perfectly fine until a few suspend-wakeup cycles have passed. After a few cycle, the screen blanks out and the system does not go to sleep. Nothing responds and I have to do a hard reboot after which everything works the same. Release: Description: Ubuntu 18.04.2 LTS Release: 18.04 pm-utils: Installed: 1.4.1-17 Candidate: 1.4.1-17 Version table: *** 1.4.1-17 500 500 http://in.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://in.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status Expected pm-suspend to work every time. Instead, pm-suspend fails to put the system to sleep after a few cycles. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pm-utils 1.4.1-17 Uname: Linux 5.0.4 x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 21:20:39 2019 InstallationDate: Installed on 2019-02-13 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1822642/+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 1822634] [NEW] grub boot fail
Public bug reported: no linux file found 16.04 GMT ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 17:04:05 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] [103c:30ea] InstallationDate: Installed on 2019-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316] Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6bf08b7f-515d-43b6-865e-0ea3b9f55772 ro recovery nomodeset SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0A dmi.board.name: 30EA dmi.board.vendor: Quanta dmi.board.version: 86.09 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: Compaq Presario F700 Notebook PC dmi.product.sku: KW336EA#ABU dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- 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/1822634 Title: grub boot fail Status in xorg package in Ubuntu: New Bug description: no linux file found 16.04 GMT ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 17:04:05 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] [103c:30ea] InstallationDate: Installed on 2019-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316] Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6bf08b7f-515d-43b6-865e-0ea3b9f55772 ro recovery nomodeset SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0A dmi.board.name: 30EA dmi.board.vendor: Quanta dmi.board.version: 86.09 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dm
[Desktop-packages] [Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
*** This bug is a duplicate of bug 978120 *** https://bugs.launchpad.net/bugs/978120 I had the same problem with Lenovo when I'm running Ubuntu 14.04 and I also faced some issue whenever I tried to set up a printer with the laptop I tried to solve this problem from the help of various post but no result came than I finally got a solution from this site: https://uaewebsitedevelopment.com/digital-marketing-services/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/998087 Title: printer ERROR: invalidaccess OFFENDING COMMAND: filter Status in cups-filters package in Ubuntu: Fix Released Status in cups-filters source package in Precise: Fix Released Status in cups-filters source package in Quantal: Fix Released Bug description: This is probably related to bug #960666 but is when trying to print to an HP LaserJet 4050. When trying to print graphics (I have tried both from Geany and from Document Viewer (viewing a PDF), the printer prints a blank page and then a page with the text: ERROR: invalidaccess OFFENDING COMMAND: filter STACK: /SubFileDecode endstream 0 --nostringval-- --nostringval-- 11 false (above was when trying to print from geany) but I think the PDF printed the same text. This printer worked perfectly in the previous 3 versions of Xubuntu but I get this error in Xubuntu 12.04, so I know it's not a printer problem. Interestingly, the Ubuntu test page prints perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+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 1796265] Re: Ubuntu Dock is missing after unlocking screen
I think I have a similar problem. It started on 24-JAN-2019 I think. When I return to my PC after a while I hit Escape to get rid of the shield as normal (I don't have a password lock) and return to my desktop but with all my previous running applications missing. The left hand bar is present and I can click on it but nothing happens. If I use Ctrl-Alt-F1 and enter my password again I am returned to my desktop with everything as I left it and can resume work. I am having to do this every time I return to my PC. I have no custom Gnome extensions. -- 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/1796265 Title: Ubuntu Dock is missing after unlocking screen Status in gnome-shell package in Ubuntu: Expired Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: After locking the screen, unlocking it again does not return me to a properly working gnome-shell. I can see the desktop background and the top panel (which is responsive). However I cannot access the activities overview, and the Ubuntu dock is missing. One time I noticed that the search field from the activities overview was visible, and it was possible to search for an application. The search did return results, and it was possible to start applications, but they did not show up on the screen. In some cases I could run gnome-shell -r, but this would end the whole session and return me to the login screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 12:44:13 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-03 (458 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796265/+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 1800062]
Hint: Read the documenation. Look for .htm files that contain "halftone". Ghostscript supports PostScript Level 3 halftones and includes some tools to do special dithering/halftoning. -- 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/1800062 Title: Ghostscript command line: /usr/bin/gs :Unrecoverable error: undefined in .putdeviceprops Status in GS-GPL: Fix Released Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Bug description: PDF file data fail to rendering to raster data. We were reported a bug from our printer users: I print file use papersize A5 (Ubuntu 16.04.1(x64),Ghostscript 9.18) is Okay. But, after I update (apt-get upgrade) to Ubuntu 16.04.5(x64),Ghostscript 9.25, I print the same file with the same driver there is an error reports: "Filter Error" I figure out that all the papersize with define "LeadingEdge" can't print success after update. (with "LeadingEdge":A5, Statement, A4(without "LeadingEdge") is print Okay). I view the "CUPS Error Log",there is an error reports when print job fails: "Ghostscript command line: /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE=cups -sstdout=%stderr -sOutputFile=%stdout -sMediaType=Plain -sOutputType=Pass=1,Direction=1 -r600x600 -dLeadingEdge=1 -dMediaPosition=7 -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=595 -dcupsBitsPerColor=8 -dcupsColorOrder=0 -dcupsColorSpace=1 -scupsPageSizeName=A5 -I/usr/share/cups/fonts -c \'<>setpagedevice\' -f -_ Unrecoverable error: undefined in .putdeviceprops" Ubuntu 18.04(x64), Ghostscript 9.22 also have the same problem. -- ghostscript had confirm that this a bug of ghostscript 9.22(and the later version). Below information is the correspondence of ghostscript: https://bugs.ghostscript.com/show_bug.cgi?id=700023 --- Our printer driver users(also users of Ubuntu 16.04) can't do their normal print jobs. So, we are eagerly hopping that you can offer us a patch(Ubuntu 16.04) to fix this bug? To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1800062/+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 1791915] [NEW] ubuntu18 amd64
Public bug reported: boot up failed *4... may be the [root] could not read f? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 11 10:03:57 2018 DistUpgraded: 2018-08-15 14:34:28,278 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] [103c:30ea] InstallationDate: Installed on 2018-04-16 (148 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lsusb: Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316] Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=86e86099-7a47-477b-9f20-abfb2e4b3a2b ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-15 (26 days ago) dmi.bios.date: 03/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0A dmi.board.name: 30EA dmi.board.vendor: Quanta dmi.board.version: 86.09 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: Compaq Presario F700 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Aug 15 08:55:41 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1791915 Title: ubuntu18 amd64 Status in xorg package in Ubuntu: New Bug description: boot up failed *4... may be the [root] could not read f? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 11 10:03:57 2018 DistUpgraded: 2018-08-15 14:34:28,278 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] [103c:30ea] InstallationDate: Installed on 2018-04-16 (148 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lsusb: Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316] Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8
[Desktop-packages] [Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter
*** This bug is a duplicate of bug 978120 *** https://bugs.launchpad.net/bugs/978120 @francisco m. I have a solution for your HP LaserJet 1320 there is a blog out there hopefully it will get your query solved https://www.printersrepairnearme.com/epson-printer-repair, hope this will help you and you're all the errors relate to the software stuck solved easily. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/998087 Title: printer ERROR: invalidaccess OFFENDING COMMAND: filter Status in cups-filters package in Ubuntu: Fix Released Status in cups-filters source package in Precise: Fix Released Status in cups-filters source package in Quantal: Fix Released Bug description: This is probably related to bug #960666 but is when trying to print to an HP LaserJet 4050. When trying to print graphics (I have tried both from Geany and from Document Viewer (viewing a PDF), the printer prints a blank page and then a page with the text: ERROR: invalidaccess OFFENDING COMMAND: filter STACK: /SubFileDecode endstream 0 --nostringval-- --nostringval-- 11 false (above was when trying to print from geany) but I think the PDF printed the same text. This printer worked perfectly in the previous 3 versions of Xubuntu but I get this error in Xubuntu 12.04, so I know it's not a printer problem. Interestingly, the Ubuntu test page prints perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/998087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1175221] Re: printing to secure windows print server requires repeated password entry
Hi G, Sorry, I can't verify this as I no longer work at that company and my current work doesn't have the same setup. On 08/12/18 13:13, gf wrote: > Hello Ray, > Thank you for submitting this bug and reporting a problem with cups and > printing. You made this bug report some time ago and Ubuntu has been updated > since then. > > Could you confirm that this is no longer a problem and that we can close the > ticket? > If it is still a problem, are you still interested in finding a solution to > this bug? > If you are, could you let us know, and in the current version, run the > following (only once): > apport-collect BUGNUMBER > and upload the updated logs and and any other logs that are relevant for this > particular issue. > > Thank you again for helping make Ubuntu better. > G > > ** Changed in: cups (Ubuntu) >Status: New => Incomplete > -- 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/1175221 Title: printing to secure windows print server requires repeated password entry Status in cups package in Ubuntu: Incomplete Bug description: Our users authenticate via Active Directory to login to Ubuntu 12.04 VMs/desktops. We even use libpam-mount to automatically mount their windows home directories. However, when we set up printers via CUPS that connect to secured printers over samba on a windows server, whenever a user prints any job, they have to authenticate, even if they already have done so before. This happens on *every* document they print. Checking the Remember credentials checkbox has no effect. Ideally, we would like CUPS to work the same way as libpam-mount - that is to automatically pass AD credentials from winbind/krb to the print server rather than ask. Description: Ubuntu 12.04.2 LTS Release: 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 Date: Wed May 1 11:51:59 2013 Lpstat: device for DataRoom-Color: smb://novusnycdc01/DataRoom-Color device for DataRoom-Color2: smb://novusnycdc01/DataRoom-Color Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet MachineType: innotek GmbH VirtualBox MarkForUpload: True Papersize: letter PpdFiles: DataRoom-Color2: Generic PostScript Printer Foomatic/Postscript (recommended) DataRoom-Color: Generic PostScript Printer Foomatic/Postscript (recommended) ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-40-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH mtime.conffile..etc.cups.cupsd.conf: 2013-04-29T15:48:57.301852 mtime.conffile..etc.pam.d.cups: 2013-04-30T10:10:30.283918 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1175221/+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 1739391] [NEW] Shotwell scrolling results in white screen
Public bug reported: I have scaling set to 175% but everything except 100% results in the same bug. Touchpad scrolling does not work in the image library view and when I grab the scroll bar with the mouse (trackpad) and scroll it down, the shotwell library window fills with white and shotwell needs to be restarted. I can reproduce this every time. Note that if I switch to xorg, I don't get this error (but I can't do fractional scaling) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: shotwell 0.26.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 20 01:23:34 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1739391 Title: Shotwell scrolling results in white screen Status in shotwell package in Ubuntu: New Bug description: I have scaling set to 175% but everything except 100% results in the same bug. Touchpad scrolling does not work in the image library view and when I grab the scroll bar with the mouse (trackpad) and scroll it down, the shotwell library window fills with white and shotwell needs to be restarted. I can reproduce this every time. Note that if I switch to xorg, I don't get this error (but I can't do fractional scaling) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: shotwell 0.26.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 20 01:23:34 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1739391/+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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Also note that the previous (current) version of network-manager (1.2.6-0ubuntu0.16.04.1) is also failing s390x autopkgtest. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: SRU REQUEST: Debdiff (nm-dhcp-helper.debdiff) attached. Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug was fixed upstream in 1.4. [Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hundreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 * NOTE: The final comment on the upstream GNOME bug claims that the fix is incomplete. However, it is possible that the running NetworkManager was not restarted (see Regression Potential notes above), which is why nm-dhcp-helper is falling back to Event. The remainder of the log messages in that final comment are from a custom wrapper the submitter was running around nm-dhcp-helper. I have deployed the exact same patch (without said wrapper) to real-world systems and tested extensively, and see nothing but successful DHCP lease renewal notifications using D-Bus Notify, not D-Bus Event. I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
The autopkgtest failure on s390x is in a test that checks rfkill integration. s390 kernels do not have CONFIG_RFKILL set. Behavior change might have something to do with the recent change to s390x autopkgtest from LXC containers to VMs? https://lists.ubuntu.com/archives/ubuntu-devel/2017-November/040052.html Successful s390 autpkgtests of previous versions of network-manager skipped this test (among others): > urfkill-integration SKIP Test requires machine-level isolation but testbed does not provide that -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: SRU REQUEST: Debdiff (nm-dhcp-helper.debdiff) attached. Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug was fixed upstream in 1.4. [Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hundreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 * NOTE: The final comment on the upstream GNOME bug claims that the fix is incomplete. However, it is possible that the running NetworkManager was not restarted (see Regression Potential notes above), which is why nm-dhcp-helper is falling back to Event. The remainder of the log messages in that final comment are from a custom wrapper the submitter was running around nm-dhcp-helper. I have deployed the exact same patch (without said wrapper) to real-world systems and tested extensively, and see nothing but successful DHCP lease renewal notifications using D-Bus Notify, not D-Bus Event. I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] na
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Version 1.2.6-0ubuntu0.16.04.2 has been deployed here to several machines that were experiencing the bug multiple times per day. All DHCP renewal requests since deployment have resulted in renewal notifications being successfully delivered to NetworkManager. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: SRU REQUEST: Debdiff (nm-dhcp-helper.debdiff) attached. Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug was fixed upstream in 1.4. [Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hundreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 * NOTE: The final comment on the upstream GNOME bug claims that the fix is incomplete. However, it is possible that the running NetworkManager was not restarted (see Regression Potential notes above), which is why nm-dhcp-helper is falling back to Event. The remainder of the log messages in that final comment are from a custom wrapper the submitter was running around nm-dhcp-helper. I have deployed the exact same patch (without said wrapper) to real-world systems and tested extensively, and see nothing but successful DHCP lease renewal notifications using D-Bus Notify, not D-Bus Event. I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Sorry for the delay - I was away for a week. I have deployed the packages from -proposed and will confirm after keeping an eye on DHCP lease renewals for a while. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: SRU REQUEST: Debdiff (nm-dhcp-helper.debdiff) attached. Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug was fixed upstream in 1.4. [Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hundreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 * NOTE: The final comment on the upstream GNOME bug claims that the fix is incomplete. However, it is possible that the running NetworkManager was not restarted (see Regression Potential notes above), which is why nm-dhcp-helper is falling back to Event. The remainder of the log messages in that final comment are from a custom wrapper the submitter was running around nm-dhcp-helper. I have deployed the exact same patch (without said wrapper) to real-world systems and tested extensively, and see nothing but successful DHCP lease renewal notifications using D-Bus Notify, not D-Bus Event. I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Sjors: I'm interested to know how it goes for you with this update (either from the included debdiff, or from the packages when they hit -proposed.) We were seeing the exact same symptoms you were, and deep-dove into your backported fix from the GNOME bug and it all seems like it should fix the issue. We've tested extensively with your fix and the symptoms completely disappeared, even from the machines most frequently affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: In Progress Bug description: SRU REQUEST: Debdiff (nm-dhcp-helper.debdiff) attached. Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug was fixed upstream in 1.4. [Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hundreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 * NOTE: The final comment on the upstream GNOME bug claims that the fix is incomplete. However, it is possible that the running NetworkManager was not restarted (see Regression Potential notes above), which is why nm-dhcp-helper is falling back to Event. The remainder of the log messages in that final comment are from a custom wrapper the submitter was running around nm-dhcp-helper. I have deployed the exact same patch (without said wrapper) to real-world systems and tested extensively, and see nothing but successful DHCP lease renewal notifications using D-Bus Notify, not D-Bus Event. I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
** Description changed: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). - - The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 2708 seconds. However, at 03:21:07 (exactly 2 hours and 1 second after the last lease reported by NetworkManager) Avahi and NTP report that the IP address is gone: jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 192.168.0.166 on eth0. jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.166. jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer relevant for mDNS. jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, active_time=111819 secs So I suspect NetworkManager dropped the IP address from the interface, because it wasn't informed by dhclient that the lease was renewed. The logs don't explicitly say this, so I may have to turn on more verbose debugging logs in NetworkManager or dhclient to verify this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 7 14:48:59 2017 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2016-11-04 (214 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) IpRoute: - default via 192.168.0.5 dev eth0 proto static metric 100 - 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 - 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 metric 100 + default via 192.168.0.5 dev eth0 proto static metric 100 + 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 + 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 metric 100 IwConfig: - lono wireless extensions. - - eth1 no wireless extensions. - - eth0 no wireless extensions. + lono wireless extensions. + + eth1 no wireless extensions. + + eth0 no wireless extensions. NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEn
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Correction/Addendum to the SRU justification above: Fixed in current Ubuntu. Bionic uses NM 1.8.x. This bug was fixed in 1.4. [Impact] * This LP bug's original submitter backported the upstream 1.4 fix to 1.2, not Upstream. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 2708 seconds. However, at 03:21:07 (exactly 2 hours and 1 second after the last lease reported by NetworkManager) Avahi and NTP report that the IP address is gone: jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 192.168.0.166 on eth0. jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.166. jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer relevant for mDNS. jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, active_time=111819 secs So I suspect NetworkManager dropped the IP address from the interface, because it wasn't informed by dhclient that the lease was renewed. The logs don't explicitly say this, so I may have to turn on more verbose debugging logs in NetworkManager or dhclient to verify this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 7 14:48:59 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8)
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
[Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Upstream backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hudreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * Minimal. Upstream's patch falls back to the former behavior if the new behavior is not supported or times out. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 ** Bug watch added: Red Hat Bugzilla #1373276 https://bugzilla.redhat.com/show_bug.cgi?id=1373276 ** Patch added: "nm-dhcp-helper.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1696415/+attachment/5006066/+files/nm-dhcp-helper.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 2708 seconds. However, at 03:21:07 (exactly 2 hours and 1 second after the last lease reported by NetworkManager) Avahi and NTP report that the IP address is gone: jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 192.168.0.166 on eth0. jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.166. jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer relevant for mDNS. jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, active_time=111819 s
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Upstream GNOME bug fixed. I've applied the fix to Xenial's NM and tested. SRU incoming. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 2708 seconds. However, at 03:21:07 (exactly 2 hours and 1 second after the last lease reported by NetworkManager) Avahi and NTP report that the IP address is gone: jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 192.168.0.166 on eth0. jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.166. jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer relevant for mDNS. jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, active_time=111819 secs So I suspect NetworkManager dropped the IP address from the interface, because it wasn't informed by dhclient that the lease was renewed. The logs don't explicitly say this, so I may have to turn on more verbose debugging logs in NetworkManager or dhclient to verify this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 7 14:48:59 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-04 (214 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) IpRoute: default via 192.168.0.5 dev eth0 proto static metric 100 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 metric 100 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEna
[Desktop-packages] [Bug 1688670] [NEW] I can't play You tube videos.
Public bug reported: I haven't been able to play you tube videos on the you tube website, the Google Web Store-You Tube Player, the SMplayer, VML Player or any of your available applications. Either the videos are just refused to be accepted, or on the you tube site, they play way too fast, are choppy, at best (that includes with the You Tube Player). I have yet to be able to play a You Tube video, in any format, successfully since I installed Ubuntu Kylin (be mistake, I wanted the regular 16.04 Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: /dev/sda1: clean, 196491/9707520 files, 2100864/38812672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 5 17:22:49 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller [8086:8108] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. System Controller Hub (SCH Poulsbo) Graphics Controller [1043:83ce] InstallationDate: Installed on 2017-04-19 (16 days ago) InstallationMedia: Ubuntu-Kylin 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215) MachineType: ASUSTeK Computer INC. 1101HA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic root=UUID=6bee3dab-66d4-4c0b-a66f-e25c50c12b34 ro locale=zh_CN quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0317 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1101HA dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0317:bd09/24/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1101HA dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri May 5 16:37:29 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1688670 Title: I can't play You tube videos. Status in xorg package in Ubuntu: New Bug description: I haven't been able to play you tube videos on the you tube website, the Google Web Store-You Tube Player, the SMplayer, VML Player or any of your available applications. Either the videos are just refused to be accepted, or on the you tube site, they play way too fast, are choppy, at best (that includes with the You Tube Player). I have yet to be able to play a You Tube video, in any format, successfully since I installed Ubuntu Kylin (be mistake, I wanted the regular 16.04 Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: /dev/sda1: clean, 196491/9707520 files, 2100864/38812672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 5 17:22:49 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingIn
[Desktop-packages] [Bug 1676993] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 ** This bug has been marked a duplicate of bug 1676380 Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures -- 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/1676993 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 21:45:47 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-18 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: device for HP-Officejet-Pro-6830: usb://HP/Officejet%20Pro%206830?serial=TH58M8112P&interface=1 Lsusb: Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 003: ID 1058:10b8 Western Digital Technologies, Inc. Elements Portable (WDBU6Y, WDBUZG) Bus 001 Device 002: ID 0c45:6300 Microdia PC Microscope camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Compaq-Presario KQ368AA-ABD SR5421DE Papersize: a4 PpdFiles: HP-Officejet-Pro-6830: HP Officejet Pro 6830, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.10 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.10:bd02/21/2008:svnCompaq-Presario:pnKQ368AA-ABDSR5421DE:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KQ368AA-ABD SR5421DE dmi.sys.vendor: Compaq-Presario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676993/+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 1676993] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Can confirm. Saw this failure on dozens of machines today when 2.1.3-4 failed to upgrade to 2.1.3-4ubuntu0.2. -- 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/1676993 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 21:45:47 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-18 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: device for HP-Officejet-Pro-6830: usb://HP/Officejet%20Pro%206830?serial=TH58M8112P&interface=1 Lsusb: Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 003: ID 1058:10b8 Western Digital Technologies, Inc. Elements Portable (WDBU6Y, WDBUZG) Bus 001 Device 002: ID 0c45:6300 Microdia PC Microscope camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Compaq-Presario KQ368AA-ABD SR5421DE Papersize: a4 PpdFiles: HP-Officejet-Pro-6830: HP Officejet Pro 6830, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.10 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.10:bd02/21/2008:svnCompaq-Presario:pnKQ368AA-ABDSR5421DE:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KQ368AA-ABD SR5421DE dmi.sys.vendor: Compaq-Presario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676993/+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 1646420] Re: Files (Nautilus) does not appear in Launcher or Alt-Tab
Same problem, 16.04 updated -- 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/1646420 Title: Files (Nautilus) does not appear in Launcher or Alt-Tab Status in nautilus package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: When Nautilus is unpinned, it does not show up in the Launcher, even when it is running. It does not show up the list displayed by alt-tab either. Even when Nautilus is pinned, it does not indicate (with a tiny arrow to the left of the icon) that it is running, and clicking on the icon in the launcher doesn't switch to it. This is regression from bug #1578792. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity 7.5.0+16.10.20160906.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.98 Mon Sep 19 17:31:03 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 1 10:51:33 2016 DistUpgraded: 2016-10-13 21:56:42,291 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM107 [GeForce GTX 750 Ti] [1462:8a9b] MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-28-generic root=/dev/mapper/vgcherries-vgcherriesroot ro cryptopts=target=cryptcherries,source=/dev/disk/by-uuid/1ae5c201-a8c8-458f-a364-6cda7717c24f,lvm=vgcherries quiet splash SourcePackage: unity UpgradeStatus: Upgraded to yakkety on 2016-10-13 (48 days ago) dmi.bios.date: 10/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd10/24/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Thu Dec 1 10:40:32 2016 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1646420/+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 1582414] Re: No HDMI audio on Lenovo pro dock with T440s
check if this is a dupe of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467190/ -- 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/1582414 Title: No HDMI audio on Lenovo pro dock with T440s Status in pulseaudio package in Ubuntu: Confirmed Bug description: pavucontrol shows Display Port/HDMI output as "(unplugged)" and cannot be chosen as a sink. This is only a problem with the dock; audio works when plugging HDMI through the laptop's DP input. The audio did work with the dock in Ubuntu 14.04. Did something in jack detection change? Anyway, my work around is to plug a 3.4mm audio cable into the dock and power the speakers that way, but it would be nice to use the HDMI audio again. I would love to have a work around. I've attached the output from alsa-info.sh, just in case this is useful. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: weinberg 2221 F pulseaudio /dev/snd/controlC2: weinberg 2221 F pulseaudio /dev/snd/controlC0: weinberg 2221 F pulseaudio /dev/snd/controlC1: weinberg 2221 F pulseaudio CurrentDesktop: Unity Date: Mon May 16 17:18:06 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-05-06 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1582414/+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 1310594] Re: Lenovo Onelink Pro Dock - No audio via Dock-HDMI
*** This bug is a duplicate of bug 1467190 *** https://bugs.launchpad.net/bugs/1467190 ** This bug has been marked a duplicate of bug 1467190 No audio over DisplayPort MST -- 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/1310594 Title: Lenovo Onelink Pro Dock - No audio via Dock-HDMI Status in alsa-driver package in Ubuntu: New Bug description: Sound over Laptop HDMI works, but won't work over Dock with Kernels newer than 2.16 in all ubuntu releases since trusty. Persists with latest bios (state 16.08.16) Freshinstall makes no difference. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310594/+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 1310594] Re: Lenovo Onelink Pro Dock - No audio via Dock-HDMI
*** This bug is a duplicate of bug 1467190 *** https://bugs.launchpad.net/bugs/1467190 what a shame - still not working - tried it in xenial and yakkety again -- 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/1310594 Title: Lenovo Onelink Pro Dock - No audio via Dock-HDMI Status in alsa-driver package in Ubuntu: New Bug description: Sound over Laptop HDMI works, but won't work over Dock with Kernels newer than 2.16 in all ubuntu releases since trusty. Persists with latest bios (state 16.08.16) Freshinstall makes no difference. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310594/+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 1647276] Re: ps2epsi fails after December 01 update
Just in case you aren't following the bug forwarded to us, we have closed the bug as INVALID Basically, the bug report was incomplete, and confusing -- the title and follow up info to us indicated ps2epsi, but the description comment "This means that I am unable to convert from a ps to a PDF and have the correct (tight) bounding box." indicates that a PDF was being created. ps2epsi does not create a PDF (ghostscript can, using ps2pdf, not ps2epsi. We did try ps2epsi and the %%BoundingBox looks fine. Please try and do a better job of describing bugs in the future, bu including the command line and describing the "before" and "after" results in as much detail as possible, particularly what you think is incorrect in the "after". -- 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/1647276 Title: ps2epsi fails after December 01 update Status in ghostscript package in Ubuntu: New Bug description: ps2epsi conversion was working fine before the December 2 update. Now? Broken. This means that I am unable to convert from a ps to a PDF and have the correct (tight) bounding box. Start-Date: 2016-12-02 10:42:35 Commandline: /usr/bin/unattended-upgrade Upgrade: libgs9:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~dfsg~0-0ubuntu2.2), ghostscript:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~df sg~0-0ubuntu2.2), ghostscript-x:amd64 (9.18~dfsg~0-0ubuntu2, 9.18~dfsg~0-0ubuntu2.2), libgs9-common:amd64 (9.18~dfsg~0 -0ubuntu2, 9.18~dfsg~0-0ubuntu2.2) End-Date: 2016-12-02 10:42:37 Description: Ubuntu 16.04.1 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1647276/+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 1621732] [NEW] gedit doesn't show last newline
Public bug reported: echo 'foo' | tee -a testfile od -t x1 testfile 000 66 6f 6f 0a 004 gedit testfile It shows foo as if it doesn't end in a linefeed. In other words I'd expect the last place I could set the cursor as below the line with foo but instead the last place is right after the last o. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 9 00:39:20 2016 InstallationDate: Installed on 2013-10-23 (1051 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (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 gedit in Ubuntu. https://bugs.launchpad.net/bugs/1621732 Title: gedit doesn't show last newline Status in gedit package in Ubuntu: New Bug description: echo 'foo' | tee -a testfile od -t x1 testfile 000 66 6f 6f 0a 004 gedit testfile It shows foo as if it doesn't end in a linefeed. In other words I'd expect the last place I could set the cursor as below the line with foo but instead the last place is right after the last o. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 9 00:39:20 2016 InstallationDate: Installed on 2013-10-23 (1051 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1621732/+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 1310594] Re: Lenovo Onelink Pro Dock - No audio via Dock-HDMI
** Summary changed: - Lynx Point-LP HD Audio - no way to get sound working in 5.1 mode over HDMI working + Lenovo Onelink Pro Dock - No audio via Dock-HDMI ** Description changed: - With Lynx Point-LP HD Audio, there's no way to use HDMI 5.1 output. Video works though. Does neither work with HDMI onboard nor with Lenovo Onelink Pro Dock. I can activate the 5.1 profile, but it falls back to normal speakers (not hdmi). If I click on Digital Stereo (HDMI) at this point and restart, stereo works. - Deleted all pulse/phonon related stuff in my Home Profile - no change. + Sound over Laptop HDMI works, but won't work over Dock with Kernels + newer than 2.16 in all ubuntu releases since trusty. Persists with + latest bios (state 16.08.16) Freshinstall makes no difference. + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO -- 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/1310594 Title: Lenovo Onelink Pro Dock - No audio via Dock-HDMI Status in alsa-driver package in Ubuntu: New Bug description: Sound over Laptop HDMI works, but won't work over Dock with Kernels newer than 2.16 in all ubuntu releases since trusty. Persists with latest bios (state 16.08.16) Freshinstall makes no difference. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310594/+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 1598030] [NEW] Firefox will not sync
Public bug reported: I think a localhost name problem I will download & reinstall ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 47.0+build3-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ray1493 F pulseaudio BuildID: 20160606113944 Channel: Unavailable CurrentDesktop: Unity Date: Fri Jul 1 15:08:55 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-06-30 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enx0c5b8f279a64 proto static metric 100 default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev enx0c5b8f279a64 scope link metric 1000 192.168.1.0/24 dev enx0c5b8f279a64 proto kernel scope link src 192.168.1.100 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js [Profile]/extensions/supp...@lastpass.com/defaults/preferences/defaults.js ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=47.0/20160606113944 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1E dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C5 dmi.board.vendor: HP dmi.board.version: 97.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1E:bd12/25/2015:svnHP:pnHP250G4NotebookPC:pvrType1ProductConfigId:rvnHP:rn80C5:rvr97.45:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G4 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1598030 Title: Firefox will not sync Status in firefox package in Ubuntu: New Bug description: I think a localhost name problem I will download & reinstall ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 47.0+build3-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ray1493 F pulseaudio BuildID: 20160606113944 Channel: Unavailable CurrentDesktop: Unity Date: Fri Jul 1 15:08:55 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-06-30 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enx0c5b8f279a64 proto static metric 100 default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev enx0c5b8f279a64 scope link metric 1000 192.168.1.0/24 dev enx0c5b8f279a64 proto kernel scope link src 192.168.1.100 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js [Profile]/extensions/supp...@lastpass.com/defaults/preferences/defaults.js ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=47.0/20160606113944 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1E dmi.board.asset.tag: Type2 - Board Asse
[Desktop-packages] [Bug 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled
Disabling sensors in Bios makes Suspend work again STM Micro HID Sensor HUB, working through IIO HID accelerometer sensor rotation sensor magnetometer sensor angular velocity sensor (aka gyroscope) inclination sensor ambient light sensor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1593981 Title: pm-utils suspend fails every 2nd time with gyro-sensors enabled Status in pm-utils package in Ubuntu: New Bug description: If I turn on sensors (connected to usb) in the BIOS of my Lenovo Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time. Disabling async doesn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+attachment/4686161/+files/dmesg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1593981 Title: pm-utils suspend fails every 2nd time with gyro-sensors enabled Status in pm-utils package in Ubuntu: New Bug description: If I turn on sensors (connected to usb) in the BIOS of my Lenovo Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time. Disabling async doesn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled
** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+attachment/4686162/+files/lspci -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1593981 Title: pm-utils suspend fails every 2nd time with gyro-sensors enabled Status in pm-utils package in Ubuntu: New Bug description: If I turn on sensors (connected to usb) in the BIOS of my Lenovo Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time. Disabling async doesn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled
** Attachment added: "lsusb" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+attachment/4686163/+files/lsusb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1593981 Title: pm-utils suspend fails every 2nd time with gyro-sensors enabled Status in pm-utils package in Ubuntu: New Bug description: If I turn on sensors (connected to usb) in the BIOS of my Lenovo Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time. Disabling async doesn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1593981] Re: pm-utils suspend fails every 2nd time with gyro-sensors enabled
sudo pm-suspend from commandline works, closing the lid or using KDEs suspend button won't -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1593981 Title: pm-utils suspend fails every 2nd time with gyro-sensors enabled Status in pm-utils package in Ubuntu: New Bug description: If I turn on sensors (connected to usb) in the BIOS of my Lenovo Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time. Disabling async doesn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1593981] [NEW] pm-utils suspend fails every 2nd time with gyro-sensors enabled
Public bug reported: If I turn on sensors (connected to usb) in the BIOS of my Lenovo Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time. Disabling async doesn't help. ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1593981 Title: pm-utils suspend fails every 2nd time with gyro-sensors enabled Status in pm-utils package in Ubuntu: New Bug description: If I turn on sensors (connected to usb) in the BIOS of my Lenovo Thinkpad S1 Yoga suspend fails (immediately wakes up) every 2nd time. Disabling async doesn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1593981/+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 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
I have the same (or very similar) problem on a fresh 16.04 install (same problem on 15.10 upgraded to 16.04, but I reinstalled to be sure). Dell Latitude E4300 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller If I login with unity 8, I just get a black screen. Interestingly, sometimes I get a partially rendered desktop - however, I cannot get the launcher to work, switching windows doesn't work, and in general interacting with it is impossible. Another odd thing is that if I do this, after I login on lightdm, I am presented a different login screen - the password text field isn't properly aligned either which is odd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtdeclarative package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Bug description: This bug Makes the pc UNUSABLE when I try to launch Unity 8 and Mir, after writing the password on the login (in the image attached) the bar to enter the password disappears and my computer screen stays stuck without them let me do anything. the connection begins to separate and reattach alone and I can only move the cursor. it makes the computer unusable and I am forced to restart forced to then enter into Unity 7. represented in the screenshot is the lock status after entering the password. Version: unity8.12+16.04.201604.01.1 Version of Mir : 0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1102001] Re: CUPS recommends incorrect driver for Samsung ML-1670
Guys, any link to a driver that works? I found the CLP-310 driver in the official samsung page, but I couldn't get it to work. Where do I find the foomatic driver? I had been using my ML-1675 printer no problem until a few months ago on my two machines with Ubuntu 14.04 installed and right now, after perhaps a few updates, it has stopped working all together. It only prints a page saying the driver is not the right one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/1102001 Title: CUPS recommends incorrect driver for Samsung ML-1670 Status in splix package in Ubuntu: Incomplete Status in splix package in Unity Linux: New Bug description: STR: 1) From the Printers dialogue, select Add Printer. 2) Select "Samsung ML-1670" from the devices list (connected via USB) 3) Select "Select printer from database" and "Samsung (recommended)" 4) Select "ML-1660 (recommended)" from the Models, and "Samsung ML-1660, 2.0.0 [en] (recommended)" from Drivers 5) Click through and Apply 6) Print a test page The test page isn't printed. Instead a plain text page is printed that says: INTERNAL ERROR - Please use the proper driver. POSITION : 0x0 (0) SYSTEM : h6fw_5.49/xl_op LINE : 180 VERSION : SPL 5.49 10-20-2010 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CheckboxSubmission: dd3689fa6394f60ec14dbe98d0bab891 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Sun Jan 20 10:25:54 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (880 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) KernLog: Jan 20 09:59:31 sixtymilesmile kernel: [54885.307388] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jan 20 09:59:31 sixtymilesmile kernel: [54885.308453] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Lpstat: device for Phaser-6100: usb://Xerox/Phaser%206100?serial=REP167734... device for Samsung-ML-1670-Series: usb://Samsung/ML-1670%20Series?serial=Z6GEBKFB502893V. device for Xerox-Phaser-6100: ipps://xerox/printers/raw device for Xerox-Xerox-Phaser-6100DN: dnssd://Xerox%20Phaser%206100DN%20(XRXf0ae4d08)._printer._tcp.local/ MachineType: Sony Corporation VPCF11J0E MarkForUpload: True Papersize: a4 PpdFiles: Samsung-ML-1670-Series: Samsung ML-1660, 2.0.0 Xerox-Xerox-Phaser-6100DN: Xerox Phaser 6100, 2.0.0 Phaser-6100: Xerox Phaser 6100 Foomatic/Postscript Xerox-Phaser-6100: Xerox Phaser 6100, 2.0.0 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-22-generic root=/dev/mapper/hostname-root ro acpi_sleep=nonvs splash quiet nomodeset xbmc=autostart,nodiskmount loglevel=0 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-11-05 (75 days ago) dmi.bios.date: 02/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0260Y6 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0260Y6:bd02/26/2010:svnSonyCorporation:pnVPCF11J0E:pvrC604LLNJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF11J0E dmi.product.version: C604LLNJ dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/1102001/+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 1251779] Re: fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build
*** This bug is a duplicate of bug 859101 *** https://bugs.launchpad.net/bugs/859101 I received an E mail about this bug and,while reading the Forums,a few people started arguing and name calling. This is NOT kool for any of the Developers & Volunteers.Some of the older machines don't have the Architecture to handle a Linux Platform.In some cases you can install a light version of Mint-LXDE.I've had some limitations but give it a shot. Thank you,Ray The Bearman -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1251779 Title: fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build Status in fglrx-installer package in Ubuntu: New Bug description: Problem with HP laptop with AMD chip(ATI Graphics). AMD's seem to have this issue ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic i686 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DKMSBuildLog: DKMS make.log for fglrx-8.960 for kernel 3.8.0-33-generic (i686) Fri Nov 15 15:31:29 MST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-33-generic/build/include not found or incomplete file: /lib/modules/3.8.0-33-generic/build/include/linux/version.h DKMSKernelVersion: 3.8.0-33-generic Date: Fri Nov 15 15:31:38 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.960: added DuplicateSignature: DKMS make.log for fglrx-8.960 for kernel 3.8.0-33-generic (i686) AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-33-generic/build/include not found or incomplete file: /lib/modules/3.8.0-33-generic/build/include/linux/version.h GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS780M/RS780MN [Mobility Radeon HD 3200 Graphics] [1002:9612] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30fc] InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.2) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC MarkForUpload: True PackageVersion: 2:8.960-0ubuntu1.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=384eaf56-806c-479d-8836-936f7299877f ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.48 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30FC dmi.board.vendor: Compal dmi.board.version: 01.99 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.48:bd06/17/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr1:rvnCompal:rn30FC:rvr01.99:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 1 dmi.sys.vendor: Hewlett-Packard make.log: DKMS make.log for fglrx-8.960 for kernel 3.8.0-33-generic (i686) Fri Nov 15 15:31:29 MST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-33-generic/build/include not found or incomplete file: /lib/modules/3.8.0-33-generic/build/include/linux/version.h version.compiz: compiz 1:0.9.7.12-0ubuntu2 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.3 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1251779/+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 1024606] Re: gnome-contacts stopped showing contacts from Google accounts
Still unfixed on Trusty, c'mon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-contacts in Ubuntu. https://bugs.launchpad.net/bugs/1024606 Title: gnome-contacts stopped showing contacts from Google accounts Status in gnome-contacts package in Ubuntu: Confirmed Bug description: In precise, one could add a Google account in gnome-online-accounts, and its contacts would show up in gnome-contacts. This is broken in quantal. To reproduce from a fresh account: 1. Start gnome-contacts. 2. At the prompt for choosing between “Online Accounts” and “Use Local Address Book”, click “Online Accounts”. 3. Click “+”, select Account Type “Google”, follow the prompts to log into a Google account. 4a. In precise, the gnome-contacts window immediately switches to prompt you to choose between “Local Address Book” and “Google”. Click “Google” and “Select”, and after a little while, all your Google contacts show up. 4b. In quantal, nothing happens. The prompt from step 2 has not changed, and there is no way to select “Google”. (If you choose “Local Address Book”, then the only option under “Change Address Book” from the menu will be “Local Address Book”.) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-contacts 3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.3-0ubuntu4 Architecture: amd64 Date: Fri Jul 13 23:03:55 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202) SourcePackage: gnome-contacts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1024606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1493416] Re: NVIDIA drivers would not work so I switched to neuveau
340.65 and older propriotary that came with 15.04 none of them work. On Sat, Sep 19, 2015 at 7:14 PM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Ray Brown, thank you for reporting this and helping make Ubuntu better. > Could you please advise which driver version specifically you were > trying to use? > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1493416 > > Title: > NVIDIA drivers would not work so I switched to neuveau > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > The reason I was checking was because my HDMI monitor is not being > recognized. Also it says that my graphics card is not being used??? I > am a noob so not sure how to set the card up??? Why wasn't it > detected??? > > ProblemType: Bug > DistroRelease: Ubuntu 15.04 > Package: xorg 1:7.7+7ubuntu4 > Uname: Linux 4.2.0-040200-generic x86_64 > .tmp.unity.support.test.1: > > ApportVersion: 2.17.2-0ubuntu1.4 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > Date: Tue Sep 8 10:09:16 2015 > DistUpgraded: Fresh install > DistroCodename: vivid > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GK106 [GeForce GTX 650 Ti] [10de:11c6] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: eVga.com. Corp. Device [3842:3651] > InstallationDate: Installed on 2014-11-21 (291 days ago) > InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 > (20140722.2) > MachineType: Dell Inc. Inspiron 530 > ProcEnviron: >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-040200-generic > root=UUID=ae4afb7d-0223-40e6-9e77-024d551f1222 ro quiet splash vt.handoff=7 > Renderer: Software > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 02/24/2009 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.0.18 > dmi.board.name: 0RY007 > dmi.board.vendor: Dell Inc. > dmi.chassis.type: 3 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: OEM > dmi.modalias: > dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: > dmi.product.name: Inspiron 530 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.60-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 > version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.9.0-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917-1~exp1ubuntu2.2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.11-1ubuntu2build1 > xserver.bootTime: Tue Sep 8 09:09:45 2015 > xserver.configfile: default > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: > > xserver.version: 2:1.17.1-0ubuntu3 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1493416/+subscriptions > -- 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/1493416 Title: NVIDIA drivers would not work so I switched to neuveau Status in xorg package in Ubuntu: Incomplete Bug description: The reason I was checking was because my HDMI monitor is not being recognized. Also it says that my graphics card is not being used??? I am a noob so not sure how to set the card up??? Why wasn't it detected??? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.2.0-040200-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Compo
[Desktop-packages] [Bug 1493416] [NEW] NVIDIA drivers would not work so I switched to neuveau
Public bug reported: The reason I was checking was because my HDMI monitor is not being recognized. Also it says that my graphics card is not being used??? I am a noob so not sure how to set the card up??? Why wasn't it detected??? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.2.0-040200-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 8 10:09:16 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 650 Ti] [10de:11c6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3651] InstallationDate: Installed on 2014-11-21 (291 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 530 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-040200-generic root=UUID=ae4afb7d-0223-40e6-9e77-024d551f1222 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Sep 8 09:09:45 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install ubuntu vivid -- 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/1493416 Title: NVIDIA drivers would not work so I switched to neuveau Status in xorg package in Ubuntu: New Bug description: The reason I was checking was because my HDMI monitor is not being recognized. Also it says that my graphics card is not being used??? I am a noob so not sure how to set the card up??? Why wasn't it detected??? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.2.0-040200-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 8 10:09:16 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 650 Ti] [10de:11c6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3651] InstallationDate: Installed on 2014-11-21 (291 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 530 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-040200-generic root=UUID=ae4afb7d-0223-40e6-9e77-024d551f1222 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc
[Desktop-packages] [Bug 1392435] Re: nautilus crashes on Close All Windows
This bug affects multiple Ubuntu versions: Ubuntu 14.04.2 (64 bit), Ubuntu 15.04 (64 bit) 1. Install Ubuntu and reboot into the newly installed system 2. Open nautilus window 3. Press Ctrl+Q or click File > Close All Windows to close it 4. After repeat step 2 and step 3 several times, nautilus will become unresponsive (or just crash) -- 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/1392435 Title: nautilus crashes on Close All Windows Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus crashes every time I click File > Close All Windows (Ctrl + Q) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1392435/+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 1448567] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) no 5 GHz wireless
HI, just wondering if there is any update on this? Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1448567 Title: Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) no 5 GHz wireless Status in network-manager package in Ubuntu: Confirmed Bug description: Fresh install of 15.04 on a Macbook Pro 12,1. >Network controller [0280]: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) I copied brcmfmac43602-pcie.bin (https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/brcm/) into /lib/firmware/brcm which enabled the wireless to pick up some SSIDs, but not all (almost positive the only ones seen are 2.4GHz). --- I was referred to this document: https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx Then I ran: $ lspci -vvnn | grep -A 9 Network 03:00.0 Network controller [0280]: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) Subsystem: Apple Inc. Device [106b:0133] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac I find the PCI device ID here: https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211#brcmfmac (Chipset BCM43602, ID: 14e4:43ba) I dropped the relevant firmware files from the repo given a bit further down that page (repo: https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/tree/brcm) into /lib/firmware/brcm/ ...still no 5 GHz. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448567/+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 1454930] [NEW] package empathy-common 3.8.6-0ubuntu9.2 failed to install/upgrade: failed to stat (dereference) existing symlink `/usr/share/help/sl/empathy/irc-start-conversati
Public bug reported: I have no idea what is going on I get the error every time I restart with dual monitors with an intel chipset equiped with nVidia optimus. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: empathy-common 3.8.6-0ubuntu9.2 Uname: Linux 4.0.0-04-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Wed May 13 19:55:04 2015 DuplicateSignature: package:empathy-common:3.8.6-0ubuntu9.2:failed to stat (dereference) existing symlink `/usr/share/help/sl/empathy/irc-start-conversation.page': Input/output error ErrorMessage: failed to stat (dereference) existing symlink `/usr/share/help/sl/empathy/irc-start-conversation.page': Input/output error InstallationDate: Installed on 2015-04-10 (34 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: empathy Title: package empathy-common 3.8.6-0ubuntu9.2 failed to install/upgrade: failed to stat (dereference) existing symlink `/usr/share/help/sl/empathy/irc-start-conversation.page': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: empathy (Ubuntu) Importance: Low Status: Invalid ** Tags: amd64 apport-package hardware-error need-duplicate-check third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1454930 Title: package empathy-common 3.8.6-0ubuntu9.2 failed to install/upgrade: failed to stat (dereference) existing symlink `/usr/share/help/sl/empathy/irc-start-conversation.page': Input/output error Status in empathy package in Ubuntu: Invalid Bug description: I have no idea what is going on I get the error every time I restart with dual monitors with an intel chipset equiped with nVidia optimus. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: empathy-common 3.8.6-0ubuntu9.2 Uname: Linux 4.0.0-04-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 Date: Wed May 13 19:55:04 2015 DuplicateSignature: package:empathy-common:3.8.6-0ubuntu9.2:failed to stat (dereference) existing symlink `/usr/share/help/sl/empathy/irc-start-conversation.page': Input/output error ErrorMessage: failed to stat (dereference) existing symlink `/usr/share/help/sl/empathy/irc-start-conversation.page': Input/output error InstallationDate: Installed on 2015-04-10 (34 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: empathy Title: package empathy-common 3.8.6-0ubuntu9.2 failed to install/upgrade: failed to stat (dereference) existing symlink `/usr/share/help/sl/empathy/irc-start-conversation.page': Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1454930/+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 1292041] Re: Lockscreen doesn't turn off the screen
Ditto! Same issue here. Newly installed, updated and "upgraded" Ubuntu 14.04 LTS. Monitor ASUS 27" through HDMI. After the established timeout, screen does blank out, and monitor detects the "poweroff" and starts powering off. But then the lock screen comes up with request to log in password, and monitor comes back up again and stays on infinitely. I'd say this definitely looks like a bug, because the monitor does detect the shutdown sequence. It looks like a bug (or missing monitor shutdown sequence) on the lock/login screen. -- 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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
this is very annoying Install: Ubuntu Gnome 14.04.2 64-bit CPU: AMD A6-3620 APU GPU Type: Radeon HD 6530D Please fix, really wanted to play steam :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 Status in AMD fglrx video driver: Invalid Status in fglrx-installer package in Ubuntu: In Progress Status in fglrx-installer-updates package in Ubuntu: In Progress Bug description: Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2 Expected behavior: fglrx would intall Observed behavior: fglrx is not installed as follows Attempt to install fglrx fails as follows: zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fglrx-updates : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 E: Unable to correct problems, you have held broken packages. Attempt to insatll xorg-video-abi-15 yields: zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15 Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Attempting to install xserver-xorg-core instead yields: zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1424491/+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 1436591] [NEW] Launcher needs a 'Show All Windows' option
Public bug reported: All applications with a Launcher icon have a set of standard commands, such as "Unlock from Launcher" and "Quit". They should all have a "Show All Windows" command as well. It is really bothersome when I have Terminal open and click on the Launcher icon and I see one window come forward. I may have 6 or 7 windows, but I have to go to each one in turn to bring it forward. I know that I can see the titles of all the windows and I can see the "zoomed out" view of all the windows. But I actually want to bring all the windows of an application to the front and I cannot. Please consider adding this feature. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 25 15:16:52 2015 InstallationDate: Installed on 2015-03-19 (6 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (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 unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1436591 Title: Launcher needs a 'Show All Windows' option Status in unity package in Ubuntu: New Bug description: All applications with a Launcher icon have a set of standard commands, such as "Unlock from Launcher" and "Quit". They should all have a "Show All Windows" command as well. It is really bothersome when I have Terminal open and click on the Launcher icon and I see one window come forward. I may have 6 or 7 windows, but I have to go to each one in turn to bring it forward. I know that I can see the titles of all the windows and I can see the "zoomed out" view of all the windows. But I actually want to bring all the windows of an application to the front and I cannot. Please consider adding this feature. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 25 15:16:52 2015 InstallationDate: Installed on 2015-03-19 (6 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1436591/+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 1428307] [NEW] when screen is locked and I open my laptop, a past screen is flashed
Public bug reported: I close my laptop, which locks the screen. I then open the laptop. Sometimes I must hit the power button to get the screen to unlock. But before I see the password prompt, I see something else. I see a past random screen. It goes by quickly, in less than a second. But this is still not acceptable. The screen should not show _any_ information before the user has logged in. It would not be bad if I could somehow determine what this screen is, because then I would make sure it is blank. But it seems random. Sometimes it seems to be the screen I had visible when I closed up the laptop. Sometimes it seems to be the screen I had visible at one of the last several times I closed the laptop. It does not seem very deterministic. It is hard to know which screen it is going to flash at me before the password prompt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 4 12:30:51 2015 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: 1: AppId = gedit, Flags = 1, Reason = There are unsaved documents GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 0 InstallationDate: Installed on 2014-01-31 (397 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to trusty on 2014-08-14 (202 days ago) ** Affects: gnome-screensaver (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 gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1428307 Title: when screen is locked and I open my laptop, a past screen is flashed Status in gnome-screensaver package in Ubuntu: New Bug description: I close my laptop, which locks the screen. I then open the laptop. Sometimes I must hit the power button to get the screen to unlock. But before I see the password prompt, I see something else. I see a past random screen. It goes by quickly, in less than a second. But this is still not acceptable. The screen should not show _any_ information before the user has logged in. It would not be bad if I could somehow determine what this screen is, because then I would make sure it is blank. But it seems random. Sometimes it seems to be the screen I had visible when I closed up the laptop. Sometimes it seems to be the screen I had visible at one of the last several times I closed the laptop. It does not seem very deterministic. It is hard to know which screen it is going to flash at me before the password prompt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 4 12:30:51 2015 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: 1: AppId = gedit, Flags = 1, Reason = There are unsaved documents GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 0 InstallationDate: Installed on 2014-01-31 (397 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to trusty on 2014-08-14 (202 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1428307/+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 1415645] [NEW] [HDA-Intel - HDA Intel, playback] No sound at all
Public bug reported: played one track. when I tried to play another track app ;hung up. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raywin 1639 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 28 16:03:02 2015 PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raywin 1639 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-08-19 (162 days ago) dmi.bios.date: 12/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0410 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5GC-MX/1333 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0410:bd12/19/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GC-MX/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: System Product Name dmi.product.version: Rev 1.xx dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1415645 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: played one track. when I tried to play another track app ;hung up. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raywin 1639 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 28 16:03:02 2015 PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raywin 1639 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-08-19 (162 days ago) dmi.bios.date: 12/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0410 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5GC-MX/1333 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0410:bd12/19/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GC-MX/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: System Product Name dmi.product.version: Rev 1.xx dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1415645/+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 1410656] Re: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
I do have 2 screens operating independently -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1410656 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Bug description: Just getting that a problem is detected... ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Wed Jan 14 11:28:19 2015 InstallationDate: Installed on 2014-08-24 (143 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1410656/+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 890705] Re: temp file links left in /tmp to ppd file in /etc/cups after printing
I had the same thing as Marcel noted in comment #8. My /tmp directory was filled with links to a ppd file under /etc/cups. I had to reboot in recovery mode to remove them. There were more a million, there were at least one link for every 13-digit hexademical number starting with the same 6 digits so at least 2^28, or approximately a quarter of a billion. I had to create a script to delete them because it was too many arguments for rm to handle. -- 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/890705 Title: temp file links left in /tmp to ppd file in /etc/cups after printing Status in colord package in Ubuntu: Confirmed Status in cups package in Ubuntu: Invalid Bug description: smoser@brickies:~/t/query$ ls -altr /tmp | grep cups | wc -l 24 smoser@brickies:~/t/query$ ls -altr /tmp | grep cups lrwxrwxrwx 1 27 22:01 4ec1d626d9c1e -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:10 4ec1d82e590c4 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:11 4ec1d86793e28 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:12 4ec1d899ddac3 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:13 4ec1d8ca65743 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:14 4ec1d8fc60981 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:14 4ec1d92ce256e -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:15 4ec1d95ec33e9 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:16 4ec1d98e7dc69 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:17 4ec1d9c07720b -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:18 4ec1d9f190626 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:18 4ec1da23d893b -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:19 4ec1da5434731 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:21 4ec1dad0e26ae -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:22 4ec1db085aa32 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:23 4ec1db3b399d0 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:24 4ec1db6aef2c6 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:25 4ec1db9cb3ce8 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:26 4ec1dbcd66aa5 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:26 4ec1dc0078de0 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:27 4ec1dc302ed89 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:28 4ec1dc6283de6 -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:29 4ec1dc939456a -> /etc/cups/ppd/MFC-420CN.ppd lrwxrwxrwx 1 27 22:30 4ec1dcc685f46 -> /etc/cups/ppd/MFC-420CN.ppd # ls output above had user , group and Day trimmed for width's sake. # user and group were smoser, day was 'Nov 14' (yesterday). I actually printed 24 copies of a document last night around that time, so that is likely what resulted in these links. The ppd file in question is: $ dpkg -S /usr/share/ppd/Brother/brmfc420cn_cups.ppd brother-cups-wrapper-extra: /usr/share/ppd/Brother/brmfc420cn_cups.ppd $ dpkg-query --show brother-cups-wrapper-extra brother-cups-wrapper-extra1.2.1-0ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.0-11 ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0 Uname: Linux 3.1.0-2-generic x86_64 ApportVersion: 1.26-0ubuntu1 Architecture: amd64 CupsErrorLog: W [15/Nov/2011:07:40:51 -0500] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/MFC_420CN_Gray__' has already been added W [15/Nov/2011:07:40:51 -0500] failed to AddProfile: org.freedesktop.ColorManager.Failed:profile object path '/org/freedesktop/ColorManager/profiles/MFC_420CN_RGB__' has already been added Date: Tue Nov 15 09:17:26 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for MFC-420CN: usb://Brother/MFC-420CN?serial=BROL5F736191 MachineType: LENOVO 7417CTO Papersize: letter PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MFC-420CN: Brother MFC-420CN CUPS v1.1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.1.0-2-generic root=UUID=f9832678-e9fb-41c5-8edb-5edd5200ed0a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2011-11-07 (8 days ago) dmi.bios.date: 12/06/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET91WW (3.21 ) dmi.board.name: 7417CTO 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:bvr7UET91WW(3.21):bd12/06/2010:svnLENOVO:pn7417CTO:pvrThinkPadT400:rvnLENOVO:rn7417CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7417CTO dmi.product.version:
[Desktop-packages] [Bug 1386466] [NEW] alt-backtick switcher does not iterate through all windows
Public bug reported: There is a serious problem with how the alt-backtick (or alt-grave) switching works. Say I have 10 windows open in Firefox. It is almost impossible to iterate through all 10 of them. This is, I think, for 2 reasons. First, every time the "spread" comes up, the windows are in a different, and seemingly random, order. If I hit alt-grave over and over again, I just observed it cycling back and forth between 2 windows. It goes between the start window and another, and I have no idea how that window was chosen. How do I look at the 2nd window, then the 3rd, the the 4th, and so on? As of now, I have to look at the spread and, for each one, remember which one I have looked at and which I have not. If there are 3 windows, this is fine. But if there are 10 or 12? No. The fact that the windows come up in random order (mentioned above) makes this harder. I cannot even remember the positions of the windows I have examined. I have to actually find the window content. It would be nice if the job of remember which windows I have seen as I iterated through the available windows was not a job that I had to do, but a job that software could do for me. Is there software that can do this for me? If so, please let me know which it is. thanx - ray ps: I have read through these for help: http://www.reddit.com/r/Ubuntu/comments/jv5vy/ubuntu_1110_so_far_screenshot_tour_by_jono_bacon/c2fk1bs http://askubuntu.com/questions/28086/what-are-unitys-keyboard-and-mouse- shortcuts http://design.canonical.com/2012/03/task-switching-in-ubuntu-and-a -introduction-to-the-spread/ Let me know if there is other doc that shows how to configure window switching or what key-combo to use. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Oct 27 17:11:22 2014 InstallationDate: Installed on 2014-01-31 (269 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-08-14 (74 days ago) ** Affects: unity (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 unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1386466 Title: alt-backtick switcher does not iterate through all windows Status in “unity” package in Ubuntu: New Bug description: There is a serious problem with how the alt-backtick (or alt-grave) switching works. Say I have 10 windows open in Firefox. It is almost impossible to iterate through all 10 of them. This is, I think, for 2 reasons. First, every time the "spread" comes up, the windows are in a different, and seemingly random, order. If I hit alt-grave over and over again, I just observed it cycling back and forth between 2 windows. It goes between the start window and another, and I have no idea how that window was chosen. How do I look at the 2nd window, then the 3rd, the the 4th, and so on? As of now, I have to look at the spread and, for each one, remember which one I have looked at and which I have not. If there are 3 windows, this is fine. But if there are 10 or 12? No. The fact that the windows come up in random order (mentioned above) makes this harder. I cannot even remember the positions of the windows I have examined. I have to actually find the window content. It would be nice if the job of remember which windows I have seen as I iterated through the available windows was not a job that I had to do, but a job that software could do for me. Is there software that can do this for me? If so, please let me know which it is. thanx - ray ps: I have read through these for help: http://www.reddit.com/r/Ubuntu/comments/jv5vy/ubuntu_1110_so_far_screenshot_tour_by_jono_bacon/c2fk1bs http://askubuntu.com/questions/28086/what-are-unitys-keyboard-and- mouse-shortcuts http://design.canonical.com/2012/03/task-switching-in-ubuntu-and-a -introduction-to-the-spread/ Let me know if there is other doc that shows how to configure window switching or what key-combo to use. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mo
[Desktop-packages] [Bug 1385875] [NEW] new tab page showing erratic behaviour with thumbnails
Public bug reported:
new tab page of firefox by default shows a grid of 3x3 thumbnails.
changed it to 4x3 (4 columns and 3 rows). faced no problem till version
30. with version 31, the lower row disappeared. it showed only a grid of
4x2. the about:config showed the option correctly (4x3). after upgrading
to version 32, again firefox started showing the grid of 4x3.
unfortunately, it reappeared with the upgrade to version 33. again, only
the grid of 4x2!
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 33.0+build2-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dr 1724 F pulseaudio
BuildID: 20141013200257
CRDA:
country IN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 20)
Channel: Unavailable
CurrentDesktop: XFCE
Date: Sun Oct 26 18:47:20 2014
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2014-04-16 (193 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.100 metric 9
MostRecentCrashID: bp-9aea8df0-a1ea-418e-8477-5709d2130410
Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so
(adobe-flashplugin)
PrefErrors: Unexpected character '' before pref @
[Profile]/extensions/amin.eft_bmno...@gmail.com/defaults/preferences/pref.js:1
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/zoteroopenofficeintegrat...@zotero.org/defaults/preferences/zoteroOpenOfficeIntegration.js
[Profile]/extensions/{3e0e7d2a-070f-4a47-b019-91fe5385ba79}/defaults/preferences/defaults.js
[Profile]/extensions/isreaditla...@ideashower.com/defaults/preferences/prefs.js
Profiles: Profile0 (Default) - LastVersion=33.0/20141013200257 (In use)
RelatedPackageVersions: adobe-flashplugin 11.2.202.411-0trusty1
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
bp-9aea8df0-a1ea-418e-8477-5709d2130410
bp-7a947e12-78d5-4bf3-b263-6c3af2130204
bp-57d93762-5979-4293-aab5-962a22120829
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/20/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 5ECN41WW(V4.00)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Mainboard version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G580
dmi.modalias:
dmi:bvnLENOVO:bvr5ECN41WW(V4.00):bd12/20/2012:svnLENOVO:pn20150:pvrLenovoG580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoG580:
dmi.product.name: 20150
dmi.product.version: Lenovo G580
dmi.sys.vendor: LENOVO
** Affects: firefox (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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1385875
Title:
new tab page showing erratic behaviour with thumbnails
Status in “firefox” package in Ubuntu:
New
Bug description:
new tab page of firefox by default shows a grid of 3x3 thumbnails.
changed it to 4x3 (4 columns and 3 rows). faced no problem till
version 30. with version 31, the lower row disappeared. it showed only
a grid of 4x2. the about:config showed the option correctly (4x3).
after upgrading to version 32, again firefox started showing the grid
of 4x3. unfortunately, it reappeared with the upgrade to version 33.
again, only the grid of 4x2!
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 33.0+build2-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dr 1724 F pulseaudio
BuildID: 20141013200257
CRDA:
country IN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 20)
Channel: Unavailable
CurrentDesktop: XFCE
Date: Sun Oct 26 18:47:20 2014
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5)
[Desktop-packages] [Bug 1363557] [NEW] Password textfield missing when unlocking
Public bug reported: Intermittently the password textfield will be completely missing from the unlock screen. The user's name appears and the background graphic which usually surrounds the textfield is present, but the textfield itself is missing. This typically happens when multiple users are logged into the computer. Unfortunately I do not have reliable steps to repeat the problem. There are a number of workarounds. Sometimes I can use ctrl-alt-f7 or -f8 to switch to another user, log that user out and get to the log in screen with all the users listed. Then the original user can log in. Sometimes it is necessary to switch to ctrl-alt-f1 and restart lightdm. Sometimes I need to log into the machine remotely and restart lightdm. Sometimes all of these fail and it is necessary to restart the computer. If there is something I could do to gather more information the next the computer is in this state, I would be happy to do so. Unfortunately I cannot run ubuntu-bug while the problem is exhibited, as there is no access to the GUI. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 14.04.1 LTS Release:14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center unity: Installed: 7.2.2+14.04.20140714-0ubuntu1.1 Candidate: 7.2.2+14.04.20140714-0ubuntu1.1 Version table: *** 7.2.2+14.04.20140714-0ubuntu1.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen The unlock screen would contain a textfield to accept the user's password. 4) What happened instead The unlock screen contained no place to enter the user's password. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,imgpng,move,place,animation,vpswitch,grid,session,resize,snap,gnomecompat,workarounds,mousepoll,unitymtgrabhandles,wall,expo,ezoom,fade,scale,unityshell] CurrentDesktop: Unity Date: Sat Aug 30 22:16:21 2014 InstallationDate: Installed on 2014-05-25 (97 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (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 unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1363557 Title: Password textfield missing when unlocking Status in “unity” package in Ubuntu: New Bug description: Intermittently the password textfield will be completely missing from the unlock screen. The user's name appears and the background graphic which usually surrounds the textfield is present, but the textfield itself is missing. This typically happens when multiple users are logged into the computer. Unfortunately I do not have reliable steps to repeat the problem. There are a number of workarounds. Sometimes I can use ctrl-alt-f7 or -f8 to switch to another user, log that user out and get to the log in screen with all the users listed. Then the original user can log in. Sometimes it is necessary to switch to ctrl-alt-f1 and restart lightdm. Sometimes I need to log into the machine remotely and restart lightdm. Sometimes all of these fail and it is necessary to restart the computer. If there is something I could do to gather more information the next the computer is in this state, I would be happy to do so. Unfortunately I cannot run ubuntu-bug while the problem is exhibited, as there is no access to the GUI. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center unity: Installed: 7.2.2+14.04.20140714-0ubuntu1.1 Candidate: 7.2.2+14.04.20140714-0ubuntu1.1 Version table: *** 7.2.2+14.04.20140714-0ubuntu1.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubun
[Desktop-packages] [Bug 1359350] [NEW] window resize handle is now too far below window, windows become unresizable
Public bug reported: When I move my cursor to the bottom right corner of any window, the cursor changes to the "resizing handle" and I can resize the window. But, between 14.02 LTS and 14.04 LTS, then indicator appears farther down. Now, the indicator changes a few pixels below the outside edge of the window. What this means is that when I window's bottom edge is flush with the bottom of my screen, I am COMPLETELY UNABLE to resize the window. It is a bit annoying. :-) The distance from the bottom corner to show the resize indicator used to be rather small. It can be frustratingly hard to hit. But now, with these windows, it is completely impossible. This behavior has noticeably changed between 14.02 LTS and 14.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Aug 20 11:51:12 2014 InstallationDate: Installed on 2014-01-31 (201 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-08-14 (6 days ago) ** Affects: unity (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 unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1359350 Title: window resize handle is now too far below window, windows become unresizable Status in “unity” package in Ubuntu: New Bug description: When I move my cursor to the bottom right corner of any window, the cursor changes to the "resizing handle" and I can resize the window. But, between 14.02 LTS and 14.04 LTS, then indicator appears farther down. Now, the indicator changes a few pixels below the outside edge of the window. What this means is that when I window's bottom edge is flush with the bottom of my screen, I am COMPLETELY UNABLE to resize the window. It is a bit annoying. :-) The distance from the bottom corner to show the resize indicator used to be rather small. It can be frustratingly hard to hit. But now, with these windows, it is completely impossible. This behavior has noticeably changed between 14.02 LTS and 14.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Aug 20 11:51:12 2014 InstallationDate: Installed on 2014-01-31 (201 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-08-14 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1359350/+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 1357572] [NEW] dragging Firefox or Terminal windows to other workspace causes a hang
Public bug reported: I enabled workspaces and then I started to drag windows to a second workspace. First, I started dragging a few Terminal windows. I had no problem. Then I dragged a Firefox window that was showing a pdf that I have local on my system and the UI hanged. I had to to a hard reboot. Then I restored my Firefox windows. Then I tried to do the same thing again and it hung while dragging the same window. I had to to a hard reboot. Then I restored my Firefox windows. Then I had given up on that one Firefox window, but, at this point, dragging he second Terminal window across into the other workspace caused the UI to hang. I have not seen visible errors other than the hang. I am somewhat new to Linux, having been on Mac OS X for many years, so I do not know where these things might be logged (if they are). Let me know if I can do something to help diagnose this. I can run something manually, in a debugger, or whatever. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Fri Aug 15 14:48:10 2014 InstallationDate: Installed on 2014-01-31 (196 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-08-14 (1 days ago) ** Affects: unity (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 unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1357572 Title: dragging Firefox or Terminal windows to other workspace causes a hang Status in “unity” package in Ubuntu: New Bug description: I enabled workspaces and then I started to drag windows to a second workspace. First, I started dragging a few Terminal windows. I had no problem. Then I dragged a Firefox window that was showing a pdf that I have local on my system and the UI hanged. I had to to a hard reboot. Then I restored my Firefox windows. Then I tried to do the same thing again and it hung while dragging the same window. I had to to a hard reboot. Then I restored my Firefox windows. Then I had given up on that one Firefox window, but, at this point, dragging he second Terminal window across into the other workspace caused the UI to hang. I have not seen visible errors other than the hang. I am somewhat new to Linux, having been on Mac OS X for many years, so I do not know where these things might be logged (if they are). Let me know if I can do something to help diagnose this. I can run something manually, in a debugger, or whatever. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Fri Aug 15 14:48:10 2014 InstallationDate: Installed on 2014-01-31 (196 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-08-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1357572/+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 1348803] Re: Lenovo Yoga 11e Thinkpad - touchscreen not working
cannot even find a device via lsusb (on my lenovo yoga pro thinkpad everything works) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/1348803 Title: Lenovo Yoga 11e Thinkpad - touchscreen not working Status in “linux” package in Ubuntu: New Bug description: Touchscreen doesnt react on any touches ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 25 22:27:42 2014 InstallationDate: Installed on 2014-05-01 (85 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: linuxadmin 2599 F pulseaudio linuxadmin 2888 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/sda3 InstallationDate: Installed on 2014-05-01 (85 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b451 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20DA001CGM Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=fd312f10-1687-45af-99be-2a06db18629c ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N15ET21W (1.07) dmi.board.asset.tag: Not Available dmi.board.name: 20DA001CGM dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrN15ET21W(1.07):bd06/13/2014:svnLENOVO:pn20DA001CGM:pvrThinkPadYoga11e:rvnLENOVO:rn20DA001CGM:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20DA001CGM dmi.product.version: ThinkPad Yoga 11e dmi.sys.vendor: LENOVO --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: linuxadmin 2599 F pulseaudio linuxadmin 2888 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/sda3 InstallationDate: Installed on 2014-05-01 (85 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b451 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20DA001CGM Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=fd312f10-1687-45af-99be-2a06db18629c ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N15ET21W (1.07) dmi.board.asset.tag: Not Available dmi.board.name: 20DA001CGM dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrN15ET21W(1.07):bd06/13/2014:svnLENOVO:pn20DA001CGM:pvrThinkPadYoga11e:rvnLENOVO:rn20
[Desktop-packages] [Bug 1348803] [NEW] Lenovo Yoga 11e Thinkpad - touchscreen not working
Public bug reported: Touchscreen doesnt react on any touches ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 25 22:27:42 2014 InstallationDate: Installed on 2014-05-01 (85 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: linuxadmin 2599 F pulseaudio linuxadmin 2888 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/sda3 InstallationDate: Installed on 2014-05-01 (85 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b451 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20DA001CGM Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=fd312f10-1687-45af-99be-2a06db18629c ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N15ET21W (1.07) dmi.board.asset.tag: Not Available dmi.board.name: 20DA001CGM dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrN15ET21W(1.07):bd06/13/2014:svnLENOVO:pn20DA001CGM:pvrThinkPadYoga11e:rvnLENOVO:rn20DA001CGM:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20DA001CGM dmi.product.version: ThinkPad Yoga 11e dmi.sys.vendor: LENOVO --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: linuxadmin 2599 F pulseaudio linuxadmin 2888 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/sda3 InstallationDate: Installed on 2014-05-01 (85 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b451 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20DA001CGM Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=fd312f10-1687-45af-99be-2a06db18629c ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N15ET21W (1.07) dmi.board.asset.tag: Not Available dmi.board.name: 20DA001CGM dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrN15ET21W(1.07):bd06/13/2014:svnLENOVO:pn20DA001CGM:pvrThinkPadYoga11e:rvnLENOVO:rn20DA001CGM:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20DA001CGM dmi.product.version: ThinkPad Yoga 11e dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected 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/1348803 Title: Lenovo Yoga 11e Thinkpad - touchscreen not working Status in “linux” package in Ubuntu: New Bug description: Touchscreen doesnt react on any touches ProblemT
[Desktop-packages] [Bug 1341350] [NEW] Additional DNS servers, search domains settings not honored
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 14.04 LTS Release:14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center network-manager: Installed: 0.9.8.8-0ubuntu7 Candidate: 0.9.8.8-0ubuntu7 Version table: *** 0.9.8.8-0ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status network-manager-pptp: Installed: 0.9.8.2-1ubuntu2 Candidate: 0.9.8.2-1ubuntu2 Version table: *** 0.9.8.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The 'Additional DNS servers' and 'Additional search domains' settings would be respected when the 'Use connection for resources only on this resource' checkbox is checked. 4) What happened instead When configuring a PPTP VPN, on the IPv4 settings tab, set the 'Additional DNS servers' to the IP address of the VPN DNS server; the 'Additional search domains' to the domain suffix of of the VPN respectively. Furthermore hit the 'Routes' button and select the 'Use connection for resources only on this resource' checkbox. Furthermore set up a route for the VPN. Once connected to the network, attempts to resolve names on the network failed. The same configuration without the above settings works to resolve names, however all network traffic is funneled through the VPN. If names are resolved using the command line utility dig and specifiying the DNS server, it works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-pptp 0.9.8.2-1ubuntu2 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: Unity Date: Sun Jul 13 17:22:39 2014 InstallationDate: Installed on 2014-05-25 (49 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-pptp (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 network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1341350 Title: Additional DNS servers, search domains settings not honored Status in “network-manager-pptp” package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center network-manager: Installed: 0.9.8.8-0ubuntu7 Candidate: 0.9.8.8-0ubuntu7 Version table: *** 0.9.8.8-0ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status network-manager-pptp: Installed: 0.9.8.2-1ubuntu2 Candidate: 0.9.8.2-1ubuntu2 Version table: *** 0.9.8.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The 'Additional DNS servers' and 'Additional search domains' settings would be respected when the 'Use connection for resources only on this resource' checkbox is checked. 4) What happened instead When configuring a PPTP VPN, on the IPv4 settings tab, set the 'Additional DNS servers' to the IP address of the VPN DNS server; the 'Additional search domains' to the domain suffix of of the VPN respectively. Furthermore hit the 'Routes' button and select the 'Use connection for resources only on this resource' checkbox. Furthermore set up a route for the VPN. Once connected to the network, attempts to resolve names on the network failed. The same configuration without the above settings works to resolve names, however all network traffic is funneled through the VPN. If names are resolved using the command line utility dig and specifiying the DNS server, it works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-pptp 0.9.8.2-1ubuntu2 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: Unity Date: Sun Jul 13 17:22:39 2014 InstallationDate: Installed on 2014-05-25 (49 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source
[Desktop-packages] [Bug 1338175] [NEW] Spurious 'Invalid password' message when switching users
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ~$ apt-cache policy lightdm lightdm: Installed: 1.10.1-0ubuntu1 Candidate: 1.10.1-0ubuntu1 Version table: *** 1.10.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.0-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen When switching users and entering the correct password no 'Invalid password' message should be displayed. 4) What happened instead When switching from one user to another after entering the password, I intermittently (although more often than not) get the 'Invalid password' message briefly before being taken to the desktop. Just to clarify, the correct password is being entered and the user is being taken to the desktop so this is really just an inconvenience. Also, I noticed that it is no longer possible to use the keyboard sequence Alt+W when the lock screen is on to switch users since upgrading to 14.04 - there doesn't seem to be a way to switch users using the keyboard from the lock screen in 14.04. Not sure what the proper channel is to address this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sat Jul 5 20:01:02 2014 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2014-05-25 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1338175 Title: Spurious 'Invalid password' message when switching users Status in “lightdm” package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ~$ apt-cache policy lightdm lightdm: Installed: 1.10.1-0ubuntu1 Candidate: 1.10.1-0ubuntu1 Version table: *** 1.10.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.0-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3) What you expected to happen When switching users and entering the correct password no 'Invalid password' message should be displayed. 4) What happened instead When switching from one user to another after entering the password, I intermittently (although more often than not) get the 'Invalid password' message briefly before being taken to the desktop. Just to clarify, the correct password is being entered and the user is being taken to the desktop so this is really just an inconvenience. Also, I noticed that it is no longer possible to use the keyboard sequence Alt+W when the lock screen is on to switch users since upgrading to 14.04 - there doesn't seem to be a way to switch users using the keyboard from the lock screen in 14.04. Not sure what the proper channel is to address this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sat Jul 5 20:01:02 2014 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2014-05-25 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1338175/+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 857651] Re: Unable to hide users from login screen / user switcher
workaround: delete line 143 (username section, containing text: greeter.lastLoggedInUser) /usr/share/kde4/apps/lightdm-kde-greeter/themes/classic/main.qml -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in D-Bus interfaces for querying and manipulating user account information: Confirmed Status in “accountsservice” package in Ubuntu: Triaged Status in “lightdm” package in Ubuntu: Triaged Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+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 857651] Re: Unable to hide users from login screen / user switcher
could at least "don't show last logged in network users" work somehow? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in D-Bus interfaces for querying and manipulating user account information: Confirmed Status in “accountsservice” package in Ubuntu: Triaged Status in “lightdm” package in Ubuntu: Triaged Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+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 1256646] Re: [ASUS M3N78-VM, Nvidia MCP77/78 HDMI, Digital Out, HDMI] No sound at all
I am no longer experiencing this issue after upgrading to 14.4 (kernel 3.13.0-24). -- 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/1256646 Title: [ASUS M3N78-VM, Nvidia MCP77/78 HDMI, Digital Out, HDMI] No sound at all Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Status in “alsa-lib” package in Ubuntu: New Bug description: Sound stopped working on upgrade from 13.4 to 13.10. Up until then, sound via HDMI worked fine. Now, I get no sound through HDMI. Checked the Sound Settings and alsa mixer and everything looks fine. If I hook up speakers to the microphone port I get sound. I used "ubuntu-bug -s audio" to report this bug (very nice BTW). If there is any additional information you need or anything you would like me to try, I am game for it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ray2389 F pulseaudio /dev/snd/controlC1: ray2389 F pulseaudio Date: Sun Dec 1 09:35:49 2013 InstallationDate: Installed on 2011-10-02 (791 days ago) InstallationMedia: Edubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Built-in Audio - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ray2389 F pulseaudio /dev/snd/controlC1: ray2389 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [System Product Name, Nvidia MCP77/78 HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to saucy on 2013-11-03 (27 days ago) dmi.bios.date: 04/09/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1009 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3N78-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1009:bd04/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1256646/+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 1310594] Re: Lynx Point-LP HD Audio - no way to get sound working in 5.1 mode over HDMI working
** Summary changed: - Lynx Point-LP HD Audio - no way to get sound over HDMI working + Lynx Point-LP HD Audio - no way to get sound working in 5.1 mode over HDMI working ** Description changed: - With Lynx Point-LP HD Audio, there's no way to use HDMI sound output. - Video works though. Does neither work with HDMI onboard nor with Lenovo - Onelink Pro Dock + With Lynx Point-LP HD Audio, there's no way to use HDMI 5.1 output. Video works though. Does neither work with HDMI onboard nor with Lenovo Onelink Pro Dock. I can activate the 5.1 profile, but it falls back to normal speakers (not hdmi). + Deleted all pulse/phonon related stuff in my Home Profile - no change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO ** Description changed: - With Lynx Point-LP HD Audio, there's no way to use HDMI 5.1 output. Video works though. Does neither work with HDMI onboard nor with Lenovo Onelink Pro Dock. I can activate the 5.1 profile, but it falls back to normal speakers (not hdmi). + With Lynx Point-LP HD Audio, there's no way to use HDMI 5.1 output. Video works though. Does neither work with HDMI onboard nor with Lenovo Onelink Pro Dock. I can activate the 5.1 profile, but it falls back to normal speakers (not hdmi). If I click on Digital Stereo (HDMI) at this point and restart, stereo works. Deleted all pulse/phonon related stuff in my Home Profile - no change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO -- 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/1310594 Title: Lynx Point-LP HD Audio - no way to get sound working in 5.1 mode over HDMI working Status in “alsa-driver” package in Ubuntu: New Bug description: With Lynx Point-LP HD Audio, there's no way to use HDMI 5.1 output. Video works though. Does neither work with HDMI onboard nor with Lenovo Onelink Pro Dock. I can activate the 5.1 profile, but it falls back to normal speakers (not hdmi). If I click on Digital Stereo (HDMI) at this point and restart, stereo works. Deleted all pulse/phonon related stuff in my Home Profile - no change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14
[Desktop-packages] [Bug 1310594] [NEW] Lynx Point-LP HD Audio - no way to get sound over HDMI working
Public bug reported: With Lynx Point-LP HD Audio, there's no way to use HDMI sound output. Video works though. Does neither work with HDMI onboard nor with Lenovo Onelink Pro Dock ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1310594 Title: Lynx Point-LP HD Audio - no way to get sound over HDMI working Status in “alsa-driver” package in Ubuntu: New Bug description: With Lynx Point-LP HD Audio, there's no way to use HDMI sound output. Video works though. Does neither work with HDMI onboard nor with Lenovo Onelink Pro Dock ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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: KDE Date: Mon Apr 21 14:23:10 2014 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310594/+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 1303597] [NEW] Heavy graphic glitches leading to desktop reset on Haswel-ULT with i915
Public bug reported: This occours most of the time when using firefox. Probably the screenshot speaks for itself. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 7 08:15:01 2014 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "screenshot of graphic errors" https://bugs.launchpad.net/bugs/1303597/+attachment/4071089/+files/screenshot1.png -- 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/1303597 Title: Heavy graphic glitches leading to desktop reset on Haswel-ULT with i915 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: This occours most of the time when using firefox. Probably the screenshot speaks for itself. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 7 08:15:01 2014 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1303597/+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 1300620] Re: [Lenovo ThinkPad S1 Yoga] Middle button does not work for scrolling
#!/bin/bash
TOUCHPAD="SynPS/2 Synaptics TouchPad"
TRACKPOINT="TPPS/2 IBM TrackPoint"
killall -9 syndaemon
echo "touchpad on"
xinput set-prop "${TOUCHPAD}" "Synaptics Off" 0
echo "setting soft button areas"
#Order: RightButtonAreaLeft, RightButtonAreaRight, RightButtonAreaTop,
RightButtonAreaBottom, MiddleButtonAreaLeft, MiddleButtonAreaRight,
MitddleButtonAreaTop, MiddleButtonAreaBottom"
xinput set-prop "${TOUCHPAD}" "Synaptics Soft Button Areas" 4000, 0, 4063, 0,
3000, 4000, 4063, 1500
#xinput set-prop "${TOUCHPAD}" "Synaptics Soft Button Areas" 4000, 0, 0, 4466,
3000, 3999, 0, 1500
echo "enable twofingerscrolling in both directions"
xinput set-prop "${TOUCHPAD}" "Synaptics Two-Finger Scrolling" 1, 1
echo "shortening upper and lower edge to reserve space for 'just button'
actions. Order: left, right, top, bottom"
xinput set-prop "${TOUCHPAD}" "Synaptics Area" 0, 0, 1500, 4000
#workaround for just scrolling
#xinput set-prop "${TOUCHPAD}" "Synaptics Area" 0, 4000, 1500, 0
echo "enabling palm detection"
xinput set-prop "${TOUCHPAD}" "Synaptics Palm Detection" 1
#echo "Middle mouse button emulation for scrolling on trackpoint"
#xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation" 1
#xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Button" 2
#xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Timeout" 200
#xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Axes" 6 7 4 5 #
horizontal und vertikal
echo "enable tap events"
# RTCornerButton, RBCornerButton, LTCornerButton, LBCornerButton, TapButton1,
TapButton2, TapButton3
xinput set-prop "${TOUCHPAD}" "Synaptics Tap Action" 2, 3, 1, 1, 1, 3, 0
echo "list actual properties"
xinput list-props "${TOUCHPAD}"
echo "no touch while typing"
syndaemon -i 0.5 -d
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
--
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/1300620
Title:
[Lenovo ThinkPad S1 Yoga] Middle button does not work for scrolling
Status in “xorg” package in Ubuntu:
Confirmed
Bug description:
On clickpads (Touchpads with no button) middle mouse button doesn't
work for scrolling with trackpoint (I've configured a soft middlemouse
button area)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
CurrentDesktop: KDE
Date: Tue Apr 1 09:02:37 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: kubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
(rev 0b) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:2217]
InstallationDate: Installed on 2014-03-25 (6 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324)
LightdmGreeterLog:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei
oder Verzeichnis nicht gefunden
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135:
Unable to assign [undefined] to QString usersession
LightdmGreeterLogOld:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei
oder Verzeichnis nicht gefunden
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135:
Unable to assign [undefined] to QString usersession
MachineType: LENOVO 20C0S0AX00
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed
root=UUID=389305e0-f86b-4068-a352-fe5597926b87 ro rootflags=subvol=@
kopt=root=/dev/mapper/ray-root quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GQET34WW (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C0S0AX00
dmi.board.vendor: LENOVO
d
[Desktop-packages] [Bug 1246683] Re: Middle button does not work for scrolling
done: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300620 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246683 Title: Middle button does not work for scrolling Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: With my Lenovo T440s laptop the Trackpad/Trackpoint laptop scrolling does not work when pressing middle button + moving the Trackpoint. evdev seems to be set correctly ( http://paste.ubuntuusers.de/416732/ ). Middle button itself works fine for middle clicks just no scrolling. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 Uname: Linux 3.12.0-031200rc7-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 12:36:14 2013 InstallationDate: Installed on 2013-10-17 (13 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MarkForUpload: True SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1246683/+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 1300620] [NEW] Middle button does not work for scrolling [other Hardware]
Public bug reported: I'm refering to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- input-evdev/+bug/1246683/comments/45 On clickpads (Touchpads with no button) middle mouse button doesn't work for scrolling with trackpoint (I've configured a soft middlemouse button area) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Tue Apr 1 09:02:37 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2217] InstallationDate: Installed on 2014-03-25 (6 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: LENOVO 20C0S0AX00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=389305e0-f86b-4068-a352-fe5597926b87 ro rootflags=subvol=@ kopt=root=/dev/mapper/ray-root quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET34WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S0AX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET34WW(1.14):bd02/26/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S0AX00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 08:36:37 2014 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1044 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu 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/1300620 Title: Middle button does not work for scrolling [other Hardware] Status in “xorg” package in Ubuntu: New Bug description: I'm refering to https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-input-evdev/+bug/1246683/comments/45 On clickpads (Touchpads with no button) middle mouse button doesn't work for scrolling with trackpoint (I've configured a soft middlemouse button area) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2
[Desktop-packages] [Bug 1297718] Re: ELAN Touchscreen 04f3:0254 not recognized correctly on Lenovo Thinkpad Yoga
sorry, stupid mistake ** Summary changed: - Touchscreen not recognized correctly on Lenovo Thinkpad Yoga + ELAN Touchscreen 04f3:0254 not recognized correctly on Lenovo Thinkpad Yoga ** Package changed: xf86-input-wacom (Ubuntu) => linux-meta (Ubuntu) ** Changed in: linux-meta (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1297718 Title: ELAN Touchscreen 04f3:0254 not recognized correctly on Lenovo Thinkpad Yoga Status in “linux-meta” package in Ubuntu: New Bug description: xsetwacom doesn't list my wacom toucscreen But it works as a singlebutton mouse: xsetwacom --list devices Wacom ISDv4 EC Pen stylus id: 11 type: STYLUS Wacom ISDv4 EC Pen eraser id: 14 type: ERASER ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-wacom 1:0.23.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 26 10:06:53 2014 InstallationDate: Installed on 2014-03-25 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324) SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1297718/+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 1287148] Re: [Lenovo ThinkPad X1 Carbon] Clickpad + Trackpoint cannot emulate middle button scrolling
*** This bug is a duplicate of bug 1246683 *** https://bugs.launchpad.net/bugs/1246683 ** This bug has been marked a duplicate of bug 1246683 Middle button does not work for scrolling -- 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/1287148 Title: [Lenovo ThinkPad X1 Carbon] Clickpad + Trackpoint cannot emulate middle button scrolling Status in “xorg” package in Ubuntu: Confirmed Bug description: I'm testing with a freshly-updated Trusty Tahir daily (2014/March/2) on a Lenovo X1 Carbon (2014 refresh) laptop. IBM/Lenovo Thinkpad laptops have a "Trackpoint": a red "joystick mouse" in the middle of the keyboard. Historically this is accompanied by three mouse buttons directly below the space bar. One beloved feature: if you hold down the middle mouse button, you can scroll a window up/down/left/right with the Trackpoint. This feature is implemented in X with the "Evdev Wheel Emulation" properties of the xinput driver for the Trackpoint device. The latest Thinkpad laptops (X240, X1 Carbon 2014 refresh) remove the hard buttons, and have a "clickpad" instead of a trackpad.One must use the "soft" mouse buttons provided by the clickpad. But now we have a problem. The clickpad soft buttons are implemented in the Synaptic driver. And the Synaptic driver doesn't support middle- button-scrolling. If I run % xinput --list-props "TPPS/2 IBM TrackPoint" I see property entries starting with "Evdev Wheel Emulation". Setting them on this device doesn't enable middle-button-scrolling. And if I run % xinput --list-props "SynPS/2 Synaptics TouchPad" I don't see those property entries at all. I tried setting them manually with "xinput --set-int-prop" but they were ignored. One of the maintainers of Arch Linux got middle-button-scrolling with a Trackpoint + clickpad to work! But he had to create a new driver. It looks like he started with the evdev driver, and merged in support for the Synaptics and Trackpoint devices. The resulting driver is published here: https://bitbucket.org/esrevinu/xf86-input-evdev-trackpoint It would be fantastic if Ubuntu 14.04 also supported this feature. Thanks! --- .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2218] InstallationDate: Installed on 2014-03-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) MachineType: LENOVO 20A7CTO1WW Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=265f35f3-eb2b-48a6-bbed-84255b758df9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty ubuntu reproducible Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GRET29WW (1.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET29WW(1.06):bd12/03/2013:svnLENOVO:pn20A7CTO1WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CTO1WW:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CTO1WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Mar 13 11:21:03 2014 xserver.configfile: default xserver.errors: xserver.
[Desktop-packages] [Bug 1246683] Re: Touchpad middle button does not work for scrolling with trackpoint (ultranav)
persists on trusty with xserver-xorg-input-synaptic 1.7.99 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246683 Title: Touchpad middle button does not work for scrolling with trackpoint (ultranav) Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: With my Lenovo T440s laptop the Trackpad/Trackpoint laptop scrolling does not work when pressing middle button + moving the Trackpoint. evdev seems to be set correctly ( http://paste.ubuntuusers.de/416732/ ). Middle button itself works fine for middle clicks just no scrolling. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 Uname: Linux 3.12.0-031200rc7-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 12:36:14 2013 InstallationDate: Installed on 2013-10-17 (13 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MarkForUpload: True SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1246683/+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 1246683] Re: Touchpad middle button does not work for scrolling with trackpoint (ultranav)
** Summary changed: - Middle button does not work for scrolling + Touchpad middle button does not work for scrolling with trackpoint (ultranav) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246683 Title: Touchpad middle button does not work for scrolling with trackpoint (ultranav) Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: With my Lenovo T440s laptop the Trackpad/Trackpoint laptop scrolling does not work when pressing middle button + moving the Trackpoint. evdev seems to be set correctly ( http://paste.ubuntuusers.de/416732/ ). Middle button itself works fine for middle clicks just no scrolling. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 Uname: Linux 3.12.0-031200rc7-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 12:36:14 2013 InstallationDate: Installed on 2013-10-17 (13 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MarkForUpload: True SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1246683/+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 1297718] Re: Touchscreen not recognized correctly on Lenovo Thinkpad Yoga
xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=9[slave pointer (2)] ⎜ ↳ Wacom ISDv4 EC Pen stylus id=11 [slave pointer (2)] ⎜ ↳ Wacom ISDv4 EC Pen eraser id=14 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)id=17 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Integrated Camera id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] ↳ ThinkPad Extra Buttonsid=13 [slave keyboard (3)] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1297718 Title: Touchscreen not recognized correctly on Lenovo Thinkpad Yoga Status in “xf86-input-wacom” package in Ubuntu: New Bug description: xsetwacom doesn't list my wacom toucscreen But it works as a singlebutton mouse: xsetwacom --list devices Wacom ISDv4 EC Pen stylus id: 11 type: STYLUS Wacom ISDv4 EC Pen eraser id: 14 type: ERASER ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-wacom 1:0.23.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 26 10:06:53 2014 InstallationDate: Installed on 2014-03-25 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324) SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1297718/+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 1297718] Re: Touchscreen not recognized correctly on Lenovo Thinkpad Yoga
Bus 001 Device 004: ID 056a:00ec Wacom Co., Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x056a Wacom Co., Ltd idProduct 0x00ec bcdDevice1.31 iManufacturer 1 Tablet iProduct2 ISD-V4 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 239 Report Descriptor: (length is 239) Item(Global): Usage Page, data= [ 0x01 ] 1 Generic Desktop Controls Item(Local ): Usage, data= [ 0x02 ] 2 Mouse Item(Main ): Collection, data= [ 0x01 ] 1 Application Item(Global): Report ID, data= [ 0x01 ] 1 Item(Local ): Usage, data= [ 0x01 ] 1 Pointer Item(Main ): Collection, data= [ 0x00 ] 0 Physical Item(Global): Usage Page, data= [ 0x09 ] 9 Buttons Item(Local ): Usage Minimum, data= [ 0x01 ] 1 Button 1 (Primary) Item(Local ): Usage Maximum, data= [ 0x02 ] 2 Button 2 (Secondary) Item(Global): Logical Minimum, data= [ 0x00 ] 0 Item(Global): Logical Maximum, data= [ 0x01 ] 1 Item(Global): Report Count, data= [ 0x02 ] 2 Item(Global): Report Size, data= [ 0x01 ] 1 Item(Main ): Input, data= [ 0x02 ] 2 Data Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Report Count, data= [ 0x01 ] 1 Item(Global): Report Size, data= [ 0x06 ] 6 Item(Main ): Input, data= [ 0x03 ] 3 Constant Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Usage Page, data= [ 0x01 ] 1 Generic Desktop Controls Item(Local ): Usage, data= [ 0x30 ] 48 Direction-X Item(Local ): Usage, data= [ 0x31 ] 49 Direction-Y Item(Global): Logical Minimum, data= [ 0x81 ] 129 Item(Global): Logical Maximum, data= [ 0x7f ] 127 Item(Global): Report Size, data= [ 0x08 ] 8 Item(Global): Report Count, data= [ 0x02 ] 2 Item(Main ): Input, data= [ 0x06 ] 6 Data Variable Relative No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Main ): End Collection, data=none Item(Main ): End Collection, data=none Item(Global): Usage Page, data= [ 0x0d ] 13 Digitizer Item(Local ): Usage, data= [ 0x02 ] 2 Pen Item(Main ): Collection, data= [ 0x01 ] 1 Application Item(Global): Report ID, data= [ 0x02 ] 2 Item(Local ): Usage, data= [ 0x20 ] 32 Stylus Item(Main ): Collection, data= [ 0x00 ] 0 Physical Item(Local ): Usage, data= [ 0x42 ] 66 Tip Switch Item(Local ): Usage, data= [ 0x44 ] 68 Barrel Switch Item(Local ): Usage, data= [ 0x45 ] 69 Eraser Item(Local ): Usage, data= [ 0x3c ] 60 Invert Item(Local ): Usage, data= [ 0x00 ] 0 Undefined Item(Local ): Usage, data= [ 0x32 ] 50 In Range I
[Desktop-packages] [Bug 1297718] [NEW] Touchscreen not recognized correctly on Lenovo Thinkpad Yoga
Public bug reported: xsetwacom doesn't list my wacom toucscreen But it works as a singlebutton mouse: xsetwacom --list devices Wacom ISDv4 EC Pen stylus id: 11 type: STYLUS Wacom ISDv4 EC Pen eraser id: 14 type: ERASER ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-wacom 1:0.23.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 26 10:06:53 2014 InstallationDate: Installed on 2014-03-25 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324) SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xf86-input-wacom (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 xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1297718 Title: Touchscreen not recognized correctly on Lenovo Thinkpad Yoga Status in “xf86-input-wacom” package in Ubuntu: New Bug description: xsetwacom doesn't list my wacom toucscreen But it works as a singlebutton mouse: xsetwacom --list devices Wacom ISDv4 EC Pen stylus id: 11 type: STYLUS Wacom ISDv4 EC Pen eraser id: 14 type: ERASER ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-wacom 1:0.23.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 26 10:06:53 2014 InstallationDate: Installed on 2014-03-25 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324) SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1297718/+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 1091898] Re: LibreOffice Calc only import 49 lines of CSV file
I had the same problem and I found that if you changed the Text delimiter to a single quote you will get all your rows imported. -- 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/1091898 Title: LibreOffice Calc only import 49 lines of CSV file Status in “libreoffice” package in Ubuntu: Expired Bug description: I have a CSV file when when I use LibreOffice Calc to open it - it only imports the first 49 lines. Use MS Excel 2010 I can open the whole file normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1091898/+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
