[Desktop-packages] [Bug 2077027] Re: /usr/lib/update-notifier/list-oem-metapackages:AttributeError:/usr/lib/update-notifier/list-oem-metapackages@56:write_oem_metapackage_list:system_device_specific_m
Here is the traceback: Traceback (most recent call last): File "/usr/lib/update-notifier/list-oem-metapackages", line 56, in write_oem_metapackage_list(cache, STAMP_FILE) File "/usr/lib/update-notifier/list-oem-metapackages", line 29, in write_oem_metapackage_list packages = UbuntuDrivers.detect.system_device_specific_metapackages( File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 593, in system_device_specific_metapackages for p in packages_for_modalias(apt_cache, alias): File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in packages_for_modalias apt_cache_hash = hash(package.get_fullname() for package in apt_cache.packages) AttributeError: 'Cache' object has no attribute 'packages' ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2077027 Title: /usr/lib/update-notifier/list-oem- metapackages:AttributeError:/usr/lib/update-notifier/list-oem- metapackages@56:write_oem_metapackage_list:system_device_specific_metapackages:packages_for_modalias Status in ubuntu-drivers-common package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier. This problem was most recently seen with package version 3.192.64, the problem page at https://errors.ubuntu.com/problem/6c3b052520985dd0e06006d1065881ea3b8d0735 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2077027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060730] Re: totem cannot install codecs via packagekit
** Changed in: totem (Ubuntu) Status: Invalid => Triaged ** Also affects: totem (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: packagekit (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: totem (Ubuntu Oracular) Importance: Undecided Status: Triaged ** Also affects: packagekit (Ubuntu Oracular) Importance: Undecided Status: Invalid ** Changed in: totem (Ubuntu Noble) Status: New => Triaged ** Changed in: totem (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: totem (Ubuntu Oracular) Milestone: None => ubuntu-24.10-beta -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit Status in App Center: Triaged Status in packagekit package in Ubuntu: Invalid Status in totem package in Ubuntu: Triaged Status in packagekit source package in Noble: New Status in totem source package in Noble: Triaged Status in packagekit source package in Oracular: Invalid Status in totem source package in Oracular: Triaged Bug description: While attempting to play a video on Ubuntu noble desktop for raspberry pi, totem attempts to locate a package for the H.264 codec but cannot find a service providing org.freedesktop.PackageKit. This is strange given that packagekit is installed, provides packagekit.service, which declares that it provides that name over DBus. Specifically, the following is output by totem: ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder) ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder) ** Message: 21:13:39.414: PackageKit: xid = 0 ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit) ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files ** Message: 21:13:39.441: No installation candidate for missing plugins found. The packagekit.service is defined as: $ systemctl cat packagekit.service # /usr/lib/systemd/system/packagekit.service [Unit] Description=PackageKit Daemon # PK doesn't know how to do anything on ostree-managed systems; # currently the design is to have dedicated daemons like # eos-updater and rpm-ostree, and gnome-software talks to those. ConditionPathExists=!/run/ostree-booted Wants=network-online.target [Service] Type=dbus BusName=org.freedesktop.PackageKit User=root ExecStart=/usr/libexec/packagekitd And just to demonstrate packagekit is actually running: $ systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static) Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s ago Main PID: 1565 (packagekitd) Tasks: 4 (limit: 3864) Memory: 6.2M (peak: 6.7M) CPU: 180ms CGroup: /system.slice/packagekit.service └─1565 /usr/libexec/packagekitd Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - PackageKit Daemon... Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - PackageKit Daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060693] Re: No welcome/login sound on Ubuntu desktop
Could we sort this out for Oracular? ** Also affects: libcanberra (Ubuntu Oracular) Importance: Undecided Status: Confirmed ** Also affects: libcanberra (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: libcanberra (Ubuntu Noble) Status: New => Confirmed ** Changed in: libcanberra (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: libcanberra (Ubuntu Oracular) Milestone: None => ubuntu-24.10-beta -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/2060693 Title: No welcome/login sound on Ubuntu desktop Status in libcanberra package in Ubuntu: Confirmed Status in libcanberra source package in Noble: Confirmed Status in libcanberra source package in Oracular: Confirmed Bug description: Under the Ubuntu desktop for Raspberry Pi, for several recent releases, the startup sound from the Yaru sound theme has failed to play both at the initial setup (from oem-config, where it used to play just before language selection), and at the greeter. This worked in Jammy (22.04), but on at least mantic (23.10) and the forthcoming noble (24.04) (and possibly earlier), this has failed. It's not due to a crash in canberra-gtk-play (used to play the sound). The only hint that something has failed appears in the oem-config.log: Failed to play sound: Not available Unfortunately there's nothing else in the log that hints at why canberra-gtk-play is failing. There are several similar bug report, but I doubt they are related given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a very different sound stack and predates the preinstalled desktop images). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2052913] Re: [Xorg] Large performance regression in fullscreen windows
** Also affects: mutter (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: mutter (Ubuntu Noble) Status: New => Triaged ** Changed in: mutter (Ubuntu Noble) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Milestone: noble-updates => later -- 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/2052913 Title: [Xorg] Large performance regression in fullscreen windows Status in Mutter: New Status in mutter package in Ubuntu: Triaged Status in mutter source package in Noble: Triaged Bug description: Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble (gnome-shell 45.3-1ubuntu1) Default Ubuntu GNOME desktop environment used with no user added extensions. GPU driverstack identical between the two distros (eliminated as a variable). Linux kernel identical between distros (eliminated as a variable) CPU, GPU, and RAM clocks pinned to max. Test case: Minecraft Java Edition (shared drive with identical setup between Ubuntu versions). Fullscreen 1080p. Xorg display server. FPS (uncapped): Ubuntu Jammy: 177fps Ubuntu Noble: 140fps Observations: Ubuntu Jammy: gnome-shell process cpu% when camera is still: 0-1% gnome-shell process cpu% when camera is moving: 10-20% Memory Bandwidth (CPU and GPU shared): 40% Ubuntu Noble: gnome-shell process cpu% when camera is still: 20-55% gnome-shell process cpu% when camera is moving: 30-55% Memory Bandwidth (CPU and GPU shared): 50% In both cases GPU utilization is observed to be near 100%. So in summary, large performance regression regression which appears to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on ubuntu jammy when there the camera is still (even with a fps graph drawn onscreen) in stark contrast to ubuntu noble. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2052913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
** Changed in: gtk4 (Ubuntu Noble) Milestone: None => noble-updates ** Changed in: mesa (Ubuntu Noble) Milestone: None => noble-updates -- 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/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013107] Re: GNOME does not display high contrast app icons
** Tags added: rls-oo-incoming ** Changed in: gnome-shell (Ubuntu Noble) Milestone: ubuntu-23.10 => noble-updates ** Also affects: gnome-shell (Ubuntu Oracular) Importance: High Status: Triaged ** Also affects: gnome-themes-extra (Ubuntu Oracular) Importance: Undecided Status: Invalid ** Also affects: yaru-theme (Ubuntu Oracular) Importance: Undecided Status: Won't Fix ** Changed in: gnome-shell (Ubuntu Oracular) Milestone: ubuntu-23.10 => ubuntu-24.10-beta ** Changed in: gnome-shell (Ubuntu Mantic) Milestone: ubuntu-23.10 => None -- 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/2013107 Title: GNOME does not display high contrast app icons Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-themes-extra package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Won't Fix Status in gnome-shell source package in Mantic: Won't Fix Status in gnome-shell source package in Noble: Triaged Status in gnome-shell source package in Oracular: Triaged Status in gnome-themes-extra source package in Oracular: Invalid Status in yaru-theme source package in Oracular: Won't Fix Bug description: gnome-accessibility-themes (3.28-2ubuntu1) offers an incomplete set of high contrast icons, resulting in a very inconsistent look when the user enables Accessibility > Seeing > High Contrast from gnome- control-center. A screenshot showing of the current sad state of affairs is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2013107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
I don't see an upload of ubuntu-drivers-common in the unapproved queue or in -proposed which addresses this bug so I'm setting it back to In Progress. Fix Committed should *not* be used for Ubuntu bug tasks if the fix is in some "upstream" branch. ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Fix Committed => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Noble) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Noble: In Progress Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init [ Test Plan ] Open Settings and verify the only monitors shown are your real monitors. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2060268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725921] Re: [regression] Combobox menus have gray text on gray background
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ubuntu-themes (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1725921 Title: [regression] Combobox menus have gray text on gray background Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: Fix Released Status in ubuntu-themes source package in Artful: Won't Fix Status in ubuntu-themes source package in Bionic: Fix Released Bug description: [Impact] Regression: After a recent update, combobox menus have gray text on gray background making them almost unreadable. [Test Case] 1. Open GIMP and start a new file. 2. At the bottom of the window click on the 'px' combo box. 3. Verify the menu that appears has readable text (light grey text on a dark grey background). [Regression Potential] Very low. The fix changes the theme for "gtk-combobox-popup-menu" only. So theoretically it should not be possible for the fix to affect anything other than combobox menus. [Other Info] The regression happened in updates to 18.04, 17.10 and 16.04 around late 2017 - January 2018. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723874] Re: First installation of a snap reports an error "Connection reset by peer"
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: snapd-glib (Ubuntu Artful) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1723874 Title: First installation of a snap reports an error "Connection reset by peer" Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Artful: Won't Fix Bug description: Test Case 1. On a freshly installed system when snapd has never been used or initialized before (ie core is not installed) open gnome-software 2. Select a snap 3. Install it 4. Wait until it is installed Actual result At some point gnome-software reports an error "Installation failed: connection reset by peer" It was actually installing core, restarted snapd, then the package. But gnome-software reports the error when snapd is restarted, loses the connection to the daemon and does not track the progress of the installation of the snap package Expected result It reports the installation of core then the installation of the snap package, or report everything in a single transaction but in any case does not report an error since everything is going as expected. Attached the changes that are occurring when the first snap is installed on a fresh system ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 09:26:38 2017 InstallationDate: Installed on 2013-09-03 (1503 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu1 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1723874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721049] Re: "Got unknown content type text/html" error viewing flatpack packages
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-software (Ubuntu Artful) Status: Confirmed => Won't Fix -- 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/1721049 Title: "Got unknown content type text/html" error viewing flatpack packages Status in GNOME Software: Expired Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Artful: Won't Fix Bug description: Whenever I view a Flatpak package in gnome-software, an in-app notification appears saying: > Sorry, something went wrong > Got unknown content type text/html from reviews.ubuntu.com Since this is modal, I then need to dismiss it before being able to do anything else. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 4 01:31:10 2017 InstallationDate: Installed on 2015-07-22 (804 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InstalledPlugins: gnome-software-plugin-flatpak 3.26.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snapN/A SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1721049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729713] Re: Update gdm3 to 3.26.2.1
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gdm3 (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1729713 Title: Update gdm3 to 3.26.2.1 Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Artful: Won't Fix Bug description: I'm filing a placeholder bug. I am not working on a gdm3 3.26.2.1 SRU at this time. But you can feel free to do that! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1729713/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-control-center (Ubuntu Artful) Status: Confirmed => Won't Fix -- 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/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Won't Fix Status in mutter source package in Artful: Won't Fix Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mutter (Ubuntu Artful) Status: Confirmed => Won't Fix -- 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/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Won't Fix Status in mutter source package in Artful: Won't Fix Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989959] Re: Incorrect ESM coverage information
Looking at both Ubuntu 22.04 and Ubuntu 24.04 the message indicated in comment #1 appears in software-properties-gtk so I am setting this to Fix Released. ** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Released ** Changed in: software-properties (Ubuntu) Milestone: ubuntu-22.04.2 => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1989959 Title: Incorrect ESM coverage information Status in software-properties package in Ubuntu: Fix Released Bug description: Software Properties says that Extended Security Maintenance provides security updates for over 3 Ubuntu packages, see lines 1269 and 1346 in data/gtkbuilder/main.ui. According to https://ubuntu.com/16-04, Canonical provides extended security maintenance for binary packages that reside in the "main" Ubuntu repository, which contains about 7000 architecture-specific packages depending on the Ubuntu release. Moreover, ESM is only provided for a part of packages, not for all packages in the "main" repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1989959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-software (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1723362 Title: gnome-software spams error messages to journald and causes 100% CPU usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Invalid Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Confirmed Status in snapd-glib source package in Xenial: Confirmed Status in gnome-software source package in Artful: Won't Fix Status in snapd-glib source package in Artful: Won't Fix Status in gnome-software source package in Bionic: Invalid Status in snapd-glib source package in Bionic: Fix Released Bug description: gnome-software spams this message to journald: Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 10:58:38 2017 InstallationDate: Installed on 2016-10-25 (352 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721762] Re: Cancelled installation of snap continues
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: snapd-glib (Ubuntu Artful) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1721762 Title: Cancelled installation of snap continues Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Zesty: Fix Released Status in snapd-glib source package in Artful: Won't Fix Status in snapd-glib source package in Bionic: Fix Released Bug description: with core candidate: 16-2.28.1 Test Case 1. Install a snap package 2. When the installation is ongoing, press Cancel 3. Verify that installation stopped (snap changes then snap change ID) Expected result Installation is cancelled Actual result It continues in the background and gnome-software shows the wrong state ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 13:38:01 2017 InstallationDate: Installed on 2014-07-23 (1170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-06-13 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1721762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752197] Re: Videos won't resume after being paused
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: webkit2gtk (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1752197 Title: Videos won't resume after being paused Status in WebKit: Fix Released Status in epiphany-browser package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk source package in Artful: Won't Fix Bug description: On my Ubuntu 17.10 system, Epiphany Browser 3.26.1 has trouble playing YouTube videos. I can play a video from the start point without trouble, but if I pause the video the screen will freeze and stay that way after restarting the video, if I leave the page and go back later it will show a black screen. In both cases the soundtrack continues without problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: epiphany-browser 3.26.1-1ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 27 17:27:50 2018 InstallationDate: Installed on 2017-12-06 (83 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/webkit-open-source/+bug/1752197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2074302] Re: Asus Laptop (R558U) does not suspend after upgrade to 24.04
It also looks like you version of the kernel is out of date. You might try updating to 6.8.0-39.39 and see if that helps resolve the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2074302 Title: Asus Laptop (R558U) does not suspend after upgrade to 24.04 Status in linux package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I was previously running Ubuntu 23.10 on my laptop. I performed a `dist-upgrade` about a week back. Since the upgrade to 24.04 my laptop does not suspend - either by pressing the power-key (previously working on 23.10) or by using the GNOME system power menu. My laptop has integrated Intel graphics as well as NVIDIA GeForce 930MX (GM108M), but i haven't installed proprietary video drivers. It is currently using xserver-x-org-video-nouveau as the video driver. My system reports as running a wayland session, but I find the above X.Org detail confusing. There is currently one inhibitor running `gsd-media-keys`. I filed a bug under systemd as ubuntu-bug would not let me file a bug without a package name. If this is incorrect, please change the package-name as appropriate. I would like to restore previous functionality - system suspend on command. I'd be happy to provide additional logs and to troubleshoot any possible fixes. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.2 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 19:11:12 2024 InstallationDate: Installed on 2019-04-20 (1926 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X556UR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-07-20 (8 days ago) dmi.bios.date: 10/24/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UR.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UR.309:bd10/24/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X556UR dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722603] Re: No automatic driver install for Apple facetime camera ( experimental working driver available)
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ubuntu-drivers-common (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1722603 Title: No automatic driver install for Apple facetime camera ( experimental working driver available) Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Status in linux source package in Artful: Won't Fix Status in ubuntu-drivers-common source package in Artful: Won't Fix Bug description: the integrated facetime camera does not work on Ubuntu 22.04 out of the box. the current workaround is outlined here: https://github.com/patjak/bcwc_pcie/wiki/Get-Started#additional-notes would it be possible to have this driver supported by ubuntu-drivers ? Manual Dkms Solution : git clone https://github.com/ekimiateam/facetimehd git clone https://github.com/patjak/facetimehd-firmware make -C facetimehd-firmware/ deb cp facetimehd-firmware/debian/*.deb . cd facetimehd/ dpkg-buildpackage -us -uc cd .. sudo apt install ./facetimehd*.deb - ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1906 F pulseaudio /dev/snd/controlC1: peter 1906 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-04-05 (553 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: Apple Inc. MacBookPro12,1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=540e40c6-4d83-4c9e-8dfe-18c9ab5e2234 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-09 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving tr
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ubuntu-mate-artwork (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1750465 Title: upgrade attempting to process triggers out of order (package plymouth- theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed) Status in apt package in Ubuntu: Invalid Status in budgie-artwork package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in ubuntu-gnome-default-settings package in Ubuntu: Fix Released Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in apt source package in Xenial: Invalid Status in kubuntu-settings source package in Xenial: Confirmed Status in plymouth source package in Xenial: Fix Released Status in ubuntu-gnome-default-settings source package in Xenial: Confirmed Status in ubuntu-mate-artwork source package in Xenial: Confirmed Status in apt source package in Artful: Invalid Status in budgie-artwork source package in Artful: Fix Released Status in kubuntu-settings source package in Artful: Won't Fix Status in plymouth source package in Artful: Fix Released Status in ubuntu-gnome-default-settings source package in Artful: Won't Fix Status in ubuntu-mate-artwork source package in Artful: Won't Fix Bug description: [SRU Justification] A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail because of trying to process triggers out of order. Since the trigger being run is that of the currently-installed plymouth package, it is not guaranteed to be sufficient to fix the version of the package in 18.04. [Test case] 1. Install plymouth-themes-ubuntu-text from -proposed. 2. Run a release upgrade with each of update-manager -d, do-release-upgrade -d, and apt-get dist-upgrade (the last after manually changing sources.list). 3. Verify that in each case, the upgrade completes successfully, with no errors about out-of-order trigger configuration. [Regression potential] noawait triggers have been supported in dpkg since 1.16.1, which is older than the version in precise (https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html). A noawait trigger is considered appropriate whenever the triggered package does not need to block the triggering package. There is no reason for a plymouth theme package to need to block configuration of an essential package in this case. noawait triggers are well-exercised in the distro now, so the risk of regression from this change should be low. There is unfortunately not a known reproducer for the original bug, so the test case, while it should guard against regressions, is not strong confirmation that the bug is fixed. [Original description] Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Feb 18 23:41:49 2018 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-10-24 (118 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.5.1 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago) dm
[Desktop-packages] [Bug 1725821] Re: mutter 3.26 doesn't properly unredirect windows
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mutter (Ubuntu Artful) Status: Incomplete => Won't Fix -- 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/1725821 Title: mutter 3.26 doesn't properly unredirect windows Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Artful: Won't Fix Bug description: Impact == A regression in mutter 3.26 (compared to 3.24) makes game performance much worse for some users (users with Nvidia graphics?) Test Case = Regression Potential Other Info == LP: #1725649 tracks another issue fixed by these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving tr
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: kubuntu-settings (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1750465 Title: upgrade attempting to process triggers out of order (package plymouth- theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed) Status in apt package in Ubuntu: Invalid Status in budgie-artwork package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in ubuntu-gnome-default-settings package in Ubuntu: Fix Released Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in apt source package in Xenial: Invalid Status in kubuntu-settings source package in Xenial: Confirmed Status in plymouth source package in Xenial: Fix Released Status in ubuntu-gnome-default-settings source package in Xenial: Confirmed Status in ubuntu-mate-artwork source package in Xenial: Confirmed Status in apt source package in Artful: Invalid Status in budgie-artwork source package in Artful: Fix Released Status in kubuntu-settings source package in Artful: Won't Fix Status in plymouth source package in Artful: Fix Released Status in ubuntu-gnome-default-settings source package in Artful: Won't Fix Status in ubuntu-mate-artwork source package in Artful: Won't Fix Bug description: [SRU Justification] A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail because of trying to process triggers out of order. Since the trigger being run is that of the currently-installed plymouth package, it is not guaranteed to be sufficient to fix the version of the package in 18.04. [Test case] 1. Install plymouth-themes-ubuntu-text from -proposed. 2. Run a release upgrade with each of update-manager -d, do-release-upgrade -d, and apt-get dist-upgrade (the last after manually changing sources.list). 3. Verify that in each case, the upgrade completes successfully, with no errors about out-of-order trigger configuration. [Regression potential] noawait triggers have been supported in dpkg since 1.16.1, which is older than the version in precise (https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html). A noawait trigger is considered appropriate whenever the triggered package does not need to block the triggering package. There is no reason for a plymouth theme package to need to block configuration of an essential package in this case. noawait triggers are well-exercised in the distro now, so the risk of regression from this change should be low. There is unfortunately not a known reproducer for the original bug, so the test case, while it should guard against regressions, is not strong confirmation that the bug is fixed. [Original description] Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Feb 18 23:41:49 2018 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-10-24 (118 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.5.1 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago) dmi.b
[Desktop-packages] [Bug 1679989] Re: CVE-2016-10165: heap OOB read parsing crafted ICC profile
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: lcms2 (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/1679989 Title: CVE-2016-10165: heap OOB read parsing crafted ICC profile Status in lcms2 package in Ubuntu: Confirmed Status in lcms2 source package in Precise: Won't Fix Status in lcms2 source package in Trusty: Confirmed Status in lcms2 source package in Xenial: Confirmed Status in lcms2 source package in Zesty: Confirmed Status in lcms2 source package in Artful: Won't Fix Status in lcms2 package in Debian: Fix Released Bug description: The Type_MLU_Read function in cmstypes.c in Little CMS (aka lcms2) allows remote attackers to obtain sensitive information or cause a denial of service via an image with a crafted ICC profile, which triggers an out-of-bounds heap read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lcms2/+bug/1679989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742403] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-inst
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: network-manager (Ubuntu Artful) Status: Fix Committed => Won't Fix -- 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/1742403 Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config- connectivity-ubuntu package post-installation script subprocess returned error exit status 1 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Bug description: [Description] Installation of network-manager-config-connectivity fails if network-manager is not running. The patch appends " || true " to force-reload in the postinst script to not fail in this case. [QA] Test Case: 1. On a machine without network-manager already install (eg server install) install network-manager-config-connectivity-ubuntu Expected Result: It installs successfully with all its dependencies buckets on errors.u.c https://errors.ubuntu.com/problem/ff73bf3ac18fbeb732d1d4f6676a15e24e7f7399 https://errors.ubuntu.com/problem/6da94ccacd3e341967667bc1e7b2e83e4ac82026 [Regression potential] Low to none. If the fix works the package will install, and if it does not work it will still fail to install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Wed Jan 10 08:50:17 2018 ErrorMessage: installed network-manager-config-connectivity-ubuntu package post-installation script subprocess returned error exit status 1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-03 (1589 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: network-manager Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1742403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760758] Re: /usr/lib/ibus/ibus-engine-libpinyin:ibus-engine-libpinyin: pinyin.cpp:991\357\274\232bool pinyin_set_zhuyin_scheme(pinyin_context_t*, ZhuyinScheme): \345\201\207\3
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ibus-libpinyin (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1760758 Title: /usr/lib/ibus/ibus-engine-libpinyin:ibus-engine-libpinyin: pinyin.cpp:991\357\274\232bool pinyin_set_zhuyin_scheme(pinyin_context_t*, ZhuyinScheme): \345\201\207\350\256\276 \342\200\230(0)\342\200\231 \345\244\261\350\264\245\343\200\202 Status in ibus-libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Xenial: New Status in ibus-libpinyin source package in Artful: Won't Fix Status in ibus-libpinyin source package in Bionic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ibus-libpinyin. This problem was most recently seen with package version 1.7.3-2, the problem page at https://errors.ubuntu.com/problem/93033df7be22fcd00507d4744cd85fe4a72b727f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1760758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: snapd-glib (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1723362 Title: gnome-software spams error messages to journald and causes 100% CPU usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Invalid Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Confirmed Status in snapd-glib source package in Xenial: Confirmed Status in gnome-software source package in Artful: Won't Fix Status in snapd-glib source package in Artful: Won't Fix Status in gnome-software source package in Bionic: Invalid Status in snapd-glib source package in Bionic: Fix Released Bug description: gnome-software spams this message to journald: Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 10:58:38 2017 InstallationDate: Installed on 2016-10-25 (352 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728617] Re: Scrolled window broken when containing an eventbox
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gtk+3.0 (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1728617 Title: Scrolled window broken when containing an eventbox Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Artful: Won't Fix Bug description: https://github.com/gnumdk/lollypop/issues/1279 Ubuntu is shipping 074_eventbox_scroll_mask.patch, this patch is really strange, it adds a scroll mask on all eventbox breaking all applications using eventbox in scrolled windows. This patch is not in Debian and should be removed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728617/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1675453] Re: During d-i install of ubuntu-server from mini.iso I get no login prompt
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: grub2 (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1675453 Title: During d-i install of ubuntu-server from mini.iso I get no login prompt Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Invalid Status in grub2 source package in Artful: Won't Fix Status in grub2-signed source package in Artful: Won't Fix Status in plymouth source package in Artful: Invalid Bug description: STEPS: 1. Grab the mini.iso from http://archive.ubuntu.com/ubuntu/dists/zesty/main/installer-amd64/current/images/netboot/mini.iso 2. Boot it 3. Run the installer and from the tasksel list select ubuntu basic server and openssh server in addition to the default selected base 4. Complete the install remove the media and reboot EXPECTED: I expect to see a login prompt ACTUAL: I get a blank screen with a cursor top left. SSH logins work as expected WORKAROUND: Flip to an alternate TTY and you get the login prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1675453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1675453] Re: During d-i install of ubuntu-server from mini.iso I get no login prompt
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: grub2-signed (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1675453 Title: During d-i install of ubuntu-server from mini.iso I get no login prompt Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Invalid Status in grub2 source package in Artful: Won't Fix Status in grub2-signed source package in Artful: Won't Fix Status in plymouth source package in Artful: Invalid Bug description: STEPS: 1. Grab the mini.iso from http://archive.ubuntu.com/ubuntu/dists/zesty/main/installer-amd64/current/images/netboot/mini.iso 2. Boot it 3. Run the installer and from the tasksel list select ubuntu basic server and openssh server in addition to the default selected base 4. Complete the install remove the media and reboot EXPECTED: I expect to see a login prompt ACTUAL: I get a blank screen with a cursor top left. SSH logins work as expected WORKAROUND: Flip to an alternate TTY and you get the login prompt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1675453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving tr
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ubuntu-gnome-default-settings (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1750465 Title: upgrade attempting to process triggers out of order (package plymouth- theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed) Status in apt package in Ubuntu: Invalid Status in budgie-artwork package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in ubuntu-gnome-default-settings package in Ubuntu: Fix Released Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in apt source package in Xenial: Invalid Status in kubuntu-settings source package in Xenial: Confirmed Status in plymouth source package in Xenial: Fix Released Status in ubuntu-gnome-default-settings source package in Xenial: Confirmed Status in ubuntu-mate-artwork source package in Xenial: Confirmed Status in apt source package in Artful: Invalid Status in budgie-artwork source package in Artful: Fix Released Status in kubuntu-settings source package in Artful: Won't Fix Status in plymouth source package in Artful: Fix Released Status in ubuntu-gnome-default-settings source package in Artful: Won't Fix Status in ubuntu-mate-artwork source package in Artful: Won't Fix Bug description: [SRU Justification] A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail because of trying to process triggers out of order. Since the trigger being run is that of the currently-installed plymouth package, it is not guaranteed to be sufficient to fix the version of the package in 18.04. [Test case] 1. Install plymouth-themes-ubuntu-text from -proposed. 2. Run a release upgrade with each of update-manager -d, do-release-upgrade -d, and apt-get dist-upgrade (the last after manually changing sources.list). 3. Verify that in each case, the upgrade completes successfully, with no errors about out-of-order trigger configuration. [Regression potential] noawait triggers have been supported in dpkg since 1.16.1, which is older than the version in precise (https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html). A noawait trigger is considered appropriate whenever the triggered package does not need to block the triggering package. There is no reason for a plymouth theme package to need to block configuration of an essential package in this case. noawait triggers are well-exercised in the distro now, so the risk of regression from this change should be low. There is unfortunately not a known reproducer for the original bug, so the test case, while it should guard against regressions, is not strong confirmation that the bug is fixed. [Original description] Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Feb 18 23:41:49 2018 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-10-24 (118 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.5.1 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days
[Desktop-packages] [Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-software (Ubuntu Artful) Status: Triaged => Won't Fix -- 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/1716409 Title: Unable to install flatpakref on Ubuntu artful Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Artful: Won't Fix Bug description: I saw a news article with a link to install a flatpak. http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4 I clicked the link expecting to be able to install the flatpak, but the experience appears broken. I'm on an up to date Artful install What I did was:- Click on http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4 Click the flathub link:- https://flathub.org/repo/appstream/io.github.Pithos.flatpakref This downloaded the flatpakref file. I clicked the file in my browser, nothing happened I then tried finding the file in nautilus and double clicked it. GNOME Software launched and presented an error "Don't know how to handle 'file:///home/alan/Downloads/io.github.Pithos.flatpakref' (see screenshot). If I search for pithos in GNOME Software I am able to find the older version from the deb repo, but not the newer version from flathub. Do we not support flatpak/flathub out of the box? Or is my system uniquely hosed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746773] Re: Search for Skype in GNOME Software doesn't list Skype as the first match
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-software (Ubuntu Artful) Status: Fix Committed => Won't Fix -- 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/1746773 Title: Search for Skype in GNOME Software doesn't list Skype as the first match Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Artful: Won't Fix Status in gnome-software source package in Bionic: Fix Released Bug description: When searching for Skype in GNOME Software on Ubuntu 18.04 daily, Skype is not the first match that is listed. See the attached screenshot. ## Expected behaviour When searching for Skype, Skype should be the first match. ## Actual behaviour I search for Skype and the first match is not Skype. ## Steps to reproduce the behaviour * Open Ubuntu Software * Click the search icon and enter 'skype' ## Ubuntu version * Ubuntu 18.04 daily ## ubuntu-software version Package: ubuntu-software Version: 3.26.5-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1746773/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716579] Re: gnome-software uses a very high cpu amount
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-software (Ubuntu Artful) Status: In Progress => Won't Fix -- 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/1716579 Title: gnome-software uses a very high cpu amount Status in gnome-software package in Ubuntu: In Progress Status in gnome-software source package in Artful: Won't Fix Bug description: The room was silent, when the fan of my laptop suddenly started making noise. I checked it and it was because of the intense amount of CPU in use because of gnome software. Gnome Software CPU use was over 60%. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.25.91-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 08:29:01 2017 InstallationDate: Installed on 2017-08-21 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.25.91-1ubuntu5 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gtk+3.0 (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1700319 Title: GTK3 menus don't work over SSH forwarding Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Artful: Won't Fix Bug description: * Impact GTK interfaces used over SSH might miss their menus * Test case --- - connect via ssh -X to a cygwin server - start an application that is using menus (e.g virt-manager) -> the menus should work * Regression potential -- check that gtk softwares have working menus and look the same Original Bug Report --- When connecting remotely (either SSH X11 forwarding or direct to X11 server), drop down menus do not display properly. Bug upstream in gtk3: https://bugzilla.gnome.org/show_bug.cgi?id=780101 Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3 Server: Windows 10 Cygwin/X 1.19.2-1 Programs exhibiting this problem: evince 3.24.0 (and any other gtk3 apps with menus along the top). Patch applied to gtk3 in cygwin to fix this problem and attached to this post: https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch Console errors: (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed (evince:7390): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: The name org.freedesktop.portal.Desktop is not owned (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu) (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu) *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1700319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.n
[Desktop-packages] [Bug 1629600] Re: Installed application from .deb does not appear unless Ubuntu is restarted
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-software (Ubuntu Artful) Status: Triaged => Won't Fix -- 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/1629600 Title: Installed application from .deb does not appear unless Ubuntu is restarted Status in One Hundred Papercuts: Confirmed Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Xenial: New Status in gnome-software source package in Zesty: Invalid Status in gnome-software source package in Artful: Won't Fix Bug description: I'm using Ubuntu 16.04 x64 and the installed version of gnome-software is 3.20.1 * I install a desktop application from a .deb package. I tried several methods (apt install, dpkg -i, xdg-open then click on install button). * After the installation, I control that the application is visible from the system: * The application appears correctly in the application list in Unity Dash * The application appears in the "Open With" menu list in Nautilus (because of registered mime types) * The package name of the application can be used as an argument of apt commands (apt show, apt remove...) and dpkg (dpkg -l, dpkg -L...) * I start gnome-software. * I click on the "installed" tab to get the list of installed applications. expected result: the freshly installed application is in the list actual result: the freshly installed application is not in the list. If I reboot my computer and start gnome-software, the installed application appears in the list. It looks like there is some kind of cache that is not refreshed at the right moment. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1629600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728653] Re: Update evolution-data-server to 3.26.3
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: evolution-data-server (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1728653 Title: Update evolution-data-server to 3.26.3 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Artful: Won't Fix Bug description: Note to SRU Team I guess we might as well wait for 3.26.4 now, scheduled for January 9. Impact == evolution-data-server (e-d-s) has released a new stable bugfix release. (These will happen about once every month until 3.28 is released.) Updating e-d-s is required to update evolution to 3.26.3 (LP: #1728655) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.26 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1728653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: xorg-server (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: New Status in greybird-gtk-theme package in Ubuntu: Fix Released Status in xfce4-panel package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in greybird-gtk-theme source package in Cosmic: Won't Fix Status in xfce4-panel source package in Cosmic: Won't Fix Status in xorg-server source package in Cosmic: Won't Fix Status in greybird-gtk-theme source package in Disco: Fix Released Status in xfce4-panel source package in Disco: Fix Released Status in xorg-server source package in Disco: Won't Fix Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: xfce4-panel (Ubuntu Cosmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: New Status in greybird-gtk-theme package in Ubuntu: Fix Released Status in xfce4-panel package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in greybird-gtk-theme source package in Cosmic: Won't Fix Status in xfce4-panel source package in Cosmic: Won't Fix Status in xorg-server source package in Cosmic: Won't Fix Status in greybird-gtk-theme source package in Disco: Fix Released Status in xfce4-panel source package in Disco: Fix Released Status in xorg-server source package in Disco: Won't Fix Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: greybird-gtk-theme (Ubuntu Cosmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: New Status in greybird-gtk-theme package in Ubuntu: Fix Released Status in xfce4-panel package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in greybird-gtk-theme source package in Cosmic: Won't Fix Status in xfce4-panel source package in Cosmic: Won't Fix Status in xorg-server source package in Cosmic: Won't Fix Status in greybird-gtk-theme source package in Disco: Fix Released Status in xfce4-panel source package in Disco: Fix Released Status in xorg-server source package in Disco: Won't Fix Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: systemd (Ubuntu Cosmic) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1726160 Title: On login, display rotates to wrong orientation [HP Pavilion] Status in IIO Sensor Proxy: Fix Released Status in systemd: Fix Released Status in iio-sensor-proxy package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in iio-sensor-proxy source package in Bionic: Invalid Status in systemd source package in Bionic: Triaged Status in iio-sensor-proxy source package in Cosmic: Invalid Status in systemd source package in Cosmic: Won't Fix Status in iio-sensor-proxy source package in Disco: Invalid Status in systemd source package in Disco: Fix Released Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039D222412102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807983] Re: Update gnome-desktop3 to 3.30.2
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-desktop3 (Ubuntu Cosmic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1807983 Title: Update gnome-desktop3 to 3.30.2 Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Cosmic: Won't Fix Bug description: Impact == This updates the GNOME version number reported in Settings > Details > About to 3.30.2 This is the final scheduled point release for GNOME 3.30. I'm also cherry-picking a potential crash bug fix from the gnome-3-30 branch since there might not be another 3.30 release tarball. This also includes the fix for LP: #1807127 Test Case = From Ubuntu 18.10, open the Settings app. Navigate to Details > About The GNOME version number should say 3.30.2 Regression Potential There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827029] Re: Extended characters in OSK don't get entered
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mutter (Ubuntu Cosmic) Status: In Progress => Won't Fix -- 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/1827029 Title: Extended characters in OSK don't get entered Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Won't Fix Status in mutter source package in Disco: Fix Released Bug description: [Impact] This bug affects any of the "extended characters" clicked on from the long-press popup in the Screen Keyboard. [Test Case] 1. Open GNOME Settings > Universal Access 2. Enable the Screen Keyboard. (Optionally, turn on Always Show Universal Access Menu to make turning the Screen Keyboard on and off easier.) 3. Open Text Editor 4. Click the u button on the Screen Keyboard 5. Long-press the u button on the Screen Keyboard for a few seconds. 6. On the popup, click the ü character. What Happens In Step 4, u is entered in the Text Editor document. Nothing is entered in Step 5. [Regression Potential] The code to be backported only affects OSK. Check that normal OSK keys (e.g. a,b,c,...) normally works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827029/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: snapd (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1794953 Title: GNOME Calculator snap has wrong theme in live session Status in snapd: Fix Released Status in gnome-calculator package in Ubuntu: Invalid Status in snapd package in Ubuntu: Confirmed Status in gnome-calculator source package in Cosmic: Invalid Status in snapd source package in Cosmic: Won't Fix Bug description: Running GNOME Calculator (or System Monitor, for example) runs the app with Adwaita theme instead of Yaru when in the live session. This seems to resolve itself when used in the real session. Steps to reproduce: * Launch a live USB stick in a VM (note: you might need to use nomodeset until that is fixed) * Open any of the seeded snaps and note that the theme is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1794953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-desktop3 (Ubuntu Cosmic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1807127 Title: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: Fix Released Status in gnome-desktop3 source package in Cosmic: Won't Fix Bug description: Impact == Thumbnailing doesn't work on Ubuntu 18.04 LTS or 18.10 on 32-bit installs. Test Case = Install Ubuntu 18.10 32-bit Install the update. Log out and log back in. Download a picture from the internet. Open your file browser to the directory that contains the picture. The file should show a thumbnail preview. Regression Potential This fix was cherry-picked to the stable gnome-3-30 branch. It was additionally tested by Iain Lane on usrmerged and non-usrmerged systems. (We don't support usrmerge for Ubuntu 18.04 LTS or 18.10.) Other Info == Triaged as Critical for 18.04 LTS since this was a regression introduced in the security update that backported the bubblewrap hardening to the gnome-desktop3 thumbnailer. Original Bug Report === Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu. Looks like same issue in upstream - https://bugzilla.redhat.com/show_bug.cgi?id=1651952 Cause - bubblewrap runs with --ro-bind /lib64 option, then fails. Workaround - create empty /lib64 directory at root. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 12:07:28 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-desktop3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Eoan) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in gcc-9 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Status in backport-iwlwifi-dkms source package in Eoan: Fix Released Status in gcc-9 source package in Eoan: Won't Fix Status in linux source package in Eoan: Fix Released Status in nvidia-graphics-drivers-390 source package in Eoan: Won't Fix Status in nvidia-graphics-drivers-430 source package in Eoan: Fix Released Status in virtualbox source package in Eoan: Won't Fix Status in xtables-addons source package in Eoan: Won't Fix Bug description: [SRU Justification for backport-iwlwifi-dkms] [Impact] FTBFS against v5.3 kernels on Eoan/Focal. [Fix] * Backport fix from upstream commit f47729b94e11 (backport: rename ktime_get_boot_ns for v5.3+). * Also updates -fcf-protection=none usage for bug 1830961. [Test Case] Verified DKMS module build on linux-oem/linux-oem-osp1/linux-generic >= 4.10 kernels on series Xenial/Bionic/Cosmic/Disco/Eoan and Focal. [Regression Risk] Low. There is no functional changes in comparison to 7906-0ubuntu1. original bug description Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed
Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.
** Changed in: ubuntu-drivers-common (Ubuntu Eoan)
Status: Confirmed => Won't Fix
--
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/1856407
Title:
nvidia-435 is in eoan, linux-restricted-modules only builds against
430, ubiquity gives me the self-signed modules experience instead of
using the Canonical-signed modules
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in ubuntu-meta package in Ubuntu:
New
Status in linux source package in Eoan:
Fix Released
Status in linux-restricted-modules source package in Eoan:
Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
Won't Fix
Status in ubuntu-drivers-common source package in Eoan:
Won't Fix
Status in ubuntu-meta source package in Eoan:
Won't Fix
Bug description:
SRU Justification
Impact: The nvidia-435 drivers are missing from linux-restricted-
modules in eoan. On install ubuntu-drivers picks 435 as the newest
version, and users must use self-signed dkms drivers and enroll a MOK.
Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.
Test Case: A test build is available in ppa:sforshee/test-builds.
Verify that signed drivers for nvidia-435 can be installed for eoan
via the linux-modules-nvidia-435-{generic,lowlatency} packages.
Regression Potential: The nvidia-435 l-r-m drivers are new packages
built from the same source as the nvidia-435 dkms driver, so
regressions are unlikely.
---
The linux-restricted-modules package exists so that users who install
the nvidia drivers can get known-good, signed modules instead of
having to locally self-sign and enroll a signing key through MOK. But
lrm in eoan is only building driver packages for nvidia 390 and 430,
and nvidia 435 is present in eoan.
So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
newest driver instead of using the signed 430 driver.
We should never allow the archive to get into this situation. We
should be enforcing that any version of the nvidia driver that we
expect ubuntu-drivers to install by default on any hardware is
integrated into linux-restricted-modules, and we should ensure that
ubuntu-drivers always prefers the signed drivers over other options.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed
Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.
** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan)
Status: Confirmed => Won't Fix
--
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/1856407
Title:
nvidia-435 is in eoan, linux-restricted-modules only builds against
430, ubiquity gives me the self-signed modules experience instead of
using the Canonical-signed modules
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in ubuntu-meta package in Ubuntu:
New
Status in linux source package in Eoan:
Fix Released
Status in linux-restricted-modules source package in Eoan:
Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
Won't Fix
Status in ubuntu-drivers-common source package in Eoan:
Won't Fix
Status in ubuntu-meta source package in Eoan:
Won't Fix
Bug description:
SRU Justification
Impact: The nvidia-435 drivers are missing from linux-restricted-
modules in eoan. On install ubuntu-drivers picks 435 as the newest
version, and users must use self-signed dkms drivers and enroll a MOK.
Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.
Test Case: A test build is available in ppa:sforshee/test-builds.
Verify that signed drivers for nvidia-435 can be installed for eoan
via the linux-modules-nvidia-435-{generic,lowlatency} packages.
Regression Potential: The nvidia-435 l-r-m drivers are new packages
built from the same source as the nvidia-435 dkms driver, so
regressions are unlikely.
---
The linux-restricted-modules package exists so that users who install
the nvidia drivers can get known-good, signed modules instead of
having to locally self-sign and enroll a signing key through MOK. But
lrm in eoan is only building driver packages for nvidia 390 and 430,
and nvidia 435 is present in eoan.
So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
newest driver instead of using the signed 430 driver.
We should never allow the archive to get into this situation. We
should be enforcing that any version of the nvidia driver that we
expect ubuntu-drivers to install by default on any hardware is
integrated into linux-restricted-modules, and we should ensure that
ubuntu-drivers always prefers the signed drivers over other options.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914051] Re: `ubuntu-drivers list-oem --package-list` is broken
Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ubuntu-drivers-common (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931514] Re: SRU: The NVIDIA X server Settings is blank when under Intel mode
Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ubuntu-drivers-common (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ubuntu-drivers-common (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Won't Fix Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921949] Re: libreoffice-math save icon reset upon arrow action
Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libreoffice (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- 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/1921949 Title: libreoffice-math save icon reset upon arrow action Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Won't Fix Status in libreoffice source package in Focal: Won't Fix Status in libreoffice source package in Groovy: Won't Fix Status in libreoffice source package in Hirsute: Won't Fix Bug description: The save icon (in libreoffice-math only) will indicate there are changes to be saved. However, if you arrow anywhere, it changes the save icon to indicate there are no changes needing to be saved. You can close the doc in this state and you *will not* be prompted to save/discard changes and all changes will be lost. Steps to reproduce: 1. open new math doc 2. add any equation -> see the save icon indicates there are changes that need to be saved. 3. arrow anywhere -> see the save icon go back to indicating there are no changes. You can keep making changes to see the save icon indicate there are changes. Then arrow to make it go away. You can do this repeatedly. This problem manifests itself in: - bionic vm with stock 6.0.7-0ubuntu0.18.04.10 - focal vm with stock 6.4.6-0ubuntu0.20.04.1 - hirsute vm with 7.1.2~rc2-0ubuntu0.21.04.1~lo4 (provided by the prereleases ppa) - a debian 10 vm, with stock 6.1.5-3+deb10u7 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1921949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930937] Re: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop
Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: screen-resolution-extra (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Confirmed Status in screen-resolution-extra source package in Groovy: Won't Fix Status in screen-resolution-extra source package in Hirsute: Won't Fix Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops
Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: nvidia-prime (Ubuntu Hirsute) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Fix Released Status in nvidia-prime package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-prime source package in Hirsute: Won't Fix Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] Information for Focal, refer to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: nvidia-prime (Ubuntu Hirsute) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-prime source package in Hirsute: Won't Fix Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: marco (Ubuntu Impish) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Fix Released Status in marco package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in marco source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Status in marco source package in Impish: Won't Fix Status in xorg-server source package in Impish: Won't Fix Status in marco source package in Jammy: Fix Released Status in xorg-server source package in Jammy: Fix Released Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856032] Re: Removable media icon stays on the dock after eject.
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: Confirmed => Won't Fix -- 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/1856032 Title: Removable media icon stays on the dock after eject. Status in OEM Priority Project: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: Won't Fix Bug description: 1) Ubuntu 19.10 2) Dock 3) I placed a DVD in the optical drive. An optical disc with a DVD tag appeared on the dock. I pressed the button on the optical drive to open it. I removed the disc and pressed in the tray. The icon should have disappeared from the dock. 4) The icon did NOT disappear from the dock. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947519] Re: Unless gedit is installed, "Appearance" causes control center to crash
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-control-center (Ubuntu Impish) Status: Triaged => Won't Fix -- 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/1947519 Title: Unless gedit is installed, "Appearance" causes control center to crash Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Impish: Won't Fix Bug description: Ubuntu 21.10. Gedit not installed from deb (I use a Flatpak version). Steps to reproduce: - sudo apt remove gedit - sudo apt autoremove - gnome-control-center ubuntu Expected: control center opens with Appearance tab shown Experienced: nothing happens, log in terminal: (gnome-control-center:27462): GLib-GIO-ERROR **: 22:03:20.416: Settings schema 'org.gnome.gedit.preferences.editor' is not installed ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 21:57:23 2021 InstallationDate: Installed on 2021-06-30 (109 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1947519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948008] Re: Copying and pasting files between desktop and Nautilus does not work
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Impish) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting files between desktop and Nautilus does not work Status in Gnome Shell Extension Desktop Icons Ng: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons-ng source package in Focal: Invalid Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Won't Fix Status in gnome-shell source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons source package in Impish: Invalid Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Won't Fix Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1948008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Committed Status in xorg-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Won't Fix Status in xorg-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Won't Fix Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK afcaaac96767d77 print_edid: Fix a format string error 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) 53173fdab492f0f render: Fix build with gcc 12 69774044716039f present: Check for NULL to prevent crash --- original info [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: urfkill (Ubuntu Kinetic) Status: New => Won't Fix -- 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/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in urfkill package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in network-manager source package in Jammy: Invalid Status in urfkill source package in Jammy: New Status in linux source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Invalid Status in urfkill source package in Kinetic: Won't Fix Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989590] Re: Can't click on dock items if status drop-down is shown
Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-shell (Ubuntu Kinetic) Status: Fix Committed => Won't Fix -- 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/1989590 Title: Can't click on dock items if status drop-down is shown Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Kinetic: Won't Fix Status in gnome-shell source package in Lunar: Fix Released Bug description: Steps: 1. open any of the system status drop-downs 2. click on any app icon in the Ubuntu Dock Expected: 1. the system status drop-down goes away Current: 1. nothing happens ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 16:49:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (13 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013128] Re: mesa: set info.separate_shader for ARB programs
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: mesa (Ubuntu Lunar) Status: Triaged => Won't Fix -- 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/2013128 Title: mesa: set info.separate_shader for ARB programs Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: In Progress Status in mesa source package in Kinetic: Won't Fix Status in mesa source package in Lunar: Won't Fix Status in mesa source package in Mantic: Fix Released Bug description: [Impact] There's a shader bug in 22.2.x, fixed upstream in commit https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782 but since 22.2.x is already EOL, we need to backport it. [Test case] Install update, check that the application from the submitter works. [Where things could go wrong] This is a oneliner that flips a bool, but it's hard to imagine use-cases which would expect the old value. -- I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled into debian's repo. I do not know the proper way to request an updated version be made for Ubuntu. I've manually installed many different versions of libmesa to test on my own that it was working in an older version, is broken in this update, and was fixed again in 22.3.4 and 22.3.5. The one-line fix is implemented here in libmesa's repo: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782 Unfortunately I'm not using libmesa directly. I'm programming an application using fox-toolkit which interfaces with libmesa behind the scenes for me. I reported my issue to them first, and they stated it appears to be in the mesa library, which is what ultimately led me down the path to their repo, debian's repo, and here. Please let me know if I'm in the right spot, and, if so, what my next step is to properly report this. -- Feature Request: Upgrade mesa libraries to apply upstream bugfix to a bug introduced in 22.2.5-0ubuntu0.1~22.04.1. I was directed to report this bug via my question at answers.launchpad.net/ubuntu: https://answers.launchpad.net/ubuntu/+question/705988 Please let me know if you need further information. Thanks! > lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 > apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 22.2.5-0ubuntu0.1~22.04.1 Candidate: 22.2.5-0ubuntu0.1~22.04.1 Version table: *** 22.2.5-0ubuntu0.1~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 22.0.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: i3 Date: Tue Mar 28 15:30:59 2023 InstallationDate: Installed on 2022-04-28 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2013128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in broadcom-sta source package in Lunar: Won't Fix Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Won't Fix Status in broadcom-sta source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Fix Released Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039187] Re: Thunderbird doesn't accept URI attachments anymore
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: xdg-desktop-portal-gtk (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2039187 Title: Thunderbird doesn't accept URI attachments anymore Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk source package in Focal: New Status in xdg-desktop-portal-gtk source package in Jammy: New Status in xdg-desktop-portal-gtk source package in Lunar: Won't Fix Status in xdg-desktop-portal-gtk source package in Mantic: Won't Fix Bug description: The desktop portal constructs an mailto: url with an attachment= but thunderbird upstream explicitly decided to not allow adding files from an URL for security reasons. One can still use the -compose option though, as this patch does. Test case - * Install the proposed package. * Log out and back in. * Set Thunberbird as default client in Gnome Control Panel. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. * Thunderbird should open with the corresponding files attached. * [For regression testing] Set Evolution as the default. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. It only attaches one file, this is however not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: mesa (Ubuntu Lunar)
Status: New => Won't Fix
--
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in mesa source package in Lunar:
Won't Fix
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
X-HWE-Bug: Bug #2047389
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Won't Fix
--
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in mesa source package in Lunar:
Won't Fix
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
X-HWE-Bug: Bug #2047389
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: software-properties (Ubuntu Lunar)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Fix Released
Status in software-properties source package in Focal:
Won't Fix
Status in software-properties source package in Jammy:
Triaged
Status in software-properties source package in Kinetic:
Won't Fix
Status in software-properties source package in Lunar:
Won't Fix
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995092] Re: Wrong ubuntu logo in About section in darkmode
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-control-center (Ubuntu Lunar) Status: Triaged => Won't Fix -- 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/1995092 Title: Wrong ubuntu logo in About section in darkmode Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Lunar: Won't Fix Bug description: Bug only on Ubuntu 22.10 and Ubuntu 23.04 The ubuntu logo used when darkmode is selected on the "About" page of Settings is not the right one. There is two ubuntu logo stored in /usr/share/pixmaps/: -ubuntu-logo-text.png -ubuntu-logo-text-dark.png It seams that for some reasons the "ubuntu-logo-text-dark.png" is not used at it should be in darkmode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1995092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: nemo (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- 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: Won't Fix Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: Won't Fix Status in caja source package in Lunar: Won't Fix Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Won't Fix 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
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: caja (Ubuntu Lunar) Status: New => Won't Fix -- 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: Won't Fix Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: Won't Fix Status in caja source package in Lunar: Won't Fix Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Won't Fix 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 2007702] Re: [SRU] Deb version numbering is misleading
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: chromium-browser (Ubuntu Lunar) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2007702 Title: [SRU] Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Incomplete Status in chromium-browser source package in Jammy: Incomplete Status in chromium-browser source package in Lunar: Won't Fix Status in chromium-browser source package in Mantic: Won't Fix Bug description: [Impact] For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [Test plan] Install the package and confirm the version change with e.g. dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' [Regression potential] If the version were incorrectly constructed the deb build could fail. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009767] Re: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Lunar) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: External HDMI monitor is laggy on NVIDIA-525 reverse PRIME system Status in OEM Priority Project: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: Fix Committed Status in xorg-server source package in Focal: New Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Committed Status in xorg-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Committed Status in xorg-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Lunar: Won't Fix Status in xorg-server source package in Lunar: Fix Released Bug description: [Impact] NVIDIA driver has a hardcoded version check to see if a bug has been fixed in the xserver version. It does not help to backport the fix to the jammy xserver, as the driver has no way to check if the fix is there or not. We need to backport xorg-server from kinetic to jammy. [Test case] install xserver update, check that lagginess is gone [Regression potential] This is a backport of kinetic xorg-server to jammy, with 34 new upstream commits of which three were already backported due to CVE's, and a bugfix. 18 commits only touch darwin/XQuartz and won't affect us. As such, there should be a low chance of things breaking. Here's a list of the remaining 12 commits with above filtered out: 6bf62381d0a1fb5 xserver 21.1.4 855b96a85bc0711 xfree86: Fix event data alignment in inputtest driver b713e717c34d539 dix: Correctly save replayed event into GrabInfoRec cd3d21d8c44a35c xkb: fix XkbSetMap when changing a keysym without changing a keytype f575524314e9f20 Revert "os: Try to discover the current seat with the XDG_SEAT var first" 433f53a1a08390a tests: Fix build failure from missing micmap.c 3868f364728ae0c xf86-input-inputtest: Fix build on systems without SOCK_NONBLOCK afcaaac96767d77 print_edid: Fix a format string error 663af2f17eec2cc X11Application: Ensure TIS operations are done on the main thread bd3564cf377deac rootless: Dead code removal (ROOTLESS_REDISPLAY_DELAY is already defined) 53173fdab492f0f render: Fix build with gcc 12 69774044716039f present: Check for NULL to prevent crash --- original info [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be black in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Workaround] Downgrade to NVIDIA driver 515. [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012994] Re: Automatic Date & Time switch shows as insensitive when enabled
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-control-center (Ubuntu Lunar) Status: Triaged => Won't Fix -- 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/2012994 Title: Automatic Date & Time switch shows as insensitive when enabled Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Lunar: Won't Fix Bug description: Go to Settings > Date & Time and toggle the "Automatic Date & Time" switch. When enabled it shows as insensitive (i.e. grey instead of orange). The "Automatic Time Zone" switch below behaves as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023183] Re: network-manager autokpgtest failure (nm.py)
Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: network-manager (Ubuntu Lunar) Status: Confirmed => Won't Fix -- 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/2023183 Title: network-manager autokpgtest failure (nm.py) Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Lunar: Won't Fix Status in network-manager source package in Mantic: Won't Fix Status in network-manager source package in Noble: Fix Released Bug description: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024377] Re: Adsys can't fetch GPOs
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: adsys (Ubuntu Mantic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2024377
Title:
Adsys can't fetch GPOs
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Jammy:
Fix Released
Status in adsys source package in Mantic:
Won't Fix
Bug description:
This bug is not being verified individually because of the use of the
SRU exception process (LP: #2059756)
-
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums,
Reddit or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
backend, I can log with Active Directory users however when adsys is
installed I can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get
policies for "ubuntu": can't download all gpos and assets: one or more
error while fetching GPOs and assets: can't download "ubuntuRoot":
can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
It happens when using "adsysctl update -m" or "adsysctl update
usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
"adsysctl update" too.
I've upgrade the machine to 22.10 and the error changed to:
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER').
After upgrade to 23.04 the error persist same as the above.
Full info 22.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
We will only use the defaults, env variables or flags.
DEBUG Connecting as [[2504:109556]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
DEBUG Analyzing "assets"
DEBUG Analyzing "ubuntuRoot"
INFO No assets directory with GPT.INI file found on AD, skipping assets
download
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": can't download all gpos and assets: one or more error while fetching
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs
refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
Full info 23.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
DEBUG Connecting as [[58811:006019]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER')
Additional info:
Domain Controller and machine are on the same subnet without firewall on any
level;
Domain Controller is a Windows Server 2019 updated to the last security
version;
Both machine and user are on the same OU with "no heritage" enabled and just
one policy added to permit usern..
[Desktop-packages] [Bug 2044112] Re: Add dependency on nfs-common
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: adsys (Ubuntu Mantic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2044112 Title: Add dependency on nfs-common Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Fix Released Status in adsys source package in Mantic: Won't Fix Bug description: This bug is not being verified individually because of the use of the SRU exception process (LP: #2059756) - The nfs-common package is required if NFS shares are to be mounted on the client. Unlike cifs-utils, this package is not installed by default on Ubuntu Desktop. Given that we declare the former as a dependency we should do the same with nfs-common. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2044112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051363] Re: Cannot perform certificate auto-enroll without NDES installed
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: adsys (Ubuntu Mantic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2051363
Title:
Cannot perform certificate auto-enroll without NDES installed
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Jammy:
Fix Released
Status in adsys source package in Mantic:
Won't Fix
Bug description:
This bug is not being verified individually because of the use of the
SRU exception process (LP: #2059756)
-
NDES role should not be mandatory in order to perform certificate
auto-enrollment with adsys.
Samba/ADSys is able to take advantage of the NDES endpoint to install
the root certificate chain, but is also able to infer the certificate
information from LDAP.
Due to a bug in the Samba implementation of cert-autoenroll, the root
cert is not parsed properly if the NDES component is not installed --
so in the current state attempting auto-enrollment without NDES
installed will result in an error like the following:
2024-01-08 16:11:07.809|[W26775]| Failed to fetch the root certificate chain.
| {}
2024-01-08 16:11:07.809|[W05621]| The Network Device Enrollment Service is
either not installed or not configured. | {}
2024-01-08 16:11:07.809|[W11946]| Installing the server certificate only. | {}
Traceback (most recent call last):
File "", line 142, in
File "", line 89, in main
File "", line 20, in enroll
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py",
line 502, in __enroll
self.apply(guid, ca, cert_enroll, ca, ldb, trust_dir,
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py",
line 369, in apply
data = applier_func(*args, **kwargs)
^
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py",
line 274, in cert_enroll
root_certs = getca(ca, url, trust_dir)
^
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py",
line 221, in getca
cert = load_der_x509_certificate(ca['cACertificate'],
^^
File "/usr/lib/python3/dist-packages/cryptography/x509/base.py", line 528,
in load_der_x509_certificate
return rust_x509.load_der_x509_certificate(data)
^
TypeError: argument 'data': 'str' object cannot be converted to 'PyBytes'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2051363/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: adsys (Ubuntu Mantic)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2049061
Title:
adsysctl update with a domain user fails if KRB5CCNAME is not set
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Jammy:
Fix Released
Status in adsys source package in Mantic:
Won't Fix
Bug description:
This bug is not being verified individually because of the use of the
SRU exception process (LP: #2059756)
-
In an environment where /etc/krb5.conf sets "default_ccache_name =
FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable
set, running "adsysctl update" with a AD domain user will fail.
If you either export the variable with the path to the kerberos ticket
OR run the command "adsysctl update
" it works.
The adsysctl command should fallback to the default location when
KRB5CCNAME is not defined or have a mechanism to query klist and find
the Kerberos tickets location.
Given that adsys can't find Kerberos tickets when `klist` does. It
seems like a feature parity issue, granted, an edge case.
Here is an example of a reproducer:
https://pastebin.ubuntu.com/p/FjyTWQChjM/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: adsys 0.9.2~22.04.2
ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1014-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: us-west-2
CloudSubPlatform: metadata (http://169.254.169.254)
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 11:39:06 2024
Ec2AMI: ami-00094f7041bb1b79d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: us-west-2b
Ec2Imageid: ami-00094f7041bb1b79d
Ec2InstanceType: t3.large
Ec2Instancetype: t3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: us-west-2
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
sssd 2.6.3-1ubuntu3.2
python3-samba 2:4.15.13+dfsg-0ubuntu1.5
SourcePackage: adsys
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf:
[deleted]
modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054445] Re: Regresion in sssd backend configuration
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: adsys (Ubuntu Mantic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2054445 Title: Regresion in sssd backend configuration Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Fix Released Status in adsys source package in Mantic: Won't Fix Bug description: This bug is not being verified individually because of the use of the SRU exception process (LP: #2059756) - This is a regression from when we added support for multiple AD backends (see https://github.com/ubuntu/adsys/pull/467) Previously adsys would use the first domain from `sssd.conf` and potentially override it if `ad_domain` is explicitly set for the domain, see: https://github.com/ubuntu/adsys/blob/32a830f2a8204cc8b896094bad512ed619fbf6b7/internal/adsysservice/adsysservice.go#L279-L280 The current implementation raises an error if we are not able to find an `ad_domain` setting in the domain section, even if we already have a domain (`sssdDomain`): https://github.com/ubuntu/adsys/blob/c68d2cc999d25b1cb408a9e31775a76d2af4c8c7/internal/ad/backends/sss/sss.go#L62-L65 Ideally we should set `domain` to `sssdDomain` if we cannot find a value for `ad_domain`, which will mimic the behavior previous to the refactor. While by default joining a domain with `realm join` will set the appropriate configuration values in `sssd.conf` so this doesn't happen, this is a regression we should aim to fix. ### Steps to reproduce it 1. Join an AD domain with sssd (e.g. using `realm join`) 2. Install the latest version of adsys, run `adsysctl update -m -vv`, everything should work 3. Comment out the `ad_domain` line from `/etc/sssd/sssd.conf` 4. `adsysctl update -m -vv` now fails, and the adsysd service does not start anymore 5. (Optional) To confirm the functionality prior to the regression, re-attempt the steps above on Ubuntu 22.04 using the adsys version currently in the archive (0.9.2) -- adsys is able to correctly determine the domain even without the `ad_domain` setting. GitHub issue: https://github.com/ubuntu/adsys/issues/910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2054445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923052] Re: screen reader does not read ubiquity window after it is launched in "Try Ubuntu" session
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: orca (Ubuntu Mantic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window after it is launched in "Try Ubuntu" session Status in at-spi2-core package in Ubuntu: Incomplete Status in orca package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Confirmed Status in at-spi2-core source package in Jammy: Incomplete Status in orca source package in Jammy: Incomplete Status in ubiquity source package in Jammy: Confirmed Status in at-spi2-core source package in Mantic: Won't Fix Status in orca source package in Mantic: Won't Fix Status in ubiquity source package in Mantic: Won't Fix Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923052] Re: screen reader does not read ubiquity window after it is launched in "Try Ubuntu" session
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: at-spi2-core (Ubuntu Mantic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window after it is launched in "Try Ubuntu" session Status in at-spi2-core package in Ubuntu: Incomplete Status in orca package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Confirmed Status in at-spi2-core source package in Jammy: Incomplete Status in orca source package in Jammy: Incomplete Status in ubiquity source package in Jammy: Confirmed Status in at-spi2-core source package in Mantic: Won't Fix Status in orca source package in Mantic: Won't Fix Status in ubiquity source package in Mantic: Won't Fix Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: broadcom-sta (Ubuntu Mantic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in broadcom-sta source package in Lunar: Won't Fix Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Triaged Status in broadcom-sta source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Fix Released Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: linux (Ubuntu Mantic) Status: Triaged => Won't Fix -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Won't Fix Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038669] Re: Add Raspberry Pi 5 support
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: libcamera (Ubuntu Mantic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcamera in Ubuntu. https://bugs.launchpad.net/bugs/2038669 Title: Add Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in libcamera source package in Mantic: Won't Fix Bug description: placeholder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2038669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039187] Re: Thunderbird doesn't accept URI attachments anymore
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: xdg-desktop-portal-gtk (Ubuntu Mantic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/2039187 Title: Thunderbird doesn't accept URI attachments anymore Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk source package in Focal: New Status in xdg-desktop-portal-gtk source package in Jammy: New Status in xdg-desktop-portal-gtk source package in Lunar: New Status in xdg-desktop-portal-gtk source package in Mantic: Won't Fix Bug description: The desktop portal constructs an mailto: url with an attachment= but thunderbird upstream explicitly decided to not allow adding files from an URL for security reasons. One can still use the -compose option though, as this patch does. Test case - * Install the proposed package. * Log out and back in. * Set Thunberbird as default client in Gnome Control Panel. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. * Thunderbird should open with the corresponding files attached. * [For regression testing] Set Evolution as the default. * Open Nautilus and try to attach two files to the same email. They can be creatively named, it should not break on weird characters. It only attaches one file, this is however not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/2039187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: modemmanager (Ubuntu Mantic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2039611 Title: [SRU] Fix fcc-unlock script for Lenovo X13s Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Mantic: Won't Fix Status in modemmanager source package in Noble: Fix Released Bug description: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional symlink in /usr/share/ModemManager/fcc- unlock.available.d/ whose name is the PCIe ID of this specific device. PCIe IDs are documented here: https://cateee.net/lkddb/web- lkddb/MHI_BUS.html. Also links in this folder have no effect on the system, unless the user manually enable the appropriate fcc unlock script, typically by adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model script. [ Other Info ] I am working on a debdiff, and will upload shortly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040292] Re: network-manager SRU flags system for restart required but also restarted the service
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: network-manager (Ubuntu Mantic) Status: New => Won't Fix -- 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/2040292 Title: network-manager SRU flags system for restart required but also restarted the service Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Mantic: Won't Fix Bug description: [ Impact ] * During an upgrade (or installation) of the network-manager package, its debian/network-manager.postinst maintainer script restarts NetworkManager.service and also requests users to reboot their system. * It requests a reboot, by calling into /usr/share/update-notifier/notify-reboot-required and listing "network-manager" in /var/run/reboot-required.pkgs * Restarting the systemd service AND asking for a reboot isn't needed. Just the service restart is enough and we shouldn't ask for a reboot as that is bad UX [ Test Plan ] * Reboot your system (or clear /var/run/reboot-required.pkgs) echo "" | sudo tee /var/run/reboot-required.pkgs * Install network-manager from mantic-proposed apt install [--reinstall] -t mantic-proposed network-manager * Observe that the NetworkManager.service was restarted by this operation: "active (running) [...] 2 min ago" systemctl status Networkmanager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; preset: enabled) Active: active (running) since Wed 2023-10-25 15:21:27 CEST; 2min ago Docs: man:NetworkManager(8) Main PID: 3880250 (NetworkManager) Tasks: 4 (limit: 28344) Memory: 6.1M CPU: 425ms CGroup: /system.slice/NetworkManager.service └─3880250 /usr/sbin/NetworkManager --no-daemon * Observe that network-manager was NOT written to /var/run/reboot-required.pkgs cat /var/run/reboot-required.pkgs * Observe that no GUI popped up asking you for a reboot because of NetworkManager [ Where problems could occur ] * This change is touching a maintainer script (.postinst) * Failures or syntax errors could leave the network-manager package unconfigured * It could break installation of the network-manager package [ Other Info ] * This SRU should probably just be staged, using `block-proposed-mantic` and bundled with the next upload. === original description === After applying the network-manager SRU in mantic, I get a notification that a system restart is required to fully apply updates. This immediately raised a question, because I KNOW my network connection was restarted when the SRU was installed (I have a VPN that did not auto-reconnect). And I checked the state of the process - it was definitely restarted and is running from the binary currently on disk. The network-manager postinst has the following code: # request a reboot (NM tears down interfaces on restart # which is not the way we want to go) [ -x /usr/share/update-notifier/notify-reboot-required ] && \ /usr/share/update-notifier/notify-reboot-required But the service restart is also happening. debian/rules currently has: override_dh_installsystemd: dh_installsystemd -pnetwork-manager --no-start NetworkManager-dispatcher.service NetworkManager-wait-online.service nm-priv-helper.service dh_installsystemd -pnetwork-manager --no-also NetworkManager.service No other systemd overrides. Nothing inhibits the restart of the service. It needs to be one or the other. And if we're doing SRUs of network- manager, then this is bad UX for users applying their daily updates and should be fixed in SRU. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 08:19:38 2023 InstallationDate: Installed on 2019-12-23 (1401 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-10-16 (8 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2040292/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 2041478] Re: /usr/bin/gnome-calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: gnome-calendar (Ubuntu Mantic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2041478 Title: /usr/bin/gnome- calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event Status in gnome-calendar package in Ubuntu: Fix Committed Status in gnome-calendar source package in Mantic: Won't Fix Status in gnome-calendar source package in Noble: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 45.0-1, the problem page at https://errors.ubuntu.com/problem/556afecb4d0b594b8bfdac2aa521cb12fa243a76 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2041478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: network-manager (Ubuntu Mantic) Status: Confirmed => Won't Fix -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in Netplan: Fix Released Status in NetworkManager: New Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Confirmed Status in netplan.io source package in Jammy: Fix Released Status in network-manager source package in Jammy: Confirmed Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Won't Fix Status in netplan.io source package in Lunar: Fix Released Status in network-manager source package in Lunar: Won't Fix Status in netplan.io source package in Mantic: Fix Released Status in network-manager source package in Mantic: Won't Fix Status in netplan.io source package in Noble: Fix Released Status in network-manager source package in Noble: Confirmed Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007702] Re: [SRU] Deb version numbering is misleading
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: chromium-browser (Ubuntu Mantic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2007702 Title: [SRU] Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Incomplete Status in chromium-browser source package in Jammy: Incomplete Status in chromium-browser source package in Lunar: Incomplete Status in chromium-browser source package in Mantic: Won't Fix Bug description: [Impact] For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [Test plan] Install the package and confirm the version change with e.g. dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' [Regression potential] If the version were incorrectly constructed the deb build could fail. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023183] Re: network-manager autokpgtest failure (nm.py)
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will not be fixed for that specific release. ** Changed in: network-manager (Ubuntu Mantic) Status: Confirmed => Won't Fix -- 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/2023183 Title: network-manager autokpgtest failure (nm.py) Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Lunar: Confirmed Status in network-manager source package in Mantic: Won't Fix Status in network-manager source package in Noble: Fix Released Bug description: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055088] Re: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie
** Also affects: software-properties (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2055088 Title: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie Status in software-properties package in Ubuntu: New Status in software-properties source package in Noble: New Bug description: software-properties-gtk is used on the official gtk desktops such as budgie. Currently in the debian control file it has a recommendation to install the session manager for that desktop - so gnome-session-bin for GNOME based desktops, mate-session for mate desktop and so on. budgie-desktop for noble now uses budgie-session as its session manager instead of gnome-session. Because of the current recommendation, gnome-session-bin is installed on budgie-desktop. It no longer needs to be installed. software-properties needs an update to its alternate recommendations so that budgie-desktop doesnt pull in gnome-session-bin incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package
** Also affects: glib2.0 (Ubuntu Noble) Importance: High Status: In Progress ** Changed in: glib2.0 (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2063221 Title: Drop libglib2.0-0 transitional package Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Noble: In Progress Bug description: Impact -- apt can struggle with ordering when handling the massive Y2028 time_t transition when upgrading to Ubuntu 24.04 LTS. It was identified that dropping the libglib2.0-0 transitional package can help apt do things in the correct order. Test Case - Is libglib2.0-0 built? Other Info -- This is related to LP: #2061918 for the thunderbird deb to snap upgrade There are likely several other Launchpad bugs that can be resolved by this update and some other workarounds in other packages, like in the transitional thunderbird package. https://salsa.debian.org/gnome-team/glib/-/merge_requests/34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
Julian had an idea on how to fix this on IRC: 07:12 < juliank> Ah yes, to solve the specific instance of the thunderbird snap and similar ones, one could also add Depends: libglib2.0-0t64 to their deb2snap packages -- 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/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 Status in thunderbird package in Ubuntu: Confirmed Bug description: This happened during an upgrade from Mantic to Noble. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 16 13:15:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-10 (2076 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SnapChanges: IDStatus Spawn Ready Summary 3563 Error 2024-04-16T13:15:26-07:00 2024-04-16T13:15:42-07:00 Install "thunderbird" snap 3564 Done2024-04-16T13:22:00-07:00 2024-04-16T13:22:09-07:00 Install "thunderbird" snap SourcePackage: thunderbird Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063127] Re: package thunderbird 2:1snap1-0ubuntu3 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2061918 *** https://bugs.launchpad.net/bugs/2061918 ** This bug has been marked a duplicate of bug 2061918 package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 -- 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/2063127 Title: package thunderbird 2:1snap1-0ubuntu3 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 Status in thunderbird package in Ubuntu: New Bug description: this occurred after booting up after upgrading to NN dev version ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 21 16:02:21 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-29 (53 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: thunderbird Title: package thunderbird 2:1snap1-0ubuntu3 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2063127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory
** Also affects: chromium-browser (Ubuntu Noble) Importance: High Assignee: Nathan Teodosio (nteodosio) Status: Invalid ** Also affects: snapd (Ubuntu Noble) Importance: Undecided Status: Triaged ** Changed in: snapd (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2061981 Title: chromium fails to start with non-standard home directory Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: Triaged Status in chromium-browser source package in Noble: Invalid Status in snapd source package in Noble: Triaged Bug description: CURRENT WORKAROUND -- snap disconnect chromium:dot-local-share-applications snap disconnect chromium:dot-local-share-icons Those are just "quality of life" interfaces (c.f. LP:1732482) that most users probably do not even use, disconnecting them will cause no breakage. (Of course, a proper diagnosis and fix is due.) ORIGINAL REPORT --- cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist- dir=$HOME 0 0): cannot use invalid home directory "/home/department/user_name": permission denied Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory /home/department/user_name Used to work fine up to last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Apr 17 10:32:18 2024 InstallationDate: Installed on 2017-03-24 (2580 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Snap.Changes: ID Status Spawn Ready Summary 206 Error 2024-04-16T19:08:43+02:00 2024-04-16T19:16:51+02:00 Remove "chromium" snap 207 Done2024-04-16T19:17:27+02:00 2024-04-16T19:18:44+02:00 Remove "chromium" snap 208 Done2024-04-16T19:18:46+02:00 2024-04-16T19:19:47+02:00 Install "chromium" snap 209 Done2024-04-17T10:31:58+02:00 2024-04-17T10:32:02+02:00 Connect chromium:password-manager-service to snapd:password-manager-service SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062178] Re: Disable location services in gnome-control-center
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- 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/2062178 Title: Disable location services in gnome-control-center Status in gnome-control-center: New Status in Release Notes for Ubuntu: New Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center package in Debian: Unknown Bug description: Impact -- Mozilla Location Services will be closed to all third parties (including Ubuntu, GNOME, KDE, etc.) on June 12, 2024. Unfortunately, there does not appear to be any suitable replacement for our typical desktop and laptop users. (Mobile devices like phones may have GPS that could be used but those devices would only rarely be using Ubuntu and gnome-control-center.) To avoid later UI changes and disruption only a few months from now, the Ubuntu Desktop team would prefer to disable location services before Ubuntu 24.04 LTS is released. Details --- Specifically, this hides - Privacy & Security > Location - Date & Time > Automatic Timezone - Displays > Night Light > Schedule > Sunrise to Sunset + This last one wasn't done yet, but I expect it for gnome-control-center 46.1 which will be an SRU https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3014 Other Info -- https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2959 gnome-control-center 46.1 to be released in a few days will also disable Location Services by default but with a build-time option for distros who have different deadlines and user profiles. If an alternative location provider is found that works well enough for our users, we intend to re-enable this feature with a Stable Release Update if possible. Because of this issue, Ubuntu has disabled the Location page in gnome- initial-setup for 24.04 LTS already. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2062178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
** Changed in: firefox (Ubuntu Noble) Milestone: ubuntu-24.04-beta => ubuntu-24.04 ** Changed in: firefox (Ubuntu Noble) Milestone: ubuntu-24.04 => noble-updates -- 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/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Noble: Confirmed Status in snapd source package in Noble: Confirmed Bug description: When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade fails consistently at the `Installing the firefox snap` step. This was first detected on Jenkins [1], then reproduced locally with `auto-upgrade-testing`, then finally by manually running a `do- release-upgrade -d` in a VM. [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade- list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull (Jenkins full log attached) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.17 ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri Nov 17 18:24:22 2023 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
This ended up causing my release upgrade to go burst into flames. That's documented in https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/2061923 . -- 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/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 Status in thunderbird package in Ubuntu: New Bug description: This happened during an upgrade from Mantic to Noble. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 16 13:15:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-10 (2076 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SnapChanges: IDStatus Spawn Ready Summary 3563 Error 2024-04-16T13:15:26-07:00 2024-04-16T13:15:42-07:00 Install "thunderbird" snap 3564 Done2024-04-16T13:22:00-07:00 2024-04-16T13:22:09-07:00 Install "thunderbird" snap SourcePackage: thunderbird Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061918] [NEW] package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
Public bug reported: This happened during an upgrade from Mantic to Noble. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 16 13:15:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-10 (2076 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SnapChanges: IDStatus Spawn Ready Summary 3563 Error 2024-04-16T13:15:26-07:00 2024-04-16T13:15:42-07:00 Install "thunderbird" snap 3564 Done2024-04-16T13:22:00-07:00 2024-04-16T13:22:09-07:00 Install "thunderbird" snap SourcePackage: thunderbird Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cuqa-manual-testing need-duplicate-check noble ** Tags added: cuqa-manual-testing -- 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/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 Status in thunderbird package in Ubuntu: New Bug description: This happened during an upgrade from Mantic to Noble. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 16 13:15:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-10 (2076 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SnapChanges: IDStatus Spawn Ready Summary 3563 Error 2024-04-16T13:15:26-07:00 2024-04-16T13:15:42-07:00 Install "thunderbird" snap 3564 Done2024-04-16T13:22:00-07:00 2024-04-16T13:22:09-07:00 Install "thunderbird" snap SourcePackage: thunderbird Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
