[Desktop-packages] [Bug 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
Thanks @Dan. Will try to make an exception request for Oracular. Proposed a MR for Oracular just in case. https://code.launchpad.net/~mschiu77/ubuntu/+source/alsa-utils/+git/alsa-utils/+merge/472762 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/2073552 Title: Add SoundWire devices to alsa-info reported in ACPI Status in alsa-utils package in Ubuntu: New Status in alsa-utils source package in Jammy: In Progress Status in alsa-utils source package in Noble: In Progress Bug description: [SRU Justifications] [Impact] Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on Soundwire instead of HDA, but the soundwire devices are not well reflected on the alsa-info report. In order to meet the increasing demands for SoundWire debugging, we must enable alsa-info to provide more information about SoundWire. [Fix] Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with v1.2.12 and we may not have to backport to Oracular. The reported information can reflect which soundwire devices are connected and which soundware link the device connects to. It's quite sufficient for what driver should be ready and what tplg/firmware file should be loaded. [Test Case] 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device. 2. Install the new alsa-utils debian package 3. Execute `alsa-info` to generate the report 4. Check if the section "ACPI SoundWire Device Status Information" exists in the output report. [Where problems could occur] It's simply an additional soundwire information when ACPI exposed the soundwire device. The risk for regression is low. [Other Info] Verify if the official Oracular starts from version v1.2.12 to determine if we have to land it on Oracular. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2077587] Re: Refresh WebExtensions portal patch
I have a couple of questions with the test plan - as it stands, I don't see where we're performing before/after tests of the xdg-desktop-portal package? That is - where, in the test plan steps, do we actually install the package from proposed? Do we need to > delete ~/.local/share/flatpak/db/webextensions and reboot to ensure a > pristine state after upgrading xdg-desktop-portal? Do we need to *not* delete those, to test upgrades? Do we need to test both? Also, it's not clear what the manually-downloaded snap is for? The description is currently: > even though the main firefox snap distributed via the snap store > currently ships an older revision of the firefox-side patch for > compatibility for jammy users, a build of the firefox snap from > the above link can be downloaded and installed to ensure that the > current older firefox-side implementation is used It seems to say that the snap store ships an old revision of the firefox-side patch, but we should also download this specific snap, which has the current old revision of the firefox-side patch? Is this so that we can test the old codepath even once the snap-store firefox is updated to the *new* codepath? The only other question is: Is this likely to be the final xdg-desktop- portal implementation, or is it expected that further revisions will be needed? Feel free to give me a ping in #ubuntu-release once you've answered these! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2077587 Title: Refresh WebExtensions portal patch Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Jammy: New Status in xdg-desktop-portal source package in Noble: Incomplete Status in xdg-desktop-portal source package in Oracular: Fix Released Bug description: [ Impact ] * Without this change, firefox users on jammy who rely on the WebExtensions portal for firefox add-ons that need a native executable to function correctly will experience breakage when the latest version of the firefox native messaging patch is landed upstream in the near future. https://phabricator.services.mozilla.com/D140803 An instance of such breakage already happened earlier this year when we refreshed the firefox native messaging patch we carry in the firefox snap to the latest revision under review in Mozilla Phabricator and inadvertently broke native messaging for users of firefox snap on jammy. https://discourse.ubuntu.com/t/firefox-122-snap-temporary-native-messaging-breakage-for-ubuntu-22-04-users-fixed-since/41940 * The newer changes to the WebExtensions portal are being backported because jammy and noble are the current primary targets for the effort of enabling native messaging in the firefox snap, and once the firefox implementation lands in the firefox snap, we want this to continue working seamlessly and as expected. Moreover, with both the firefox-side and portal-side patches being nearly ready for merge in the corresponding upstreams, it makes sense to ship an up-to-date version of the portal patch in jammy and noble to provide a uniform platform for the firefox-side patch across these two LTS releases, helping ease the maintenance burden and lessen the difference between them from this aspect should the need to debug and fix potential issues in firefox or in the portal arise later in the future. * The impact of updating xdg-desktop-portal in jammy from 1.14.4 to 1.14.6 should be minimal and positive, given that they are purely bug fix micro releases: https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.14.5 https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.14.6 * Updating the WebExtensions portal in xdg-desktop-portal before updating the firefox-side implementation in the firefox snap is fine and covered as part of the test plan. [ Test Plan ] * To test and verify the native messaging portal works as expected, we can test the extensions.gnome.org browser integration before and after updating our installed xdg-desktop-portal package: - in a fully up-to-date Ubuntu VM, install the chrome-gnome-shell deb package - if it exists, delete ~/.local/share/flatpak/db/webextensions and reboot to ensure a pristine state - run the firefox snap and browse to https://addons.mozilla.org/firefox/addon/gnome-shell-integration/ and click the "Add to Firefox" blue button - accept the firefox prompt to install the extension - you will soon be prompted by GNOME Shell (with a modal dialog) to allow firefox to use the WebExtensions portal to start the native connector, click "Allow" - browse to https://extensions.gnome.org/local/ - see tha
[Desktop-packages] [Bug 2077587] Re: Refresh WebExtensions portal patch
** Changed in: xdg-desktop-portal (Ubuntu Noble) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2077587 Title: Refresh WebExtensions portal patch Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Jammy: New Status in xdg-desktop-portal source package in Noble: Incomplete Status in xdg-desktop-portal source package in Oracular: Fix Released Bug description: [ Impact ] * Without this change, firefox users on jammy who rely on the WebExtensions portal for firefox add-ons that need a native executable to function correctly will experience breakage when the latest version of the firefox native messaging patch is landed upstream in the near future. https://phabricator.services.mozilla.com/D140803 An instance of such breakage already happened earlier this year when we refreshed the firefox native messaging patch we carry in the firefox snap to the latest revision under review in Mozilla Phabricator and inadvertently broke native messaging for users of firefox snap on jammy. https://discourse.ubuntu.com/t/firefox-122-snap-temporary-native-messaging-breakage-for-ubuntu-22-04-users-fixed-since/41940 * The newer changes to the WebExtensions portal are being backported because jammy and noble are the current primary targets for the effort of enabling native messaging in the firefox snap, and once the firefox implementation lands in the firefox snap, we want this to continue working seamlessly and as expected. Moreover, with both the firefox-side and portal-side patches being nearly ready for merge in the corresponding upstreams, it makes sense to ship an up-to-date version of the portal patch in jammy and noble to provide a uniform platform for the firefox-side patch across these two LTS releases, helping ease the maintenance burden and lessen the difference between them from this aspect should the need to debug and fix potential issues in firefox or in the portal arise later in the future. * The impact of updating xdg-desktop-portal in jammy from 1.14.4 to 1.14.6 should be minimal and positive, given that they are purely bug fix micro releases: https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.14.5 https://github.com/flatpak/xdg-desktop-portal/releases/tag/1.14.6 * Updating the WebExtensions portal in xdg-desktop-portal before updating the firefox-side implementation in the firefox snap is fine and covered as part of the test plan. [ Test Plan ] * To test and verify the native messaging portal works as expected, we can test the extensions.gnome.org browser integration before and after updating our installed xdg-desktop-portal package: - in a fully up-to-date Ubuntu VM, install the chrome-gnome-shell deb package - if it exists, delete ~/.local/share/flatpak/db/webextensions and reboot to ensure a pristine state - run the firefox snap and browse to https://addons.mozilla.org/firefox/addon/gnome-shell-integration/ and click the "Add to Firefox" blue button - accept the firefox prompt to install the extension - you will soon be prompted by GNOME Shell (with a modal dialog) to allow firefox to use the WebExtensions portal to start the native connector, click "Allow" - browse to https://extensions.gnome.org/local/ - see that firefox is able to talk to the native connector and display a list of the currently installed GNOME Shell extensions Note: the WebExtensions portal can also be tested using other firefox browser extensions that use native messaging, such as https://keepassxc.org * To test and verify that the firefox snap's native messaging portal support continues to work as intended after the portal is updated in xdg-desktop-portal, download and install the test snap from https://launchpad.net/~bandali/+snap/firefox-snap-nm-cur-old-patch (even though the main firefox snap distributed via the snap store currently ships an older revision of the firefox-side patch for compatibility for jammy users, a build of the firefox snap from the above link can be downloaded and installed to ensure that the current older firefox-side implementation is used): - in a fully up-to-date Ubuntu VM, download the newest test firefox snap from the above link and install it by running a command like 'sudo snap install --dangerous filename.snap' in the terminal - follow the steps of the above test case and verify that native messaging continues to work as intended in the firefox snap. * We continue running the upstream xdg-desktop-portal
[Desktop-packages] [Bug 2077969] Re: my ubuntu taskbar disappeared and when I go to settings>ubuntu desktop this messages appears "no ubuntu settings found" and "oops, something has gone wrong. Please
Hi there and thanks for the report. Was this during an installation or just during normal operation of your installed system? ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2077969 Title: my ubuntu taskbar disappeared and when I go to settings>ubuntu desktop this messages appears "no ubuntu settings found" and "oops, something has gone wrong. Please report a bug in Launchpad" Status in subiquity: New Status in gnome-control-center package in Ubuntu: New Bug description: my ubuntu taskbar disappeared and when I go to settings>ubuntu desktop this messages appears "no ubuntu settings found" and "oops, something has gone wrong. Please report a bug in Launchpad". I think I deleted some package wrongly while trying to use tactile app and gnome-extensions. Can you guys help me? Didnt find anything on internet. Best regards. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 10:41:49 2024 InstallationDate: Installed on 2024-06-16 (73 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: subiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2077969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Hello Xavier, or anyone else affected, Accepted apparmor into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/4.0.1really4.0.1-0ubuntu0.24.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apparmor (Ubuntu Noble) Status: Triaged => Fix Committed ** Tags removed: verification-done verification-done-noble ** Tags added: verification-needed verification-needed-noble -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in Wike: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Fix Committed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in foliate package in Ubuntu: Fix Committed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Fix Released Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Fix Released Status in guix package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Fix Released Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Fix Released Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Fix Released Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Fix Released Status in qutebrowser package in Ubuntu: Fix Released Status in rssguard package in Ubuntu: Fix Released Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Fix Released Status in tellico package in Ubuntu: Fix Released Status in tor package in Ubuntu: Confirmed Status in wike package in Ubuntu: Fix Committed Status in apparmor source package in Noble: Fix Committed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- Mailing list: http
[Desktop-packages] [Bug 2061326] Re: 24.04 beta hangs at desktop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2061326 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/2061326 Title: 24.04 beta hangs at desktop Status in mesa package in Ubuntu: New Bug description: I have a Thinkpad T510 dual boot windows and Ubuntu Budgie 22.04 Booting the 24.04 Ubuntu Budgie livecd, I notice that instead of the nice desktop graphics for Budgie I get a text line saying Ubuntu Budgie 24.04. Then when the desktop finally loads the liveCD locks up tight. Only a hard reset works. I have tried the Ubuntu 24.04 beta with same results. If I take the boot option "safe graphics" the live cd session loads correctly and does not hang. /$ inxi -FZRa System: Host: rob-ThinkPad-T510 Kernel: 6.8.0-11-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=35c54a5b-4746-419b-a598-d3d408c9066a ro quiet splash vt.handoff=7 Desktop: Budgie v: 10.9.1 tk: GTK v: 3.24.41 wm: budgie-wm with: budgie-panel,plank tools: gnome-screensaver,gsd-screensaver-proxy dm: LightDM v: 1.30.0 Distro: Budgie 24.04 LTS (Noble Numbat) base: Ubuntu Machine: Type: Laptop System: LENOVO product: 4384AJ9 v: ThinkPad T510 serial: Chassis: type: 10 serial: Mobo: LENOVO model: 4384AJ9 serial: uuid: BIOS: LENOVO v: 6MET92WW (1.52 ) date: 09/26/2012 Battery: ID-1: BAT0 charge: 47.8 Wh (97.8%) condition: 48.9/47.5 Wh (103.0%) volts: 11.7 min: 10.8 model: LGC 42T4848 type: Li-ion serial: 39414 status: discharging Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: 22-c2-4c-cc charge: 55% (should be ignored) rechargeable: yes status: discharging CPU: Info: model: Intel Core i7 M 620 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2 built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11 Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB Speed (MHz): avg: 1720 high: 2667 min/max: 1199/2667 boost: enabled scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1199 2: 2667 3: 1553 4: 1463 bogomips: 21280 Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown mitigation: PTI Type: mmio_stale_data status: Unknown: No mitigations Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300 Display: x11 server: X.Org v: 21.1.11 compositor: budgie-wm driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31") Monitor-1: LVDS-1 model: Lenovo 0x40b0 built: 2010 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2 size: 345x194mm (13.58x7.64") diag: 396mm (15.6") ratio: 16:9 modes: 1366x768 API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast surfaceless: drv: crocus x11: drv: crocus inactive: gbm,wayland API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 24.0.3-1ubuntu3 glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics (ILK) device-ID: 8086:0046 memory: 1.46 GiB unified: yes Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo 5 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403 API: ALSA v: k6.8.0-11-generic status: kernel-api tools: alsactl,alsam
[Desktop-packages] [Bug 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
@Dan, I though the alsa-utils of Oracular should be rebased on v1.2.12 and I don't know how it will happen. Can you suggest what I should do? I think the correct way is to trigger the sync? Or I should do it manually? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/2073552 Title: Add SoundWire devices to alsa-info reported in ACPI Status in alsa-utils package in Ubuntu: New Status in alsa-utils source package in Jammy: In Progress Status in alsa-utils source package in Noble: In Progress Bug description: [SRU Justifications] [Impact] Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on Soundwire instead of HDA, but the soundwire devices are not well reflected on the alsa-info report. In order to meet the increasing demands for SoundWire debugging, we must enable alsa-info to provide more information about SoundWire. [Fix] Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with v1.2.12 and we may not have to backport to Oracular. The reported information can reflect which soundwire devices are connected and which soundware link the device connects to. It's quite sufficient for what driver should be ready and what tplg/firmware file should be loaded. [Test Case] 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device. 2. Install the new alsa-utils debian package 3. Execute `alsa-info` to generate the report 4. Check if the section "ACPI SoundWire Device Status Information" exists in the output report. [Where problems could occur] It's simply an additional soundwire information when ACPI exposed the soundwire device. The risk for regression is low. [Other Info] Verify if the official Oracular starts from version v1.2.12 to determine if we have to land it on Oracular. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2076264] [NEW] Secondary external display intermittently goes black
Public bug reported: After upgrade to mantic, running with primary laptop display and secondary display via a dock, the secondary display will intermittently go black for 1-2 seconds. This was happening a few times a week, and at the moment started happening once every few minutes. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 12:34:10 2024 DistUpgraded: 2024-05-20 16:37:33,170 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:2315] InstallationDate: Installed on 2023-12-17 (235 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: LENOVO 21HM002GUS ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-05-20 (79 days ago) dmi.bios.date: 05/13/2024 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: N3XET54W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 21HM002GUS dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN3XET54W(1.29):bd05/13/2024:br1.29:efr1.19:svnLENOVO:pn21HM002GUS:pvrThinkPadX1CarbonGen11:rvnLENOVO:rn21HM002GUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21HM_BU_Think_FM_ThinkPadX1CarbonGen11: dmi.product.family: ThinkPad X1 Carbon Gen 11 dmi.product.name: 21HM002GUS dmi.product.sku: LENOVO_MT_21HM_BU_Think_FM_ThinkPad X1 Carbon Gen 11 dmi.product.version: ThinkPad X1 Carbon Gen 11 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2076264 Title: Secondary external display intermittently goes black Status in xorg package in Ubuntu: New Bug description: After upgrade to mantic, running with primary laptop display and secondary display via a dock, the secondary display will intermittently go black for 1-2 seconds. This was happening a few times a week, and at the moment started happening once every few minutes. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 12:34:10 2024 DistUpgraded: 2024-05-20 16:37:33,170 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:2315] InstallationDate: Installed on 2023-12-17 (235 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: LENOVO 21HM002GUS ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-05-20 (79 days ago) dmi.bios.date: 05/13/2024 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: N3XET54W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 21HM002GUS dmi.board.v
[Desktop-packages] [Bug 2072742] Re: [SRU] Backport gnome-calendar 46.1
Hello Nathan, or anyone else affected, Accepted gnome-calendar into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- calendar/46.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2072742 Title: [SRU] Backport gnome-calendar 46.1 Status in gnome-calendar package in Ubuntu: Fix Released Status in gnome-calendar source package in Noble: Fix Committed Bug description: Impact -- This is a new Gnome Calendar release, which contains mostly translation updates but also changes to key binding handling. Here is the news file: https://download.gnome.org/sources/gnome- calendar/46/gnome-calendar-46.1.news Test plan - https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar Regression potential Particular key bindings (particularly of dialog windows) could stop to work. Other information - This falls under the GNOME microrelease exception already approved by the SRU team. See https://wiki.ubuntu.com/StableReleaseUpdates/GNOME for the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2072742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043820] Proposed package upload rejected
An upload of ubuntu-release-upgrader to noble-proposed has been rejected from the upload queue for the following reason: "Changing the "The package %s is marked for removal..." string to an f"" string unnecessarily breaks translations, and it looks like the Amharic translation got broken (it retains the old translation, containing a '%s' - I'm not *sure* what python will do when it hits that, but it's not going to be what we want). Otherwise looks fine to me.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in firefox source package in Noble: Confirmed Status in snapd source package in Noble: Confirmed Status in ubuntu-release-upgrader source package in Noble: In Progress Bug description: [Impact] Upgrades from Jammy to Noble can fail if snap transition packages are installed after the new systemd has been unpacked, but before systemd- resolved has been unpacked. In practice, this manifests on at least Xubuntu upgrades during the chromium-browser snap transition. [Test Plan] Without this fix, the snap store connectivity check will fail when installing the chromium-browser snap because systemd-resolved is not present, so DNS lookups fail during the connectivity check. With the fix in place, the systemd-resolved stub resolver should be disabled during the upgrade so that DNS lookups succeed even when systemd-resolved is not yet unpacked on the system again. So, to test this fix, we should run an upgrade on a Xubuntu 22.04 system: $ do-release-upgrade -d And verify that (a) the chromium-browser installation (and snap store connectivity check) succeeds, and (b) that the stub resolver is not in use during the upgrade. $ cat /etc/resolv.conf $ cat /run/systemd/resolved.conf.d/dist-upgrade-no-stub-resolver.conf [Where problems could occur] This patch disables the systemd-resolved stub resolver by writing a drop-in to /run/systemd/resolved.conf.d. If there was a mistake in the drop-in, it would not correctly disable the stub resolver. [Original Description] When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade fails consistently at the `Installing the firefox snap` step. This was first detected on Jenkins [1], then reproduced locally with `auto-upgrade-testing`, then finally by manually running a `do- release-upgrade -d` in a VM. [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade- list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull (Jenkins full log attached) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.17 ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri Nov 17 18:24:22 2023 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Jammy: Fix Committed Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: [ Impact ] openssh-server is always installed to the target machine regardless of the user's explicit choice to not have it installed. Backporting the fix will allow image builds to pick up it up and become available for the next point release. The upload fixes the bug by removing ssh-import-id from the server- minimal seed and meta-package such that it's not part of the base layer copied over during install. [ Test Plan ] live images -- Test 1: 1. Download the latest server installer image from https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/ 2. Perform a regular install using the image and on the "SSH configuration" screen make sure "Install OpenSSH server" is NOT selected. 3. Finish the install and reboot the machine. 4. Login to the rebooted machine using the credentials provided during install. 5. Using "apt-cache policy openssh-server" and "apt-cache policy ssh-import-id" confirm neither are installed. live images -- Test 2: - Perform Test 1 but instead opt-in to installing openssh-server and ensure it is installed in the target system. live-images -- Test 3: - Perform Test 2 but in a completely offline fashion. pre-installed images: - Download the latest preinstalled image from: https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/ - Boot the image and, using the same commands as above, confirm openssh-server and ssh-import-id ARE installed [ Where problems could occur ] - openssh-server could be included in the build through other means than identified by the proposed upload, causing the package to be still installed by default. - openssh-server and ssh-import-id could fail to become part of the pool, prohibiting offline install of the packages. - Changes to the seeds could cause preinstalled images to lack the package. - The image build(s) may produce errors if they rely on openssh-server or ssh-import-id already being available in a layer in which it's now no longer included. (I can't say it's likely but it is worth mentioning) [ Other Info ] * I have built test images for ubuntu-cpc, both minimized and non-minimized, with my seed changes and verified those images will still correctly contain ssh-import-id and open-ssh-server [ Original Description] With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
I performed the preinstalled image tests today using the amd64 image from [1] and can confirm openssh-server and ssh-import-id are installed. [1] https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/20240805.1/ ** Changed in: ubuntu-meta (Ubuntu Jammy) Milestone: ubuntu-22.04.2 => ubuntu-22.04.5 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Jammy: Fix Committed Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: [ Impact ] openssh-server is always installed to the target machine regardless of the user's explicit choice to not have it installed. Backporting the fix will allow image builds to pick up it up and become available for the next point release. The upload fixes the bug by removing ssh-import-id from the server- minimal seed and meta-package such that it's not part of the base layer copied over during install. [ Test Plan ] live images -- Test 1: 1. Download the latest server installer image from https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/ 2. Perform a regular install using the image and on the "SSH configuration" screen make sure "Install OpenSSH server" is NOT selected. 3. Finish the install and reboot the machine. 4. Login to the rebooted machine using the credentials provided during install. 5. Using "apt-cache policy openssh-server" and "apt-cache policy ssh-import-id" confirm neither are installed. live images -- Test 2: - Perform Test 1 but instead opt-in to installing openssh-server and ensure it is installed in the target system. live-images -- Test 3: - Perform Test 2 but in a completely offline fashion. pre-installed images: - Download the latest preinstalled image from: https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/ - Boot the image and, using the same commands as above, confirm openssh-server and ssh-import-id ARE installed [ Where problems could occur ] - openssh-server could be included in the build through other means than identified by the proposed upload, causing the package to be still installed by default. - openssh-server and ssh-import-id could fail to become part of the pool, prohibiting offline install of the packages. - Changes to the seeds could cause preinstalled images to lack the package. - The image build(s) may produce errors if they rely on openssh-server or ssh-import-id already being available in a layer in which it's now no longer included. (I can't say it's likely but it is worth mentioning) [ Other Info ] * I have built test images for ubuntu-cpc, both minimized and non-minimized, with my seed changes and verified those images will still correctly contain ssh-import-id and open-ssh-server [ Original Description] With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2075558] [NEW] [snap] Thunderbird icon missing in KDE task bar
Public bug reported: Since the upgrade to Kubuntu 24.04 and hence the migration of Thunderbird from DEB to Snap, the Thunderbird icon in the task bar is missing. See attached screenshot. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of Thunderbird in taskbar" https://bugs.launchpad.net/bugs/2075558/+attachment/5802072/+files/Screenshot_20240802_092407.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2075558 Title: [snap] Thunderbird icon missing in KDE task bar Status in thunderbird package in Ubuntu: New Bug description: Since the upgrade to Kubuntu 24.04 and hence the migration of Thunderbird from DEB to Snap, the Thunderbird icon in the task bar is missing. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2075558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04
I performed all of the live-image tests today using [1] and can confirm they pass. I had also considered the fact that the changes might regress the installer's ability to use ssh-import-id during the install process, so I tested that too and can confirm it still works. [1] https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/20240802.1/jammy-live-server-amd64.iso -- 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/1974483 Title: autoinstall ssh:install-server:false is misleading in 22.04 Status in subiquity: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Jammy: Fix Committed Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: [ Impact ] openssh-server is always installed to the target machine regardless of the user's explicit choice to not have it installed. Backporting the fix will allow image builds to pick up it up and become available for the next point release. The upload fixes the bug by removing ssh-import-id from the server- minimal seed and meta-package such that it's not part of the base layer copied over during install. [ Test Plan ] live images -- Test 1: 1. Download the latest server installer image from https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-live/ 2. Perform a regular install using the image and on the "SSH configuration" screen make sure "Install OpenSSH server" is NOT selected. 3. Finish the install and reboot the machine. 4. Login to the rebooted machine using the credentials provided during install. 5. Using "apt-cache policy openssh-server" and "apt-cache policy ssh-import-id" confirm neither are installed. live images -- Test 2: - Perform Test 1 but instead opt-in to installing openssh-server and ensure it is installed in the target system. live-images -- Test 3: - Perform Test 2 but in a completely offline fashion. pre-installed images: - Download the latest preinstalled image from: https://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/ - Boot the image and, using the same commands as above, confirm openssh-server and ssh-import-id ARE installed [ Where problems could occur ] - openssh-server could be included in the build through other means than identified by the proposed upload, causing the package to be still installed by default. - openssh-server and ssh-import-id could fail to become part of the pool, prohibiting offline install of the packages. - Changes to the seeds could cause preinstalled images to lack the package. - The image build(s) may produce errors if they rely on openssh-server or ssh-import-id already being available in a layer in which it's now no longer included. (I can't say it's likely but it is worth mentioning) [ Other Info ] * I have built test images for ubuntu-cpc, both minimized and non-minimized, with my seed changes and verified those images will still correctly contain ssh-import-id and open-ssh-server [ Original Description] With 22.04, openssh-server is baked into the image curtin copies to the target. The ssh:install-server key no longer controls whether openssh-server gets installed. It should be easy enough to have the bit of code that installs openssh-server when the key is true also remove it when the key is false. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1974483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023572] Re: SRU gjs 1.72.4 to jammy
Has the test plan (https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs) been executed? It's great that GNOME Shell seems stable, but there are other consumers of gjs that need testing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2066902] Re: Night Light occasionally gets stuck
Re-opening this bug as the SRU did not, in fact, fix it, but we don't want to have to re-verify all the other fixes in this upload. ** Changed in: mutter (Ubuntu Noble) Status: Fix Released => Triaged ** Tags removed: fixed-in-mutter-46.2 fixed-upstream noble verification- failed verification-failed-noble -- 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/2066902 Title: Night Light occasionally gets stuck Status in Mutter: New Status in mutter package in Ubuntu: Triaged Status in mutter source package in Noble: Triaged Status in mutter source package in Oracular: Triaged Bug description: [ Impact ] Since installing Ubuntu 24.04, every now and then Night Light gets stuck when my screen is locked at night and I unlock it in the morning. The screen is then very orange (more so than normally is the case with Night Light), and disabling it with the button in in the top bar menu does nothing. The only ways to restore the screen to normal are disabling and enabling the colour profile or running `gdbus call -e -o /org/gnome/SettingsDaemon/Color -d org.gnome.SettingsDaemon.Color -m org.gnome.SettingsDaemon.Color.NightLightPreview 1` [ Test Plan ] Unknown. Requires OP verification. [ Where problems could occur ] Night light and colour profiles are one in the same feature so touching one always risks affecting the other. Since all such gamma changes get committed along with other screen updates, there is the risk (particularly with atomic mode setting) that a mistake in any one change will cause the entire screen update to fail, resulting in black frames. [ Other Info ] I have never been able to find anything remotely relevant in any system logs regarding this issue. It also does not happen every day, but probably once every seven to ten days or so. My PC has an AMD RX550 GPU using the amdgpu driver. I'm not sure if it makes a difference, but so far I've not seen this problem on my other machines with Intel IGPs. The upstream bug report can be found here: https://gitlab.gnome.org/GNOME/mutter/-/issues/3439 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2066902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind
Re-opening this bug as the SRU did not, in fact, fix it, but we don't want to have to re-verify all the other fixes in this upload. ** Changed in: mutter (Ubuntu Noble) Status: Fix Released => Triaged ** Tags removed: fixed-in-mutter-46.2 fixed-upstream verification-failed verification-failed-noble -- 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/2026194 Title: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind Status in Mutter: Fix Released Status in mutter package in Ubuntu: Triaged Status in mutter source package in Noble: Triaged Status in mutter source package in Oracular: Triaged Bug description: [ Impact ] Clicking on some maximized or fullscreen windows may not respond and the clicks fall through to the window behind. [ Test Plan ] If auto login is not enabled, enable auto login and reboot. The issue can immediately be observed with first party apps such as the software settings GUI where apt sources, update settings, and GPU drivers are located. Have anything open behind it and then try to use it. Dragging the window to another location outside of the bounds of its default size and position makes it completely unusable because it clicks through to the window behind it no matter where you click. If the desktop is behind it, then the window will be usable but entities on the desktop will be clicked if they're located beneath what you clicked on in the window. This behavior is identical for any affected application. [ Where problems could occur ] The bug and the fix appears to be X11-specific, but that can affect Wayland sessions too via Xwayland. The risk here is in the sizing and interactivity of any X11 window. Mistakes in this area can result in other bugs similar to this one where the visual boundaries of a window do not match with its input boundaries. [ Original description ] Initially I thought this was an issue with IntelliJ and filed a bug there: https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind But when I had the same issue with GIMP, I realized it's an Ubuntu or GNOME issue instead. I am assuming this is a gnome-shell problem. Every once in a while, when I maximize or tile (Win+Right) the IntelliJ window, a bottom fraction of the window (somewhere around a quarter) becomes impossible to interact with, with the mouse. Clicking in that lower area will give focus to the thing behind IntelliJ, and if it's a window, raise it to the foreground. if I restore the window so that it is not maximized, the entire window is interactive with the mouse once again. This also happened with GIMP. The attached "Screencast" is a recording. I had to crop it to hide personal information. The attached screenshot shows the state of my screen so you have context, with a bright green color used to replace personal information. For the first 10s of the recording, I simply moused over to show how the cursor changes around a quarter from the bottom of the screen. For the next 10s, I left click, then move, then left click, then move, until focus changes to Sublime, the window behind IntelliJ. For the remainder of the video I show that right-clicking and mousing over works fine on the top three quarters, until I reach the bottom again, and then the right click is sent to Sublime. Ubuntu 23.04 gnome-shell version 44.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 12:05:46 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-19 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2026194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967707] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" This is almost harmless except that it wastes disk space and the high frequency of messages (one per frame) impacts desktop performance. [ Test Plan ] 0. Start with either an Nvidia-only desktop providing that bug 2060268 is NOT fixed yet; or an Nvidia desktop which also has an integrated GPU enabled such that Nvidia is configured as the primary (boot) GPU in the BIOS and a monitor is plugged into EACH GPU. 1. Log into a Wayland session. 2. Run: journalctl -f /usr/bin/gnome-shell and verify there is not a flood of messages with each screen redraw. [ Where problems could occur ] Wayland multi-GPU startup is the code affected here so any configuration expecting to use multiple GPUs simultaneously in a Wayland session may be affected. While bug 2060268 is unresolved even single GPU Nvidia systems will be affected due to the phantom GPU resulting from that bug. [ Original description ] Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016013] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2016013 Title: gnome-initial-setup doesn't get centered if Desktop Icons NG is loaded in a Wayland session Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] New windows don't get centered if Desktop Icons NG is loaded. With vanilla GNOME, if an app window is too large for tiling (larger than a quarter of the screen) then it will be centered by default. But this doesn't happen when DING is loaded, probably because DING is incorrectly treated as an app window. The scope of this bug has now been reduced to only cover gnome- initial-setup. [ Test Plan ] 1. Log into a Wayland session. 2. Run: sudo apt install gnome-initial-setup 3. Run: /usr/libexec/gnome-initial-setup --existing-user 4. Verify: The window is centered. [ Where problems could occur ] Anywhere in window placement when a new window opens. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038801] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2038801 Title: Secondary GPU frame rates are held back by dynamic-max-render-time Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] Secondary GPU frame rates are held back by dynamic-max-render-time as shown on this amdgpu setup connected to a 60 Hz monitor: main: 30 FPS main + CLUTTER_PAINT=disable-dynamic-max-render-time: 60 FPS https://gitlab.gnome.org/GNOME/mutter/-/issues/3070 [ Test Plan ] This is imprecise because many machines won't exhibit a measurable difference... 1. Set up a dual GPU machine with dual monitors using an open source driver such as amdgpu or nouveau. If you are using Mutter 46 or later then the closed source Nvidia driver may also be used in theory. 2. In a Wayland session, check that the frame rate being achieved on the monitor connected to the secondary GPU is at least that of the refresh rate. 3. Add CLUTTER_PAINT=disable-dynamic-max-render-time to /etc/environment and reboot. 4. In a Wayland session, check that the frame rate on the monitor connected to the secondary GPU has not changed (didn't get better) after the environment change. 5. Remove the change from /etc/environment. [ Where problems could occur ] Anywhere in frame scheduling and frame rate performance, since that is what changed. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2038801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050865] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: Fix Released Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Noble: Confirmed Status in mutter source package in Noble: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Oracular: Confirmed Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Upstream Mutter release 46.1 resolved ONE cause of this assertion failure, but apparently not all causes. So we are separating the two scenarios of Tiling Assistant active and disabled. The Mutter fix only addresses the crash when Tiling Assistant is disabled. [ Test Plan ] This needs more detail and community help... On a machine that was previously affected by the crash... 1. gnome-extensions disable tiling-assist...@ubuntu.com 2. Disconnect the HDMI cable Expect: The shell has not crashed and continues to function. [ Where problems could occur ] Potentially anywhere in Gnome Shell. Judging by the fix it relates to automatic window placement when monitors are added and removed. [ Original description ] I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061739] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2061739 Title: crash in meta_wayland_transaction_commit Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] gnome-shell occasionally crashes in meta_wayland_transaction_commit. [ Test Plan ] Unknown. Requires user verification. [ Where problems could occur ] Anywhere in screen contents correctness or graphics performance in Wayland sessions. Although few possible side effects are worse than the shell crashing. The real risk is that some more frequent regression occurs affecting more people. [ Original description ] Hi, The system is Ubuntu Noble with a regular daily updates. This happens many times since few days ago but not clear at all how to reproduce it. Regards, Patrice ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Apr 16 09:26:16 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-05-24 (1789 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2019-05-28 (1785 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2061739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2062377] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] In a Xorg session, changing the desktop cursor theme to anything other than Yaru or Adwaita results in gnome-shell crashing. [ Test Plan ] 1. Log into a Xorg session. 2. sudo apt install gnome-tweaks 3. In the Tweaks app under Appearance, select DMZ-white or Redglass cursor theme. 4. Move the cursor over various window edges such that the cursor shape should change. 5. Move the cursor over the top panel. 6. Verify the cursors you see are the expected ones and not just a grey square. 7. Verify the shell has not frozen or crashed. [ Where problems could occur ] Since the entire cursor selection stack changed both in the lead up to this bug and in fixing it, any aspect of the mouse pointer (cursor) selection logic could be affected. In any app, in both Xorg and Wayland sessions. [ Other Info ] The Wayland version of this issue is bug 2063869. [ Original description ] ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:38:02 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2024-04-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git2
[Desktop-packages] [Bug 2063869] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2063869 Title: Missing default cursor Status in Mutter: Fix Released Status in dmz-cursor-theme package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] In a Wayland session, changing the desktop cursor theme to anything other than Yaru or Adwaita results in a pale grey square as the cursor. [ Test Plan ] 1. Log into a Wayland session. 2. sudo apt install gnome-tweaks 3. In the Tweaks app under Appearance, select DMZ-white or Redglass cursor theme. 4. Move the cursor over various window edges such that the cursor shape should change. 5. Move the cursor over the top panel. 6. Verify the cursors you see are the expected ones and not just a grey square. [ Where problems could occur ] Since the entire cursor selection stack changed both in the lead up to this bug and in fixing it, any aspect of the mouse pointer (cursor) selection logic could be affected. In any app, in both Xorg and Wayland sessions. [ Other Info ] The Xorg version of this issue is bug 2062377. [ Original description ] After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse pointer works correctly when the pointer is over a window, but shows a pale grey square when over the desktop or Ubuntu top bar. This appears to happen because the /usr/share/icons/DMZ-White/cursors/default file (or symlink) is missing. Doing the following appears to fix the problem: 1. cd /usr/share/icons/DMZ-White/cursors 2. ln -s left_ptr default 3. In gnome-tweaks change to some other mouse pointer. 4. In gnome-tweaks change back to DMZ-White. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: dmz-cursor-theme 0.4.5ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 18:39:40 2024 Dependencies: InstallationDate: Installed on 2020-07-14 (1382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: dmz-cursor-theme UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064735] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2064735 Title: Update mutter to 46.1 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: I am not working on this SRU but I'm filing this in case someone else works on it later. Impact -- There is a new bugfix release in the stable 46 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/46.1/NEWS Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2066931] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2066931 Title: Primary GPU displays nothing if the secondary GPU is using nouveau in a Wayland session Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] Wayland sessions log in to a black screen, if a secondary GPU exists that's using the nouveau driver and has a secondary monitor plugged into it. [ Test Plan ] 0. Find a machine with hybrid graphics: Intel integrated, Nvidia discrete. 1. Plug a second monitor into one of the ports wired to the discrete GPU. 2. Stick to the default nouveau graphics driver for Nvidia. No proprietary drivers. 3. Reboot. Verify the login screen appears and you can successfully log into a Wayland session. [ Where problems could occur ] Although the bug affects dual GPU multi-monitor systems, what is failing here is the primary monitor on the primary GPU. So the potential risk is that the primary display starts failing on more types of machines in Wayland sessions. [ Original description ] after upgrade from mantic to noble, my laptop booted to the firmware splash screen with Ubuntu logo, plus a mouse cursor. The gdm login screen did not appear. Switching to disable wayland (as in the attached modified config file) fixed this so that the login screen appears. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 23 08:06:45 2024 InstallationDate: Installed on 2019-12-23 (1613 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago) mtime.conffile..etc.gdm3.custom.conf: 2024-05-22T16:33:18.326823 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2066931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2068598] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2068598 Title: Mutter release 46.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Bug description: [ Impact ] Release Mutter 46.2 to Oracular and eventually SRU to Noble. [ Test Plan ] Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter [ Where problems could occur ] Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2068598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2070437] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2070437 Title: Debug mode MUTTER_DEBUG_TRIPLE_BUFFERING=always doesn't work anymore Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] Debug mode MUTTER_DEBUG_TRIPLE_BUFFERING=always doesn't result in triple buffering being used anymore. [ Test Plan ] 1. Add MUTTER_DEBUG_TRIPLE_BUFFERING=always to /etc/environment 2. Reboot. 3. Log into a Wayland session. 4. Open a Terminal window and drag it in circles with the mouse. 5. Verify there is a slight lag between the mouse pointer position and the window position. This means it's always triple buffering (or you accidentally logged into a Xorg session). [ Where problems could occur ] Anywhere in frame scheduling, including screen freezes and stutter. [ Other Info ] This regression occurred in 46.0 as a result of jbicha and myself working a little too independently. Jeremy identified that the upstream branch supported 46 and cherry-picked that for the Noble release, while I was still working on creating a stable maintenance branch for 46 in https://gitlab.gnome.org/Community/Ubuntu/mutter/-/tree/triple- buffering-v4-46 Fortunately it's very low priority and nobody has actually reported it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2070437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2070438] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2070438 Title: Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Fix Released Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46. [ Test Plan ] 0. Find a monitor that is VRR capable. 1. Set CLUTTER_PAINT=damage-region in /etc/environment 2. gsettings set org.gnome.mutter experimental-features '["variable-refresh-rate"]' 3. Reboot. 4. Log into a Wayland session. 5. Don't panic. The screen is meant to turn red whenever something changes. 6. In Settings > Display verify that variable refresh rate is detected and enabled. 7. Open Google Chrome (Firefox won't work) and start an animation like https://www.vsynctester.com/ 8. Press F11 to make it full screen. 9. Verify the screen has now stopped being red. 10. Press F11 again to exit full screen. 11. Verify the screen has gone red again. If the screen went black at the end, don't panic. That's a separate bug 2066080. [ Where problems could occur ] Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate. [ Other Info ] First reported upstream in: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_206 We DO NOT recommend enabling the VRR feature anyway because it is still buggy (bug 2066080) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2070438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073552] Re: Add SoundWire devices to alsa-info reported in ACPI
** Description changed: [SRU Justifications] [Impact] Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on Soundwire instead of HDA, but the soundwire devices are not well reflected on the alsa-info report. In order to meet the increasing demands for SoundWire debugging, we must enable alsa-info to provide more information about SoundWire. [Fix] - Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire devices reported in ACPI"). The reported information can reflect which soundwire devices are connected and which soundware link the device connects to. It's quite sufficient for what driver should be ready and what tplg/firmware file should be loaded. + Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with v1.2.12 and we may not have to backport to Oracular. The reported information can reflect which soundwire devices are connected and which soundware link the device connects to. It's quite sufficient for what driver should be ready and what tplg/firmware file should be loaded. [Test Case] - 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device. + 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device. 2. Install the new alsa-utils debian package 3. Execute `alsa-info` to generate the report - 4. Check if the section "ACPI SoundWire Device Status Information" exists in the output report. + 4. Check if the section "ACPI SoundWire Device Status Information" exists in the output report. [Where problems could occur] It's simply an additional soundwire information when ACPI exposed the soundwire device. The risk for regression is low. + + [Other Info] + Verify if the official Oracular starts from version v1.2.12 to determine if we have to land it on Oracular. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/2073552 Title: Add SoundWire devices to alsa-info reported in ACPI Status in alsa-utils package in Ubuntu: New Status in alsa-utils source package in Jammy: In Progress Status in alsa-utils source package in Noble: In Progress Bug description: [SRU Justifications] [Impact] Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on Soundwire instead of HDA, but the soundwire devices are not well reflected on the alsa-info report. In order to meet the increasing demands for SoundWire debugging, we must enable alsa-info to provide more information about SoundWire. [Fix] Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with v1.2.12 and we may not have to backport to Oracular. The reported information can reflect which soundwire devices are connected and which soundware link the device connects to. It's quite sufficient for what driver should be ready and what tplg/firmware file should be loaded. [Test Case] 1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device. 2. Install the new alsa-utils debian package 3. Execute `alsa-info` to generate the report 4. Check if the section "ACPI SoundWire Device Status Information" exists in the output report. [Where problems could occur] It's simply an additional soundwire information when ACPI exposed the soundwire device. The risk for regression is low. [Other Info] Verify if the official Oracular starts from version v1.2.12 to determine if we have to land it on Oracular. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/2073552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@trurl42, seems you have different machine which I will need alsa-info and dmesg for your config. Could you file another bug and attached the detail information as comment #1. -- 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/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063984] Re: package chromium-browser 1:124.0.6367.78-0ubuntu0.22.04.1sav0 failed to install/upgrade: le sous-processus nouveau chromium-browser paquet pre-installation script
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709.ReportingBugs. The package of chromium for 24.04/noble is https://bugs.launchpad.net/ubuntu/+source/chromium- browser/2:1snap1-0ubuntu2 which is not what you're using. If you wish to file a bug report on your chromium package, you'd have to file it with whomever packaged it (PPA owner), as it's not a Ubuntu 24.04 package. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063984 Title: package chromium-browser 1:124.0.6367.78-0ubuntu0.22.04.1sav0 failed to install/upgrade: le sous-processus nouveau chromium-browser paquet pre-installation script a renvoyé un état de sortie d'erreur 1 Status in chromium-browser package in Ubuntu: Invalid Bug description: This bug occurred while upgrading from 23.10 to 24.04. I had replaced snap chromium by a deb from a ppa before. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: chromium-browser 1:124.0.6367.78-0ubuntu0.22.04.1sav0 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 28 07:22:02 2024 Desktop-Session: 'None' 'None' '/root/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: le sous-processus nouveau chromium-browser paquet pre-installation script a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2024-01-16 (103 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) InstalledPlugins: Load-Avg-1min: 0.47 Load-Processes-Running-Percent: 0.1% MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic root=UUID=d8bcc836-e92f-47d0-a950-dcf166f80df1 ro rootflags=subvol=@ quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A SourcePackage: chromium-browser Title: package chromium-browser 1:124.0.6367.78-0ubuntu0.22.04.1sav0 failed to install/upgrade: le sous-processus nouveau chromium-browser paquet pre-installation script a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to noble on 2024-04-28 (0 days ago) dmi.bios.date: 07/01/2013 dmi.bios.release: 8.15 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd07/01/2013:br8.15:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:sku491531-B21: dmi.product.name: ProLiant DL160 G6 dmi.product.sku: 491531-B21 dmi.sys.vendor: HP modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2063476] Re: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2
Ok, this was introduced upstream somewhere between 2.36.0 (jammy release) and 2.44.0 (jammy-updates). webkit2gtk now detects whether gbm_bo_create_with_modifiers2 exists at build time; if so, it uses them. This is not a problem for the main archive, as the libgbm that mesa provides includes those symbols, but some proprietary drivers include their own libgbm (notably, here, the ARM MALI drivers) and this change has accidentally and silently broken the effective driver ABI for Ubuntu 22.04. In this case here it seems like it will be easy enough to patch the code to dynamically resolve gbm_bo_create_with_modifiers2 - the upstream code already has an implementation for where this is not available at build time. That's not an archive-wide solution, though. It's not *entirely* obvious to me whether this should be considered an SRU regression - I'm inclined to think so, but I don't hold that opinion strongly. I'll take the temperature of the SRU team on this. -- 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/2063476 Title: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 Status in gnome-control-center package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Cannot run gnome-control-center due to missing symbol lookup. Please see the output of the console: ``` ubuntu@kria:~$ gnome-control-center -h gnome-control-center: symbol lookup error: /lib/aarch64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8 ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136 Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk1p1) Date: Thu Apr 25 16:57:26 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@ Paramvir Could you try new kernel and update the information? Thanks ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- 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/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@trurl42, does the sound used to work before (older kernel than 6.5)? >From the kernel log, the line out has no trivial problem. I need to know is >this a regression or something else. Thanks [5.221075] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC3254: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [5.221080] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) -- 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/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
Hi Jeff, apologies for the delay in getting back to you. Based on the crash report provided it looks like it was a bug with the tracker package. I think this should be sorted by now though! ** Changed in: subiquity Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: Invalid Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061327] Re: 24.04 beta hangs at desktop
duplicate filing of https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061326 ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/2061327 Title: 24.04 beta hangs at desktop Status in mesa package in Ubuntu: Invalid Bug description: I have a Thinkpad T510 dual boot windows and Ubuntu Budgie 22.04 Booting the 24.04 Ubuntu Budgie livecd, I notice that instead of the nice desktop graphics for Budgie I get a text line saying Ubuntu Budgie 24.04. Then when the desktop finally loads the liveCD locks up tight. Only a hard reset works. I have tried the Ubuntu 24.04 beta with same results. If I take the boot option "safe graphics" the live cd session loads correctly and does not hang. /$ inxi -FZRa System: Host: rob-ThinkPad-T510 Kernel: 6.8.0-11-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=35c54a5b-4746-419b-a598-d3d408c9066a ro quiet splash vt.handoff=7 Desktop: Budgie v: 10.9.1 tk: GTK v: 3.24.41 wm: budgie-wm with: budgie-panel,plank tools: gnome-screensaver,gsd-screensaver-proxy dm: LightDM v: 1.30.0 Distro: Budgie 24.04 LTS (Noble Numbat) base: Ubuntu Machine: Type: Laptop System: LENOVO product: 4384AJ9 v: ThinkPad T510 serial: Chassis: type: 10 serial: Mobo: LENOVO model: 4384AJ9 serial: uuid: BIOS: LENOVO v: 6MET92WW (1.52 ) date: 09/26/2012 Battery: ID-1: BAT0 charge: 47.8 Wh (97.8%) condition: 48.9/47.5 Wh (103.0%) volts: 11.7 min: 10.8 model: LGC 42T4848 type: Li-ion serial: 39414 status: discharging Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: 22-c2-4c-cc charge: 55% (should be ignored) rechargeable: yes status: discharging CPU: Info: model: Intel Core i7 M 620 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2 built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11 Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB Speed (MHz): avg: 1720 high: 2667 min/max: 1199/2667 boost: enabled scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1199 2: 2667 3: 1553 4: 1463 bogomips: 21280 Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown mitigation: PTI Type: mmio_stale_data status: Unknown: No mitigations Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300 Display: x11 server: X.Org v: 21.1.11 compositor: budgie-wm driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31") Monitor-1: LVDS-1 model: Lenovo 0x40b0 built: 2010 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2 size: 345x194mm (13.58x7.64") diag: 396mm (15.6") ratio: 16:9 modes: 1366x768 API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast surfaceless: drv: crocus x11: drv: crocus inactive: gbm,wayland API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 24.0.3-1ubuntu3 glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics (ILK) device-ID: 8086:0046 memory: 1.46 GiB unified: yes Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo 5 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403 API: ALSA v: k6.8.0-11-generic status: kernel-api tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin tools: pw-cat,pw-cli,wpctl Network: Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e v: kernel
[Desktop-packages] [Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
That works! Thanks Andreas. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: Fix Committed Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
Yes, a no-change rebuild fixes the issue. Please see attached debdiff for the fix. I have provided a PPA with the build and tests: PPA: https://launchpad.net/~cpete/+archive/ubuntu/upower arm64 autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete- upower/noble/arm64/u/upower/20240407_191552_37f4e@/log.gz arm64 autopkgtests artifacts: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete- upower/noble/arm64/u/upower/20240407_191552_37f4e@/artifacts.tar.gz ** Patch added: "upower_1.90.2-8build3_1.90.2-8build4.debdiff" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+attachment/5762206/+files/upower_1.90.2-8build3_1.90.2-8build4.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: In Progress Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060375] Re: Error appeared when updating Snap on Ubuntu 20
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2060375 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/2060375 Title: Error appeared when updating Snap on Ubuntu 20 Status in gnome-software package in Ubuntu: New Bug description: see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2060375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060335] [NEW] upower/1.90.2-8build3 autopkgtest failure on arm64
Public bug reported: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz ** Affects: upower (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: In Progress ** Tags: update-excuse ** Description changed: - autopkgtests fail, only on arm64, with the following output: + autopkgtests fail, only on arm64, after a no-change-rebuild, with the + following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' - 689s + 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 - 689s + 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 - 689s + 689s 689s -- 689s Ran 66 tests in 194.378s - 689s + 689s 689s FAILED (fai
[Desktop-packages] [Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
I estimate another ncr could fix the issue. Building and testing in a ppa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: In Progress Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060080] Re: 23.13.9-2ubuntu5 is FTBFS on armhf
So something changed to add -Werror=implicit-function-declaration at build time (gcc didn't change so maybe dpkg?), which should have caused the other arches to fail as well but since they ran at different times they pulled different versions of build dependencies. This will likely get fixed on a rebuild and these are getting queued en masse, so I'm marking as invalid unless we have a reason to track this later. ** Changed in: accountsservice (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2060080 Title: 23.13.9-2ubuntu5 is FTBFS on armhf Status in accountsservice package in Ubuntu: Invalid Bug description: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2060080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060080] [NEW] 23.13.9-2ubuntu5 is FTBFS on armhf
Public bug reported: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz ** Affects: accountsservice (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: In Progress ** Changed in: accountsservice (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2060080 Title: 23.13.9-2ubuntu5 is FTBFS on armhf Status in accountsservice package in Ubuntu: In Progress Bug description: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2060080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Yes, please make sure the flaky tests are marked as such in the autopkgtests. SRUs are not released until either the test passes or the package version is marked as badtest in the britney hints. (A retry has caused it to pass on armhf) -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058435] [NEW] After recent update, pulseaudio crashes
Public bug reported: Intel ALC269VB Analog worked fine until today's update. Now all I get is "dummy output" and after running ubuntu-bug, the diagnostic says that pulseaudio has crashed. Reloading does not help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_46_49_generic_97 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 19 22:28:54 2024 InstallationDate: Installed on 2018-12-04 (1932 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2058435 Title: After recent update, pulseaudio crashes Status in pulseaudio package in Ubuntu: New Bug description: Intel ALC269VB Analog worked fine until today's update. Now all I get is "dummy output" and after running ubuntu-bug, the diagnostic says that pulseaudio has crashed. Reloading does not help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_46_49_generic_97 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 19 22:28:54 2024 InstallationDate: Installed on 2018-12-04 (1932 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2058435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058310] [NEW] Dummy output with Celeron Silver audio
Public bug reported: Built in speakers have alsa driver as sof-audio-pci-intel-apl, but there is no sound. I believe the CPU sound unit is essx-8336. Many people have reported similar problems, with the system sound being "dummy output". My bluetooth ear buds do work. Endeavour-OS and Fedora 39 live images do work with this machine, as does the Win 11 dual boot, so the hardware works. Will this problem be fixed in version 24.04? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 21:29:33 2024 InstallationDate: Installed on 2024-03-11 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2023 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GM118C_V33.1180.01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 140.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-16T20:22:40.610992 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2058310 Title: Dummy output with Celeron Silver audio Status in alsa-driver package in Ubuntu: New Bug description: Built in speakers have alsa driver as sof-audio-pci-intel-apl, but there is no sound. I believe the CPU sound unit is essx-8336. Many people have reported similar problems, with the system sound being "dummy output". My bluetooth ear buds do work. Endeavour-OS and Fedora 39 live images do work with this machine, as does the Win 11 dual boot, so the hardware works. Will this problem be fixed in version 24.04? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 21:29:33 2024 InstallationDate: Installed on 2024-03-11 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2023 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GM118C_V33.1180.01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 140.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-16T20:22:40.610992 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post t
[Desktop-packages] [Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
Hi, Thanks for your report and providing some logs! Could you try the install again and run `sudo apport-cli -u 2055418 -c /var/crash/*.crash` in the terminal? This should collect a bit more information and dump it here so we can investigate further. Thank you, Chris ** Also affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: New Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051738] [NEW] Suspend button does not respond to mouse click, only touchcreen
Public bug reported: So, this is pretty weird. In the Shell quick settings panel (the one accessed by clicking on the wifi/bluetooth/sound/battery part of the top bar), in the Shutdown submenu, the "Suspend" button - and *only* the Suspend button - does not respond to mouse clicks. I cannot use it to suspend the system with either the touchpad or an external mouse. The other buttons in that menu respond to mouse clicks, and the Suspend button responds when I use the touchscreen to tap it. I've attached a screencast in an attempt to demonstrate this (although it obviously doesn't show when I'm actually clicking the mouse). This behaviour has been going on for a while, at least the whole Mantic cycle, but maybe longer. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 09:21:31 2024 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-26 (949 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.2-0ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-22 (101 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Screencast of failing to click on the suspend button" https://bugs.launchpad.net/bugs/2051738/+attachment/5743692/+files/Screencast%20from%202024-01-31%2009-26-10.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2051738 Title: Suspend button does not respond to mouse click, only touchcreen Status in gnome-shell package in Ubuntu: New Bug description: So, this is pretty weird. In the Shell quick settings panel (the one accessed by clicking on the wifi/bluetooth/sound/battery part of the top bar), in the Shutdown submenu, the "Suspend" button - and *only* the Suspend button - does not respond to mouse clicks. I cannot use it to suspend the system with either the touchpad or an external mouse. The other buttons in that menu respond to mouse clicks, and the Suspend button responds when I use the touchscreen to tap it. I've attached a screencast in an attempt to demonstrate this (although it obviously doesn't show when I'm actually clicking the mouse). This behaviour has been going on for a while, at least the whole Mantic cycle, but maybe longer. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 09:21:31 2024 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-26 (949 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.2-0ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-22 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2051738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Thank you for taking the time to report this bug and helping to make Ubuntu (Studio) better. @Bluesbrother (or the original posted to askubu..) Can you please add what your installation media was, ie. `cat /var/log/installer/media-info` as your original post on askubu implies you release-upgraded to noble, and thus this issue may only occur on upgrades, rather than fresh installs. Ideally an `apport-collect` would gather this (& more details), but you aren't the original report of this bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Confirmed Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on Launchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2051313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : http
[Desktop-packages] [Bug 2051116] [NEW] How to fix Libmtp panic?
Public bug reported: I have been asked to report this by GAD3R. My original question to askubuntu on 23-1-2024 was titled "How to fix 'Unable to open mtp device "xxx,yyy"' but the title has been changed somehow to the above. My original question was: "This is a question which seems to have been asked many times - mostly between 5 and ten years ago. I still have had this intermittently (as do others I see with a variety of phones, computers and ubuntu versions) trying to connect my Nokia 3.4 to my Dell based Ubuntu 22.04. Usually a disconnect/reconnect of the cable makes it work. However, there was one period last September when I could not get it to work at all. I simply gave up for a few weeks until it suddenly started working again - Yippee! - Until this week, when it has failed again. I strongly suspect there is some update somewhere which is causing this on/off behaviour. I've tried different USB ports and cables. Running gmtp makes no difference - it says 'No device attached' - despite my phone showing up in my file manager etc AND gmtp (wrongly) recognising it as a Nexus/Pixel as below! I have obviously looked at many other threads and sources to try and sort this out and I see that the most often responses are for the outputs of lsusb and mtp-detect to be posted so, here are mine: $ lsusb Bus 001 Device 005: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 001 Device 004: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 001 Device 038: ID 18d1:4ee2 Google Inc. Nexus/Pixel Device (MTP + debug) Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ mtp-detect libmtp version: 1.1.19 Listing raw device(s) Device 0 (VID=18d1 and PID=4ee2) is a Google Inc Nexus/Pixel (MTP+ADB). Found 1 device(s): Google Inc: Nexus/Pixel (MTP+ADB) (18d1:4ee2) @ bus 1, dev 12 Attempting to connect device(s) LIBMTP PANIC: Unable to find interface & endpoints of device Unable to open raw device 0 OK. Interesting that my device is listed as a Nexus/Pixel - which it is not! It would be really nice to get a definitive, permanent 'fix' for this ongoing problem." The first answer I received was as follows: "mtp, lsusb... use the PCIID to identify the connected devices, in your case VID=18d1 , PID=4ee2 is known as Nexus/Pixel Device (MTP + debug) To update the PCIID database list use: sudo update-pciids. Other way to mount your device: install jmtpfs: sudo apt install jmtpfs mkdir devicemnt sudo chown $USER:$USER devicemnt jmtpfs -o allow_other devicemnt/ ls devicemnt To unmount: fusermount -u devicemnt" My response was: "Thanks for the response. running mtp prompted me to install ferret-vis - which I did. lsusb then ran as before but updating the pciids achieved still the same error as before. Using the second scenario, all went well until I got: $ jmtpfs devicement/ Device 0 (VID=18d1 and PID=4ee2) is a Google Inc Nexus/Pixel (MTP+ADB). LIBMTP PANIC: Unable to find interface & endpoints of device terminate called after throwing an instance of 'MtpErrorCantOpenDevice' what(): Can't open device Aborted (core dumped) - so I'm still stuck. thanks again anyway." Also, running 'mtp' now invites me to use 'Fprint'...? For the record, using Ubuntu 22.04.3 LTS (with any file management package) Chris ** Affects: libmtp (Ubuntu) Importance: Undecided Status: New ** Tags: connection libmtp mtp usb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/2051116 Title: How to fix Libmtp panic? Status in libmtp package in Ubuntu: New Bug description: I have been asked to report this by GAD3R. My original question to askubuntu on 23-1-2024 was titled "How to fix 'Unable to open mtp device "xxx,yyy"' but the title has been changed somehow to the above. My original question was: "This is a question which seems to have been asked many times - mostly between 5 and ten years ago. I still have had this intermittently (as do others I see with a variety of phones, computers and ubuntu versions) trying to connect my Nokia 3.4 to my Dell based Ubuntu 22.04. Usually a disconnect/reconnect of the cable makes it work. However, there was one period last September when I could not get it to work at all. I simply gave up for a few weeks until it suddenly started working again - Yippee! - Until this week, when it has failed again. I strongly suspect there is some update somewhere which is causing thi
[Desktop-packages] [Bug 2022073] Re: Font/Character Rendering Issue
the affected address is hosted locally not publicly available... i've re-attached the image ** Attachment added: "ubuntu-chromium-snap-font-bug.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2022073/+attachment/5741780/+files/ubuntu-chromium-snap-font-bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2022073 Title: Font/Character Rendering Issue Status in chromium-browser package in Ubuntu: New Bug description: I've been building some single purpose kiosks using Ubuntu server on RaspberyPis (models 3 and 4). It's a minimal build that uses matchbox- window-manager and chromium in kiosk mode. Prior to 22.04 we had no issues (see 'correct font' link). Building new Pi images from a base 22.04 install I'm encountering these font issues. My process is pretty simple. We use the RaspberryPi Imager to create the base install, then update && upgrade. After that we have some scripts to install our packages and some configurations files to auto login and run our xinit script at the end of .bashrc to open the webpage. Everything is working fine except for this issue with the font. From what I can tell the specific font in the css of the webpage is not installed, but sans-serif is the fallback in the css code and that appears to be used, but it is just rendering wierd. Looking for similar issues online I have tried to refresh the font cache but not much else comes up. I've managed to install chrome (proper) from the debian stable repository and have no issues. This is not an ideal workaround due to other issues that will surely arise. I am attaching an image with 3 screen clips (2 buggy font renders and 1 correct from an older build that doesn't have this issue). ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: User Name 5.15.0-1029.31-raspi 5.15.98 Uname: Linux 5.15.0-1029-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: arm64 CasperMD5CheckResult: unknown Date: Thu Jun 1 09:41:58 2023 ImageMediaBuild: 20230217.1 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Snap: chromium 113.0.5672.126 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 5Error 2023-05-22T16:39:36-04:00 2023-06-01T09:18:39-04:00 Auto-refresh snaps "chromium", "snapd" 7Done2023-06-01T09:19:28-04:00 2023-06-01T09:20:47-04:00 Auto-refresh snap "chromium" SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2022073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network
Is there any movement on this issue? I am having the same problem if I don't remove Airprint capabilities from all my network printers. I can't do that because if I do iOS devices can't print. Does anyone have any other ideas? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups package in Ubuntu: Triaged Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1753509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048438] Re: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2048438 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2048438 Title: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop Status in xwayland package in Ubuntu: New Bug description: I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated GPU. I installed Ubuntu 23.10, and it defaults to using Wayland and connected it to an external Dell Dell P2720D monitor via HDMI. The UI under Settings > Displays then "Mirror", the default setting works, and I see the display duplicated as expected, with the large external monitor having a low resolution limited to that of the laptop. But if I switch to "Join" does not allow to Apply with message: > Changes Cannot be Applied. This could be due to hardware limitations. Logging off and changing to X allows "Join" to work, so it is a Wayland issue. Is there a way to make it work on Wayland? Mostly out of morbid curiosity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2048438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048441] Re: Firefox cannot save/read a credit card number
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2048441 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/2048441 Title: Firefox cannot save/read a credit card number Status in firefox package in Ubuntu: New Bug description: Firefox has a functionality to save and auto-fill credit cards. Saving can be done when entering the information of a card in a web page, or in Settings/Privacy & Security/Saved Credit Cards. Currently, with Kubuntu's version of Firefox 118.0.2, nothing happens when saving. In the "Browser Console" of Firefox, when saving from the Settings menu, I get the following message: NS_ERROR_ABORT: User canceled OS unlock entry encrypt resource://gre/modules/OSKeyStore.sys.mjs:320 editDialog.js:232:15 If the same is done with the non-snap version downloaded from Mozilla, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047802] [NEW] [Precision 7780, Realtek ALC289, Black Headphone Out, Right] Headphone not used when connected during boot
Public bug reported: When the headphone is connected before the computer is booted the sound is played on the speakers and not on the headphone. When I remove the headphone and insert it back, the sound then switches correctly to the headphone. => This seems to be an boot / initialization issue, because generally the hardware does work $ lsb_release -rd Description:Ubuntu 22.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cm 2246 F pulseaudio /dev/snd/controlC1: cm 2246 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jan 2 08:04:24 2024 InstallationDate: Installed on 2023-08-26 (128 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Precision 7780, Realtek ALC289, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2023 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0342YC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd11/13/2023:br1.8:efr1.6:svnDellInc.:pnPrecision7780:pvr:rvnDellInc.:rn0342YC:rvrA00:cvnDellInc.:ct10:cvr:sku0C42: dmi.product.family: Precision dmi.product.name: Precision 7780 dmi.product.sku: 0C42 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kernel-sound ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2047802 Title: [Precision 7780, Realtek ALC289, Black Headphone Out, Right] Headphone not used when connected during boot Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When the headphone is connected before the computer is booted the sound is played on the speakers and not on the headphone. When I remove the headphone and insert it back, the sound then switches correctly to the headphone. => This seems to be an boot / initialization issue, because generally the hardware does work $ lsb_release -rd Description:Ubuntu 22.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cm 2246 F pulseaudio /dev/snd/controlC1: cm 2246 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jan 2 08:04:24 2024 InstallationDate: Installed on 2023-08-26 (128 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Precision 7780, Realtek ALC289, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2023 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0342YC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd11/13/2023:br1.8:efr1.6:svnDellInc.:pnPrecision7780:pvr:rvnDellInc.:rn0342YC:rvrA00:cvnDellInc.:ct10:cvr:sku0C42: dmi.product.family: Precision dmi.product.name: Precision 7780 dmi.product.sku: 0C42 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2047802
[Desktop-packages] [Bug 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2
Hello Daniel, or anyone else affected, Accepted mutter into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- 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/2046360 Title: Heavy stuttering in Firefox with mutter 45.1/45.2 Status in mutter package in Ubuntu: New Status in mutter source package in Mantic: Fix Committed Bug description: There is heavy stuttering visible in Firefox with mutter 45.1/45.2. This is a regression introduced upstream in mutter 45.1 (8f27ebf8), although it only hurts the triple buffering patch so that's where it's fixed: https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689 https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45 [ Workaround ] In /etc/environment: MUTTER_DEBUG_TRIPLE_BUFFERING=always or "never" also works. Just not "auto". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2046360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045980] [NEW] AppArmor config denies 'k' access to suggest.sqlite-shm
Public bug reported: This occurs in the ESR builds from ppa:mozillateam/ppa. My dmesg log is filled with lines such as: [ 3015.575852] audit: type=1400 audit(1702042069.563:12459): apparmor="DENIED" operation="file_lock" class="file" profile="firefox" name="/home/chris/.cache/mozilla/firefox/pws2qa7b.default/suggest.sqlite- shm" pid=25154 comm=4267494F5468727E506F6F6C202332 requested_mask="k" denied_mask="k" fsuid=1000 ouid=1000 Possibly relatedly, a number of sites would start to load and then freeze. At times they would allow scrolling but not clicking or typing, or the tab throbber would keep going. Closing firefox required a SIGTERM to fully shut down, while these requests continued to be made. Looking through the AppArmor profile, there was a line: owner @{HOME}/.{firefox,mozilla}/**/*.{db,parentlock,sqlite}* k, I added the following to /etc/apparmor.d/local/usr.bin.firefox: owner @{HOME}/.cache/mozilla/firefox/**/*.sqlite* k, This definitely resolves the dmesg issue, and it seems to be resolving the intermittent hanging issue. Reloading the apparmor profile without restarting firefox seems to have been successful. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor esr -- 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/2045980 Title: AppArmor config denies 'k' access to suggest.sqlite-shm Status in firefox package in Ubuntu: New Bug description: This occurs in the ESR builds from ppa:mozillateam/ppa. My dmesg log is filled with lines such as: [ 3015.575852] audit: type=1400 audit(1702042069.563:12459): apparmor="DENIED" operation="file_lock" class="file" profile="firefox" name="/home/chris/.cache/mozilla/firefox/pws2qa7b.default/suggest.sqlite- shm" pid=25154 comm=4267494F5468727E506F6F6C202332 requested_mask="k" denied_mask="k" fsuid=1000 ouid=1000 Possibly relatedly, a number of sites would start to load and then freeze. At times they would allow scrolling but not clicking or typing, or the tab throbber would keep going. Closing firefox required a SIGTERM to fully shut down, while these requests continued to be made. Looking through the AppArmor profile, there was a line: owner @{HOME}/.{firefox,mozilla}/**/*.{db,parentlock,sqlite}* k, I added the following to /etc/apparmor.d/local/usr.bin.firefox: owner @{HOME}/.cache/mozilla/firefox/**/*.sqlite* k, This definitely resolves the dmesg issue, and it seems to be resolving the intermittent hanging issue. Reloading the apparmor profile without restarting firefox seems to have been successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045753] Re: Ubuntu stuck on the boot screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2045753 Title: Ubuntu stuck on the boot screen Status in xorg package in Ubuntu: New Bug description: I'm using nomodeset option as a workaround, but I'd prefer a permanent solution. I have no idea what I'm doing, so if I'm not specific enough, just ask. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.5.0-060500-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 11:42:55 2023 DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed bbswitch/0.8, 6.5.0-14-generic, x86_64: installed nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:8537] InstallationDate: Installed on 2020-05-20 (1295 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7 nomodeset RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg UpgradeStatus: Upgraded to mantic on 2023-10-18 (49 days ago) dmi.bios.date: 04/27/2020 dmi.bios.release: 11.1 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8537 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD0097RK4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 81.42 dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:br11.1:efr81.42:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:sku5PQ09EA#AKD: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G6 dmi.product.sku: 5PQ09EA#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2045753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Ah, jbicha had already retriggered the autopkgtests, and they now pass. Huzzah! -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Released Status in evince source package in Jammy: Fix Released Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Retriggered the autopkgtest to use the correct apparmor version; let's see if that fixes things. -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: Fix Committed Status in apparmor source package in Lunar: Fix Released Status in evince source package in Lunar: Fix Released Status in apparmor package in Debian: Fix Released Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044157] [NEW] Firefox 120.0+build2-0ubuntu0.18.04.1~mt1 - Unity Global Menu Missing
Public bug reported: Upon upgrade from Firefox 119 to 120 noticed that the Unity Global Menu no longer works. Rolling back the package to 119 and installing FireFox ESR global menu works as expected. This is the package that is on the mozillateam PPA. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2044157 Title: Firefox 120.0+build2-0ubuntu0.18.04.1~mt1 - Unity Global Menu Missing Status in firefox package in Ubuntu: New Bug description: Upon upgrade from Firefox 119 to 120 noticed that the Unity Global Menu no longer works. Rolling back the package to 119 and installing FireFox ESR global menu works as expected. This is the package that is on the mozillateam PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2044157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
OOoooh, right. This is releasable, and has a sensible changelog, it's just that LP isn't showing the full changes file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug description: [ Impact ] * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production. In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production. NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product. We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts. [ Test Plan ] * Steps to make sure it works: 1. pick a cutting edge nvidia graphic. 2. remove nv-525 from the pool by removing restricted in jammy-updates and jammy-security 3. check the nv support status: ``` $ ubuntu-drivers list oem-fix-gfx-nvidia-ondemandmode libfprint-2-tod1-broadcom oem-somerville-cinccino-meta ``` 4. modify custom file ``` $ cat /etc/custom_supported_gpus.json { "chips": [ { "devid": "0x24BA", "name": "TEST 24BA", "branch": "580.1234", "features": [ "runtimepm" ] }, { "devid": "0x25BC", "name": "TEST 25BC", "branch": "510", "features": [ "runtimepm" ] } ] } ``` 5. make sure the hook works ``` $ ubuntu-drivers list nvidia-driver-510, (kernel modules provided by nvidia-dkms-510) oem-fix-gfx-nvidia-ondemandmode libfprint-2-tod1-broadcom oem-somerville-cinccino-meta [ Where problems could occur ] * This feature only impact target system has a custom file "/etc/custom_supported_gpus.json". And it won't generate automatically which should not impact normal users [ Other Info ] * the patches are picked from - https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3 - https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115 - https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b. * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042972] Re: Display perfomance issue
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. A support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2042972 Title: Display perfomance issue Status in xorg package in Ubuntu: New Bug description: After booting, sometimes I am not able to quickly open apps, it takes more than 5 mins to launch and in most of them dark mode is not shown. It used to come back to normal but now it stays the same. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 00:11:58 2023 DistUpgraded: Fresh install DistroCodename: mantic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-H GT1 [UHD Graphics] [1043:13fc] NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA107M [GeForce RTX 3050 Mobile] [1043:13fc] InstallationDate: Installed on 2023-10-29 (9 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic root=UUID=5188fb64-a6dc-4300-a704-0666d8ca03ba ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2023 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FX506HCB.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506HCB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.11 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX506HCB.313:bd03/03/2023:br5.19:efr3.11:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506HCB_FX506HCB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506HCB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506HCB_FX506HCB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040077] Re: Drop-down calendar not drawn correctly when clicking into next month.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2040077 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2040077 Title: Drop-down calendar not drawn correctly when clicking into next month. Status in gnome-shell package in Ubuntu: New Bug description: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040068] Re: Can't connect my Synology NAS from Ubuntu 22.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2040068 Title: Can't connect my Synology NAS from Ubuntu 22.04 Status in gvfs package in Ubuntu: New Bug description: I purchased a Synology DS723+ NAS (under DSM 7.2-64570). I access it without any problem from a Huawei MateBook 14s running Ubuntu 22.04. I can't do it, however, from an Acer Swift 5 also running Ubuntu 22.04. Seen from this PC, I get the following message: "Unable to access location Failed to get list of shares from server: Invalid argument." When I look at my NAS log, the connection attempt gives the following message: "Host [192.168.1.22] failed to connect via [SMB] due to [SMB1 not permitted]." While the message obtained after a successful connection with the other PC is the following: "User [xxx] from [xxx(192.168.1.36)] via [CIFS(SMB3)] accessed shared folder [Photos]." I tried to compare the differences between the 2 PCs running Ubuntu 22.04 without success. Samba was not initially installed on the Acer Swift 5 initially, but the installation did not correct the problem. After reading different posts, I understand that the SMB1 connection is disabled by default since Ubuntu 20.04: I therefore do not understand why the Acer Swift 5 seems to connect like that. And when I run "journalctl -f" on my Acer and then try to connect to the NAS, here is what I get: oct. 09 21:56:32 xxx gvfsd[9205]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. oct. 09 21:56:47 xxx gvfsd[9205]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 18:06:52 2023 InstallationDate: Installed on 2020-02-21 (1337 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: Upgraded to jammy on 2022-09-04 (412 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2040068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039711] Re: Unable to use Wayland
I have multiple crash files: _opt_brave.com_brave_brave.1000.crash _usr_bin_gjs-console.1000.crash _usr_lib_xorg_Xorg.0.crash _opt_Signal_signal-desktop.1000.crash _usr_libexec_goa-daemon.1000.crash 2. I have run the ubuntu-bug command against each (xorg required sudo due to being owned by root), each popped up with a bug submission, so I sent it, but was not provided with any bug IDs. How do I retrieve these? I assume the contents inside the .uploaded files: 0e5027b2-6cfe-11ee-9aee-fa163ec44ecd 7bb73989-6d05-11ee-9aee-fa163ec44ecd c93998ea-6d12-11ee-9aee-fa163ec44ecd 25a6-6dd2-11ee-9aef-fa163ec44ecd 06d5f3dc-6e29-11ee-9af3-fa163ec44ecd 3. https://errors.ubuntu.com/oops/0e5027b2-6cfe-11ee-9aee-fa163ec44ecd https://errors.ubuntu.com/oops/7bb73989-6d05-11ee-9aee-fa163ec44ecd https://errors.ubuntu.com/oops/6df4c856-6d0d-11ee-b845-fa163e171f02 https://errors.ubuntu.com/oops/0d81f9c2-6d11-11ee-b846-fa163e171f02 https://errors.ubuntu.com/oops/25a6-6dd2-11ee-9aef-fa163ec44ecd https://errors.ubuntu.com/oops/06d5f3dc-6e29-11ee-9af3-fa163ec44ecd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2039711 Title: Unable to use Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: Purged ubuntu-desktop and gdm3 completely and reinstalled. Unable to login with Wayland, after about a minute or so of giving credentials for login, the login prompt reappears. X11 works, but takes about 3 minutes to actually load to desktop. Started two days ago after an update (I presume is the cause). If I move .config from home directory, I am able to login to both again but will break within a few hours ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 12:05:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-08 (251 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/gnome-shell/+bug/2039711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039711] Re: Unable to use Wayland
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039711/+attachment/5710996/+files/prevjournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2039711 Title: Unable to use Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: Purged ubuntu-desktop and gdm3 completely and reinstalled. Unable to login with Wayland, after about a minute or so of giving credentials for login, the login prompt reappears. X11 works, but takes about 3 minutes to actually load to desktop. Started two days ago after an update (I presume is the cause). If I move .config from home directory, I am able to login to both again but will break within a few hours ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 12:05:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-08 (251 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/gnome-shell/+bug/2039711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039711] Re: Unable to use Wayland
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039711/+attachment/5710995/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2039711 Title: Unable to use Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: Purged ubuntu-desktop and gdm3 completely and reinstalled. Unable to login with Wayland, after about a minute or so of giving credentials for login, the login prompt reappears. X11 works, but takes about 3 minutes to actually load to desktop. Started two days ago after an update (I presume is the cause). If I move .config from home directory, I am able to login to both again but will break within a few hours ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 12:05:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-08 (251 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/gnome-shell/+bug/2039711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2039711] [NEW] Unable to use Wayland; Long login times for X11
Public bug reported: Purged ubuntu-desktop and gdm3 completely and reinstalled. Unable to login with Wayland, after about a minute or so of giving credentials for login, the login prompt reappears. X11 works, but takes about 3 minutes to actually load to desktop. Started two days ago after an update (I presume is the cause). If I move .config from home directory, I am able to login to both again but will break within a few hours ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 12:05:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-08 (251 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: Purged ubuntu-desktop and gdm3 completely and reinstalled. Unable to login with Wayland, after about a minute or so of giving credentials for login, the login prompt reappears. X11 works, but takes about 3 minutes to actually load to desktop. Started two days ago after an update (I presume is the cause). - If I move .config from home directory, I am able to login to both a + If I move .config from home directory, I am able to login to both again + but will break within a few hours ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 12:05:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-08 (251 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2039711 Title: Unable to use Wayland; Long login times for X11 Status in gnome-shell package in Ubuntu: New Bug description: Purged ubuntu-desktop and gdm3 completely and reinstalled. Unable to login with Wayland, after about a minute or so of giving credentials for login, the login prompt reappears. X11 works, but takes about 3 minutes to actually load to desktop. Started two days ago after an update (I presume is the cause). If I move .config from home directory, I am able to login to both again but will break within a few hours ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 12:05:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-08 (251 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/gnome-shell/+bug/2039711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
It seems that it's already been retried once in the main archive. I note that your PPA builds *without* -proposed enabled, whereas the archive will build *with* -proposed enabled - possibly this is why it fails in the archive and succeeds in your PPA? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug description: [ Impact ] * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production. In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production. NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product. We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts. [ Test Plan ] * Steps to make sure it works: 1. pick a cutting edge nvidia graphic. 2. remove nv-525 from the pool by removing restricted in jammy-updates and jammy-security 3. check the nv support status: ``` $ ubuntu-drivers list oem-fix-gfx-nvidia-ondemandmode libfprint-2-tod1-broadcom oem-somerville-cinccino-meta ``` 4. modify custom file ``` $ cat /etc/custom_supported_gpus.json { "chips": [ { "devid": "0x24BA", "name": "TEST 24BA", "branch": "580.1234", "features": [ "runtimepm" ] }, { "devid": "0x25BC", "name": "TEST 25BC", "branch": "510", "features": [ "runtimepm" ] } ] } ``` 5. make sure the hook works ``` $ ubuntu-drivers list nvidia-driver-510, (kernel modules provided by nvidia-dkms-510) oem-fix-gfx-nvidia-ondemandmode libfprint-2-tod1-broadcom oem-somerville-cinccino-meta [ Where problems could occur ] * This feature only impact target system has a custom file "/etc/custom_supported_gpus.json". And it won't generate automatically which should not impact normal users [ Other Info ] * the patches are picked from - https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3 - https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115 - https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b. * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
Gunnar asked > But this makes me wonder if there is a need to special case other flavors besides MATE. I've noted a number of users report 'garbled' or 'unreadable' text on discord (testing-cycles) & Ubuntu-MATE discourse (#1) but one of those reports led us back here, alas I'm not aware of any beyond Jim Markus who've actually followed up with an actual bug report, and I can't provide any useful info. I have run a test looking for this issue specifically with Lubuntu (lunar -> mantic) and did NOT experience an issue on a virtualbox VM. Links shouldn't be necessary; but included anyway #1: https://ubuntu-mate.community/t/ubuntu-mate-23-10-testing/26876/11 #2: http://iso.qa.ubuntu.com/qatracker/milestones/446/builds/282097/testcases/1310/results -- 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/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Triaged Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Triaged Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038717] Re: Built-in speackers don't sound
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- 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/2038717 Title: Built-in speackers don't sound Status in pulseaudio package in Ubuntu: New Bug description: Built-in speackers don't produce any sound in HP Envy, although the system settings and pavucontrol detect them and the sound is displayed in the sound bars. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 10:49:46 2023 InstallationDate: Installed on 2023-04-12 (177 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2023 dmi.bios.release: 15.20 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8A2C dmi.board.vendor: HP dmi.board.version: 23.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.43 dmi.modalias: dmi:bvnInsyde:bvrF.20:bd04/13/2023:br15.20:efr23.43:svnHP:pnHPENVYLaptop16-h0xxx:pvrType1ProductConfigId:rvnHP:rn8A2C:rvr23.43:cvnHP:ct10:cvrChassisVersion:sku6H668EA#ABE: dmi.product.family: 103C_5335M8 HP ENVY dmi.product.name: HP ENVY Laptop 16-h0xxx dmi.product.sku: 6H668EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2038717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028082] Re: Update glib to 2.76.4
Hello Jeremy, or anyone else affected, Accepted glib2.0 into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.76.4-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2030959] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: Fix Released Bug description: [ Impact ] Cursor sometimes stutters after heavy shell animations in 42.9 if there is no GUI animation in response to its movement. And it doesn't stop stuttering until GUI redraws occur (giving the frame clock an opportunity to measure lower GPU usage). This is different to the recent bug fix that probably caused it: Bug 2023766: * only occurs when moving over animated GUIs. * never recovers or corrects itself. * was spatial jittering at full frame rate. * reduced the frame rate of the GUI below it. This bug: * only occurs when moving over non-animated GUIs. * does recover and correct itself. * is stuttering at seemingly half frame rate, but perfect spatially. * does not reduce the frame rate of the the GUI below. I think the reason we only see this in 42 (jammy) is because that predates the change in the triple buffering algorithm to scale based on "dynamic max render time" alone. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and then reboot. [ Test Plan ] 1. Stress GNOME Shell maximally by repeatedly entering/leaving the overview and/or scrolling the app grid. 2. Stop suddenly and wiggle the mouse over some part of the desktop that DOES NOT respond to mouse movement. Such as the wallpaper or some blank grey space next to the app grid. Expect: The mouse cursor does not get stuck in half frame rate. [ Where problems could occur ] In desktop frame timing since the clutter frame clock is being changed. Although risk is minimal since we're just reverting to the pre-July state of that code. [ Other Info ] The patch being dropped was found to not really be required in GNOME 42: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/comments/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
gdm3 looks good to me, but I haven't accepted it yet as it depends on the gnome-settings-daemon patches and I think it's best to resolve those questions before accepting gdm3 into -proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: Incomplete Status in sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm- smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
> Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. Do I read the gnome-settings-daemon patches correctly, and this actually just entirely drops support for auth via NSS? So the regression potential is that if someone has set up auth via a custom system nss database, this *will* break login for them? (Unrelatedly, patches like smartcard-Use-autopointers.patch and smartcard-manager-Use-mutex-auto-lockers-when-convenient.patch are the sort of refactoring patches that we prefer not to see in SRUs. I don't think they're a blocker, but they make reviewing more difficult) ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in GNOME Settings Daemon: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Fix Released Status in gdm3 source package in Focal: In Progress Status in gnome-settings-daemon source package in Focal: Incomplete Status in sssd source package in Focal: In Progress Status in gdm3 package in Debian: Fix Released Bug description: [ Impact ] the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. [ Test case ] 1. When in GDM, insert a smartcard 2. The GDM interface should require for an user 3. The user should be set (or empty may be provided, depending on sssd configuration) 4. The smartcard PIN should be requested and once introduce the user must login. Note that this requires configuring sssd before, a simple local configuration could require having sssd.conf filled with: ```ini [sssd] enable_files_domain = True services = pam [certmap/implicit_files/$USER] matchrule = .*YOUR CARD IDENTIFIER* [pam] pam_cert_auth = True ``` The UI authentication can also be simulated via pamtester: # Must be ran as user sudo apt install pamtester pamtester -v gdm-smartcard $USER authenticate Expected output is + pamtester -v gdm-smartcard ubuntu authenticate pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...) pamtester: performing operation - authenticate PIN for Test Organization Sub Int Token: pamtester: successfully authenticated --- Alternatively, if no smartcard or hardware is available, this can be tested and simulated using these scripts (they will reset the system setup at each run, but it's suggested to run them in a VM, lxd container or in a test installation): https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \ sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh - wget https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh The script will generate some fake CA authority, issue some certificates, will install them in some software-based smartcards (using softhsm2) and test that they work properly to login with gdm- smartcard. Using `WAIT` environment variable set (to any value) will make it to restart gdm at each iteration so that an user can try to access, using the username that launched the script and the pin of 123456. [ Regression potential ] Smartcard authentication using custom methods using via a custom configured system nss database may not work anymore. --- ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://laun
[Desktop-packages] [Bug 2034105] Update Released
The verification of the Stable Release Update for xserver-xorg-video- amdgpu has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: Fix Committed Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Released Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023215] Re: [SRU] appstream-glib can't handle em or code tags, breaking Flathub
Ooof, double oops. That's the *flatpak* version they've described, not the appstream-glib version they've tested. Nathan Teodosio: could you (or someone else) double-check that this is fixed specifically by appstream-glib 0.7.16-1ubuntu2 in Focal? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/2023215 Title: [SRU] appstream-glib can't handle em or code tags, breaking Flathub Status in appstream-glib package in Ubuntu: Fix Released Status in appstream-glib source package in Focal: Fix Committed Status in appstream-glib source package in Jammy: Fix Released Bug description: [ Impact ] * Currently, any application that is using modern AppStream metadata containing / tags in their description, and that is still using the deprecated appstream-glib will fail to parse this data. * Unfortunately, this affects some high-visibility applications now, like Flatpak, which are unable to perform proper searches. See https://github.com/flatpak/flatpak/issues/5434 for reference. * This kind of issue may potentially affect more tools as well. [ Test Plan ] 1. Open a terminal and run sudo apt install flatpak 2. Then run flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo 3. Run flatpak search meld The broken output may look something like: F: Failed to parse /var/lib/flatpak/appstream/flathub/x86_64/active/appstream.xml.gz file: Error on line 1960 char 29: already set ' Organic Maps is a free Android & iOS offline maps app for travelers, tourists, hikers, and cyclists. It uses crowd-sourced OpenStreetMap data and is developed with love by ' and tried to replace with ' (' No matches found 4. Install the updated appstream-glib packages. 5. Restart your computer then log back in. 6. Open a terminal and run flatpak search meld The working output looks something like Name DescriptionApplication ID Version Branch Remotes Meld Compare and merge your files org.gnome.meld 3.22.0 stable flathub [ Where problems could occur ] * The reverse-dependencies for appstream-glib in Ubuntu Jammy are: flatpak-tests unity libmalcontent-ui-0-0 libappstream-glib-dev gir1.2-appstreamglib-1.0 appstream-util flatpak * Flatpak should continue to work, and there should be no new errors in GNOME/Unity. [ Other Info ] * None. Updating this should mainly help Flatpak users and should have no ill effects on any other component of the OS. * This issue was fixed upstream in appstream-glib 0.8.1 which is available in Ubuntu 22.10 and newer releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/2023215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023215] Re: [SRU] appstream-glib can't handle em or code tags, breaking Flathub
Oops! Looks like the last commenter meant to set this into the verification-done state, rather than -failed, as they've got correct output. Fixing and releasing. ** Tags removed: verification-failed-focal verification-needed ** Tags added: verification-done-focal ** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/2023215 Title: [SRU] appstream-glib can't handle em or code tags, breaking Flathub Status in appstream-glib package in Ubuntu: Fix Released Status in appstream-glib source package in Focal: Fix Committed Status in appstream-glib source package in Jammy: Fix Released Bug description: [ Impact ] * Currently, any application that is using modern AppStream metadata containing / tags in their description, and that is still using the deprecated appstream-glib will fail to parse this data. * Unfortunately, this affects some high-visibility applications now, like Flatpak, which are unable to perform proper searches. See https://github.com/flatpak/flatpak/issues/5434 for reference. * This kind of issue may potentially affect more tools as well. [ Test Plan ] 1. Open a terminal and run sudo apt install flatpak 2. Then run flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo 3. Run flatpak search meld The broken output may look something like: F: Failed to parse /var/lib/flatpak/appstream/flathub/x86_64/active/appstream.xml.gz file: Error on line 1960 char 29: already set ' Organic Maps is a free Android & iOS offline maps app for travelers, tourists, hikers, and cyclists. It uses crowd-sourced OpenStreetMap data and is developed with love by ' and tried to replace with ' (' No matches found 4. Install the updated appstream-glib packages. 5. Restart your computer then log back in. 6. Open a terminal and run flatpak search meld The working output looks something like Name DescriptionApplication ID Version Branch Remotes Meld Compare and merge your files org.gnome.meld 3.22.0 stable flathub [ Where problems could occur ] * The reverse-dependencies for appstream-glib in Ubuntu Jammy are: flatpak-tests unity libmalcontent-ui-0-0 libappstream-glib-dev gir1.2-appstreamglib-1.0 appstream-util flatpak * Flatpak should continue to work, and there should be no new errors in GNOME/Unity. [ Other Info ] * None. Updating this should mainly help Flatpak users and should have no ill effects on any other component of the OS. * This issue was fixed upstream in appstream-glib 0.8.1 which is available in Ubuntu 22.10 and newer releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/2023215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session
I attempted an install QA test of Ubuntu Desktop mantic daily (0908.2) on - hp dc7700 (c2d-e6320, 8gb amd/ati rv610/radeon hd2400 pro/xt) I didn't see the installer, briefly got one error message (didn't have time to recognize/read), then screen went white with oh no, something went wrong... and I was kicked from gnome.. I've tagged this bug report, as I got 502 server errors on ubuntu-bug; and looking it looks like this is what I had anyway. -- 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/2034672 Title: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session Status in Mutter: Fix Released Status in mesa package in Ubuntu: In Progress Status in mutter package in Ubuntu: Fix Released Bug description: Mantic 20230907 on Latitude 3320 Crash on boot of the live session ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.482 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 08:02:08 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694028853 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~rc-0ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0 Title: gnome-shell crashed with signal 5 in g_log_structured_array() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2034672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
Hello Kai-Chuan, or anyone else affected, Accepted xserver-xorg-video-amdgpu into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video- amdgpu/22.0.0-1ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034105] Proposed package upload rejected
An upload of xserver-xorg-video-amdgpu to jammy-proposed has been rejected from the upload queue for the following reason: "This looks good, but you've included two slightly different versions of the patch? Please re-upload with just one :)". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2034105 Title: Cursor didn't show up in X session when output from amd dgpu Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Fix Committed Bug description: [ Impact ] * There is no cursor in Xorg session when output from AMD Navi3.x dgpu [ Test Plan ] * Test on the DT with AMD Navi3.x dgpu * Attach external monitor to AMD Navi3.x dgpu * Switch to Xorg session when login * Check if cursor is appeared and works properly [ Where problems could occur ] * The implementation checks DRM_CAP_CURSOR_WIDTH and DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if kernel can't report the caps. * The user might see different cursor size after the patch applied, since the driver will ask kernel for it but not the hard coded one. [ Other Info ] * Upstream commit: https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614 * The patch has been included in mantic and lunar already To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903705] Re: gnome-terminal messes up output when in a large directory and maximize the window
I just did: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/7998 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #7998 https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/7998 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1903705 Title: gnome-terminal messes up output when in a large directory and maximize the window Status in gnome-terminal package in Ubuntu: New Bug description: when I "cd" to a directory with a large name, let's say 100 chars, and maximize and demaximize the window, new rows are inserted and also some output is missing. in every repetition the problem becomes worse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 13:00:47 2020 InstallationDate: Installed on 2020-05-03 (190 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1903705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028780] [NEW] 116.0+build1-0ubuntu0.18.04.1~mt1 Unity Global Menu Missing
Public bug reported: This package is on the Mozillateam PPA and affects Bionic. The update from 115 to 116 appears to have broken the Unity Menu bar patch again. I noticed in the previous incident that this is an unsupported build. Going forward should PPA issues still be reported here or should they be submitted elsewhere? The same testing as the previous incident confirms that it is exclusive to the new deb package. Previous Incident https://bugs.launchpad.net/bugs/2025299 Description: Please accept my apologies if this is the incorrect place to submit this bug. Using Ubuntu 18.04 ESR (Unity Desktop). Upon upgrade from Firefox 114 to 115 noticed that the Unity Global Menu no longer works. Rolling back the package to 114 and installing 102.12 ESR global menu works as expected. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ppa -- 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/2028780 Title: 116.0+build1-0ubuntu0.18.04.1~mt1 Unity Global Menu Missing Status in firefox package in Ubuntu: New Bug description: This package is on the Mozillateam PPA and affects Bionic. The update from 115 to 116 appears to have broken the Unity Menu bar patch again. I noticed in the previous incident that this is an unsupported build. Going forward should PPA issues still be reported here or should they be submitted elsewhere? The same testing as the previous incident confirms that it is exclusive to the new deb package. Previous Incident https://bugs.launchpad.net/bugs/2025299 Description: Please accept my apologies if this is the incorrect place to submit this bug. Using Ubuntu 18.04 ESR (Unity Desktop). Upon upgrade from Firefox 114 to 115 noticed that the Unity Global Menu no longer works. Rolling back the package to 114 and installing 102.12 ESR global menu works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2028780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966167] Update Released
The verification of the Stable Release Update for yaru-theme has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in yaru-theme source package in Jammy: Fix Released Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979037] Update Released
The verification of the Stable Release Update for yaru-theme has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1979037 Title: Monitor numbers are almost invisible in an Ubuntu/Yaru session Status in Yaru Theme: New Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in yaru-theme source package in Jammy: Fix Released Bug description: [ Impact ] Monitor numbers (displayed in the top left corner of each screen while in the Screen Display settings) are almost invisible in an Ubuntu/Yaru session. But they are big and bold in a GNOME (Adwaita) session. Both using Wayland. [ Test case ] Run: env XDG_RUNTIME_DIR=/tmp/.test.runtime XDG_SESSION_TYPE=wayland \ MUTTER_DEBUG_NUM_DUMMY_MONITORS=2 \ GNOME_SHELL_SESSION_MODE=ubuntu \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode In the nested shell, open Settings, go to Display panel The display OSDs should properly show Now repeat on the Appearance panel too [ Regression potential ] Nothing really, other OSDs may have wrong theming, but it's basically impossible To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1979037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
** Changed in: archlinux Status: New => Invalid -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: Invalid Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
There's also an askubuntu question about this issue: https://askubuntu.com/questions/1471028/fatalcredentials-cc127 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Relaying the information from https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 as it is not publicly visible: ``` Hmmm this looks like https://bugs.chromium.org/p/chromium/issues/detail?id=1365674#c8 again. I don't know why using clone(CLONE_NEWUSER ...) would return EACCES (which causes the crash). It's not documented to return that error code and I couldn't find anything in 5.19 that would change that. Glibc doesn't seem to change the error code either. We have a spike of crashes here recently (unsurprisingly, most of them on this 5.19.0 -1010-nvidia-lowlatency #10-Ubuntu kernel). I would call this an upstream Ubuntu bug for now. ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992688] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020834] Please test proposed package
Hello Matthew, or anyone else affected, Accepted adsys into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path.
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Hello Matthew, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2~22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy ** Changed in: adsys (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there w
[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
Hello Matthew, or anyone else affected, Accepted adsys into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.9.2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: In Progress Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test- example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.12.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11b
[Desktop-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Update from https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 as it's not public visible: ``` @Reporter, Thanks for filing the Issue. Please find the magic signature & stack trace for the crash id# 8e7f32382b1ddc1c Magic signature : [Assert] sandbox::`anonymous namespace'::CheckCloneNewUserErrno Stack Trace Thread 0 chrome (id: 0x00010cf6)crashedMAGIC SIGNATURE THREADcontent_copy 0x560a0003ddb3(chrome -immediate_crash.h:146)??logging::LogMessage::~LogMessage() 0x560a022d31f7(chrome -logging.cc:1107)??logging::ErrnoLogMessage::~ErrnoLogMessage() 0x560a0619dcdd(chrome -logging.cc:1101)logging::ErrnoLogMessage::~ErrnoLogMessage() 0x560a01a7f08d(chrome -check.cc:198)??logging::CheckError::~CheckError() 0x560a0735454a(chrome -credentials.cc:126)sandbox::(anonymous namespace)::CheckCloneNewUserErrno(int) 0x560a01f159fc(chrome -credentials.cc:280)sandbox::Credentials::CanCreateProcessInNewUserNS() 0x560a01f156ff(chrome -zygote_host_impl_linux.cc:114)content::ZygoteHostImpl::Init(base::CommandLine const&) 0x560a01f0efc4(chrome -content_main_runner_impl.cc:382)content::(anonymous namespace)::InitializeZygoteSandboxForBrowserProcess(base::CommandLine const&) 0x560a01f0efc4(chrome -content_main_runner_impl.cc:1033)content::ContentMainRunnerImpl::Initialize(content::ContentMainParams) 0x560a0204a6bd(chrome -content_main.cc:301)content::RunContentProcess(content::ContentMainParams, content::ContentMainRunner*) 0x560a0204a6bd(chrome -content_main.cc:343)content::ContentMain(content::ContentMainParams) 0x560a020487ff(chrome -chrome_main.cc:187)ChromeMain 0x7f29a5029d8f(libc.so.6 + 0x00029d8f) 0x7f29a5f4c03f(ld-linux-x86-64.so.2 + 0x0003a03f) 0x7f29a5029e3f(libc.so.6 + 0x00029e3f) 0x560a033991c9(chrome + 0x05c281c9)_start 0x7ffc8a640b07 As per crash ID (8e7f32382b1ddc1c) adding Internals>Core [...] ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I did an check and can confirm that the chromium-browser as installed by the usual 22.04 package is *NOT* affected. But Google chrome well as google-chrome-beta installed by the PPA deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main do show the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
Today apt want's to update my nvidia driver from 510.108.03-0ubuntu0.22.04.1 to 525.125.06-0ubuntu0.22.04.1 Based on the bad experience of the unwanted kernel update I'm not sure whether I should take the risk. Hopefully one of the maintainers reacts to this bug soon and gives more advice about how to solve the issue and clean up the system -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
When booting just select an older kernel - and hope that the maintainers are quickly cleaning the mess -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Coming back to this report here: as expected but now confirmed: when I boot the old kernel everything is working normally. So the cause is *confirmed* to be the different/upgraded kernel that was installed without my request (as described in https://bugs.launchpad.net/ubuntu/+source/linux-signed- nvidia-5.19/+bug/2025538 ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I just checked the chromium bug tracker: the link is valid, but it is flagged as "Only users with EditIssue permission or issue reporter may view.". I guess it's caused by being created from an uploaded crash report. Probably due to privacy considerations as the crash dump might contain private information. There's also no way that I can change the permissions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in chromium-browser package in Ubuntu: Confirmed Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp