[Desktop-packages] [Bug 2046150] Re: [BPO] libreoffice 7.5.9 for jammy
** Description changed: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of - https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.9-0ubuntu0.23.04.1 + https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1776/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231208_175608_c3b14@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231208_135706_f6680@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231208_150850_45529@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2046150 Title: [BPO] libreoffice 7.5.9 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1776/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz * [arm64]
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
The auto-hide "workaround" does not work well in case of machines that are being accessed remotely - then it is next to impossible to trigger the dock to show up. Why is such a simple and reproducible bug still around after such a long time> -- 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/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042909] Re: keyboard backlight slider and automatic brightness causes gnome-shell to freeze (mostly on MacBooks)
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed ** Tags added: fixed-in-gnome-shell-46.beta fixed-upstream -- 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/2042909 Title: keyboard backlight slider and automatic brightness causes gnome-shell to freeze (mostly on MacBooks) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Ubuntu 23.10 Gnome Shell 45.0 I expect gdm and the shell to be responsive but they freeze forcing me to reboot. Sometimes I'm able to use them but it takes some time to load. After taking a look at the journal, I see lots of messages like this: #0 564c4df768c8 i resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48) nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was AsyncReadyCallback(). == Stack trace for context 0x564c4deaab90 == #0 564c4df768c8 i resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48) nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. The offending signal was g-properties-changed on GDBusProxy 0x564c4fec8670. == Stack trace for context 0x564c4deaab90 == On successful boots this seems to auto resolve, being followed by this message: nov 07 09:21:56 perseus dbus-daemon[1758]: [session uid=1000 pid=1758] Successfully activated service 'org.freedesktop.impl.portal.desktop.gnome' nov 07 09:21:56 perseus systemd[1722]: Started xdg-desktop-portal-gnome.service - Portal service (GNOME implementation). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2042909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042909] Re: keyboard backlight slider and automatic brightness causes gnome-shell to freeze (mostly on MacBooks)
** Changed in: gnome-shell Status: New => Fix Released -- 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/2042909 Title: keyboard backlight slider and automatic brightness causes gnome-shell to freeze (mostly on MacBooks) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: Ubuntu 23.10 Gnome Shell 45.0 I expect gdm and the shell to be responsive but they freeze forcing me to reboot. Sometimes I'm able to use them but it takes some time to load. After taking a look at the journal, I see lots of messages like this: #0 564c4df768c8 i resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48) nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was AsyncReadyCallback(). == Stack trace for context 0x564c4deaab90 == #0 564c4df768c8 i resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48) nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. The offending signal was g-properties-changed on GDBusProxy 0x564c4fec8670. == Stack trace for context 0x564c4deaab90 == On successful boots this seems to auto resolve, being followed by this message: nov 07 09:21:56 perseus dbus-daemon[1758]: [session uid=1000 pid=1758] Successfully activated service 'org.freedesktop.impl.portal.desktop.gnome' nov 07 09:21:56 perseus systemd[1722]: Started xdg-desktop-portal-gnome.service - Portal service (GNOME implementation). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2042909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
** Changed in: ubuntu-desktop-installer Importance: Undecided => Unknown -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049555] [NEW] [SOF - sof-bytcht rt5640, playback] fails after a while
Public bug reported: Playing music or watching videos for couple minutes, like on Youtube. Sound will be cracked with long beep. And player will be stopped. But if I reload the page, sound will be resumed again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 16 22:44:25 2024 InstallationDate: Installed on 2024-01-14 (1 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller - Intel HDMI/DP LPE Audio Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Gummi CHT dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/20/2015:br1.10:svnAcer:pnAspireSW3-016P:pvrV1.10:rvnAcer:rnGummiCHT:rvrV1.10:cvnAcer:ct9:cvrChassisVersion:skuAspireSwitch10E_106E_1.10: dmi.product.family: CHT-CR dmi.product.name: Aspire SW3-016P dmi.product.sku: Aspire Switch 10 E_106E_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2049555 Title: [SOF - sof-bytcht rt5640, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Playing music or watching videos for couple minutes, like on Youtube. Sound will be cracked with long beep. And player will be stopped. But if I reload the page, sound will be resumed again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 16 22:44:25 2024 InstallationDate: Installed on 2024-01-14 (1 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller - Intel HDMI/DP LPE Audio Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Gummi CHT dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/20/2015:br1.10:svnAcer:pnAspireSW3-016P:pvrV1.10:rvnAcer:rnGummiCHT:rvrV1.10:cvnAcer:ct9:cvrChassisVersion:skuAspireSwitch10E_106E_1.10: dmi.product.family: CHT-CR dmi.product.name: Aspire SW3-016P dmi.product.sku: Aspire Switch 10 E_106E_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- 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/2044973 Title: ubuntu-drivers install the wrong version of Nvidia driver on some machines Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: During the SRU testing, I found some of machines installed the wrong version of Nvidia driver. They shouldn't install nvidia-driver-535-server-open on a desktop. Please have a look, thanks. If you want to have more information, please let me know. + _run sudo ubuntu-drivers devices + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@10.102.154.51 sudo ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1FB8sv1028sd0906bc03sc02i00 vendor : NVIDIA Corporation model: TU117GLM [Quadro T2000 Mobile / Max-Q] driver : nvidia-driver-535-server - distro non-free driver : nvidia-driver-535 - distro non-free driver : nvidia-driver-418-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-535-server-open - distro non-free recommended driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-525-server - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2044973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines
We discovered the same issue with T1000 cards in a bunch of Dell Precision 3660s. We believe the correct choice should be "nvidia- driver-535", but it recommends "nvidia-driver-535-server-open" instead, which prevents gdm and X from starting. dmesg provides the following error: [ 231.608701] NVRM objClInitPcieChipset: *** Chipset Setup Function Error! [ 233.147366] NVRM: Open nvidia.ko is only ready for use on Data Center GPUs. [ 233.147368] NVRM: To force use of Open nvidia.ko on other GPUs, see the [ 233.147369] NVRM: 'OpenRmEnableUnsupportedGpus' kernel module parameter described [ 233.147369] NVRM: in the README. [ 233.426588] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904) [ 233.426882] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor number 0 [ 235.365019] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904) [ 235.365336] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor number 0 [ 237.455019] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904) [ 237.455443] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor number 0 [ 239.430998] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904) [ 239.431436] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor number 0 [ 241.403724] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904) [ 241.404223] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor number 0 [ 243.384996] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904) [ 243.385389] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor number 0 Here is the output of lspci and ubuntu-drivers devices: shanew@prius:~$ sudo lspci -s 01:00.0 01:00.0 VGA compatible controller: NVIDIA Corporation TU117GL [T1000 8GB] (rev a1) shanew@prius:~$ sudo ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1FF0sv1028sd1612bc03sc00i00 vendor : NVIDIA Corporation driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-535-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-535-server-open - distro non-free recommended driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-535 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2044973 Title: ubuntu-drivers install the wrong version of Nvidia driver on some machines Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: During the SRU testing, I found some of machines installed the wrong version of Nvidia driver. They shouldn't install nvidia-driver-535-server-open on a desktop. Please have a look, thanks. If you want to have more information, please let me know. + _run sudo ubuntu-drivers devices + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@10.102.154.51 sudo ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1FB8sv1028sd0906bc03sc02i00 vendor : NVIDIA Corporation model: TU117GLM [Quadro T2000 Mobile / Max-Q] driver : nvidia-driver-535-server - distro non-free driver : nvidia-driver-535 - distro non-free driver : nvidia-driver-418-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-535-server-open - distro non-free recommended driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-525-server - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2044973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938724] Re: uses aptdaemon
Launchpad is still timing out trying to mark this as a duplicate... and it OOPS'ed when using the API too. ** No longer affects: lubuntu-update-notifier (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1938724 Title: uses aptdaemon Status in apturl package in Ubuntu: New Status in language-selector package in Ubuntu: New Status in oem-config package in Ubuntu: New Bug description: aptdaemon is not a maintained component, please use PackageKit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apturl/+bug/1938724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
** Changed in: ubuntu-desktop-installer Importance: Unknown => Undecided ** Changed in: ubuntu-desktop-installer Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
I used build 20240116 today and was able to install normally. Thank you all! -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049515] [NEW] Import iwd 2.13-1 (universe) from Debian unstable/testing (main)
Public bug reported: A few versions have been released and Ubuntu Noble still has the 2.8 version (2.8-1ubuntu1). Could it be possible to import the latest version from Debian testing fixing a bunch of issues? Debian Changelog: iwd (2.13-1) unstable; urgency=medium [ upstream ] * new release [ Jonas Smedegaard ] * build-depend on systemd-dev (not systemd); closes: bug#1060583, thanks to Michael Biebl * update copyright info: update coverage -- Jonas Smedegaard <> Sun, 14 Jan 2024 09:22:07 +0100 iwd (2.12-1) unstable; urgency=medium [ upstream ] * new release -- Jonas Smedegaard <> Sat, 30 Dec 2023 03:44:28 +0100 iwd (2.11-1) unstable; urgency=medium [ upstream ] * new release -- Jonas Smedegaard <> Fri, 15 Dec 2023 22:28:36 +0100 iwd (2.10-1) unstable; urgency=medium [ upstream ] * new release(s) [ Jonas Smedegaard ] * tighten build-dependency on libell-dev * unfuzz patches -- Jonas Smedegaard <> Thu, 30 Nov 2023 12:08:59 +0100 IWD ChangeLog: ver 2.13: Fix issue with handling netconfig and roaming conditions. Fix issue with logging requirement for CMD_EXTERNAL_AUTH. Fix issue with using OpenSSL 3.2 installations. ver 2.12: Fix issue with DPP extra settings not being used. Fix issue with DPP and PRF+ handling on AARCH64. Add support for SAE password identifiers. ver 2.11: Fix issue with handling iovecs with multiple IEs. Fix issue with handling SAE password identifiers. Fix issue with handling agent release method call. ver 2.10: Fix issue with buffer overflow for 32 byte SSIDs. Fix issue with deauthentication before FT work completes. Fix issue with power save disabling procedure. ver 2.9: Fix issue with handling certain FT failures. Fix issue with handling user-disabled bands. Fix issue with handling roam on beacon loss event. Add support for PKEX configurator. Add support for PKEX enrollee. ** Affects: iwd (Ubuntu) Importance: Undecided Status: New ** Tags: noble upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iwd in Ubuntu. https://bugs.launchpad.net/bugs/2049515 Title: Import iwd 2.13-1 (universe) from Debian unstable/testing (main) Status in iwd package in Ubuntu: New Bug description: A few versions have been released and Ubuntu Noble still has the 2.8 version (2.8-1ubuntu1). Could it be possible to import the latest version from Debian testing fixing a bunch of issues? Debian Changelog: iwd (2.13-1) unstable; urgency=medium [ upstream ] * new release [ Jonas Smedegaard ] * build-depend on systemd-dev (not systemd); closes: bug#1060583, thanks to Michael Biebl * update copyright info: update coverage -- Jonas Smedegaard <> Sun, 14 Jan 2024 09:22:07 +0100 iwd (2.12-1) unstable; urgency=medium [ upstream ] * new release -- Jonas Smedegaard <> Sat, 30 Dec 2023 03:44:28 +0100 iwd (2.11-1) unstable; urgency=medium [ upstream ] * new release -- Jonas Smedegaard <> Fri, 15 Dec 2023 22:28:36 +0100 iwd (2.10-1) unstable; urgency=medium [ upstream ] * new release(s) [ Jonas Smedegaard ] * tighten build-dependency on libell-dev * unfuzz patches -- Jonas Smedegaard <> Thu, 30 Nov 2023 12:08:59 +0100 IWD ChangeLog: ver 2.13: Fix issue with handling netconfig and roaming conditions. Fix issue with logging requirement for CMD_EXTERNAL_AUTH. Fix issue with using OpenSSL 3.2 installations. ver 2.12: Fix issue with DPP extra settings not being used. Fix issue with DPP and PRF+ handling on AARCH64. Add support for SAE password identifiers. ver 2.11: Fix issue with handling iovecs with multiple IEs. Fix issue with handling SAE password identifiers. Fix issue with handling agent release method call. ver 2.10: Fix issue with buffer overflow for 32 byte SSIDs. Fix issue with deauthentication before FT work completes. Fix issue with power save disabling procedure. ver 2.9: Fix issue with handling certain FT failures. Fix issue with handling user-disabled bands. Fix issue with handling roam on beacon loss event. Add support for PKEX configurator. Add support for PKEX enrollee. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/2049515/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Since the discussion is no more only covering Desktop I updated the title (thanks Seb128 for suggesting) ** Summary changed: - Consider removing irqbalance from default install on desktop images + Please consider no more having irqbalance enabled by default (per image/use-case/TBD) -- 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/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049513] [NEW] Remove Online Accounts integration
Public bug reported: GNOME Online Accounts for GNOME 46 has dropped its webkitgtk-powered popup dialog and now uses the user's web browser to handle logging in to Google and Microsoft. Related to that, GNOME Initial Setup is dropping its Online Accounts integration for GNOME 46. https://discourse.gnome.org/t/removing-online-accounts-from-initial- setup-46/18624 Therefore, this is an informative bug that Ubuntu Desktop plans to drop this feature for Ubuntu 24.04 LTS. ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: Triaged ** Tags: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2049513 Title: Remove Online Accounts integration Status in gnome-initial-setup package in Ubuntu: Triaged Bug description: GNOME Online Accounts for GNOME 46 has dropped its webkitgtk-powered popup dialog and now uses the user's web browser to handle logging in to Google and Microsoft. Related to that, GNOME Initial Setup is dropping its Online Accounts integration for GNOME 46. https://discourse.gnome.org/t/removing-online-accounts-from-initial- setup-46/18624 Therefore, this is an informative bug that Ubuntu Desktop plans to drop this feature for Ubuntu 24.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2049513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Solved for me on 23.10 X11 with nvidia-driver-535. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049510] [NEW] nautilus randomly crashes
Public bug reported: Random crashes in nautilus, especially since moving to 23.10, for example while changing directory, while searching for a file. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 16 14:27:43 2024 InstallationDate: Installed on 2023-06-06 (224 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-14 (94 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2049510 Title: nautilus randomly crashes Status in nautilus package in Ubuntu: New Bug description: Random crashes in nautilus, especially since moving to 23.10, for example while changing directory, while searching for a file. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 16 14:27:43 2024 InstallationDate: Installed on 2023-06-06 (224 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-14 (94 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2049510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049433] Re: [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6
I see the crash happening on the following kernels, so that seems unlikely: 5.15.0 -89-generic #99~20.04.1-Ubuntu SMP Thu Nov 2 15:16:47 UTC 2023 x86_64 38.41% 5.15.0 -91-generic #101~20.04.1-Ubuntu SMP Thu Nov 16 14:22:28 UTC 2023 x86_64 21.38% 5.11.0 -37-generic #41~20.04.2-Ubuntu SMP Fri Sep 24 09:06:38 UTC 2021 x86_64 10.51% 5.13.0 -30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 7.25% 5.15.0 -46-lowlatency #49~20.04.1-Ubuntu SMP PREEMPT Mon Aug 8 11:51:19 UTC 2022 x86_64 5.43% 5.15.0 -76-generic #83~20.04.1-Ubuntu SMP Wed Jun 21 20:23:31 UTC 2023 x86_64 5.07% 5.15.0 -88-generic #98~20.04.1-Ubuntu SMP Mon Oct 9 16:43:45 UTC 2023 x86_64 3.26% 5.14.21 -150500 #1 SMP PREEMPT_DYNAMIC Wed Oct 4 16:52:05 UTC 2023 (5dc23e0) x86_64 2.17% ... But thank you for the info, at least we can rule out a change in mesa having broken things. We can perhaps close this bug then, at least until I can investigate further what the root cause is. If any RADV user is reading this and has a repro step, please comment on http://crbug.com/1508940 -- 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/2049433 Title: [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6 Status in mesa package in Ubuntu: New Bug description: Hi, Chrome/ANGLE developer here. We've started observing crashes on Ubuntu 20.04.6 in libvulkan_radeon.so since December 5, 2023. So far, all crashes seem to come from that specific Ubuntu version, and with RADV 21.2.6. Speaking with a mesa RADV developer, that version hasn't had an update since Nov 2021. While there's always a chance that an update in ANGLE has hit a bug, the timing does not work out (Chrome Beta has been fine since November 1, but the crashes started happening on Dec 5). Has there been an update to this driver around Dec 5, 2023 in Ubuntu specifically? I'm wondering if there has been a (security) update done by the Ubuntu team that upstream mesa may not be aware of. I can't find a public history of updates to ubuntu packages (with associated dates), is it possible to look at / provide that info and see what happened around Dec 5? Additional context is crbug.com/1508940, but I'm afraid not much is visible publicly. The crash stack is nonsense unfortunately. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2049433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031229] Re: [ProArt Studiobook H7604JV_H7604JV, Realtek ALC294, Speaker, Internal] No sound at all
As of Linux kernel 6.7 sounds works. No patch needed! Marked as "fixed" as this has been fixed by the afromentioned kernel version. Not an Ubuntu specific issue anyway. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Committed -- 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/2031229 Title: [ProArt Studiobook H7604JV_H7604JV, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Bug description: No sound on clean install. Sound works through jack and bluetooth. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 2360 F pulseaudio /dev/snd/pcmC0D0p: mblack 2360 F...m pulseaudio /dev/snd/controlC1: mblack 2360 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 12 21:45:33 2023 InstallationDate: Installed on 2023-08-13 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 2360 F pulseaudio /dev/snd/pcmC0D0p: mblack 2360 F...m pulseaudio /dev/snd/controlC1: mblack 2360 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ProArt Studiobook H7604JV_H7604JV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: H7604JV.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: H7604JV 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.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH7604JV.203:bd02/08/2023:br5.27:svnASUSTeKCOMPUTERINC.:pnProArtStudiobookH7604JV_H7604JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnH7604JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ProArt Studiobook dmi.product.name: ProArt Studiobook H7604JV_H7604JV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2031229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
Thanks, yes any failure to install now needs a separate bug report. -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
Today install from ISO dated 24-01-16 created a working system despite install ends with "install failed" see bugs 2049491,2049495 (I tried 2 times) -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
@vanvugt just tested in gnome-boxes on a Dell XPS laptop and it works as it should now again :) -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 404363] Re: desktop icons aren't aligned automatically in RTL languages (Hebrew, Arabic, Persian)
** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/404363 Title: desktop icons aren't aligned automatically in RTL languages (Hebrew, Arabic, Persian) Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Bug description: Hi all, In my Mom's computer the localization is in Hebrew, meaning that all menus, folders, and Desktop icons are RTL. As an End-User, every time my Mom downloads something, or drags a file/shortcut to the desktop, the icon doesn't align itself to the grid of the other icons automatically, but instead "lands" in one area (usually the top right). Yet, the bug doesn't stop there. If that icon is left there, the upcoming icons that will be added to the desktop will land right on top of it, creating a lovely stack as shown in the pic: http://img146.imageshack.us/img146/5637/bug1p.jpg http://img91.imageshack.us/img91/9945/bug2d.jpg (credits to Shezif for posting the pics..) Considering that many users prefer the localize system language, and not plain English, i hope this is solvable quickly.. In any case, thanks in advance.. Regards, Uri To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/404363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049433] Re: [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6
it might've been a kernel update that triggers it, mesa hasn't changed. -- 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/2049433 Title: [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6 Status in mesa package in Ubuntu: New Bug description: Hi, Chrome/ANGLE developer here. We've started observing crashes on Ubuntu 20.04.6 in libvulkan_radeon.so since December 5, 2023. So far, all crashes seem to come from that specific Ubuntu version, and with RADV 21.2.6. Speaking with a mesa RADV developer, that version hasn't had an update since Nov 2021. While there's always a chance that an update in ANGLE has hit a bug, the timing does not work out (Chrome Beta has been fine since November 1, but the crashes started happening on Dec 5). Has there been an update to this driver around Dec 5, 2023 in Ubuntu specifically? I'm wondering if there has been a (security) update done by the Ubuntu team that upstream mesa may not be aware of. I can't find a public history of updates to ubuntu packages (with associated dates), is it possible to look at / provide that info and see what happened around Dec 5? Additional context is crbug.com/1508940, but I'm afraid not much is visible publicly. The crash stack is nonsense unfortunately. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2049433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
Confirmed fix released in https://cdimage.ubuntu.com/daily- live/20240116/ -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
