[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062564] Re: [FFe] Seed pemmican
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/463674 -- 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/2062564 Title: [FFe] Seed pemmican Status in pemmican package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] Add pemmican to raspi server and desktop images in order that Pi 5 users can be notified if/when overcurrent or undervolt events occur (potentially resulting in brownout, data-corruption, and all manner of other symptoms typically caused as a result of undervolt). [ Test Plan ] On all supported models of Pi: * Boot the image with pemmican installed * Ensure boot proceeds normally with package installed and that no warnings appear On the Pi 5 specifically: * Boot the image normally * Ensure boot proceeds normally with package installed and that no warnings appear * Using bench power-supply to back-feed the Pi, lower voltage until brownout occurs * Reboot and ensure undervolt warning is shown * Shutdown and boot with PSU that cannot negotiate 5A * Ensure deficient PSU warning is shown On the Pi 5 desktop image specifically: * Boot desktop image * Attach USB load tester and raise current draw until USB ports fail * Ensure overcurrent warning is displayed [ Regression Potential ] Quite low given all the tests noted above have already been performed on all supported models. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2062564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Sorry, I should give a bit more context on this issue to clarify things. The test for this issue comes from the ISO tests for the Ubuntu Desktop for Raspberry Pi images. The test intends to check whether a fresh install can play a video "out of the box". The video used in the test is https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 which is downloaded and opened normally. The video deliberately uses a codec that isn't seeded and installed by default (but is a commonly used format) in the expectation that totem will guide the user through installing the necessary bits (which it used to back in groovy, but doesn't since -- incidentally the reason this wasn't noticed in jammy is because it failed to even open the video at that point, but that's now been fixed). Seeding gstreamer1.0-packagekit is probably fine (the whole of gstreamer's in main). Seeding gnome-software is likely not (given we're using snap-store for software delivery currently). Is app-center intended to fill that gap in future? -- 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: Invalid 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:
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Failed to reproduce on noble beta images; marking invalid as that's two failures now. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Invalid Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Summary changed: - No login sound on Ubuntu desktop + No welcome/login sound on Ubuntu desktop -- 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: New 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 2060679] Re: No icons for gtk4 applications under noble
Setting to "high" because this affects the usability of several seeded, and quite basic applications (settings and the file manager to name but two). ** Changed in: gtk4 (Ubuntu) Status: New => Confirmed ** Changed in: gtk4 (Ubuntu) Importance: Undecided => High ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2060679 Title: No icons for gtk4 applications under noble Status in gtk4 package in Ubuntu: Confirmed Bug description: While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I noticed that all GTK4 applications appear to be missing various icons. All lack the minimize / maximize / close icons (which are left as three empty circles on the window), and others lack icons within the windows, e.g. on various controls like radio buttons, or folder icons in nautilus. GTK3 applications appear unaffected. I'll attach some screenshots demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Adding affects packagekit as I've no idea if this is totem's fault or packagekit's. ** Also affects: packagekit (Ubuntu) Importance: Undecided Status: New -- 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 packagekit package in Ubuntu: New Status in totem package in Ubuntu: New 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/ubuntu/+source/packagekit/+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 1993347] Re: Wrong audio output selected by default on Pi 4
And is occurring on the noble images again... ** Changed in: pipewire (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993347 Title: Wrong audio output selected by default on Pi 4 Status in PipeWire: New Status in pipewire package in Ubuntu: Confirmed Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 4, the new pipewire stack selects the "Analogue Output - Built-in Audio" by default when the system is first installed, when the HDMI output probably ought to be selected by default (the analogue output is notably lower quality due to the low resolution DAC used, and tends to only be used when there is no alternative, e.g. on DPI/DSI displays with no audio channel). This is a low priority since the default is easily changed in the gnome control center, and the new selection persists across boots (in contrast to the same issue in the older pulseaudio stack; LP: #1877194). However, it is a minor annoyance that a non-technical user may struggle to figure out initially (it also means the first-time setup sound isn't audible on first boot). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] totem cannot install codecs via packagekit
Public bug reported: 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. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- 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 totem package in Ubuntu: New 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:
[Desktop-packages] [Bug 2037015] Re: Screen corruption of slides during install on Raspberry Pi 4
There's an intriguingly different style of corruption in the noble images on the Pi 5. It's still just on the installer's slides, but it's more ... "chunky"? I'll attach a photo... ** Attachment added: "slide-corruption-2.jpg" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2037015/+attachment/5762908/+files/slide-corruption-2.jpg -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi 4 Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] No login sound on Ubuntu desktop
Public bug reported: 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). ** Affects: libcanberra (Ubuntu) Importance: Undecided Status: New -- 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 login sound on Ubuntu desktop Status in libcanberra package in Ubuntu: New 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 2060679] Re: No icons for gtk4 applications under noble
Screenshot of the greeter showing lack of icons on radio buttons for selecting Ubuntu Pro ** Attachment added: "greeter1.png" https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+attachment/5762735/+files/greeter1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2060679 Title: No icons for gtk4 applications under noble Status in gtk4 package in Ubuntu: New Bug description: While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I noticed that all GTK4 applications appear to be missing various icons. All lack the minimize / maximize / close icons (which are left as three empty circles on the window), and others lack icons within the windows, e.g. on various controls like radio buttons, or folder icons in nautilus. GTK3 applications appear unaffected. I'll attach some screenshots demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060679] Re: No icons for gtk4 applications under noble
Screenshot of gnome-control-center showing lack of icons on left menu, and title bar ** Attachment added: "gnome-control-center1.png" https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+attachment/5762732/+files/gnome-control-center1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2060679 Title: No icons for gtk4 applications under noble Status in gtk4 package in Ubuntu: New Bug description: While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I noticed that all GTK4 applications appear to be missing various icons. All lack the minimize / maximize / close icons (which are left as three empty circles on the window), and others lack icons within the windows, e.g. on various controls like radio buttons, or folder icons in nautilus. GTK3 applications appear unaffected. I'll attach some screenshots demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060679] Re: No icons for gtk4 applications under noble
Screenshot of gnome maps showing lack of controls in router planner and title bar ** Attachment added: "gnome-maps1.png" https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+attachment/5762734/+files/gnome-maps1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2060679 Title: No icons for gtk4 applications under noble Status in gtk4 package in Ubuntu: New Bug description: While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I noticed that all GTK4 applications appear to be missing various icons. All lack the minimize / maximize / close icons (which are left as three empty circles on the window), and others lack icons within the windows, e.g. on various controls like radio buttons, or folder icons in nautilus. GTK3 applications appear unaffected. I'll attach some screenshots demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060679] Re: No icons for gtk4 applications under noble
Screenshot of nautilus showing lack of icons on left bar and title bar ** Attachment added: "nautilus1.png" https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+attachment/5762733/+files/nautilus1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2060679 Title: No icons for gtk4 applications under noble Status in gtk4 package in Ubuntu: New Bug description: While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I noticed that all GTK4 applications appear to be missing various icons. All lack the minimize / maximize / close icons (which are left as three empty circles on the window), and others lack icons within the windows, e.g. on various controls like radio buttons, or folder icons in nautilus. GTK3 applications appear unaffected. I'll attach some screenshots demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060679] [NEW] No icons for gtk4 applications under noble
Public bug reported: While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I noticed that all GTK4 applications appear to be missing various icons. All lack the minimize / maximize / close icons (which are left as three empty circles on the window), and others lack icons within the windows, e.g. on various controls like radio buttons, or folder icons in nautilus. GTK3 applications appear unaffected. I'll attach some screenshots demonstrating the issue. ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2060679 Title: No icons for gtk4 applications under noble Status in gtk4 package in Ubuntu: New Bug description: While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I noticed that all GTK4 applications appear to be missing various icons. All lack the minimize / maximize / close icons (which are left as three empty circles on the window), and others lack icons within the windows, e.g. on various controls like radio buttons, or folder icons in nautilus. GTK3 applications appear unaffected. I'll attach some screenshots demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems
I'll have a look at this next week; there's a bunch of things I need to shove in ubuntu-raspi-settings anyway this cycle and something like this is already present in there but I'll see if it needs enhancing (it won't be able to rely on raspi-config though, so I'll have to change those bits out). -- 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/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in SDDM: New Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-raspi-settings package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/sddm/+bug/2044718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Failed to reproduce this on the jammy .4 images during ISO testing. Possibility it's either fixed or only occurs on later versions. Will attempt to reproduce on mantic later, if I've got the time. -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions
This may be a duplicate of LP: #2037015 -- we saw this on mantic first, then noble, in the oem-config process (the first-time setup wizard). Previously it *didn't* affect jammy, but I'm currently running through the ISO tests for the jammy .4 release and it's cropped up there now as well. -- 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/2054517 Title: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming it doesn't crash first. You first see the corruption in the initial setup wizard on first boot of noble-preinstalled-desktop-arm64+raspi.img.xz but the same corruption is then visible in the Help app on Xorg. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.43.3-1 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu7 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Feb 21 14:38:56 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
Tested on mantic install, and as Robie suggested, performed binary debdiff against old versions to ensure only change was the version number. Marking verification done. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Mantic: Fix Committed Bug description: [SRU Justification] In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). [Test case] No testing is planned beyond any autopkgtests which may be none (the package itself doesn't have any). This should not be released to -updates on its own, but should be staged in -proposed so any future SRUs needed don't fail to copy due to out-of-date packages. [Where problems may occur] It is unlikely but possible that the removal of the raspi binary package from this source package will have inadvertently modified the contents of the other remaining binary packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044382] Re: Quassel opens "another" icon under Gnome
This seems to be something to do with the version of the dash under mantic, and with the fact it's running under Wayland specifically. A similar issue came up on the Pi forums, and included an excellent minimal reproduction case (which I'll include here for simplicity). Notably, the issue does *not* occur (with either this reproduction case, or with quassel) under Xorg, only under a Wayland session: ~/.local/bin/stopwatch: #!/bin/bash echo "STOP" echo "Watch" read ~/.local/share/applications/stopwatch.desktop: [Desktop Entry] Version=1.0 Type=Application Terminal=false Icon=StopWatch Name=StopWatch Exec=gnome-terminal --class=StopWatchTerminal -- /home/ubuntu/.local/bin/stopwatch StartupWMClass=StopWatchTerminal Adjust the /home/ubuntu/ path as necessary. Pin the "StopWatch" application to the dash and launch it; under Xorg a dot appears next to the pinned application. Under Wayland, an additional "gnome-terminal- server" icon appears on the dash. -- 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/2044382 Title: Quassel opens "another" icon under Gnome Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in quassel package in Ubuntu: New Bug description: I'm unsure if this is a bug in quassel, or in the gnome dock itself. Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the left bar results in the pinned icon appearing "idle" (not running), and a second icon appearing below those that are pinned which apparently represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), hence why I'm unsure this is an issue in quassel or in the gnome dock. I'll attach a screenshot demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044382] Re: Quassel opens "another" icon under Gnome
Oh, and the issue on the Pi forums is here: https://forums.raspberrypi.com/viewtopic.php?p=2167317 -- 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/2044382 Title: Quassel opens "another" icon under Gnome Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in quassel package in Ubuntu: New Bug description: I'm unsure if this is a bug in quassel, or in the gnome dock itself. Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the left bar results in the pinned icon appearing "idle" (not running), and a second icon appearing below those that are pinned which apparently represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), hence why I'm unsure this is an issue in quassel or in the gnome dock. I'll attach a screenshot demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044382] Re: Quassel opens "another" icon under Gnome
Hmm, it certainly sounds similar in some aspects: if I click on the pinned icon for Quassel after it's already launched, it does launch another instance. However, I'm not using multiple monitors, or multiple workspaces, and currently it only occurs with Quassel. Firefox and terminal are unaffected. -- 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/2044382 Title: Quassel opens "another" icon under Gnome Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in quassel package in Ubuntu: New Bug description: I'm unsure if this is a bug in quassel, or in the gnome dock itself. Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the left bar results in the pinned icon appearing "idle" (not running), and a second icon appearing below those that are pinned which apparently represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), hence why I'm unsure this is an issue in quassel or in the gnome dock. I'll attach a screenshot demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044382] [NEW] Quassel opens "another" icon under Gnome
Public bug reported: I'm unsure if this is a bug in quassel, or in the gnome dock itself. Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the left bar results in the pinned icon appearing "idle" (not running), and a second icon appearing below those that are pinned which apparently represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), hence why I'm unsure this is an issue in quassel or in the gnome dock. I'll attach a screenshot demonstrating the issue. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Affects: quassel (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-11-23 13-42-51.png" https://bugs.launchpad.net/bugs/2044382/+attachment/5722734/+files/Screenshot%20from%202023-11-23%2013-42-51.png ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Description changed: - I'm unsure if this is a bug in quassel, or in gnome itself. Under Ubuntu - 23.10 (mantic), running Quassel from a pinned icon on the left bar - results in the pinned icon appearing "idle" (not running), and a second - icon appearing below those that are pinned which apparently represents - the running quassel instance. + I'm unsure if this is a bug in quassel, or in the gnome dock itself. + Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the + left bar results in the pinned icon appearing "idle" (not running), and + a second icon appearing below those that are pinned which apparently + represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), - hence why I'm unsure this is an issue in quassel or in gnome. I'll - attach a screenshot demonstrating the issue. + hence why I'm unsure this is an issue in quassel or in the gnome dock. + I'll attach a screenshot demonstrating the issue. -- 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/2044382 Title: Quassel opens "another" icon under Gnome Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in quassel package in Ubuntu: New Bug description: I'm unsure if this is a bug in quassel, or in the gnome dock itself. Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the left bar results in the pinned icon appearing "idle" (not running), and a second icon appearing below those that are pinned which apparently represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), hence why I'm unsure this is an issue in quassel or in the gnome dock. I'll attach a screenshot demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Thanks @eythian -- I'll take that as confirmation and mark this Fix Released ** Changed in: snapd (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: snapd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Fix Released Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Setting network-manager back to confirmed as I think the case is made that this is an issue, despite upstream having reservations about whether network-manager is quite the right place for this particular setting. Also setting netplan.io in jammy to fix released as 0.105 was back-ported there quite a while ago now and the current (22.04.3) image should support setting this at first-boot. Setting kinetic to won't fix (as it's EOL). ** Changed in: network-manager (Ubuntu Kinetic) Status: Incomplete => Won't Fix ** Changed in: network-manager (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: network-manager (Ubuntu) Status: Incomplete => Confirmed ** Changed in: netplan.io (Ubuntu Jammy) Status: Triaged => Fix Released ** Changed in: netplan Assignee: Lukas Märdian (slyon) => (unassigned) ** Also affects: network-manager (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Noble) Importance: Low Status: Confirmed ** Also affects: netplan.io (Ubuntu Noble) Importance: Medium Status: Fix Released ** Also affects: network-manager (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu Lunar) Status: New => Fix Released ** Changed in: netplan.io (Ubuntu Mantic) Status: New => Fix Released ** Changed in: network-manager (Ubuntu Lunar) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu Lunar) Status: New => Confirmed ** Changed in: network-manager (Ubuntu Mantic) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu Mantic) Status: New => Confirmed -- 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: Confirmed Status in netplan.io source package in Mantic: Fix Released Status in network-manager source package in Mantic: Confirmed 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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
This would appear to be fixed on my jammy system. Any objections to marking this fix released? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) Status in libreoffice package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Committed Status in libreoffice source package in Jammy: Fix Released Status in snapd source package in Jammy: Confirmed Bug description: Ubuntu jammy live QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Opened LibreOffice Writer as random apps in QA-test. Hit F1 to call help, and all I get is an error URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html --- File not found Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- Firefox opens as a snap; but it isn't accessing the data from LibreOffice. Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks- libreoffice-deb/27537 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 17 04:46:33 2021 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
This has been fixed for a couple of releases now (since lunar I believe), and if I recall correctly the issue was indeed the wpe backend mentioned in comment 17. That would suggest this should be "invalid" for gtk and yelp, and "fix released" for webkit2gtk. -- 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/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Incomplete Status in webkit2gtk package in Ubuntu: Incomplete Status in yelp package in Ubuntu: Incomplete Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
This appears to be partially fixed under Ubuntu 23.10. While the application (when running) still eats a few hundred meg of RAM, it does release that when closed, as opposed to hanging around persistently. Given apt usually eats over a hundred meg when processing the archive index, it's probably reasonable for a a graphical application processing a similar archive and including all the icons and pretty graphics to gobble a few hundred meg. However, it should definitely relinquish that memory when not in operation, which now appears to be the case. In other words, my major objection (that it grabbed this RAM even when not in use), appears to be addressed. However, that's not the subject line of the bug; should this be closed / revised? Are others still encountering issues with the store on mantic? -- 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/1879137 Title: The snap-store is using hundreds of MiBs of RAM. Status in GNOME Software: New Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: The snap-store process is intermittently using hundreds of megabytes of RAM. Is this normal? Is there a solution? Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
** Changed in: pulseaudio (Ubuntu) Assignee: Dave Jones (waveform) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Invalid Status in pulseaudio source package in Jammy: Confirmed Status in ubuntu-settings source package in Jammy: Invalid Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: Invalid Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838963] Re: Firefox window initially appears black when launching on Wayland
I haven't seen this issue for quite a while at this point (a year+ I think?). Is this still occurring for anyone, or can we close this? -- 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/1838963 Title: Firefox window initially appears black when launching on Wayland Status in firefox package in Ubuntu: Confirmed Bug description: Details here: https://photos.app.goo.gl/2CjpJGB1wEWU8qJw6 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 13:24:46 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/455407 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Mantic: New Bug description: In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
Thanks for the quick review! Could someone set up a "mantic" branch on the lp:~ubuntu-desktop/ubuntu/+source/ubuntu-settings repository so I can propose a merge to fix mantic too? (basically the same commit with a lower version number) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Mantic: New Bug description: In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/455178 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Mantic: New Bug description: In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Is this fixed in noble now? No. Is this due to be fixed; I've not heard anything, but happy to be corrected if this is on a roadmap somewhere? -- 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: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete 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 2007160] Re: Image properties does nothing in lunar
This looks to be working under mantic now; image properties pane appears with resolution and (if present) EXIF details. -- 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/2007160 Title: Image properties does nothing in lunar Status in nautilus package in Ubuntu: Incomplete Bug description: When testing the current lunar (23.04) pre-installed desktop image for the Raspberry Pi, I attempted to retrieve the properties of a captured JPEG from nautilus: * Right click on a JPEG image * Select "Properties" item at the bottom * Click on the "Image Properties" link at the bottom of the dialog that opens However, nothing happens when clicking on the link. I presume this is meant to go to a page listing the details that nautilus used to display (resolution, etc). I tested with a couple of different JPEGs that display their properties correctly under jammy and kinetic. I'm happy to provide test images if required, but I don't think it's specific to the JPEGs I'm using. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2007160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- 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/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: Fix Released Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy
Figured out a work-around: ensure the matching state of the rename rule matches the end-state of the rename rule so the networkd state machine stops flopping between the two rules. Linked the MP with the required change; will tag ubuntu-release to see if it's not too late for a re- spin. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/453340 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy
There does seem to be something unusual going on with the lan78xx re- initializing (or restarting?) part way through the boot sequence, causing another round of renaming to kick off (and then everything fails). Bizarre. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Argh! During ISO testing I thought I'd just quickly check this still didn't occur on a Pi 5... only to find it did, this time. I've still not encountered a Pi 4 where it *didn't* occur, but I wonder if this is a race-condition somewhere and just more prone to occurring on the slower 4. -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Oh, one other note: no output in the journal during the hang; I'm afraid the only info is from the backtrace. -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy
** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy
** Attachment added: "kern.log from unaffected 2B (rev 1.2)" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708342/+files/unaffected.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy
** Attachment added: "kern.log from affected 3B+" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708341/+files/affected.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038964] [NEW] raspi ethernet rename is racy
Public bug reported: The renaming of the ethernet interface (controlled by 10-raspi-eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: raspi-image ** Tags added: raspi-image -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
Added text to the release notes [1] detailing Pi 5 support, including the planned SRU of libcamera support. Can others double-check the raspberry pi sections look reasonable, and let me know if we want to mention anything else specific? I've also updated the "known issues" section, removing a couple of bits (totem now works and the audio output selection is now sane out of the box), and adding others (slide corruption on the pi4 during installation). Again, if there's anything missing that should be mentioned please either let me know or feel free to add it yourself! [1]: https://discourse.ubuntu.com/t/mantic-minotaur-release-notes/35534 ** Changed in: ubuntu-release-notes Status: New => In Progress -- 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/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: In Progress Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Additional observation: I re-tested this on the Pi 4 and 5. The hang only occurs on the Pi 4 and 400, but does *not* occur on the 5 -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037017] Re: Sharing tab hangs gnome-control-center
Attaching backtrace from gdb with debug symbols ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+attachment/5708243/+files/gdb.txt ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993316] Re: Non-existent audio output selected on Pi 400
No longer occurs on the Mantic final images; HDMI is selected by default. Marking fix released. ** Changed in: pipewire (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993316 Title: Non-existent audio output selected on Pi 400 Status in PipeWire: New Status in pipewire package in Ubuntu: Fix Released Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 400 (the keyboard-based model), the new pipewire stack selects a non-existent audio output by default. Specifically, the output device listed in the gnome control center is "Analogue Output - Built-in Audio". On the Raspberry Pi 4 this refers to the auxiliary output (the 3.5mm headphone jack on the board), however the Pi 400 has no such output. Under the older pulseaudio stack, this was correct (no analogue output was listed) and the HDMI output was correctly selected on the Pi 400 (though, notably, the older stack got the default output wrong on the Pi 4; see LP: #1877194). This is a low priority since the default selection is easily changed from the gnome control center, and the new selection persists across boots (in contrast to the aforementioned pulseaudio bug). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993347] Re: Wrong audio output selected by default on Pi 4
No longer occurs on the Mantic final images; HDMI is selected by default, with analog output still available as a secondary option. Marking fix released. ** Changed in: pipewire (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993347 Title: Wrong audio output selected by default on Pi 4 Status in PipeWire: New Status in pipewire package in Ubuntu: Fix Released Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 4, the new pipewire stack selects the "Analogue Output - Built-in Audio" by default when the system is first installed, when the HDMI output probably ought to be selected by default (the analogue output is notably lower quality due to the low resolution DAC used, and tends to only be used when there is no alternative, e.g. on DPI/DSI displays with no audio channel). This is a low priority since the default is easily changed in the gnome control center, and the new selection persists across boots (in contrast to the same issue in the older pulseaudio stack; LP: #1877194). However, it is a minor annoyance that a non-technical user may struggle to figure out initially (it also means the first-time setup sound isn't audible on first boot). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998782] Re: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support"
With the correct video codecs installed (for the particular test video I was using, I needed gstreamer1.0-plugins-bad which pulls in libav), this now works on the mantic final images, under both the Pi 4 and 5. ** Changed in: totem (Ubuntu) Status: Confirmed => Fix Released -- 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/1998782 Title: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support" Status in totem package in Ubuntu: Fix Released Bug description: Testing Ubuntu Lunar Daily RaspPI 4 image dated 2022-12-05 I received this error trying to play the video "big_buck_bunny" in Totem as per the testcase: This maybe a duplicate of the old bug 1969512 but as the error message is not the same a new bug is filed. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1004.10-raspi 5.19.7 Uname: Linux 5.19.0-1004-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 5 11:24:38 2022 ImageMediaBuild: 20221205 LogAlsaMixer: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -1988 [78%] [-19.88dB] [on] SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1998782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037019] Re: Full-screen youtube hangs desktop
Also fixed in the currently daily, on both Pi 4 and 5. The recent of release of mutter is likely to have been the fix in this case (according to @vanvugt). ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- 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/2037019 Title: Full-screen youtube hangs desktop Status in firefox package in Ubuntu: Fix Released Bug description: On the current Mantic beta images of Ubuntu Desktop for Raspberry Pi, running on a Raspberry Pi 4B (either 4GB or 8GB), while attempting to play a YouTube video (as part of the ISO test procedure), attempting to switch the video to full-screen resulted in a hang of the desktop. More precisely, I could still pause and resume the video with the spacebar (audio could be heard stopping or playing accordingly) but the display was frozen entirely, including the mouse pointer and I was unable to recover the desktop (attempting to switch to another virtual console with Ctrl+ a function key was unsuccessful, attempting keyboard shortcuts to shut down firefox, etc). At the point that the desktop freezes the following messages appeared in journalctl (obtained over SSH): Sep 21 22:05:52 miss-piggy kernel: vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 2104 (slots) Sep 21 22:05:52 miss-piggy kernel: vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 2040 (slots) The system is still responsive inasmuch as I can connect via SSH and kill the firefox process, but the desktop remains inaccessible. So far the only thing I've found that can bring it back is restarted the gdm service (effectively killing the running desktop) over SSH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1923363 Title: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules Status in cloud-init package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: Confirmed Status in user-setup package in Ubuntu: Invalid Status in cloud-init source package in Impish: Won't Fix Status in ubiquity source package in Impish: Invalid Status in ubuntu-settings source package in Impish: Won't Fix Status in user-setup source package in Impish: Invalid Status in cloud-init source package in Jammy: Confirmed Status in ubiquity source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: Confirmed Status in user-setup source package in Jammy: Invalid Status in cloud-init source package in Kinetic: Won't Fix Status in ubiquity source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: Won't Fix Status in user-setup source package in Kinetic: Invalid Status in cloud-init source package in Lunar: Won't Fix Status in ubiquity source package in Lunar: Invalid Status in ubuntu-settings source package in Lunar: Won't Fix Status in user-setup source package in Lunar: Invalid Status in cloud-init source package in Mantic: Fix Released Status in ubiquity source package in Mantic: Invalid Status in ubuntu-settings source package in Mantic: Confirmed Status in user-setup source package in Mantic: Invalid Bug description: We're attempting to make the GPIO system on the Raspberry Pi images work "out of the box" on the new image. By default, GPIO kernel devices are made available to members of the "dialout" group which the initial user is added to by default on our server images. However, we've noticed that this isn't the case on the desktop images. The regression potential is minimal; the group already exists and we're simply adding the freshly created user to a new group and not removing any existing memberships. The group in question ("dialout") is also rarely used these days except for providing access to serial consoles, and as mentioned above is already a default membership on the server images. The change has been tested on the desktop image successfully. A test build of the updated image will be made under https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll attach a debdiff shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Changed in: rpi-eeprom (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
The rpiboot package can be skipped for now; according to upstream the updated package won't be ready at release. The separate bug LP: #2032178 will track updates if/when I can get the uploaded. ** No longer affects: rpiboot (Ubuntu) -- 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/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037019] [NEW] Full-screen youtube hangs desktop
Public bug reported: On the current Mantic beta images of Ubuntu Desktop for Raspberry Pi, running on a Raspberry Pi 4B (either 4GB or 8GB), while attempting to play a YouTube video (as part of the ISO test procedure), attempting to switch the video to full-screen resulted in a hang of the desktop. More precisely, I could still pause and resume the video with the spacebar (audio could be heard stopping or playing accordingly) but the display was frozen entirely, including the mouse pointer and I was unable to recover the desktop (attempting to switch to another virtual console with Ctrl+ a function key was unsuccessful, attempting keyboard shortcuts to shut down firefox, etc). At the point that the desktop freezes the following messages appeared in journalctl (obtained over SSH): Sep 21 22:05:52 miss-piggy kernel: vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 2104 (slots) Sep 21 22:05:52 miss-piggy kernel: vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 2040 (slots) The system is still responsive inasmuch as I can connect via SSH and kill the firefox process, but the desktop remains inaccessible. So far the only thing I've found that can bring it back is restarted the gdm service (effectively killing the running desktop) over SSH. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: raspi-image rls-mm-incoming ** Tags added: raspi-image rls-mm-incoming -- 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/2037019 Title: Full-screen youtube hangs desktop Status in firefox package in Ubuntu: New Bug description: On the current Mantic beta images of Ubuntu Desktop for Raspberry Pi, running on a Raspberry Pi 4B (either 4GB or 8GB), while attempting to play a YouTube video (as part of the ISO test procedure), attempting to switch the video to full-screen resulted in a hang of the desktop. More precisely, I could still pause and resume the video with the spacebar (audio could be heard stopping or playing accordingly) but the display was frozen entirely, including the mouse pointer and I was unable to recover the desktop (attempting to switch to another virtual console with Ctrl+ a function key was unsuccessful, attempting keyboard shortcuts to shut down firefox, etc). At the point that the desktop freezes the following messages appeared in journalctl (obtained over SSH): Sep 21 22:05:52 miss-piggy kernel: vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 2104 (slots) Sep 21 22:05:52 miss-piggy kernel: vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 2040 (slots) The system is still responsive inasmuch as I can connect via SSH and kill the firefox process, but the desktop remains inaccessible. So far the only thing I've found that can bring it back is restarted the gdm service (effectively killing the running desktop) over SSH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037017] [NEW] Sharing tab hangs gnome-control-center
Public bug reported: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: raspi-image rls-mm-incoming ** Tags added: raspi-image rls-mm-incoming -- 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/2037017 Title: Sharing tab hangs gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037016] [NEW] Firefox redundantly appears twice in Default Apps
Public bug reported: Under the current Mantic beta, Firefox redundantly appears twice in the Web and Photos drop-downs under the "Default Apps" tab of gnome-control- center. ** Affects: gnome-control-center (Ubuntu) Importance: Low Status: New ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/2037016 Title: Firefox redundantly appears twice in Default Apps Status in gnome-control-center package in Ubuntu: New Bug description: Under the current Mantic beta, Firefox redundantly appears twice in the Web and Photos drop-downs under the "Default Apps" tab of gnome- control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026637] Re: [mantic] many useful apps are marked for auto removal
** Tags removed: rls-mm-incoming ** Tags added: foundations-todo -- 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/2026637 Title: [mantic] many useful apps are marked for auto removal Status in ubuntu-meta package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Today update want remove a lot of apps. This happens on two systems installed from ISO dated 2023-06-07 and 2023-05-21 corrado@corrado-n03-mm-0607:~$ sudo apt update && sudo apt upgrade [sudo] password for corrado: Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:4 http://archive.ubuntu.com/ubuntu mantic-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: aisleriot baobab branding-ubuntu cheese cheese-common file-roller gir1.2-rb-3.0 gnome-mahjongg gnome-mines gnome-sudoku gnome-video-effects gstreamer1.0-clutter-3.0 guile-3.0-libs libavahi-ui-gtk3-0 libcairomm-1.16-1 libcdr-0.1-1 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libcheese-gtk25 libcheese8 libclutter-gst-3.0-0 libdmapsharing-4.0-3 libevent-2.1-7 libfreehand-0.1-1 libfreerdp-client2-2 libglibmm-2.68-1 libgnome-games-support-1-3 libgnome-games-support-common libgpod-common libgpod4 libgtkmm-4.0-0 libgupnp-igd-1.0-4 libixml10 liblc3-0 libminiupnpc17 libmspub-0.1-1 libmujs2 libnatpmp1 libpagemaker-0.0-0 libpangomm-2.48-1 libqqwing2v5 libreoffice-calc libreoffice-draw libreoffice-gnome libreoffice-gtk3 libreoffice-impress librhythmbox-core10 libsdl-image1.2 libsdl1.2debian libsgutils2-1.46-2 libsigc++-3.0-0 libupnp13 libvisio-0.1-1 lp-solve media-player-info python3-mako python3-renderpm python3-reportlab-accel remmina remmina-common remmina-plugin-rdp remmina-plugin-secret remmina-plugin-vnc rhythmbox rhythmbox-data rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell shotwell-common simple-scan transmission-common transmission-gtk Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. corrado@corrado-n03-mm-0607: ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop 1.505 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 9 08:53:45 2023 InstallationDate: Installed on 2023-06-07 (31 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230607) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2026637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028054] Re: [MIR] python-rlpycairo
** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: New Status in python-reportlab package in Ubuntu: New Status in python-rlpycairo package in Ubuntu: Won't Fix Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules
** Changed in: ubuntu-settings (Ubuntu Mantic) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1923363 Title: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules Status in cloud-init package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: Confirmed Status in user-setup package in Ubuntu: Invalid Status in cloud-init source package in Impish: Won't Fix Status in ubiquity source package in Impish: Invalid Status in ubuntu-settings source package in Impish: Won't Fix Status in user-setup source package in Impish: Invalid Status in cloud-init source package in Jammy: Confirmed Status in ubiquity source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: Confirmed Status in user-setup source package in Jammy: Invalid Status in cloud-init source package in Kinetic: Won't Fix Status in ubiquity source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: Won't Fix Status in user-setup source package in Kinetic: Invalid Status in cloud-init source package in Lunar: Won't Fix Status in ubiquity source package in Lunar: Invalid Status in ubuntu-settings source package in Lunar: Won't Fix Status in user-setup source package in Lunar: Invalid Status in cloud-init source package in Mantic: Confirmed Status in ubiquity source package in Mantic: Invalid Status in ubuntu-settings source package in Mantic: Confirmed Status in user-setup source package in Mantic: Invalid Bug description: We're attempting to make the GPIO system on the Raspberry Pi images work "out of the box" on the new image. By default, GPIO kernel devices are made available to members of the "dialout" group which the initial user is added to by default on our server images. However, we've noticed that this isn't the case on the desktop images. The regression potential is minimal; the group already exists and we're simply adding the freshly created user to a new group and not removing any existing memberships. The group in question ("dialout") is also rarely used these days except for providing access to serial consoles, and as mentioned above is already a default membership on the server images. The change has been tested on the desktop image successfully. A test build of the updated image will be made under https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll attach a debdiff shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules
Added PR for cloud-init to remove the default groups that were removed (ages ago) from the desktop image (excepting the lxd group which was added in a reasonably recent commit and so is presumably wanted): https://github.com/canonical/cloud-init/pull/4258 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1923363 Title: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules Status in cloud-init package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: Confirmed Status in user-setup package in Ubuntu: Invalid Status in cloud-init source package in Impish: Won't Fix Status in ubiquity source package in Impish: Invalid Status in ubuntu-settings source package in Impish: Won't Fix Status in user-setup source package in Impish: Invalid Status in cloud-init source package in Jammy: Confirmed Status in ubiquity source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: Confirmed Status in user-setup source package in Jammy: Invalid Status in cloud-init source package in Kinetic: Won't Fix Status in ubiquity source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: Won't Fix Status in user-setup source package in Kinetic: Invalid Status in cloud-init source package in Lunar: Won't Fix Status in ubiquity source package in Lunar: Invalid Status in ubuntu-settings source package in Lunar: Won't Fix Status in user-setup source package in Lunar: Invalid Status in cloud-init source package in Mantic: Confirmed Status in ubiquity source package in Mantic: Invalid Status in ubuntu-settings source package in Mantic: Confirmed Status in user-setup source package in Mantic: Invalid Bug description: We're attempting to make the GPIO system on the Raspberry Pi images work "out of the box" on the new image. By default, GPIO kernel devices are made available to members of the "dialout" group which the initial user is added to by default on our server images. However, we've noticed that this isn't the case on the desktop images. The regression potential is minimal; the group already exists and we're simply adding the freshly created user to a new group and not removing any existing memberships. The group in question ("dialout") is also rarely used these days except for providing access to serial consoles, and as mentioned above is already a default membership on the server images. The change has been tested on the desktop image successfully. A test build of the updated image will be made under https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll attach a debdiff shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923363] Re: Users are not added to various groups (dialout, video, etc.)
Per vorlon's comments on the merge request, I've closed the merge and will re-submit an alternative method using udev rules instead of group membership. Adding ubuntu-settings for the udev rules, and cloud-init as we presumably want to remove membership in those groups from server instances too. ** Tags added: foundations-todo ** Summary changed: - Users are not added to various groups (dialout, video, etc.) + Grant access to hardware (UARTs, I2C, etc.) via custom udev rules ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Impish) Status: New => Won't Fix ** Changed in: cloud-init (Ubuntu Jammy) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Kinetic) Status: New => Won't Fix ** Changed in: cloud-init (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: cloud-init (Ubuntu Mantic) Status: New => Confirmed ** Changed in: ubiquity (Ubuntu Impish) Status: Won't Fix => Invalid ** Changed in: ubiquity (Ubuntu Jammy) Status: Confirmed => Invalid ** Changed in: ubiquity (Ubuntu Kinetic) Status: Won't Fix => Invalid ** Changed in: ubiquity (Ubuntu Lunar) Status: Won't Fix => Invalid ** Changed in: ubiquity (Ubuntu Mantic) Status: Confirmed => Invalid ** Changed in: ubuntu-settings (Ubuntu Impish) Status: New => Won't Fix ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: New => Confirmed ** Changed in: ubuntu-settings (Ubuntu Kinetic) Status: New => Won't Fix ** Changed in: ubuntu-settings (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: ubuntu-settings (Ubuntu Mantic) Status: New => Confirmed ** Changed in: user-setup (Ubuntu Impish) Status: Won't Fix => Invalid ** Changed in: user-setup (Ubuntu Jammy) Status: Confirmed => Invalid ** Changed in: user-setup (Ubuntu Kinetic) Status: Won't Fix => Invalid ** Changed in: user-setup (Ubuntu Lunar) Status: Won't Fix => Invalid ** Changed in: user-setup (Ubuntu Mantic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1923363 Title: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules Status in cloud-init package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: Confirmed Status in user-setup package in Ubuntu: Invalid Status in cloud-init source package in Impish: Won't Fix Status in ubiquity source package in Impish: Invalid Status in ubuntu-settings source package in Impish: Won't Fix Status in user-setup source package in Impish: Invalid Status in cloud-init source package in Jammy: Confirmed Status in ubiquity source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: Confirmed Status in user-setup source package in Jammy: Invalid Status in cloud-init source package in Kinetic: Won't Fix Status in ubiquity source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: Won't Fix Status in user-setup source package in Kinetic: Invalid Status in cloud-init source package in Lunar: Won't Fix Status in ubiquity source package in Lunar: Invalid Status in ubuntu-settings source package in Lunar: Won't Fix Status in user-setup source package in Lunar: Invalid Status in cloud-init source package in Mantic: Confirmed Status in ubiquity source package in Mantic: Invalid Status in ubuntu-settings source package in Mantic: Confirmed Status in user-setup source package in Mantic: Invalid Bug description: We're attempting to make the GPIO system on the Raspberry Pi images work "out of the box" on the new image. By default, GPIO kernel devices are made available to members of the "dialout" group which the initial user is added to by default on our server images. However, we've noticed that this isn't the case on the desktop images. The regression potential is minimal; the group already exists and we're simply adding the freshly created user to a new group and not removing any existing memberships. The group in question ("dialout") is also rarely used these days except for providing access to serial consoles, and as mentioned above is already a default membership on the server images. The change has been tested on the desktop image successfully. A test build of the updated image will be made under https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll attach a debdiff shortly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2014954] Re: Backport Intel Mutual Authentications - FCC Lock
Unsubscribing ~ubuntu-sponsors; please re-subscribe once Paride's comments (from 21) are addressed. I'm not setting to incomplete as it appears a decision is pending regarding waiting for the 1.30 release and I'm not sure what the schedule on that is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/2014954 Title: Backport Intel Mutual Authentications - FCC Lock Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: In Progress Status in libmbim source package in Jammy: New Status in libmbim source package in Lunar: New Bug description: [ Impact ] There exist no formal API to do the FCC unlock procedure[1] in the latest version of the modemmanger. But there is a merged commit[2] that provide this functionality for intel WWAN cards in the upstream project. Lenovo have several laptops using the Fibocom WWAN cards (Intel XMM 7560), and Lenovo are struggling to give a decent way to run the FCC unlock service without this. Until the device is unlocked, the end users are not able to use the SIM cards, and some of the affected devices have already been shipped. The end users now have to go to the Lenovo support website and download a few scripts and binaries to unlock the device to make their SIM cards work. The Lenovo wants this patch to be included in jammy, then they can provide the FCC unlock service and manage it in OEM-archive, so the end users can use SIM cards as soon as they receive the laptop. [ Test Plan ] OEM enablement engineers and Lenovo engineers will help to test if the FCC unlock would work on certain laptops with the help of a custom package[1] provided by Lenovo which contains the FCC unlock script. [ Where problems could occur ] This is a completely new feature to support Intel WWAN cards mutal authentication, which does not affect other existing features. But the feature itself might have bugs and glitches since it is a brand new one and is not widely tested by the laptop vendors, still it is better than nothing. [ Other Info ] [1] FCC unlock procedure: https://modemmanager.org/docs/modemmanager/fcc-unlock/ [2] intel-mutual-authentication: new service, fcc-lock: https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157 - when the device is first shipped or comes out of the factory, it should be protected with a lock till the device reaches the end user. This FCC lock feature will ensure the device is secured till its unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2001904] Re: URLs fail to launch in Firefox
*** This bug is a duplicate of bug 1794064 *** https://bugs.launchpad.net/bugs/1794064 ** This bug has been marked a duplicate of bug 1794064 Clicking a hyperlink in a PDF fails to open it if the default browser is a snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2001904 Title: URLs fail to launch in Firefox Status in evince package in Ubuntu: New Bug description: Opening a PDF under evince, then clicking an https: link within the PDF fails to open the link in Firefox. On the command line, evince reports: $ evince test.pdf env: ‘/snap/bin/firefox’: Permission denied In dmesg, the following message appears each time the link is clicked: [ 1366.891145] audit: type=1400 audit(1672910889.559:286): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/snap" pid=14698 comm="env" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 This may be related to (or a regression of?) LP: #964510 as it's clearly aa related, but I don't think it's a direct duplicate given the audit log is rather different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed
Also verified on a Pi 4 (mutter 44.1-0ubuntu1); video playback is smooth again! -- 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/2017097 Title: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is being stressed in which case it becomes a smooth 60 FPS. Seems like a frequency scaling issue. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always [ Test Plan ] 1. Log into the default (Wayland) session on a Raspberry Pi 4/400. 2. Set the display resolution to 1920x1080 60Hz. 3. Drag a window around and ensure it appears smooth (60Hz). [ Where problems could occur ] Triple buffering affects all frame scheduling so any mistakes can cause high CPU usage, screen freezes and stutter. Try not to make mistakes. [ Original bug ] ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Apr 20 15:13:51 2023 ImageMediaBuild: 20230417 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles
** Tags removed: rls-mm-incoming ** Tags added: foundations-todo -- 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/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft package in Ubuntu: Won't Fix Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020110] Re: Migrate netplan settings to this package
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/443210 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020110] Re: Migrate netplan settings to this package
Test package building in ppa:waveform/ubuntu-settings for mantic (https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-settings) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020110] [NEW] Migrate netplan settings to this package
Public bug reported: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016285] Re: Redundant creation of oem user in rpi desktop images
Setting to critical as this currently prevents the creation of the ubuntu rpi desktop images. ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016285] Re: Redundant creation of oem user in rpi desktop images
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/441072 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016286] [NEW] growroot-almost service failure after upgrade
Public bug reported: Users upgrading Ubuntu desktop for Raspberry Pi from kinetic to lunar may notice that the new growroot-almost.service persistently fails as the root is already resized. The unit should be updated to fail silently and prevent future runs. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/441072 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016286 Title: growroot-almost service failure after upgrade Status in ubuntu-settings package in Ubuntu: New Bug description: Users upgrading Ubuntu desktop for Raspberry Pi from kinetic to lunar may notice that the new growroot-almost.service persistently fails as the root is already resized. The unit should be updated to fail silently and prevent future runs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2016286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016285] [NEW] Redundant creation of oem user in rpi desktop images
Public bug reported: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem- config-prepare is installed at the time that ubuntu-raspi-settings- desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Milestone: None => ubuntu-23.04 ** Changed in: ubuntu-settings (Ubuntu) Milestone: None => ubuntu-23.04 ** Merge proposal linked: https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/441071 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs
Fix-released in livecd-rootfs 2.818 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2004430 Title: Migrate raspberry pi image hacks from livecd-rootfs Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: There are currently several "hacks" in livecd-rootfs that introduce unpackaged files and/or services. In particular, everything in https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with the fstab and the swapfile needs to go. The new ubuntu-image based process for generating images won't be using these; anything to do with the fstab needs to go in the image-definition yaml, and the swapfile services ought to be owned by the ubuntu-raspi-settings- desktop package anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS
This was fixed-released in livecd-rootfs 2.818 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2013080 Title: On rpi desktop images, grow root leaving slack for LUKS Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: To aid in user-implemented FDE we wish to leave 16MB of the file- system unexpanded during first boot. The growth of the partition is unaffected, but rather than relying on systemd's growfs facility in fstab, we should use a service that runs a simple script to handle calculating the resize in early boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2013080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993347] Re: Wrong audio output selected by default on Pi 4
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3158 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3158 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3158 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993347 Title: Wrong audio output selected by default on Pi 4 Status in PipeWire: Unknown Status in pipewire package in Ubuntu: Confirmed Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 4, the new pipewire stack selects the "Analogue Output - Built-in Audio" by default when the system is first installed, when the HDMI output probably ought to be selected by default (the analogue output is notably lower quality due to the low resolution DAC used, and tends to only be used when there is no alternative, e.g. on DPI/DSI displays with no audio channel). This is a low priority since the default is easily changed in the gnome control center, and the new selection persists across boots (in contrast to the same issue in the older pulseaudio stack; LP: #1877194). However, it is a minor annoyance that a non-technical user may struggle to figure out initially (it also means the first-time setup sound isn't audible on first boot). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993316] Re: Non-existent audio output selected on Pi 400
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3158 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3158 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3158 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993316 Title: Non-existent audio output selected on Pi 400 Status in PipeWire: Unknown Status in pipewire package in Ubuntu: Confirmed Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 400 (the keyboard-based model), the new pipewire stack selects a non-existent audio output by default. Specifically, the output device listed in the gnome control center is "Analogue Output - Built-in Audio". On the Raspberry Pi 4 this refers to the auxiliary output (the 3.5mm headphone jack on the board), however the Pi 400 has no such output. Under the older pulseaudio stack, this was correct (no analogue output was listed) and the HDMI output was correctly selected on the Pi 400 (though, notably, the older stack got the default output wrong on the Pi 4; see LP: #1877194). This is a low priority since the default selection is easily changed from the gnome control center, and the new selection persists across boots (in contrast to the aforementioned pulseaudio bug). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
netplan added support for configuring the regulatory domain in kinetic and it works pretty nicely (it's one of the things I test before release). However, that's relying on cloud-init to inject the netplan configuration and that's only on the server images -- it's not a solution for the preinstalled desktop images. Having said that ... it might be if cloud-init gets included in the preinstalled desktop images, but that's not happening in lunar as it caused other issues. Still, even if it did that's still a rather command-line / text-configuration-file interface that's nowhere near as "good" as having it integrated into the first time GUI setup (as RaspiOS does). -- 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: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete 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 1951586] Re: Need option to specify wifi regulatory domain
Given there doesn't seem much interest in fixing this from the network manager angle (and there's even a question as to whether that's the right place to fix this), I'm going to take a leaf out of the RaspiOS book, and see if I can persuade someone that the installer is the right place to fix this (or more specifically, the new installer, subiquity). That's not going to do anything for lunar which won't be using subiquity on the raspi images, so I'll hold off on adding the project to the "affected" list until lunar's out, but it should be something I can try and push for in the m-animal cycle. @jgneff many thanks for the additional report -- it's extremely useful to have stuff like this I can point to and say "look! It's actually a problem!" -- 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: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Fix Released Status in network-manager source package in Kinetic: Incomplete 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 1969512] Re: Totem unable to play video: "The specified movie could not be found"
I'd say this is effectively "Fix Released" at this point in that on lunar (and kinetic? Sorry, I forgot to re-test this before upgrading the old drive), Totem now fails to play the video with "could not initialize OpenGL support" which is the "fix" implemented upstream (and reflected by the upstream tracker). LP: #1998782 has been filed with this new message so I'll point to that one in the ISO tracker for the current lunar 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/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Fix Released Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Milestone: None => ubuntu-23.04 ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2013080 Title: On rpi desktop images, grow root leaving slack for LUKS Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: To aid in user-implemented FDE we wish to leave 16MB of the file- system unexpanded during first boot. The growth of the partition is unaffected, but rather than relying on systemd's growfs facility in fstab, we should use a service that runs a simple script to handle calculating the resize in early boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2013080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS
This should only be merged once LP: #2004430 as it builds upon those commits. ** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/439835 ** Merge proposal linked: https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/439842 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2013080 Title: On rpi desktop images, grow root leaving slack for LUKS Status in ubuntu-settings package in Ubuntu: New Bug description: To aid in user-implemented FDE we wish to leave 16MB of the file- system unexpanded during first boot. The growth of the partition is unaffected, but rather than relying on systemd's growfs facility in fstab, we should use a service that runs a simple script to handle calculating the resize in early boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2013080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013080] [NEW] On rpi desktop images, grow root leaving slack for LUKS
Public bug reported: To aid in user-implemented FDE we wish to leave 16MB of the file-system unexpanded during first boot. The growth of the partition is unaffected, but rather than relying on systemd's growfs facility in fstab, we should use a service that runs a simple script to handle calculating the resize in early boot. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu) Milestone: None => ubuntu-23.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2013080 Title: On rpi desktop images, grow root leaving slack for LUKS Status in ubuntu-settings package in Ubuntu: New Bug description: To aid in user-implemented FDE we wish to leave 16MB of the file- system unexpanded during first boot. The growth of the partition is unaffected, but rather than relying on systemd's growfs facility in fstab, we should use a service that runs a simple script to handle calculating the resize in early boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2013080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 861493] Re: evince doesn't print duplex on duplex-able printers
Still an issue on the current LTS (jammy, 22.04), and the current devel series (lunar, 23.04) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/861493 Title: evince doesn't print duplex on duplex-able printers Status in evince package in Ubuntu: Confirmed Bug description: I have a postscript-printer, which can print on both sides of the paper (duplex). When I print a file with "lpr -Pduplex file.pdf", everything is o.k., when I do that in evince (selecting printer duplex), it prints every page on a single sheet, so it acts not the same as lpr does. This happens with Ubuntu 10.04.3. evince is in 2.30.3-0ubuntu1.2. Greetings, Leander Jedamus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/861493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009824] [NEW] Crash in raspberrypi_ipa_proxy when compiled with LTO
Public bug reported: The libcamera 0.0.4 implementation currently in lunar has a couple of global objects which are unsafely allocated, leading to a crash in the subordinate raspberrypi_ipa_proxy process when used at runtime. The attached patch resolves the issue. ** Affects: libcamera (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: In Progress ** Patch added: "fix-lto.patch" https://bugs.launchpad.net/bugs/2009824/+attachment/5653167/+files/fix-lto.patch ** Changed in: libcamera (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: libcamera (Ubuntu) Milestone: None => ubuntu-23.04 ** Changed in: libcamera (Ubuntu) Status: New => In Progress -- 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/2009824 Title: Crash in raspberrypi_ipa_proxy when compiled with LTO Status in libcamera package in Ubuntu: In Progress Bug description: The libcamera 0.0.4 implementation currently in lunar has a couple of global objects which are unsafely allocated, leading to a crash in the subordinate raspberrypi_ipa_proxy process when used at runtime. The attached patch resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2009824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
FYI, in case anyone wants to add their monitor (and whether it succeeds or fails at suspending with the Ubuntu raspi kernel) to this ticket: $ cp /sys/devices/platform/gpu/drm/card1/card1-HDMI-A-1/edid hdmi0-monitor.edid $ cp /sys/devices/platform/gpu/drm/card1/card1-HDMI-A-2/edid hdmi1-monitor.edid As you may guess, hdmi0-monitor.edid is the EDID for the monitor plugged into HDMI0 (the socket closest to the USB-C power port on the Pi4, and the socket closest to the uSD slot on the Pi400), whilst hdmi1-monitor.edid is the EDID for the monitor plugged into HDMI1. If you have no monitor connected to a socket, you'll still get an EDID file but it'll be 0 bytes. A valid EDID file should be 256 bytes (or more? I forget the details of EDID, but there's some extended blocks I vaguely recall). Upload valid EDID files to https://www.edid.tv/edid/upload/binary/ if you wish (bear in mind this will share the serial # of your monitor but I don't think there's any particular security risk in that), and add the link here along with whether or not this particular monitor suspends successfully or not. -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Confirmed Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
Fails with this monitor: https://www.edid.tv/edid/2267/ -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Confirmed Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
I'm still seeing this behaviour (precisely as described at the top: fades to black, switches off, then switches on to black a second or two later) with the lunar daily image and the bootstrap 6.2 kernel, so it'll likely be an issue in lunar. I'll flash a jammy and kinetic image to a card in a bit and try and re- confirm them there but kinetic certainly exhibited the issue last week before I upgraded my devel system. In case this is monitor specific, the monitor I'm using is a Benq GW2270H running at 1080p. -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Confirmed Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007160] [NEW] Image properties does nothing in lunar
Public bug reported: When testing the current lunar (23.04) pre-installed desktop image for the Raspberry Pi, I attempted to retrieve the properties of a captured JPEG from nautilus: * Right click on a JPEG image * Select "Properties" item at the bottom * Click on the "Image Properties" link at the bottom of the dialog that opens However, nothing happens when clicking on the link. I presume this is meant to go to a page listing the details that nautilus used to display (resolution, etc). I tested with a couple of different JPEGs that display their properties correctly under jammy and kinetic. I'm happy to provide test images if required, but I don't think it's specific to the JPEGs I'm using. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/2007160 Title: Image properties does nothing in lunar Status in nautilus package in Ubuntu: New Bug description: When testing the current lunar (23.04) pre-installed desktop image for the Raspberry Pi, I attempted to retrieve the properties of a captured JPEG from nautilus: * Right click on a JPEG image * Select "Properties" item at the bottom * Click on the "Image Properties" link at the bottom of the dialog that opens However, nothing happens when clicking on the link. I presume this is meant to go to a page listing the details that nautilus used to display (resolution, etc). I tested with a couple of different JPEGs that display their properties correctly under jammy and kinetic. I'm happy to provide test images if required, but I don't think it's specific to the JPEGs I'm using. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2007160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs
** Changed in: livecd-rootfs (Ubuntu) Milestone: None => ubuntu-23.04 ** Changed in: ubuntu-settings (Ubuntu) Milestone: None => ubuntu-23.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2004430 Title: Migrate raspberry pi image hacks from livecd-rootfs Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are currently several "hacks" in livecd-rootfs that introduce unpackaged files and/or services. In particular, everything in https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with the fstab and the swapfile needs to go. The new ubuntu-image based process for generating images won't be using these; anything to do with the fstab needs to go in the image-definition yaml, and the swapfile services ought to be owned by the ubuntu-raspi-settings- desktop package anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/436647 ** Merge proposal linked: https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/436648 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2004430 Title: Migrate raspberry pi image hacks from livecd-rootfs Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are currently several "hacks" in livecd-rootfs that introduce unpackaged files and/or services. In particular, everything in https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with the fstab and the swapfile needs to go. The new ubuntu-image based process for generating images won't be using these; anything to do with the fstab needs to go in the image-definition yaml, and the swapfile services ought to be owned by the ubuntu-raspi-settings- desktop package anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004430] [NEW] Migrate raspberry pi image hacks from livecd-rootfs
Public bug reported: There are currently several "hacks" in livecd-rootfs that introduce unpackaged files and/or services. In particular, everything in https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with the fstab and the swapfile needs to go. The new ubuntu-image based process for generating images won't be using these; anything to do with the fstab needs to go in the image-definition yaml, and the swapfile services ought to be owned by the ubuntu-raspi-settings-desktop package anyway. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Assignee: Dave Jones (waveform) Status: New ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2004430 Title: Migrate raspberry pi image hacks from livecd-rootfs Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are currently several "hacks" in livecd-rootfs that introduce unpackaged files and/or services. In particular, everything in https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with the fstab and the swapfile needs to go. The new ubuntu-image based process for generating images won't be using these; anything to do with the fstab needs to go in the image-definition yaml, and the swapfile services ought to be owned by the ubuntu-raspi-settings- desktop package anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2001904] Re: URLs fail to launch in Firefox
Adding a trivial test PDF ** Attachment added: "test_pdf.pdf" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+attachment/5639334/+files/test_pdf.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2001904 Title: URLs fail to launch in Firefox Status in evince package in Ubuntu: New Bug description: Opening a PDF under evince, then clicking an https: link within the PDF fails to open the link in Firefox. On the command line, evince reports: $ evince test.pdf env: ‘/snap/bin/firefox’: Permission denied In dmesg, the following message appears each time the link is clicked: [ 1366.891145] audit: type=1400 audit(1672910889.559:286): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/snap" pid=14698 comm="env" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 This may be related to (or a regression of?) LP: #964510 as it's clearly aa related, but I don't think it's a direct duplicate given the audit log is rather different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2001904] [NEW] URLs fail to launch in Firefox
Public bug reported: Opening a PDF under evince, then clicking an https: link within the PDF fails to open the link in Firefox. On the command line, evince reports: $ evince test.pdf env: ‘/snap/bin/firefox’: Permission denied In dmesg, the following message appears each time the link is clicked: [ 1366.891145] audit: type=1400 audit(1672910889.559:286): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/snap" pid=14698 comm="env" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 This may be related to (or a regression of?) LP: #964510 as it's clearly aa related, but I don't think it's a direct duplicate given the audit log is rather different. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2001904 Title: URLs fail to launch in Firefox Status in evince package in Ubuntu: New Bug description: Opening a PDF under evince, then clicking an https: link within the PDF fails to open the link in Firefox. On the command line, evince reports: $ evince test.pdf env: ‘/snap/bin/firefox’: Permission denied In dmesg, the following message appears each time the link is clicked: [ 1366.891145] audit: type=1400 audit(1672910889.559:286): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/snap" pid=14698 comm="env" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 This may be related to (or a regression of?) LP: #964510 as it's clearly aa related, but I don't think it's a direct duplicate given the audit log is rather different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: New => Invalid ** Changed in: ubuntu-settings (Ubuntu Kinetic) Status: Confirmed => Invalid ** Changed in: pulseaudio (Ubuntu Jammy) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Kinetic) Assignee: Dave Jones (waveform) => (unassigned) ** Changed in: ubuntu-settings (Ubuntu) Assignee: Dave Jones (waveform) => (unassigned) ** Changed in: ubuntu-settings (Ubuntu Kinetic) Assignee: Dave Jones (waveform) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Invalid Status in pulseaudio source package in Jammy: Confirmed Status in ubuntu-settings source package in Jammy: Invalid Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: Invalid Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
Still a problem on jammy, and removing switch-on-connect does fix things there. The result of that change is that plugging in a new (never seen before) USB device does *not* automatically switch to it, but once the device has been selected as the output, it will subsequently be automatically selected when plugged in (or at least that's my experience on my PC). And it also clears up the "always selects headphones output" issue on the Pi. I'll target this to jammy given we're still getting duplicate reports about it (LP: #1995459 is the latest) ** Also affects: pulseaudio (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Confirmed Status in pulseaudio source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: Confirmed Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995459] Re: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem
*** This bug is a duplicate of bug 1877194 *** https://bugs.launchpad.net/bugs/1877194 This sounds like a duplicate of LP: #1877194 -- a workaround is available in that report (see comment 2) ** This bug has been marked a duplicate of bug 1877194 switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1995459 Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: System sound output setting always defaults to headphones instead of hdmi at startup and login and must be reset every time. No headphones are connected; only hdmi from pi 4 to TV and from TV to sound system via hdmi-arc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1017.19-raspi 5.15.60 Uname: Linux 5.15.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruzr 10351 F pulseaudio /dev/snd/controlC0: bruzr 10351 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 2 04:54:41 2022 ImageMediaBuild: 20220809 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:vc4hdmi0 failed Symptom_AlsaPlaybackTestStderr: S a m p l e f o r m a t n o t a v a i l a b l e f o r p l a y b a c k : I n v a l i d a r g u m e n t Symptom_Card: vc4-hdmi - vc4-hdmi-1 Symptom_Type: None of the above Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1995459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp