[Desktop-packages] [Bug 2056767] Re: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split
This should not impact Ubuntu Cinnamon as I don't believe there are any components that specifically rely heavily on gnome-software. ubuntucinnamon-meta will need to add the new entry for gnome-software- plugin-deb, but that's about it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2056767 Title: FFe: Sync gnome-software 46.0-4 (universe) from Debian unstable (main) with gnome-software packaging split Status in gnome-software package in Ubuntu: New Bug description: Impact -- I request permission to sync the gnome-software packaging from Debian. The biggest change is splitting gnome-software's .deb support into a separate package, gnome-software-plugin-deb, to match the existing -snap and -flatpak packages. This will allow users and flavors to specifically opt into the parts of the GNOME Software experience they want. For instance, someone may want to use only the Flatpak part because they use the Snap Store to manage .debs and Snaps. Or maybe they want a different combination. This has been requested by multiple users on Ubuntu Discourse and at least one Launchpad bug and one Debian bug. fwupd plugin I am dropping the fwupd plugin (now in a separate package too) to Suggests so upgrades to Ubuntu 24.04 LTS will likely get it uninstalled and new installs won't have it either unless a user explicitly installs it later. Ubuntu Desktop includes the firmware-updater snap. Several Ubuntu desktop flavors also include it. For people who don't want snaps, there is also the gnome-firmware app packaged as a .deb. Because Ubuntu already has update-manager to handle apt update notifications, I am also dropping the autostart file to reduce background RAM use. A few Ubuntu desktop flavors do not provide any firmware updater app at all. Ubuntu Budgie developers thought a firmware updater app was too technical for inclusion in the default Ubuntu 24.04 LTS install. autostart - I have also dropped the autostart file since the fwupd plugin is no longer included by default and Ubuntu already has ways to notify users about available apt updates (update-manager and unattended upgrades) and snaps already automatically update. Potential Problems --- gnome-software has an explicit Recommend: gnome-software-plugin-deb so that people upgrading to Ubuntu 24.04 LTS will keep the deb support installed. That recommends will be dropped for Ubuntu 26.04 LTS because it won't be needed then. (There is a Depends on the virtual packages that enable installing apps.) Full Changelog Entries -- gnome-software (46.0-4) unstable; urgency=medium * Fix typo in gnome-software-plugin-deb package description * Add lintian overrides for desktop-command-not-in-package -- Jeremy Bícha Fri, 29 Mar 2024 16:45:30 -0400 gnome-software (46.0-3) unstable; urgency=medium * Update Homepage * Release to Unstable -- Jeremy Bícha Thu, 28 Mar 2024 13:23:28 -0400 gnome-software (46.0-2) experimental; urgency=medium * Split deb support into separate gnome-software-plugin-deb package (Closes: #1066030) (LP: #2019137, #2056767) * Have each plugin provide a virtual gnome-software-plugin package * Suggest all the gnome-software plugins * Recommend gnome-software-plugin-deb for upgrades * Split firmware update support into separate fwupd plugin & recommend it except on Ubuntu which provides a separate firmware-updater app Intentionally, do not have this provides the virtual gnome-software-plugin since it doesn't allow browsing apps. * Drop patch that hides upstreams Software Sources dialog (Closes: #1060803) * Drop Depends: software-properties-gtk * Stop recommending gnome-software-plugin-snap on Ubuntu -- Jeremy Bícha Wed, 27 Mar 2024 18:33:03 -0400 Build Logs -- https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+sourcepub/15898505/+listing-archive-extra Desktop Flavors Affected GNOME Software is currently included in the default install for only Ubuntu Cinnamon. I have been in contact with Ubuntu Cinnamon lead Joshua Peisach who does not object to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2056767/+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 2056591] Re: [UIFe] Noble Flavor Wallpapers
** Also affects: ubuntucinnamon-wallpapers (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntucinnamon-environment (Ubuntu) Assignee: (unassigned) => Joshua Peisach (itzswirlz) ** Changed in: ubuntucinnamon-wallpapers (Ubuntu) Assignee: (unassigned) => Joshua Peisach (itzswirlz) ** Changed in: ubuntucinnamon-wallpapers (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/2056591 Title: [UIFe] Noble Flavor Wallpapers Status in budgie-desktop-environment package in Ubuntu: Triaged Status in budgie-wallpapers package in Ubuntu: Triaged Status in ubuntu-unity-backgrounds package in Ubuntu: Confirmed Status in ubuntu-wallpapers package in Ubuntu: Triaged Status in ubuntucinnamon-environment package in Ubuntu: Confirmed Status in ubuntucinnamon-wallpapers package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Triaged Status in ubuntustudio-look package in Ubuntu: Triaged Bug description: I am requesting a blanket UI Freeze exception for all flavor wallpaper packages in advance of the upcoming UI Freeze for a period of 5 days after it starts. The Noble wallpapers for vanilla Ubuntu will be available on March 18th, which only gives flavors 2 days to create their customized wallpapers. This is a very tight deadline, and we'd like to avoid putting the burden on flavors to request individual UIFe's or forcing them to rush update their wallpaper to make the deadline. I'd appreciate your support on granting this exception. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop-environment/+bug/2056591/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
** Changed in: ubuntucinnamon-meta (Ubuntu) Assignee: (unassigned) => Joshua Peisach (itzswirlz) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: New Status in kubuntu-meta package in Ubuntu: New Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
Yep! (Hostname says "2210Test". I meant to say Kinetic but it doesn't happen on Lunar. Want me to try backporting to other releases? -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
No reproduction on Lunar for Nemo. Syslog does not show any errors ** Attachment added: "Screenshot from 2023-02-11 18-09-13.png" https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1998060/+attachment/5646439/+files/Screenshot%20from%202023-02-11%2018-09-13.png -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
Applied the patches, not getting any nasty messages in /var/log/syslog ** Patch added: "nemo_5.4.3-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1998060/+attachment/5639800/+files/nemo_5.4.3-2ubuntu0.1.debdiff ** Changed in: nemo (Ubuntu Kinetic) Status: New => In Progress -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
Fix released for nautilus 1:43.0-1ubuntu2.1 nautilus (1:43.0-1ubuntu2.1) kinetic-security; urgency=medium * SECURITY UPDATE: crash via invalid zip file - debian/patches/CVE-2022-37290.patch: fix crash when copying an invalid file in src/nautilus-dbus-manager.c, src/nautilus-file-operations.c. - CVE-2022-37290 -- Marc Deslauriers Tue, 03 Jan 2023 12:27:45 -0500 ** Changed in: nautilus (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: nautilus (Ubuntu Lunar) Status: New => Fix Released ** Changed in: nautilus (Ubuntu Jammy) Status: New => Fix Released ** Changed in: nautilus (Ubuntu Focal) Status: New => Fix Released -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: New Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
Fix in version 5.6.1, sitting in proposed ** Changed in: nemo (Ubuntu Lunar) Status: New => Fix Committed -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: New Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: New Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: New Status in nemo source package in Kinetic: New Status in caja source package in Lunar: New Status in nautilus source package in Lunar: New Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1653351]
Please address this issue. I'm using the "mark as deleted" setting. Pressing the delete key in the message list toggles the "deleted" flag of the selected message as desired, but it also annoyingly selects the next message in the list. When I'm editing a message by changing its flags, I don't want my mail client to automatically select another message. The current message should simply stay selected. The "Deselect on Delete" addon doesn't solve my use case, because it deselects on delete instead of keeping the selection. -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Confirmed Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
taking responsibility for SRU ** Changed in: nemo (Ubuntu Kinetic) Assignee: (unassigned) => Joshua Peisach (itzswirlz) -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in nemo package in Ubuntu: New Status in caja source package in Focal: New Status in nautilus source package in Focal: New Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: New Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: New Status in nemo source package in Kinetic: New Status in caja source package in Lunar: New Status in nautilus source package in Lunar: New Status in nemo source package in Lunar: New Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
taking responsibility for SRU ** Changed in: nemo (Ubuntu Focal) Assignee: (unassigned) => Joshua Peisach (itzswirlz) -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in nemo package in Ubuntu: New Status in caja source package in Focal: New Status in nautilus source package in Focal: New Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: New Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: New Status in nemo source package in Kinetic: New Status in caja source package in Lunar: New Status in nautilus source package in Lunar: New Status in nemo source package in Lunar: New Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
taking responsibility for SRU ** Changed in: nemo (Ubuntu Jammy) Assignee: (unassigned) => Joshua Peisach (itzswirlz) -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in nemo package in Ubuntu: New Status in caja source package in Focal: New Status in nautilus source package in Focal: New Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: New Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: New Status in nemo source package in Kinetic: New Status in caja source package in Lunar: New Status in nautilus source package in Lunar: New Status in nemo source package in Lunar: New Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
Part of Debian Cinnamon Team - assign latest release with fix to me ** Changed in: nemo (Ubuntu Lunar) Assignee: (unassigned) => Joshua Peisach (itzswirlz) -- 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/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in nemo package in Ubuntu: New Status in caja source package in Focal: New Status in nautilus source package in Focal: New Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: New Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: New Status in nemo source package in Kinetic: New Status in caja source package in Lunar: New Status in nautilus source package in Lunar: New Status in nemo source package in Lunar: New Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 1989477] [NEW] Switching to dark mode in settings does not change shell theme.
Public bug reported: Changing the "Style" in the "Appearance" section of "Settings" (gnome- control-center), does not update the shell theme. When I select dark mode from settings, Libadwaita apps respond to the changes, but the shell theme and GTK3 applications do not. This has been observed on both Wayland and X11. Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10 Package Version: 1:43~rc-1ubuntu2 What I Expected: Changing the style in settings will affect all the apps that support changing light/dark mode. The shell theme will also respond to the change. What happened instead: Only libadwaita apps are affected by changing the style in Settings. GTK3 apps and the shell theme do not change. When changing to dark mode via the quick settings menu, all the apps change their color scheme appropriately. However, there is not a smooth transition when switching the style from quick settings. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic ** Attachment added: "A video of the bug." https://bugs.launchpad.net/bugs/1989477/+attachment/5615565/+files/simplescreenrecorder-2022-09-13_09.34.16.mkv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1989477 Title: Switching to dark mode in settings does not change shell theme. Status in gnome-control-center package in Ubuntu: New Bug description: Changing the "Style" in the "Appearance" section of "Settings" (gnome- control-center), does not update the shell theme. When I select dark mode from settings, Libadwaita apps respond to the changes, but the shell theme and GTK3 applications do not. This has been observed on both Wayland and X11. Ubuntu Version: Ubuntu Kinetic Kudu (development branch) | 22.10 Package Version: 1:43~rc-1ubuntu2 What I Expected: Changing the style in settings will affect all the apps that support changing light/dark mode. The shell theme will also respond to the change. What happened instead: Only libadwaita apps are affected by changing the style in Settings. GTK3 apps and the shell theme do not change. When changing to dark mode via the quick settings menu, all the apps change their color scheme appropriately. However, there is not a smooth transition when switching the style from quick settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
I can confirm for myself now aswell that I am experiencing issues. Some applications, most of them listed above in one way or another can be found to properly be unable to handle these images. Gdk-pixbuf still crashes but no longer is a buffer overwrite. Technically a win - but the key issue is apps do not know how to respond to what to do when gdk-pixbuf dies. Take eye of gnome - if you open a file directly from terminal using one of the POCs, it is fine and reads the gdk-pixbuf error correctly. But cycle to the next POC and it crashes. Probably a lot of this is apps being tied into gdk-pixbuf, and if I am correct it is a part of Gtk so apps are sort of forced to be connected to it. When one breaks down, it's like a cable wire. In the future, for stability purposes patches need to be made to apps so whenever a component like gdk-pixbuf fails, the rest of the app doesn't (or has some fallback state) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog - Eye of MATE (eom) segfaults * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
** Attachment added: "Eye of MATE Crash" https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605633/+files/EOMCrash.tar.gz ** Description changed: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog + - Eye of MATE (eom) segfaults * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 - * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md + * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still
[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
** Attachment added: "Nautilus crash" https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605632/+files/NautilusCrash.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog - Eye of MATE (eom) segfaults * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
Hmm… check Jammy/Kinetic. Can you send me the crash file/syslog? Some apps I think have proper handling of bad files while others don’t. For example, EOG can detect its a bad file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
** Description changed: [Impact] - * A buffer overwrite exists in gdk-pixbuf's thumbnailer. + * A buffer overwrite exists in gdk-pixbuf's thumbnailer. - * The GIF loader runs out of memory with specifically crafted files + * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. - * After gdk-pixbuf-thum runs out of memory, other apps can and on low + * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. - * Or, in other ways, bad gif files in other applications can open the + * Or, in other ways, bad gif files in other applications can open the door for exploits. - * Any app using gdk-pixbuf is affected, mainly file managers and image + * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] - * Take the POC's - they can be found in the issue in the GNOME repo + * Take the POC's - they can be found in the issue in the GNOME repo - * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - - Nautilus, GNOME's file manager - - Nemo, Cinnamon's file manager - - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - - PCManFM, LXDE's file manager which straight up crashes - I have not been able to produce any results with Caja (MATE's file manager) but have personally experienced issues with Nautilus. POC logs and crashes are attached. + * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: + - Nautilus, GNOME's file manager + - Nemo, Cinnamon's file manager + - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes + - PCManFM, LXDE's file manager which straight up crashes + - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) + - Eye of GNOME (eog) triggers the segfault in syslog - * If you or the system couldn't tell something is wrong, cat + * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] - * The patch itself is simple, but since gdk-pixbuf is often used with + * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. - * It is possible, and has happened in the past (which has been patched) + * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. - * That patch is essentially overflow checks - changes with GLib + * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems - * Other failures to properly handle GIFs and broken or intentionally + * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] - - * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. - * Files attached are examples or crashes - * Again, all apps using gdk-pixbuf are affected - * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ - * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md + + * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. + * Files attached are examples or crashes + * Again, all apps using gdk-pixbuf are affected + * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ + * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh
[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
** Description changed: - There is a buffer overwrite in gdk-pixbuf. I will eventually create a - whole SRU document with how to reproduce and all, but I'll just say it - is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo - causes the entire system to run out of memory. (With firefox, 1612/3922 - MB - which says something.) + [Impact] - It may be possible all apps using gdk-pixbuf can have a problem handling - files like the PoC. + * A buffer overwrite exists in gdk-pixbuf's thumbnailer. - https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 + * The GIF loader runs out of memory with specifically crafted files + with bad frame data (and images with its sizes) over the integer limit. + + * After gdk-pixbuf-thum runs out of memory, other apps can and on low + RAM systems like my old iMac, the system can completely run out of + memory. + + * Or, in other ways, bad gif files in other applications can open the + door for exploits. + + * Any app using gdk-pixbuf is affected, mainly file managers and image + viewers. + + [Test Plan] + + * Take the POC's - they can be found in the issue in the GNOME repo + + * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: + - Nautilus, GNOME's file manager + - Nemo, Cinnamon's file manager + - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes + - PCManFM, LXDE's file manager which straight up crashes + I have not been able to produce any results with Caja (MATE's file manager) but have personally experienced issues with Nautilus. POC logs and crashes are attached. + + * If you or the system couldn't tell something is wrong, cat + /var/log/syslog and enjoy the segfaults or out of memory warnings or + even kernel spam. + + [Where problems could occur] + + * The patch itself is simple, but since gdk-pixbuf is often used with + GTK apps a mistake here could be problematic. + + * It is possible, and has happened in the past (which has been patched) + that other bad GIFs can cause other crashes. + + * That patch is essentially overflow checks - changes with GLib + (GNOME's, not to be confused with glibc) and the functions used in not + only the patch but all of gdk-pixbuf can cause problems + + * Other failures to properly handle GIFs and broken or intentionally + tampered GIFs can continue and always will open the door for security + holes for other bugs + + * Again, overall a simple patch but as long as the GIFs remain handled + properly, and no changes to the GLib functions are made and to other + apps that use gdk-pixbuf (and assuming are not affected by the change + and still work), the patch does not have much regression potential. + + [Other Info] + + * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. + * Files attached are examples or crashes + * Again, all apps using gdk-pixbuf are affected + * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ + * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own
[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
Here's proposal focal patch - I noticed some whitespaces but those are in the code and not introduced by me. ** Patch added: "Proposed focal patch" https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605438/+files/gdk-pixbuf_2.40.0+dfsg-3ubuntu0.3.debdiff ** Changed in: gdk-pixbuf (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: In Progress Bug description: There is a buffer overwrite in gdk-pixbuf. I will eventually create a whole SRU document with how to reproduce and all, but I'll just say it is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo causes the entire system to run out of memory. (With firefox, 1612/3922 MB - which says something.) It may be possible all apps using gdk-pixbuf can have a problem handling files like the PoC. https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
PCManFM crashed to this. that's my last POC - I'm going to create the patch ** Attachment added: "pcmanfmcrash.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605437/+files/pcmanfmcrash.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: New Bug description: There is a buffer overwrite in gdk-pixbuf. I will eventually create a whole SRU document with how to reproduce and all, but I'll just say it is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo causes the entire system to run out of memory. (With firefox, 1612/3922 MB - which says something.) It may be possible all apps using gdk-pixbuf can have a problem handling files like the PoC. https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
Thunar, which uses tumbler for thumbnailing, produced a crash. ** Attachment added: "Tumbler (xfce thumbnailer crash)" https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605436/+files/libgdkpixbufloader-gif-crash.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: New Bug description: There is a buffer overwrite in gdk-pixbuf. I will eventually create a whole SRU document with how to reproduce and all, but I'll just say it is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo causes the entire system to run out of memory. (With firefox, 1612/3922 MB - which says something.) It may be possible all apps using gdk-pixbuf can have a problem handling files like the PoC. https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
Here is what it did to my iMac. ** Attachment added: "OldiMacSyslog" https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605435/+files/OldiMacSyslog ** Changed in: gdk-pixbuf (Ubuntu) Assignee: (unassigned) => Joshua Peisach (itzswirlz) ** Tags removed: jammy ** Tags added: bionic xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: New Bug description: There is a buffer overwrite in gdk-pixbuf. I will eventually create a whole SRU document with how to reproduce and all, but I'll just say it is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo causes the entire system to run out of memory. (With firefox, 1612/3922 MB - which says something.) It may be possible all apps using gdk-pixbuf can have a problem handling files like the PoC. https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1982898] [NEW] CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
*** This bug is a security vulnerability *** Public security bug reported: There is a buffer overwrite in gdk-pixbuf. I will eventually create a whole SRU document with how to reproduce and all, but I'll just say it is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo causes the entire system to run out of memory. (With firefox, 1612/3922 MB - which says something.) It may be possible all apps using gdk-pixbuf can have a problem handling files like the PoC. https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Assignee: Joshua Peisach (itzswirlz) Status: New ** Tags: amd64 apport-bug bionic focal xenial ** Information type changed from Private Security to Public Security ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-46829 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: New Bug description: There is a buffer overwrite in gdk-pixbuf. I will eventually create a whole SRU document with how to reproduce and all, but I'll just say it is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo causes the entire system to run out of memory. (With firefox, 1612/3922 MB - which says something.) It may be possible all apps using gdk-pixbuf can have a problem handling files like the PoC. https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I was able to open nautilus after turning WiFi off. Atom also was then able to open the project folder. -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Confirmed Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+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 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I get this error when Atom crashes. Just a bunch of "this is deprecated" " /usr/bin/atom: line 195: 16065 Killed nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1 (node:16144) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/superstring/build/Release/superstring.node'. This is deprecated, see https://github.com/electron/electron/issues/18397. " Atom not opening my project folder was what led me to realize that Nautilus was also not opening. -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Confirmed Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+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 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I have exactly the same issue but keybase is not installed on my system. I am running stock Ubuntu 22.04 . This issue happened after I did apt dist-upgrade a couple of days ago (May 4th?). I upgraded my system to 22.04 from 21.10 when 22.04 was publicly released. I used the software-updater to do the upgrade. Since then I had not had any issues at all. This issue only started after my apt dist-upgrade on around May 4th. Due to this issue I cannot run Atom as well. ** Bug watch added: github.com/electron/electron/issues #18397 https://github.com/electron/electron/issues/18397 -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Confirmed Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+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 1968382] Re: gnome-control-center crashed with SIGSEGV
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968382 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: New Bug description: When adding online accounts, ubuntu 22.04 crashes. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu10 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 17:22:12 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-04-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220408) ProcCmdline: /usr/bin/gnome-control-center ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f6124cfb2eb:mov0x8,%rax PC (0x7f6124cfb2eb) ok source "0x8" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968382/+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 1926840] Re: Display/Graphics bug
I found out what the issue was. The problem is the new linux kernal update Linux 5.8.0-50-generic. After booting up with Linux 5.8.0-48-generic (the previous one), the problem is resolved -- 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/1926840 Title: Display/Graphics bug Status in xorg package in Ubuntu: New Bug description: Ubuntu was perfect before updating it. I ran the command sudo apt update. After that, my computer graphics have become choppy. I have attached a screenshot of the problem. Description: Ubuntu 20.04.2 LTS Release: 20.04 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) Intel® HD Graphics 2500 (IVB GT1) GNOME version 3.36.8 Windowing system X11 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:20:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1028:0577] InstallationDate: Installed on 2021-02-09 (80 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. OptiPlex 7010 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=8e9a679a-a7d5-4d98-8a50-1e4ab130a8d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 12/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0WR7PY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd12/21/2015:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA03:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7010 dmi.product.sku: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926840/+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 1926840] [NEW] Display/Graphics bug
Public bug reported: Ubuntu was perfect before updating it. I ran the command sudo apt update. After that, my computer graphics have become choppy. I have attached a screenshot of the problem. Description:Ubuntu 20.04.2 LTS Release:20.04 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) Intel® HD Graphics 2500 (IVB GT1) GNOME version 3.36.8 Windowing system X11 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:20:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1028:0577] InstallationDate: Installed on 2021-02-09 (80 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. OptiPlex 7010 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=8e9a679a-a7d5-4d98-8a50-1e4ab130a8d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 12/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0WR7PY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd12/21/2015:br4.6:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA03:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7010 dmi.product.sku: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "An image so you can see what the issue is" https://bugs.launchpad.net/bugs/1926840/+attachment/5494056/+files/Untitled.png -- 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/1926840 Title: Display/Graphics bug Status in xorg package in Ubuntu: New Bug description: Ubuntu was perfect before updating it. I ran the command sudo apt update. After that, my computer graphics have become choppy. I have attached a screenshot of the problem. Description: Ubuntu 20.04.2 LTS Release: 20.04 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) Intel® HD Graphics 2500 (IVB GT1) GNOME version 3.36.8 Windowing system X11 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:20:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor
[Desktop-packages] [Bug 1923517] [NEW] tracker-store crashed with signal 5
Public bug reported: This happens with g_listenv jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi g_listenv ??:? ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Apr 12 18:16:39 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-04-07 (5 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: libc6 Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash hirsute need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1923517 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: New Bug description: This happens with g_listenv jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi g_listenv ??:? ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Apr 12 18:16:39 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-04-07 (5 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: libc6 Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1923517/+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 1660121] Re: LightDM can't use the user background on Mate
** Tags added: hirsute -- 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/1660121 Title: LightDM can't use the user background on Mate Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04 alpha 2). On Mate, the LightDM Gtk Greeter can't use the user background. It works fine on other DEs like Xfce. From what I understand, LightDM and/or the Gkt greeter (not sure which one handles the background) gets the background path from Gsettings, so I assume it can't find the one from Mate, which stores it in "org.mate.background picture-filename". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1660121/+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 1919255] [NEW] tracker-store crashed with signal 5
Public bug reported: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash hirsute need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: New Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+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 1918186] [NEW] tracker-store crashed with signal 5 in g_printerr()
Public bug reported: Just happened, didn't really do anything. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 8 14:50:14 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (8 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: evolution-data-server Signal: 5 SourcePackage: tracker StacktraceTop: g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libsqlite3.so.0 () () () Title: tracker-store crashed with signal 5 in g_printerr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash hirsute need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1918186 Title: tracker-store crashed with signal 5 in g_printerr() Status in tracker package in Ubuntu: New Bug description: Just happened, didn't really do anything. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 8 14:50:14 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (8 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: evolution-data-server Signal: 5 SourcePackage: tracker StacktraceTop: g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libsqlite3.so.0 () () () Title: tracker-store crashed with signal 5 in g_printerr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1918186/+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 1911793] [NEW] gnome-screenhot causes windows manager to freeze
Public bug reported: when running gnome-screenshot -i and selecting "select area to grab", the main window disappears, changes the cursor to the crosshairs, then reappears suddenly. At that point, the gnome windows manager is frozen, and switching windows can only be done with keyboard shortcuts. More information: Ubuntu 20.04.1 LTS gnome-screenshot: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Additional details: VMWare was running ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Description changed: when running gnome-screenshot -i and selecting "select area to grab", the main window disappears, changes the cursor to the crosshairs, then reappears suddenly. At that point, the gnome windows manager is frozen, and switching windows can only be done with keyboard shortcuts. More information: Ubuntu 20.04.1 LTS gnome-screenshot: - Installed: 3.36.0-1ubuntu1 - Candidate: 3.36.0-1ubuntu1 - Version table: - *** 3.36.0-1ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.36.0-1ubuntu1 + Candidate: 3.36.0-1ubuntu1 + Version table: + *** 3.36.0-1ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status + + Additional details: + VMWare was running ** Description changed: when running gnome-screenshot -i and selecting "select area to grab", the main window disappears, changes the cursor to the crosshairs, then reappears suddenly. At that point, the gnome windows manager is frozen, and switching windows can only be done with keyboard shortcuts. More information: - Ubuntu 20.04.1 LTS - gnome-screenshot: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Additional details: VMWare was running -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1911793 Title: gnome-screenhot causes windows manager to freeze Status in gnome-screenshot package in Ubuntu: New Bug description: when running gnome-screenshot -i and selecting "select area to grab", the main window disappears, changes the cursor to the crosshairs, then reappears suddenly. At that point, the gnome windows manager is frozen, and switching windows can only be done with keyboard shortcuts. More information: Ubuntu 20.04.1 LTS gnome-screenshot: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Additional details: VMWare was running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1911793/+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 1905153] [NEW] Brightness only works on one display, not two
Public bug reported: Dell Inspiron 15-3567, Hirsute My display setup is the laptop and on the right a monitor. As I change my brightness, lower or higher, on the laptop the brightness will change but on the monitor it won't. Not the physical monitor brightness-that obviously can't be controlled- but the content of what the monitor shows should be dimming/brightening. (For example if theoretically I turned the brightness to 0, to an all dark screen, it should be all dark on the monitor aswell, even if the monitor brightness is max, the OS is showing nothing) Yes, I looked through GNOME's settings daemon and this is most likely the package this occurs in. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 02:03:00 2020 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201120) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1905153 Title: Brightness only works on one display, not two Status in gnome-control-center package in Ubuntu: New Bug description: Dell Inspiron 15-3567, Hirsute My display setup is the laptop and on the right a monitor. As I change my brightness, lower or higher, on the laptop the brightness will change but on the monitor it won't. Not the physical monitor brightness-that obviously can't be controlled-but the content of what the monitor shows should be dimming/brightening. (For example if theoretically I turned the brightness to 0, to an all dark screen, it should be all dark on the monitor aswell, even if the monitor brightness is max, the OS is showing nothing) Yes, I looked through GNOME's settings daemon and this is most likely the package this occurs in. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 02:03:00 2020 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201120) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905153/+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 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
This iso won't install. On Tue, Nov 3, 2020 at 8:35 PM Daniel van Vugt <1902...@bugs.launchpad.net> wrote: > Please run these commands: > > ls -l /dev/dri/* > dri.txt > glxinfo > glx.txt > > and attach the resulting text files here. > > ** Changed in: mesa (Ubuntu) >Status: New => Incomplete > > ** Changed in: xf86-video-armsoc (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1902652 > > Title: > [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow > > Status in mesa package in Ubuntu: > Incomplete > Status in xf86-video-armsoc package in Ubuntu: > Incomplete > > Bug description: > 3d rendering is very slow, also when surfing the internet, webpages > take a while to render. Internet access is not the problem. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > Uname: Linux 4.19.64+ aarch64 > ApportVersion: 2.20.9-0ubuntu7.18 > Architecture: arm64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: XFCE > Date: Tue Nov 3 05:42:00 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: > > Lspci: > > ProcEnviron: >LANGUAGE=en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ > root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ > noquiet splash vt.handoff=1 > Renderer: Software > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > XorgConf: >Section "Device" > Identifier "Allwinner sun4i DRM driver" > Driver "armsoc" > Option "DRI2" "true" >EndSection > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+subscriptions > -- 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/1902652 Title: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow Status in mesa package in Ubuntu: Incomplete Status in xf86-video-armsoc package in Ubuntu: Incomplete Bug description: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage
Re: [Desktop-packages] [Bug 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow
there is no ubuntu 20 for my board. On Tue, Nov 3, 2020 at 12:25 AM Daniel van Vugt <1902...@bugs.launchpad.net> wrote: > ** Summary changed: > > - 3d rendering is very slow > + [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1902652 > > Title: > [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow > > Status in xorg package in Ubuntu: > New > > Bug description: > 3d rendering is very slow, also when surfing the internet, webpages > take a while to render. Internet access is not the problem. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > Uname: Linux 4.19.64+ aarch64 > ApportVersion: 2.20.9-0ubuntu7.18 > Architecture: arm64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: XFCE > Date: Tue Nov 3 05:42:00 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: > > Lspci: > > ProcEnviron: >LANGUAGE=en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ > root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ > noquiet splash vt.handoff=1 > Renderer: Software > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > XorgConf: >Section "Device" > Identifier "Allwinner sun4i DRM driver" > Driver "armsoc" > Option "DRI2" "true" >EndSection > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902652/+subscriptions > -- 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/1902652 Title: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow Status in mesa package in Ubuntu: New Status in xf86-video-armsoc package in Ubuntu: New Bug description: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1902652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1902652] [NEW] 3d rendering is very slow
Public bug reported: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 bionic performance 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/1902652 Title: 3d rendering is very slow Status in xorg package in Ubuntu: New Bug description: 3d rendering is very slow, also when surfing the internet, webpages take a while to render. Internet access is not the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 05:42:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902652/+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 1030022] Re: Port from legacy Xlib to modern XCB
It looks like this was already changed more recently in 2019/2020 with 4.4 - 4.6 ** Changed in: muffin (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1030022 Title: Port from legacy Xlib to modern XCB Status in Compiz: Triaged Status in 9wm package in Ubuntu: New Status in aewm package in Ubuntu: New Status in aewm++ package in Ubuntu: New Status in afterstep package in Ubuntu: New Status in amiwm package in Ubuntu: Invalid Status in blackbox package in Ubuntu: New Status in cairo package in Ubuntu: New Status in compiz package in Ubuntu: Triaged Status in ctwm package in Ubuntu: New Status in dwm package in Ubuntu: Opinion Status in enlightenment package in Ubuntu: New Status in fvwm package in Ubuntu: New Status in fvwm1 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in icewm package in Ubuntu: New Status in jwm package in Ubuntu: Invalid Status in larswm package in Ubuntu: New Status in lwm package in Ubuntu: New Status in matchbox-window-manager package in Ubuntu: New Status in metacity package in Ubuntu: Invalid Status in miwm package in Ubuntu: New Status in muffin package in Ubuntu: Fix Released Status in mutter package in Ubuntu: New Status in pekwm package in Ubuntu: New Status in ratpoison package in Ubuntu: New Status in sapphire package in Ubuntu: New Status in sawfish package in Ubuntu: New Status in spectrwm package in Ubuntu: Fix Released Status in tinywm package in Ubuntu: New Status in tritium package in Ubuntu: New Status in twm package in Ubuntu: New Status in vtwm package in Ubuntu: New Status in w9wm package in Ubuntu: New Status in windowlab package in Ubuntu: New Status in wm2 package in Ubuntu: New Status in wmaker package in Ubuntu: Opinion Status in xmonad package in Ubuntu: New Bug description: Port/rewrite the window manager to use the modern XCB (X C Binding) library instead of the old legacy Xlib. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1030022/+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 1884056] [NEW] Package Homepage links to a 404 error
Public bug reported: Package info provides Homepage: https://wslu.patrickwu.space/ It leads to a Github Pages 404 error. Appears to affect all versions. ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Tags: bitesize packaging string-fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1884056 Title: Package Homepage links to a 404 error Status in wslu package in Ubuntu: New Bug description: Package info provides Homepage: https://wslu.patrickwu.space/ It leads to a Github Pages 404 error. Appears to affect all versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1884056/+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 1880346] Re: Zooming in requires Ctrl + Shift + Plus-zoom out doesn't require shift
You do need to shift-it's intentional ** Summary changed: - Zooming in requires Ctrl + Shift + Plus-zoom out doesn't require shift + [INVALID] Zooming in requires Ctrl + Shift + Plus-zoom out doesn't require shift -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1880346 Title: [INVALID] Zooming in requires Ctrl + Shift + Plus-zoom out doesn't require shift Status in gnome-terminal package in Ubuntu: Invalid Bug description: The keybindings for gnome-terminal: Zoom In: Ctrl++ Zoom Out: Ctrl+- Zooming out works fine-however when Zooming in you must use Shift. When zooming out you do not need to shift. Ubuntu is affected by this and I found a problem in Tilix, which I will edit and post here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat May 23 19:37:22 2020 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-05-22 (1 days ago) InstallationMedia: cinnamon-remix "groovy" (20200512) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1880346/+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 1880346] [NEW] Zooming in requires Ctrl + Shift + Plus-zoom out doesn't require shift
Public bug reported: The keybindings for gnome-terminal: Zoom In: Ctrl++ Zoom Out: Ctrl+- Zooming out works fine-however when Zooming in you must use Shift. When zooming out you do not need to shift. Ubuntu is affected by this and I found a problem in Tilix, which I will edit and post here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat May 23 19:37:22 2020 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-05-22 (1 days ago) InstallationMedia: cinnamon-remix "groovy" (20200512) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug groovy ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1880346 Title: Zooming in requires Ctrl + Shift + Plus-zoom out doesn't require shift Status in gnome-terminal package in Ubuntu: Invalid Bug description: The keybindings for gnome-terminal: Zoom In: Ctrl++ Zoom Out: Ctrl+- Zooming out works fine-however when Zooming in you must use Shift. When zooming out you do not need to shift. Ubuntu is affected by this and I found a problem in Tilix, which I will edit and post here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat May 23 19:37:22 2020 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-05-22 (1 days ago) InstallationMedia: cinnamon-remix "groovy" (20200512) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1880346/+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 1877856] [NEW] Display garbled after resume from suspect
Public bug reported: I just upgraded 18.04 -> 20.04. Then after resuming from suspend on my laptop, the display is garbled blocks of random colors. It changes frequently to other random colors. Power cycling the laptop clears the issue, but only until it is suspended again. The VT3 console shows: nouveau :01:00.0: gr: PGRAPH_TLB flush idle timeout fail Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 10 05:53:41 2020 DistUpgraded: 2020-05-09 01:40:08,730 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GT218M [NVS 3100M] [1028:040a] MachineType: Dell Inc. Latitude E6410 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-05-09 (1 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0K42JR dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat May 19 22:08:24 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1877856 Title: Display garbled after resume from suspect Status in xorg package in Ubuntu: New Bug description: I just upgraded 18.04 -> 20.04. Then after resuming from suspend on my laptop, the display is garbled blocks of random colors. It changes frequently to other random colors. Power cycling the laptop clears the issue, but only until it is suspended again. The VT3 console shows: nouveau :01:00.0: gr: PGRAPH_TLB flush idle timeout fail Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 10 05:53:41 2020 DistUpgraded: 2020-05-09 01:40:08,730 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GT218M [NVS 3100M] [1028:040a] MachineType: Dell Inc. Latitude E6410 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-05-09 (1 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0K42JR dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz:
[Desktop-packages] [Bug 1870856] [NEW] Changing Icons does not automatically change on desktop
Public bug reported: Ubuntu Desktop: Please note first that I had cinnamon-remix installed-I was bored so I installed Ubuntu and Ubuntu Budgie desktops, along with gnome-tweaks and gnome-shell. I was changing the icons using GNOME Tweak Tool. In nautilus, the changes automatically would apply. However, for the desktop, the changes would NOT automatically apply. I had to re-login to see the changes. If possible, I hope you guys can install a fresh Ubuntu and confirm this. Theme used was Kimmo-Dark from Ubuntu Cinnamon, and I found this issue for pretty much all the themes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.447 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 20:39:23 2020 InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: cinnamon-remix 20.04 "focal" - all amd64 (20200401) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1870856 Title: Changing Icons does not automatically change on desktop Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Desktop: Please note first that I had cinnamon-remix installed-I was bored so I installed Ubuntu and Ubuntu Budgie desktops, along with gnome-tweaks and gnome-shell. I was changing the icons using GNOME Tweak Tool. In nautilus, the changes automatically would apply. However, for the desktop, the changes would NOT automatically apply. I had to re-login to see the changes. If possible, I hope you guys can install a fresh Ubuntu and confirm this. Theme used was Kimmo-Dark from Ubuntu Cinnamon, and I found this issue for pretty much all the themes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.447 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 20:39:23 2020 InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: cinnamon-remix 20.04 "focal" - all amd64 (20200401) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1870856/+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 1867613] Re: Ubuntu dock does not allow drag and move icons at bottom
I get the same thing-clicking and moving the icons all the way to the bottom won't work, however you can go as far down as the one above the bottom. Then if you move the bottom up, which you can,then that once will be moved to the bottom. So it's limited. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Confirmed -- 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/1867613 Title: Ubuntu dock does not allow drag and move icons at bottom Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 daily development branch @ 16/3/2020 After a clean install daily at 14/3/2020 the ubuntu dock does not allow drag and move icons anymore with the dock placed at bottom you can still mouseclick and hold the icon, but it does not make space between other icons to release starting an application still showing the icon, and add to favorites still works the dock placed left or right it works better ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 12:31:30 2020 InstallationDate: Installed on 2020-03-14 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867613/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I'm running Eoan. After studying the comments here, I installed libgtk-3-0 from focal (https://packages.ubuntu.com/focal/libgtk-3-0). This forced me to upgrade CUPS. I'm not sure if printing still works, but the cut/copy/paste issue appears to be resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1340907] Re: cannot edit tags in m4a files
I just encountered this in Ubuntu 19.10 with Rhythmbox 3.4.3. I had just replaced some MP3 files with FLAC files and then wanted to edit metadata for consistency with my library. I got the same error "File corrupted during write." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1340907 Title: cannot edit tags in m4a files Status in rhythmbox package in Ubuntu: Confirmed Bug description: Rhythmbox cannot edit m4a tags. For example, I right-click on a song and the "properties" window opens. I change a field, for example "title", and then click "close". A window opens saying "Error while saving song information. File corrupted during write." The title is unchanged in the song, as can be seen in the Rhythmbox window and can be verified with another program like Easytag. Additional details that might be useful: * The permissions on the m4a file are -rw-rw-rw- * Though the error window says the "File corrupted during write", the m4a file is in fact not even modified * There is no problem with mp3 files; for example, the process described above can be used successfully to change the title of an mp3 song * I used to be able to edit m4a tags in Ubuntu 12.10; this problem arose when I upgraded to Ubuntu 14.04 LTS. Although there exist other programs to tag m4a files, they do not provide a useable work-around. If you use such a program to change an m4a tag, then the music library comes inconsistent with Rhythmbox's "rhythmdb.xml" database. Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 11 11:42:44 2014 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2014-04-25 (77 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1340907/+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 1854633] Re: touchpad only works as mouse, no touchpad features
Ah ha! This is a bug, but it gets resolved after a laptop suspend-resume cycle. That is, the touchpad is not detected after a reboot. However, it is detected after the next suspend-resume. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1854633 Title: touchpad only works as mouse, no touchpad features Status in xserver-xorg-input-libinput package in Ubuntu: Invalid Bug description: I've never had a problem before. The touchpad worked great on all Ubuntu releases including Eoan until I installed the latest updates today. I generally use Wayland. I haven't tested the touchpad on X11. Description: Ubuntu 19.10 Release: 19.10 xserver-xorg-input-libinput: Installed: 0.29.0-1 Candidate: 0.29.0-1 Version table: *** 0.29.0-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1854633/+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 1854633] Re: touchpad only works as mouse, no touchpad features
This problem seems resolved. I'm not sure what I did to fix it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1854633 Title: touchpad only works as mouse, no touchpad features Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I've never had a problem before. The touchpad worked great on all Ubuntu releases including Eoan until I installed the latest updates today. I generally use Wayland. I haven't tested the touchpad on X11. Description: Ubuntu 19.10 Release: 19.10 xserver-xorg-input-libinput: Installed: 0.29.0-1 Candidate: 0.29.0-1 Version table: *** 0.29.0-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1854633/+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 1854633] Re: touchpad only works as mouse, no touchpad features
Since I use wayland, I'm not sure what to report instead of Xorg.0.log (https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1854633 Title: touchpad only works as mouse, no touchpad features Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I've never had a problem before. The touchpad worked great on all Ubuntu releases including Eoan until I installed the latest updates today. I generally use Wayland. I haven't tested the touchpad on X11. Description: Ubuntu 19.10 Release: 19.10 xserver-xorg-input-libinput: Installed: 0.29.0-1 Candidate: 0.29.0-1 Version table: *** 0.29.0-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1854633/+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 1854633] [NEW] touchpad only works as mouse, no touchpad features
Public bug reported: I've never had a problem before. The touchpad worked great on all Ubuntu releases including Eoan until I installed the latest updates today. I generally use Wayland. I haven't tested the touchpad on X11. Description:Ubuntu 19.10 Release:19.10 xserver-xorg-input-libinput: Installed: 0.29.0-1 Candidate: 0.29.0-1 Version table: *** 0.29.0-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1854633/+attachment/5309083/+files/devices -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1854633 Title: touchpad only works as mouse, no touchpad features Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I've never had a problem before. The touchpad worked great on all Ubuntu releases including Eoan until I installed the latest updates today. I generally use Wayland. I haven't tested the touchpad on X11. Description: Ubuntu 19.10 Release: 19.10 xserver-xorg-input-libinput: Installed: 0.29.0-1 Candidate: 0.29.0-1 Version table: *** 0.29.0-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1854633/+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 1854633] Re: touchpad only works as mouse, no touchpad features
** Attachment added: "xinput --list" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1854633/+attachment/5309084/+files/xinput -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1854633 Title: touchpad only works as mouse, no touchpad features Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I've never had a problem before. The touchpad worked great on all Ubuntu releases including Eoan until I installed the latest updates today. I generally use Wayland. I haven't tested the touchpad on X11. Description: Ubuntu 19.10 Release: 19.10 xserver-xorg-input-libinput: Installed: 0.29.0-1 Candidate: 0.29.0-1 Version table: *** 0.29.0-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1854633/+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 1850775] Re: DNS info is not loaded by dhclient
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
It should be removed from all types eventually, this was a distro wide change no an ISO specific change. ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Invalid Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Ubuntu discontinued the use of /etc/network/interfaces a number of releases ago and in 19.10 have removed ifupdown. Please see the migrating to netplan document: https://wiki.ubuntu.com/MigratingToNetplan If you need to continue using /etc/network/interfaces then there are ways to install ifupdown and disable netplan. I am closing this as invalid. ** Changed in: network-manager (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Invalid Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1603430] Re: Firefox dropdowns in wrong location
I'm on elementary OS (based on Ubuntu 18.04) and also experience this issue. As Tigran mentioned, disabling the Title Bar functions as a workaround. I presume the Client Side Decoration feature is what introduced this bug in the first place. -- 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/1603430 Title: Firefox dropdowns in wrong location Status in Linux Mint: New Status in cinnamon-desktop-environment package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: On Mint 17.3 Cinnamon 64bit. Steps to reproduce: * Do a fresh install. * Run mintupdate and update all packages. * Run firefox. * Start right clicking on the page to open the context menu. Resize the window and perhaps move it around the screen a couple of times. Right click some more. * Observer that, eventually, the context menu will start to appear in incorrect locations on the screen. The same also happens with the search bar, text fields and any other dropdown box. In the worst embodiment of the bug, the menu opens underneath the pointer and treats the release of the mouse button as a click, and so does things the user does not want to do. I believe the root cause is the following bug in GTK+ 3.10.8. Firefox switched over to using GTK+3 in version 46 which is when this bug appeared and has been there ever since. https://bugzilla.gnome.org/show_bug.cgi?id=758609 https://bugzilla.mozilla.org/show_bug.cgi?id=1022241 Mozilla aren't going to fix it because it's a GTK bug. GTK have already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not have the patch. Please roll out the patch for us 17.3 users who cannot upgrade. I can confirm that the problem is solved in Mint 18. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1603430/+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 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed ob
Disabling auto-hide of the dock seems to prevent this from happening. -- 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/1841794 Title: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f ubuntu-bug crash report for bug reported in LP: #1841680 On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 10:42:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-19 (554 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841794/+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 1841680] Re: gnome-shell crashes with SIGTRAP: Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition
Crash report bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841794, ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1841680 Title: gnome-shell crashes with SIGTRAP: Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition Status in gnome-shell package in Ubuntu: New Bug description: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+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 1841680] Re: crash signal 5: clutter.PropertyTransition
This seems to only happen when I launch apps from the dock. If I launch from a terminal or from the search, they run and do not crash. -- 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/1841680 Title: crash signal 5: clutter.PropertyTransition Status in gnome-shell package in Ubuntu: New Bug description: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+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 1841680] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1841680/+attachment/5285142/+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/1841680 Title: crash signal 5: clutter.PropertyTransition Status in gnome-shell package in Ubuntu: New Bug description: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+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 1841680] [NEW] crash signal 5: clutter.PropertyTransition
Public bug reported: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected eoan ** Tags added: apport-collected eoan ** Description changed: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2018-02-19 (553 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia + Package: gnome-shell 3.33.91-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 + RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 + Tags: eoan + Uname: Linux 5.2.0-13-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago) + UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo + _MarkForUpload: True -- 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/1841680 Title: crash signal 5: clutter.PropertyTransition Status in gnome-shell package in Ubuntu: New Bug description: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+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 1841680] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1841680/+attachment/5285144/+files/ShellJournal.txt ** Description changed: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when - opening up applications. + opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ - --- - ProblemType: Bug - ApportVersion: 2.20.11-0ubuntu7 - Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - DisplayManager: gdm3 - DistroRelease: Ubuntu 19.10 - InstallationDate: Installed on 2018-02-19 (553 days ago) - InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia - Package: gnome-shell 3.33.91-1ubuntu1 - PackageArchitecture: amd64 - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 - RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 - Tags: eoan - Uname: Linux 5.2.0-13-generic x86_64 - UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago) - UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo - _MarkForUpload: True -- 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/1841680 Title: crash signal 5: clutter.PropertyTransition Status in gnome-shell package in Ubuntu: New Bug description: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+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 1841680] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1841680/+attachment/5285145/+files/monitors.xml.txt ** Attachment removed: "ShellJournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+attachment/5285144/+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/1841680 Title: crash signal 5: clutter.PropertyTransition Status in gnome-shell package in Ubuntu: New Bug description: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+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 1841680] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1841680/+attachment/5285141/+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/1841680 Title: crash signal 5: clutter.PropertyTransition Status in gnome-shell package in Ubuntu: New Bug description: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+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 1841680] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1841680/+attachment/5285143/+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/1841680 Title: crash signal 5: clutter.PropertyTransition Status in gnome-shell package in Ubuntu: New Bug description: On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. gnome-shell journal output: https://paste.ubuntu.com/p/SYgKT6GHcG/ syslog output: https://paste.ubuntu.com/p/9YnWwKrQrB/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841680/+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 1730071] Re: Application icons appear stretched when using scaling
+1, Ubuntu 18.01 ** Attachment added: "Image of problem." https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730071/+attachment/5230105/+files/Screenshot%20from%202019-01-17%2021-16-27.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1730071 Title: Application icons appear stretched when using scaling Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: The appindicator gnome extension shows the "system tray icons" in the upper right corner of the screen. However the icons appear vertically stretched. The problem appears to be purely visual, as they still work as expected. > lsb_release -rd Description:Ubuntu 17.10 Release:17.10 > apt-cache policy gnome-shell-extension-appindicator gnome-shell-extension-appindicator: Installed: 17.10.1 Candidate: 17.10.1 Version table: *** 17.10.1 500 500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730071/+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 66566]
This change made me a little sad. I used the old hotkeys about a quarter or a third of every time I used the URL bar. -- 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/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+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 1760068] Re: Wrong resolution at unlock screen
Nevermind, the full solution from the link did in fact work for me. Using nvidia-driver-390. I am copy/pasting the solution here for any other users: 1. Create an xorg.conf file for your nVidia device. All you have to do for this is to launch the command: sudo nvidia-xconfig This will create a file /etc/X11/xorg.conf. 2. Edit the created file /etc/X11/xorg.conf and add at the end the lines: Section "Files" ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg" ModulePath "/usr/lib/xorg/modules" EndSection 3. Save and restart the X server. Now, for the first and second user you should have the nvidia driver in use, with the correct resolution and fast rendering. You can check it using the command: --- Note by JoshuaD: I did not try anything below this line - glxgears -info |grep NVIDIA which should return the nvidia opengl version. Note, there is also a problem of slow scrolling in the virtual console (Ctrl-Alt-F1). To solve this, edit /etc/default/grub and set the GRUB_CMDLINE_LINUX variable as: GRUB_CMDLINE_LINUX="video=vesafb:mtrr:3,ywrap" then do: sudo update-grub and reboot. Now, the scrolling speed in the virtual console should be very fast. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1760068] Re: Wrong resolution at unlock screen
That work around did not work for me. This bug also affects my TTY displays. Xubuntu 18.04 NVIDIA GeForce GTX 750Ti 64-bit Intel i5-8400 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1797578] [NEW] unable to open Ubuntu Software
Public bug reported: when i try to open Ubuntu Software it flashes on the launcher then the icon looks like it didn't open. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 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: Fri Oct 12 16:41:02 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3616] InstallationDate: Installed on 2018-01-21 (264 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO Lenovo H420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=510425b4-02db-49c7-91bd-587ef9d2671d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2011 dmi.bios.vendor: LENOVO dmi.bios.version: DPKT22A dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrDPKT22A:bd11/08/2011:svnLENOVO:pnLenovoH420:pvrLenovo:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Lenovo H420 dmi.product.version: Lenovo dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-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 Oct 12 15:05:52 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputKYE SYSTEMS CORP. Wired Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1797578 Title: unable to open Ubuntu Software Status in xorg package in Ubuntu: New Bug description: when i try to open Ubuntu Software it flashes on the launcher then the icon looks like it didn't open. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 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: Fri Oct 12 16:41:02 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3616] InstallationDate: Installed on 2018-01-21 (264 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO Lenovo H420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=510425b4-02db-49c7-91bd-587ef9d2671d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2011
[Desktop-packages] [Bug 1785311] Re: VLAN in GUI's network setting is under Bluetooth section
Hi! Thanks for taking the time to file a bug. I have re-assigned this to network-manager as this isn't a bug with the vlan package, but with the UI itself. It may need to be moved to yet another package, but this should get the right people's attention. Could you also let us know what version of Ubuntu you are using? (e.g. `cat /etc/os-release`) Thanks! ** Package changed: vlan (Ubuntu) => network-manager (Ubuntu) -- 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/1785311 Title: VLAN in GUI's network setting is under Bluetooth section Status in network-manager package in Ubuntu: New Bug description: I install vlan package and setup VLAN successfully. But when I check the Network settings in GUI, the created VLAN interface is under Bluetooth section. For reference, here is the screen shot of the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1785311/+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 1772711] Re: Static library for libyajl is "libyajl_s.a" and pkg-config lies about it
** Bug watch added: Debian Bug tracker #877285 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877285 ** Also affects: yajl (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877285 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yajl in Ubuntu. https://bugs.launchpad.net/bugs/1772711 Title: Static library for libyajl is "libyajl_s.a" and pkg-config lies about it Status in yajl package in Ubuntu: New Status in yajl package in Debian: Unknown Bug description: The static library for libyajl-dev is installed as /usr/lib/x86_64 -linux-gnu/libyajl_s.a and not /usr/lib/x86_64-linux-gnu/libyajl.a. This means that static linking with "-lyajl" will not find it; you need to use "-lyajl_s". This has not been explained to pkg-config (and I suspect the pkg- config file format can't express it). So when you do "pkg-config --static --libs yajl", you get back "-lyajl" and not "-lyajl_s". You also get the erroneous "-lyajl" when you ask pkg-config about anything that *depends* on yajl, such as raptor2: $ pkg-config --libs --static raptor2 -lraptor2 -lcurl -lxml2 -lxslt -lxml2 -lyajl This makes pkg-config not work for linking statically against any library that depends on yajl. The Debian bug for this problem is at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=877285 and has been sitting idel for several months. I've also opened an upstream bug at https://github.com/lloyd/yajl/issues/209 but the upstream project seems suspiciously quiet, and I think the upstream maintainer may have quit. I believe the actual problem with the upstream code is at https://github.com/lloyd/yajl/blob/5e3a7856e643b4d6410ddc3f84bc2f38174f2872/src/CMakeLists.txt#L38-L40 where CMake is told to build a static library and a dynamic library with different names. (This might be necessary on Windows, but nobody knows how to deal with it in Linux.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libyajl-dev 2.1.0-2 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 22 12:37:28 2018 Dependencies: gcc-6-base 6.2.0-3ubuntu11~12.04 [origin: unknown] libc6 2.23-0ubuntu10 libgcc1 1:6.2.0-3ubuntu11~12.04 [origin: unknown] libyajl2 2.1.0-2 multiarch-support 2.23-0ubuntu10 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-18 (1859 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: yajl UpgradeStatus: Upgraded to xenial on 2018-02-26 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yajl/+bug/1772711/+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 1765794] [NEW] xcalc displays a comma for divide instead of a forward slash
Public bug reported: xcalc has buttons down the right side. In an older release, those used to be: AC DRG y^x / * - + = Right now, my system is displaying: AC DRG y^x , * - + = Using the "," button works as the divide key. I have no idea why it's displaying a comma instead of "/" or "÷". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: x11-apps 7.7+6ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Apr 20 13:06:43 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.13.0-36-generic, x86_64: installed ExecutablePath: /usr/bin/xcalc GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] [1002:675d] (prog-if 00 [VGA controller]) Subsystem: Dell Turks PRO [Radeon HD 7570] [1028:2b20] InstallationDate: Installed on 2018-03-09 (42 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20180108.1) MachineType: Hewlett-Packard HP Z620 Workstation ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/mirror2018-m18rootalv ro SourcePackage: x11-apps UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: 2UA32102W6 dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: 2UA32102W6 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: x11-apps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu ** Attachment added: "Screenshot of xcaclc" https://bugs.launchpad.net/bugs/1765794/+attachment/5124100/+files/Screenshot_2018-04-20_13-12-07.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-apps in Ubuntu. https://bugs.launchpad.net/bugs/1765794 Title: xcalc displays a comma for divide instead of a forward slash Status in x11-apps package in Ubuntu: New Bug description: xcalc has buttons down the right side. In an older release, those used to be: AC DRG y^x / * - + = Right now, my system is displaying: AC DRG y^x , * - + = Using the "," button works as the divide key. I have no idea why it's displaying a comma instead of "/" or "÷". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: x11-apps 7.7+6ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Apr 20 13:06:43 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.13.0-36-generic, x86_64: installed ExecutablePath: /usr/bin/xcalc GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] [1002:675d] (prog-if 00 [VGA controller]) Subsystem: Dell Turks PRO [Radeon HD 7570] [1028:2b20] InstallationDate: Installed on 2018-03-09 (42 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20180108.1) MachineType: Hewlett-Packard HP Z620 Workstation ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed root=/dev/mapper/mirror2018-m18rootalv ro SourcePackage: x11-apps UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: 2UA32102W6 dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: 2UA32102W6 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias:
[Desktop-packages] [Bug 1753796] [NEW] Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre-release)
Public bug reported: On Ubuntu 18.04 with the NVIDIA development repository PPA, installing cuda-drivers I get the following error during the installation of nvidia-390: dpkg: error processing archive /var/cache/apt/archives/nvidia-390_390.30-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package libglx-mesa0:amd64 18.0.0~rc4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglx-mesa0 18.0.0~rc4-1ubuntu3 ProcVersionSignature: User Name 4.15.0-1002.2-azure 4.15.3 Uname: Linux 4.15.0-1002-azure x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Tue Mar 6 17:38:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK210GL [Tesla K80] [10de:106c] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1002-azure root=UUID=950907d2-f8b1-431a-8195-e06fbf9a814b ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 94AF2AB7-6288-E94C-9C01-1305DF401054 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu uec-images -- 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/1753796 Title: Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre- release) Status in mesa package in Ubuntu: New Bug description: On Ubuntu 18.04 with the NVIDIA development repository PPA, installing cuda-drivers I get the following error during the installation of nvidia-390: dpkg: error processing archive /var/cache/apt/archives/nvidia-390_390.30-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package libglx-mesa0:amd64 18.0.0~rc4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglx-mesa0 18.0.0~rc4-1ubuntu3 ProcVersionSignature: User Name 4.15.0-1002.2-azure 4.15.3 Uname: Linux 4.15.0-1002-azure x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Tue Mar 6 17:38:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK210GL [Tesla K80] [10de:106c] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1002-azure root=UUID=950907d2-f8b1-431a-8195-e06fbf9a814b ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias:
[Desktop-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
By commenting the lines from /etc/pulse/default.pa #.ifexists module-switch-on-connect.so #load-module module-switch-on-connect #.endif And reinstalling pulse audio and alsa-base as here: apt-get remove --purge pulseaudio rm -rf /etc/pulse apt-get install pulseaudio reboot I managed to get the audio again, but I cannot control it with the volume controls of my keyboard, neither with thw sound tray icon(that completely dissapeared) -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+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 1742449] Re: nvidia-340.104 dkms fails to build against 4.13.0-26
The reason the 4.9 kernel works is because Meltdown fixes haven't been applied to it yet. ** Description changed: Laptops like my Thinkpad W510 cannot use newer drivers than nvidia-340 because support for their old GPU was dropped in newer revisions. Meltdown/Spectre is upon us and I got 4.13.0-26 today, but nvidia-340's dkms driver will not build, for the common reason most nvidia drivers won't build against the new kernels. Looking at nvidia's official announcement I did not see a plan or release date for updates to nvidia-340, yet. - Since my laptop is my own, I'm running with the pre-KPTI 4.1.0-42 for + Since my laptop is my own, I'm running with the pre-KPTI 4.10.0-42 for now, but figured I should report this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1742449 Title: nvidia-340.104 dkms fails to build against 4.13.0-26 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Laptops like my Thinkpad W510 cannot use newer drivers than nvidia-340 because support for their old GPU was dropped in newer revisions. Meltdown/Spectre is upon us and I got 4.13.0-26 today, but nvidia-340's dkms driver will not build, for the common reason most nvidia drivers won't build against the new kernels. Looking at nvidia's official announcement I did not see a plan or release date for updates to nvidia-340, yet. Since my laptop is my own, I'm running with the pre-KPTI 4.10.0-42 for now, but figured I should report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1742449/+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 1742449] [NEW] nvidia-340.104 dkms fails to build against 4.13.0-26
Public bug reported: Laptops like my Thinkpad W510 cannot use newer drivers than nvidia-340 because support for their old GPU was dropped in newer revisions. Meltdown/Spectre is upon us and I got 4.13.0-26 today, but nvidia-340's dkms driver will not build, for the common reason most nvidia drivers won't build against the new kernels. Looking at nvidia's official announcement I did not see a plan or release date for updates to nvidia-340, yet. Since my laptop is my own, I'm running with the pre-KPTI 4.1.0-42 for now, but figured I should report this. ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1742449 Title: nvidia-340.104 dkms fails to build against 4.13.0-26 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Laptops like my Thinkpad W510 cannot use newer drivers than nvidia-340 because support for their old GPU was dropped in newer revisions. Meltdown/Spectre is upon us and I got 4.13.0-26 today, but nvidia-340's dkms driver will not build, for the common reason most nvidia drivers won't build against the new kernels. Looking at nvidia's official announcement I did not see a plan or release date for updates to nvidia-340, yet. Since my laptop is my own, I'm running with the pre-KPTI 4.1.0-42 for now, but figured I should report this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1742449/+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 1496542] Re: Running processes left after disabling screen reader
This bug also happens in Ubuntu Budgie 17.10. To be clear, my Screen Reader setting in the Universal Access application is Off. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1496542 Title: Running processes left after disabling screen reader Status in speech-dispatcher package in Ubuntu: Triaged Bug description: After I disabled my screen reader, I noticed that when running "ps xa | grep -P 'speech-dispatcher.*\.conf'" I get: 17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf 17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf 17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf 17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf So it seems as though it left some running processes behind after I disabled it. I have also attached a screenshot of my Sound settings which show that they are still running (Sound_Application_List2.png). --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: speech-dispatcher: Installed: 0.8.1-0ubuntu1 Candidate: 0.8.1-0ubuntu1 Version table: *** 0.8.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: speech-dispatcher 0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 16 20:27:00 2015 InstallationDate: Installed on 2015-07-29 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+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 1710346] Re: Drag & drop from the desktop freezes partially the PC
i can confirm that this is problem for me as well, have seen it on two fresh and fully updated installs of 17.10, each on a thinkpad t530. --josh -- 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/1710346 Title: Drag & drop from the desktop freezes partially the PC Status in nautilus package in Ubuntu: Incomplete Bug description: Hi I'm running 17.10 today's update (2017-08-12) I've put on the deskop 2 kinds of files : xx.txt and yy.odt If I right click on anyone, then cut & paste in Data Perso partition for ex, fine if I drag & drop instead, the file is frozen, some opened windows the same. The only exit is : Ctrl+Alt+Del to close and open the session $ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1710346/+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 1718719] Re: qemu can't capture keys properly under wayland
Hi! I am running Artful on my X1 Carbon Gen3. I downloaded the Ubuntu Server Artful final beta and attempt to do an install with the following qemu cli: $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d -hda vdisk.img -cdrom artful-server-amd64.iso -monitor stdio Trying to use the arrow key at the first menu does not work and errors with the unknown keycodes error. However, if I issue the `sendkey down` command from the qemu CLI it works as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1718719 Title: qemu can't capture keys properly under wayland Status in QEMU: New Status in qemu package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: This appears to be different than the previous similar bugs; patches do look to be applied to use libinput in the wayland case. Still: unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org I am using qemu-system-x86 1:2.10+dfsg-0ubuntu1 on artful. Many key inputs work correctly, but at boot the system will not properly catch the arrow keys, the above error shows up immediately after hitting Esc (for instance) to get to the boot menu. Booting from CD onto a daily Ubuntu desktop image, I can't navigate the splash menu. The same works correctly through virt-manager (which uses spice AFAICT, but wayland tends to crash when running virt-manager), and things work if I switch my session to Xorg rather than wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1718719/+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 1113420] Re: Alt+ window menu shortcuts cannot be disabled
I just wanted to play games in Ubuntu. alt-e is a crucial keybind for me in my favourite game. This little bug prevents me from playing. -- 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/1113420 Title: Alt+ window menu shortcuts cannot be disabled Status in Unity: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I find the key ergonomically very useful (it can be pressed with a thumb without moving any of the "letter" fingers) and I would like to use it for many custom keyboard shortcuts (there is a reason why it plays such a big role in Emacs and the whole OS X for that matter). Currently, though, is hardcoded to activate window menu entries (such as +F for the file menu, +E for the edit menu) and there is no way to surpass this functionality in all the applications. Personally, I find these shortcuts quite useless - they take you to "copy", "paste", and "open file" which have standard shortcuts anyway (with the exception of preferences, which for some reason don't have a standardized shortcut even though that's often the only thing a person looks for up there). Expected behaviour - What I would like to see is a global option to disable these alt+ menu shortcuts to free up the key for other uses (similar to the option already available in gnome-terminal, only global). Preferably, activating this option would also remove the first-letter underlining in the menu to indicate to users that they can't acess it through shortcuts. To reproduce: - - in Unity settings -> keyboard -> Shortcuts -> Launchers change the "Launch terminal" shortcut to ALT+T - hit -t, new terminial pops up - start Thunderbird or Okular, both of which have a "Tools" menu - note -t now opens the Tools menu - kill the application - hit -t, nothing happens (I marked nautilus for apport to collect my version numbers, but this affects most applications - didn't know what the right target is) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Feb 2 13:22:32 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'931x626+1+80'" b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true' InstallationDate: Installed on 2012-10-19 (106 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1113420/+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 1617022] Re: box width not resized for pam messages
This also affects our school district. We have been unable to find any greeter that fully displays the entire PAM message. We are using FreeIPA with Kerberos, but it should also affect anyone using modern security practices with LDAP or PAM. For example, if the user is required to change their password, and their new password is too short, they will get the message "Bad Password: To s", making the process very confusing for them. This makes it impractical to have any password requirements (minimum characters, dictionary check, etc.) because the user can't see why their password was rejected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1617022 Title: box width not resized for pam messages Status in unity-greeter package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version: 16.04.2-0ubuntu1 Is it possible to either dynamically expand the width and height of the greeter box in order to fully display PAM messages? If one uses Kerberos for authentication, the Unity greeter truncates/fades out the full text returned by PAM concerning Kerberos password/principal expiry: The attached unity-greeter-truncations.tar file contains three PNG files illustrating truncation when: - a password is about to expire. ['password_expire_soon.png'] - you enter the previous password in the 'change password' dialog and local policy prevents re-use. ['expired_same_password.png'] - you enter a password that does not meet local policy requirements in the 'change password' dialog. ['password_change_rejected.png'] The truncation can make it difficult for end-users to understand what is going on. Other display managers - such as gdm and mdm - are able to display such text in full. In the ubuntu-greeter source src/greeter-list.vala, it is possible to increase the default width of the greeter box by increasing the value below: public static const int BOX_WIDTH = 8; This is not a great solution because the login box is aesthetically unpleasant when it is that wide at all times. Furthermore, the PAM text displayed by unity-greeter is not line-wrapped, making the choice of a suitable value for BOX_WIDTH impractical. unity-greeter clearly has support for dynamically adjusting the height of the greeter box. Would it be possible, therefore, to add support for dynamically adjusting the width and to format displayed PAM text so that it is at most, say, seventy-five characters long? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1617022/+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 1715761] [NEW] My sound system does not work no matter what.
Public bug reported: My computer originally ran Windows 10. I recently put Ubuntu on it, thinking it would go onto my thumb drive, but it didn't. It has messed up my login process, but I can still eventually get to Ubuntu. But I try playing videos and I cannot hear the audio, from YouTube and advertisements. My computer has been designed to run B Play, but maybe downloading a new OS screwed it up. 1) Ubuntu 17.04 2) Unknown 3) Play any sound requested 4) Silence ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: legend 1761 F...m pulseaudio /dev/snd/controlC0: legend 1761 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Sep 7 17:01:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-07 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: legend 1761 F...m pulseaudio /dev/snd/controlC0: legend 1761 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion Notebook, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820B dmi.board.vendor: HP dmi.board.version: 82.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd03/14/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820B:rvr82.17:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1715761 Title: My sound system does not work no matter what. Status in alsa-driver package in Ubuntu: New Bug description: My computer originally ran Windows 10. I recently put Ubuntu on it, thinking it would go onto my thumb drive, but it didn't. It has messed up my login process, but I can still eventually get to Ubuntu. But I try playing videos and I cannot hear the audio, from YouTube and advertisements. My computer has been designed to run B Play, but maybe downloading a new OS screwed it up. 1) Ubuntu 17.04 2) Unknown 3) Play any sound requested 4) Silence ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: legend 1761 F...m pulseaudio /dev/snd/controlC0: legend 1761 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Sep 7 17:01:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-09-07 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: legend 1761 F...m pulseaudio /dev/snd/controlC0: legend 1761 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion Notebook, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820B dmi.board.vendor: HP dmi.board.version: 82.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd03/14/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820B:rvr82.17:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId
[Desktop-packages] [Bug 1714398] [NEW] i hear sounds only on wrong key combos or at start up drum roll, but not on youtube or kodi.
Public bug reported: my sounds worked perfect. no issues. when plugging in hdmi cable, i either had to select hdmi for sound, and or, plug in the hdmi cable then turn on the laptop while connected to the tv. after about 5 or 6 times this week, all was fine then, after shutting down the system (although we did have a few power outages and my batter doesnt charge so the system shuts straight down) I took the laptop to the other room as per susual and started kodi, the addon for watching infowars, and there was no sound. started a video on youtube, no sound. started a movie on vlc, no sound.. Now when i used to press the volume up and down button on the laptop, it used to make the noise sound. i mean, even after i lost the sound for the videos. youd hear the sound up sound down. I followed an online thing, sudo apt-get purge pulseaudio then i sudo apt-get install pulseaudio without any luck. but now it doesnt make the up/down vol sounds however, when you power on the system, it still makes the drum roll at the user sign in page. ive sudo apt-get autoromoved ive sudo apt-get update && sudo apt-get upgrade(d) obviously subtract that (d) idk what this things issue is. i guess i might reinstall. idk. jsut hate doing that sometimes. might be time. anyhow thank you kindly for your time and your patience with all this nonsense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: incog-nito 2082 F pulseaudio /dev/snd/controlC1: incog-nito 2082 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Aug 31 21:16:02 2017 InstallationDate: Installed on 2017-06-04 (88 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [Latitude E7440, Realtek ALC3226, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 091TRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn091TRH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1714398 Title: i hear sounds only on wrong key combos or at start up drum roll, but not on youtube or kodi. Status in alsa-driver package in Ubuntu: New Bug description: my sounds worked perfect. no issues. when plugging in hdmi cable, i either had to select hdmi for sound, and or, plug in the hdmi cable then turn on the laptop while connected to the tv. after about 5 or 6 times this week, all was fine then, after shutting down the system (although we did have a few power outages and my batter doesnt charge so the system shuts straight down) I took the laptop to the other room as per susual and started kodi, the addon for watching infowars, and there was no sound. started a video on youtube, no sound. started a movie on vlc, no sound.. Now when i used to press the volume up and down button on the laptop, it used to make the noise sound. i mean, even after i lost the sound for the videos. youd hear the sound up sound down. I followed an online thing, sudo apt-get purge pulseaudio then i sudo apt-get install pulseaudio without any luck. but now it doesnt make the up/down vol sounds however, when you power on the system, it still makes the drum roll at the user sign in page. ive sudo apt-get autoromoved ive sudo apt-get update && sudo apt-get upgrade(d) obviously subtract that (d) idk what this things issue is. i guess i might reinstall. idk. jsut hate doing that sometimes. might be time. anyhow thank you kindly for your time and your patience with all this nonsense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5
[Desktop-packages] [Bug 1646025] Re: libreoffice 5.1.6 for xenial
** Changed in: hundredpapercuts Status: Triaged => Fix Released -- 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/1646025 Title: libreoffice 5.1.6 for xenial Status in One Hundred Papercuts: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: LibreOffice reached the "End of Life" on november 27, 2016. Ubuntu 16.04 is delivered with with updated libreoffice 5.1.4, but the last and final release of the 5.1 family is libreoffice 5.1.6, that brings a lot of improvements and fixes: - https://wiki.documentfoundation.org/Releases/5.1.5/RC1 - https://wiki.documentfoundation.org/Releases/5.1.5/RC2 - https://wiki.documentfoundation.org/Releases/5.1.6/RC1 - https://wiki.documentfoundation.org/Releases/5.1.6/RC2 From LO 5.1.4 to LO 5.1.6 there are more than 150 fixes. For this reasons, please consider to update the LO packages to 5.1.6 in Xenial. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1646025/+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 1708933] Re: Can't add a Microsoft account to GNOME Online Accounts
I cannot reproduce this bug with gnome-online-accounts 3.24.1-0ubuntu1 on artful, which is the same version that you are running. I think by running "G_MESSAGES_DEBUG=all gnome-control-center" and then trying to add your account as usual may print any log messages of any use to the terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1708933 Title: Can't add a Microsoft account to GNOME Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: In artful: 1) Open Settings->Online Accounts 2) Click on "Microsoft" under "Add an account" 3) See an authorization window pop up, enter my user/password for Microsoft Live 4) Click next, see it ask whether it's OK to give GNOME various permissions 5) Click yes, see the window disappear But at this point, no Microsoft account appears in the active-accounts section. It just seems to have closed the window and done nothing. Is there a way to get better logging for this and try again? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 6 10:03:55 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (1669 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+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 1706305] Re: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
>From logs: dpkg: error processing package libnl-genl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1706305 Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libnl3 package in Ubuntu: Incomplete Bug description: I don't know what is the problem. I only have read the notification telling me I have a problem in ubuntu. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Tue Jul 25 12:18:43 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 libnl-3-200 3.2.29-0ubuntu2.1 DuplicateSignature: package:libnl-genl-3-200:amd64:3.2.29-0ubuntu2.1 Setting up mythes-en-au (2.1-5.4) ... dpkg: error processing package libnl-genl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-07-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1706305/+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 1706305] Re: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Thank you for taking the time to file a bug report. One of your packages is reporting that it is in an inconsistent state. This needs to be solved before you continue further operations. To help you get started please see this question and response: https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a-very-bad-inconsistent-state-error Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: libnl3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1706305 Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libnl3 package in Ubuntu: Incomplete Bug description: I don't know what is the problem. I only have read the notification telling me I have a problem in ubuntu. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Tue Jul 25 12:18:43 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 libnl-3-200 3.2.29-0ubuntu2.1 DuplicateSignature: package:libnl-genl-3-200:amd64:3.2.29-0ubuntu2.1 Setting up mythes-en-au (2.1-5.4) ... dpkg: error processing package libnl-genl-3-200:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-07-24 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1706305/+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 1702985] [NEW] Change expired password dialog missing
Public bug reported: On Ubuntu-mate 16.04.2, with FreeIPA 4.3.1.0, SSSD 1.13.4-1 and LightDM 1.18.3 (with lightdm-gtk-greeter 2.0.1-2) I am not seeing the normal prompts that should come up when a user's password has expired. When a user attempts to log in with an expired password, they should be notified that their password has expired, and then prompted to re-enter their current password. If their current password is accepted, they should then be prompted to enter a new password. If that password meets the system's requirements, they should then be prompted to enter their new password a second time to confirm it. On my system I am seeing the first message, the user is informed that their password has expired and must be changed. However, I am not seeing any subsequent prompts. The user is presented with a blank password field three times with no instruction. Their login will succeed if they know they need to enter their current password, press enter, enter their new password, press enter, and then enter their new password again, and press enter, there is just no dialog to inform them of this. If I install GDM on the same system and set it as the default, it works correctly. A text notification is displayed, telling the user what to enter in the password field (i.e "Current Password", "New Password", "Confirm New Password"). If I install the Unity-greeter that comes with Ubuntu 16.04 standard, it also works correctly. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1702985 Title: Change expired password dialog missing Status in lightdm package in Ubuntu: New Bug description: On Ubuntu-mate 16.04.2, with FreeIPA 4.3.1.0, SSSD 1.13.4-1 and LightDM 1.18.3 (with lightdm-gtk-greeter 2.0.1-2) I am not seeing the normal prompts that should come up when a user's password has expired. When a user attempts to log in with an expired password, they should be notified that their password has expired, and then prompted to re- enter their current password. If their current password is accepted, they should then be prompted to enter a new password. If that password meets the system's requirements, they should then be prompted to enter their new password a second time to confirm it. On my system I am seeing the first message, the user is informed that their password has expired and must be changed. However, I am not seeing any subsequent prompts. The user is presented with a blank password field three times with no instruction. Their login will succeed if they know they need to enter their current password, press enter, enter their new password, press enter, and then enter their new password again, and press enter, there is just no dialog to inform them of this. If I install GDM on the same system and set it as the default, it works correctly. A text notification is displayed, telling the user what to enter in the password field (i.e "Current Password", "New Password", "Confirm New Password"). If I install the Unity-greeter that comes with Ubuntu 16.04 standard, it also works correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1702985/+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 1700954] [NEW] Critical about Intel Graphics Driver Update
Public bug reported: I receive problems when I'm install that program that it not display the login screen but it's black screen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.11.7-041107-generic i686 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..05.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:05:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 375.66 Mon May 1 14:31:26 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 28 18:32:46 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-04-28 (61 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.7-041107-generic root=UUID=9b111cda-c784-49a8-a97d-03d4ec26ea04 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jun 28 17:01:45 2017 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-0ubuntu0.2 ** 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/1700954 Title: Critical about Intel Graphics Driver Update Status in xorg package in Ubuntu: New Bug description: I receive problems when I'm install that program that it not display the login screen but it's black screen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.11.7-041107-generic i686 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..05.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:05:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 375.66 Mon May 1 14:31:26 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 28 18:32:46 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-04-28 (61 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
[Desktop-packages] [Bug 1699772] Re: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing
Applications that use jsvc can increase their thread stack space with -Xss1280k or larger (Red Hat, for example, suggested -Xss2m which is much larger). -- 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/1699772 Title: linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing Status in commons-daemon package in Ubuntu: Confirmed Status in eclipse package in Ubuntu: Confirmed Status in imagej package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in octave package in Ubuntu: Confirmed Status in scilab package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+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 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochma
Can you give the output of those commands so we can make sure the issue has not changed and see what you are seeing? That will help us assist you further. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1697153 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in libnl3 package in Ubuntu: Incomplete Bug description: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+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 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochma
Take a look at the link in my previous message; it essentially boils down to: sudo apt-get install -f --reinstall libnl-genl-3-200 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1697153 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in libnl3 package in Ubuntu: Incomplete Bug description: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+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 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochma
Thank you for taking the time to file a bug report. One of your packages is reporting that it is in an inconsistent state. This needs to be solved before you continue further operations. To help you get started please see this question and response: https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a-very-bad-inconsistent-state-error Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: libnl3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1697153 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in libnl3 package in Ubuntu: Incomplete Bug description: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+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 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochma
>From terminal log (translated): Dpkg: Error processing package libnl-genl-3-200: amd64 (--configure): Package is in a very bad inconsistent condition - you should get it Again before attempting the configuration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1697153 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in libnl3 package in Ubuntu: Incomplete Bug description: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+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 1690836] Re: libnl-genl-3.0 memory leak
We also need to confirm that this is fixed in Artful. Given it is fixed in Debian stable it probably is, but confirming that it is fixed in the latest development release will be required for the SRU. ** Changed in: libnl3 (Ubuntu Trusty) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1690836 Title: libnl-genl-3.0 memory leak Status in libnl3 package in Ubuntu: Confirmed Status in libnl3 source package in Trusty: Triaged Bug description: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: 258 cb = nl_cb_clone(orig); // buffer copied not freed - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - Executing it on Debian 8.0 shows "no memory leak": sylvain@debian:~/test$ lsb_release -rd Description: Debian GNU/Linux 8.8 (jessie) Release: 8.8 sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main sylvain@debian:~/test$ valgrind --leak-check=full ./main ==26390== Memcheck, a memory error detector ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==26390== Command: ./main ==26390== start test error: can't retrieve the netlink-family id end test ==26390== ==26390== HEAP SUMMARY: ==26390== in use at exit: 0 bytes in 0 blocks ==26390== total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated ==26390== ==26390== All heap blocks were freed -- no leaks are possible ==26390== ==26390== For counts of detected and suppressed errors, rerun with: -v ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) - Executing it on Ubuntu 14.04 shows a memory leak: ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main ubuntu@ubuntu:~$ valgrind --leak-check=full ./main ==37377== Memcheck, a memory error detector ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==37377== Command: ./main ==37377== start test error: can't retrieve the netlink-family id end test ==37377== ==37377== HEAP SUMMARY: ==37377== in use at exit: 224 bytes in 1 blocks ==37377== total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated ==37377== ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==37377==at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==37377==by 0x5048FAA: nl_cb_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x504CB1E: nl_socket_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main) ==37377==by 0x401189: main (in /home/ubuntu/main) ==37377== ==37377== LEAK SUMMARY: ==37377==definitely lost: 224 bytes in 1 blocks ==37377==indirectly lost: 0 bytes in 0 blocks ==37377== possibly lost: 0 bytes in 0 blocks ==37377==still reachable: 0 bytes in 0 blocks ==37377== suppressed: 0 bytes in 0 blocks ==37377== ==37377== For counts of detected and suppressed errors, rerun with: -v ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Thanks, Sylvain Trinquet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1690836/+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 1690836] Re: libnl-genl-3.0 memory leak
@filofel, my bad yes you are right. This seems fixed in later versions and as such this requires an SRU. Next step would be to determine what changes would be required to fix. Trusty-updates has version 3.2.21-1ubuntu4 Debian stable (jessie) has version 3.2.24-2 ** Also affects: libnl3 (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1690836 Title: libnl-genl-3.0 memory leak Status in libnl3 package in Ubuntu: Confirmed Status in libnl3 source package in Trusty: Triaged Bug description: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: 258 cb = nl_cb_clone(orig); // buffer copied not freed - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - Executing it on Debian 8.0 shows "no memory leak": sylvain@debian:~/test$ lsb_release -rd Description: Debian GNU/Linux 8.8 (jessie) Release: 8.8 sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main sylvain@debian:~/test$ valgrind --leak-check=full ./main ==26390== Memcheck, a memory error detector ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==26390== Command: ./main ==26390== start test error: can't retrieve the netlink-family id end test ==26390== ==26390== HEAP SUMMARY: ==26390== in use at exit: 0 bytes in 0 blocks ==26390== total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated ==26390== ==26390== All heap blocks were freed -- no leaks are possible ==26390== ==26390== For counts of detected and suppressed errors, rerun with: -v ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) - Executing it on Ubuntu 14.04 shows a memory leak: ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main ubuntu@ubuntu:~$ valgrind --leak-check=full ./main ==37377== Memcheck, a memory error detector ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==37377== Command: ./main ==37377== start test error: can't retrieve the netlink-family id end test ==37377== ==37377== HEAP SUMMARY: ==37377== in use at exit: 224 bytes in 1 blocks ==37377== total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated ==37377== ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==37377==at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==37377==by 0x5048FAA: nl_cb_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x504CB1E: nl_socket_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main) ==37377==by 0x401189: main (in /home/ubuntu/main) ==37377== ==37377== LEAK SUMMARY: ==37377==definitely lost: 224 bytes in 1 blocks ==37377==indirectly lost: 0 bytes in 0 blocks ==37377== possibly lost: 0 bytes in 0 blocks ==37377==still reachable: 0 bytes in 0 blocks ==37377== suppressed: 0 bytes in 0 blocks ==37377== ==37377== For counts of detected and suppressed errors, rerun with: -v ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Thanks, Sylvain Trinquet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1690836/+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 1690836] Re: libnl-genl-3.0 memory leak
I believe this is the upstream project: https://github.com/tgraf/libnl ** Tags added: bitesize needs-upstream-report -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1690836 Title: libnl-genl-3.0 memory leak Status in libnl3 package in Ubuntu: Confirmed Bug description: It seems that there is a memory leak in the libnl-genl-3.0 library. The memory-leak can be seen when the function genl_ctrl_resolve() fails. It seems that this function copy a buffer and forget to deallocate it properly: 258 cb = nl_cb_clone(orig); // buffer copied not freed - The following attached source-code can help you to reproduce this behavior on Ubuntu 14.04. It forces an issue on the genl_ctrl_resolve by asking an unknown netlink-family. To compile program: g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main To detect memory-leak using Valgrind: valgrind --leak-check=full ./main - Executing it on Debian 8.0 shows "no memory leak": sylvain@debian:~/test$ lsb_release -rd Description: Debian GNU/Linux 8.8 (jessie) Release: 8.8 sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main sylvain@debian:~/test$ valgrind --leak-check=full ./main ==26390== Memcheck, a memory error detector ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==26390== Command: ./main ==26390== start test error: can't retrieve the netlink-family id end test ==26390== ==26390== HEAP SUMMARY: ==26390== in use at exit: 0 bytes in 0 blocks ==26390== total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated ==26390== ==26390== All heap blocks were freed -- no leaks are possible ==26390== ==26390== For counts of detected and suppressed errors, rerun with: -v ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) - Executing it on Ubuntu 14.04 shows a memory leak: ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 14.04.5 LTS Release: 14.04 ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 libnl-genl-3.0) -o main ubuntu@ubuntu:~$ valgrind --leak-check=full ./main ==37377== Memcheck, a memory error detector ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==37377== Command: ./main ==37377== start test error: can't retrieve the netlink-family id end test ==37377== ==37377== HEAP SUMMARY: ==37377== in use at exit: 224 bytes in 1 blocks ==37377== total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated ==37377== ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1 ==37377==at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==37377==by 0x5048FAA: nl_cb_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x504CB1E: nl_socket_alloc (in /lib/x86_64-linux-gnu/libnl-3.so.200.16.1) ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main) ==37377==by 0x401189: main (in /home/ubuntu/main) ==37377== ==37377== LEAK SUMMARY: ==37377==definitely lost: 224 bytes in 1 blocks ==37377==indirectly lost: 0 bytes in 0 blocks ==37377== possibly lost: 0 bytes in 0 blocks ==37377==still reachable: 0 bytes in 0 blocks ==37377== suppressed: 0 bytes in 0 blocks ==37377== ==37377== For counts of detected and suppressed errors, rerun with: -v ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Thanks, Sylvain Trinquet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1690836/+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
