[Desktop-packages] [Bug 1953586] Re: Gnome control center Bluetooth toggle not update immediately when turn off BT
** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Changed in: oem-priority Importance: Undecided => High -- 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/1953586 Title: Gnome control center Bluetooth toggle not update immediately when turn off BT Status in OEM Priority Project: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: [Summary] Bluetooth toggle in gnome-settings-daemon does not turn off when disabling Bluetooth from top right menu [Reproduce Steps] 1. Boot to OS and make sure BT enable 2. Turn BT off via Gnome system tray 3. Gnome control center still shows the toggle in the "on" state, but BT actually disabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1953586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953586] [NEW] Gnome control center Bluetooth toggle not update immediately when turn off BT
Public bug reported: [Summary] Bluetooth toggle in gnome-settings-daemon does not turn off when disabling Bluetooth from top right menu [Reproduce Steps] 1. Boot to OS and make sure BT enable 2. Turn BT off via Gnome system tray 3. Gnome control center still shows the toggle in the "on" state, but BT actually disabled ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1947530 somerville ** Attachment added: "BT toggle.mp4" https://bugs.launchpad.net/bugs/1953586/+attachment/5546135/+files/BT%20toggle.mp4 ** Tags added: oem-priority originate-from-1947530 somerville -- 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/1953586 Title: Gnome control center Bluetooth toggle not update immediately when turn off BT Status in OEM Priority Project: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: [Summary] Bluetooth toggle in gnome-settings-daemon does not turn off when disabling Bluetooth from top right menu [Reproduce Steps] 1. Boot to OS and make sure BT enable 2. Turn BT off via Gnome system tray 3. Gnome control center still shows the toggle in the "on" state, but BT actually disabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1953586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: [SRU]Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in OEM Priority Project: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] * When user edit and save a file in Desktop, the file icon will disappear, and the file is still there, it's bad experience for user. * Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. [Test Plan] * Edit and save a file in Desktop. $ echo "abc" > ~/a.log $ gedit ~/a.log [Where problems could occur] * It is low risk, cause I just check the fileItem in source code before call it, or else it prompt 'fileItem is undefined'. [Other Info] OS: Ubuntu 20.04.3 gnome-shell: 3.36.9 gnome-shell-extension-desktop-icons: 20.04.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953547] Re: Screen lock doesn't work
Thanks for the bug report. Please try: gsettings set org.gnome.desktop.lockdown disable-lock-screen false gsettings set org.gnome.desktop.screensaver lock-enabled true and then log in again. If the problem still happens then please open the 'Extensions' app and ensure you don't have any custom extensions installed. If the problem still happens after that then please run this command to gather more information: apport-collect 1953547 ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Tags added: impish -- 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/1953547 Title: Screen lock doesn't work Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but there is no password required anymore when the laptop awakes out of suspend. I did not change any settings and I still see "lock screen on suspend" = YES in the settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1953547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948572] Re: On Ubuntu 21.10 there is no password required anymore when the laptop awakes out of suspend
*** This bug is a duplicate of bug 1953547 *** https://bugs.launchpad.net/bugs/1953547 Make that bug 1953547 ** This bug is no longer a duplicate of bug 1950035 suspend does not lock in 20.04 ** This bug has been marked a duplicate of bug 1953547 Screen lock doesn't work -- 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/1948572 Title: On Ubuntu 21.10 there is no password required anymore when the laptop awakes out of suspend Status in gnome-shell package in Ubuntu: Incomplete Bug description: Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but there is no password required anymore when the laptop awakes out of suspend. I did not change any settings and I still see "lock screen on suspend" = YES in the settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953527] Re: Display Issue
Thanks for the bug report. Please run these commands: lspci -kv > lspci.txt xrandr --verbose > xrandr.txt and then attach the resulting text files here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1953527 Title: Display Issue Status in gnome-shell package in Ubuntu: Incomplete Bug description: One issue I have is being unable to display my screen on a tv through hdmi port despite ensuring all settings on both devices is proper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 7 11:24:28 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-09-25 (72 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/1953527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953507] Re: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess
** Summary changed: - jammy live - on adjusting display config; one display is unsuable blocky-mess + [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess ** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu) ** Tags added: radeon -- 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/1953507 Title: [radeon] jammy live - on adjusting display config; one display is unsuable blocky-mess Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: ubuntu jammy daily (canary build) live test on - dell optiplex 960 (this is my primary machine; so is normally used for entry of data & not doing the QA-testing). on adjusting the displays to match my setup (six displays; two high & three across; this box uses two in the middle with middle on top row & middle on bottom row).. the top display is still useable, but the bottom is not. This boxes are not perfectly aligned as not all my displays are the exact same size; so top display is slightly to right of bottom display the bottom resembles a digital TV with bad signal, mostly blocky & parts of it flashing (very quickly). it doesn't match the attached picture (as viewable on this box anyway.. my top display; which was LEFT prior to alignment is perfectly readable). ** actual my top display is usable, bottom is not (blocky warped picture) ** expected on adjust displays to match my config; both displays remain usable & readable. ** notes likely related to graphics card & not GNOME. If I recall correctly; this box has an older video card used as it had 2x DVI connections my screens use. My usual install on this box is jammy; but I usually use LXQt/Lubuntu and I don't experience issues.. I also have installed Xubuntu/Xfce & Ubuntu/GNOME so can test the installed OS (where I don't believe I have issue), but my install is somewhat old (artful install upgraded every six months ~30-36 hours after each release) thus is likely heavily modified. ** Picture comments My top display is ~perfect (vertical white bar to left of ubuntu-dock- items I'd not expect, but the color-blocks to the left of the 'install/firefox/thunderbird/files` is NOT visible; only a vertical WHITE bar a few pixels wide to left of the dock appears' rest of top display is perfect. My bottom display is nothing like picture; it's unusable. A mixture of black/white boxes with red/purple bits which would be the picture warped into blocky-components. When I type, I get reactions on this display with the picture changing (mostly the black & white portions which flash, the red/purple bits which are warped indri picture appear to remain static). My phone/camera isn't working, but I've taken a photograph. I didn't anticipate issues in this QA-test (it's past 1AM now) otherwise I'd not have run this QA-test now. ** further comments this is likely a duplicate... I experience this type of reaction on other boxes; likely radeon related but I've yet to look & can't even remember which video card exists in this box (I don't experience issues with the display configuration of the box with identical card to this, but it relates to display setup/config... my other box with this card is landscape+portrait I believe and doesn't have one display above the other; ie. d780; I get these issues when one display is above the other - and only with single orientation (swap top/bottom and issues don't exist)) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 7 13:52:56 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211206) MachineType: Dell Inc. OptiPlex 960 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Desktop-packages] [Bug 1953547] Re: Screen lock doesn't work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1953547 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. ** Package changed: ubuntu => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1953547 Title: Screen lock doesn't work Status in gdm3 package in Ubuntu: New Bug description: Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but there is no password required anymore when the laptop awakes out of suspend. I did not change any settings and I still see "lock screen on suspend" = YES in the settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1953547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953527] Re: Display Issue
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1953527 Title: Display Issue Status in gnome-shell package in Ubuntu: New Bug description: One issue I have is being unable to display my screen on a tv through hdmi port despite ensuring all settings on both devices is proper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 7 11:24:28 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-09-25 (72 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/1953527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953547] [NEW] Screen lock doesn't work
You have been subscribed to a public bug: Since I updated from ubuntu 21.04 to ubuntu 21.10 the suspend still works but there is no password required anymore when the laptop awakes out of suspend. I did not change any settings and I still see "lock screen on suspend" = YES in the settings. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Screen lock doesn't work https://bugs.launchpad.net/bugs/1953547 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953400] Re: shutdown not working from GNOME
Reassigning to the kernel because GNOME has no control over shutdown other than the part where GNOME exits. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) -- 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/1953400 Title: shutdown not working from GNOME Status in linux package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Thanks. We know the bug is still present. It's not fixed until 40.6. -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
Tested with iso built from live-build and import ubuntu-drivers-common from focal-proposed. After installation finished, check /var/log/installer/syslog can see error log as attachment. It says "ubiquity: chroot: failed to run command ‘prime-select’: No such file or directory", because 31ubuntu_driver_packages is called by target config hook which is run before target install stage. Also tested with 21.10 iso file and will got same error message in log. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816/+attachment/5546087/+files/syslog -- 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/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: Fix Committed Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" * Patch make system not enable RTD3 unless it's a laptop and set default GPU mode to "on-demand" [Test Plan] * Create Focal iso with live-build and import ubuntu-drivers-common from -proposed * Install Ubuntu on machine, in "Updates and other software" page select "Install third-party software for graphics and Wi-Fi hardware and additional media formats" * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. * Call "prime-select query" to make sure the default mode is "on-demand" [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to https://bugs.launchpad.net/oem-priority/+bug/1942788 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951828] Re: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
package renamed to libgsl27 in -proposed. ** Changed in: gsl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsl in Ubuntu. https://bugs.launchpad.net/bugs/1951828 Title: libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp Status in gsl package in Ubuntu: Fix Released Status in gsl package in Debian: Fix Released Bug description: From Debian bug 993324: It seems that the 2.7 upload broke the ABI of libgsl25 by removing the gsl_linalg_QR_TR_decomp symbol. src:gsl is currently blocked from entering testing because of this regression in libmath-gsl-perl_0.42-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsl/+bug/1951828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
There is no analogue codec found (according to the log in the #1), maybe your machine has a soundwire bus analogue codec? Plesae upload dmesg.txt (sudo dmesg > dmesg.txt) -- 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/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733301] Re: indicator-applet-complete 1.18.0 icon scaling
This bug was fixed in the package libayatana-indicator - 0.8.4-1ubuntu1 --- libayatana-indicator (0.8.4-1ubuntu1) impish; urgency=medium * Scale icons when loading from filename (LP: #1733301) -- Dani Llewellyn Fri, 15 Oct 2021 10:22:28 +0100 ** Changed in: libayatana-indicator (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libayatana-indicator in Ubuntu. https://bugs.launchpad.net/bugs/1733301 Title: indicator-applet-complete 1.18.0 icon scaling Status in libayatana-indicator package in Ubuntu: Fix Released Status in libayatana-indicator source package in Impish: Fix Released Bug description: [Impact] * Images loaded from filename that are not the right scale/size to for their target location in the UI are shown at their original scale/size. This means that images can be oversized in the MATE panel. * This impacts any application using the system tray on Ubuntu MATE that are describing the icon for the tray by file path instead of a stock icon name. Suck apps include most desktop Snap Packages. * The patch fixes this issue by applying a scaling process to any icons loaded by explicit path. Stock images are unaffected. [Test Plan] * Install Ubuntu Mate * Install utm-no from the Snap Store * Launch utm-no and observe whether the tray shows a small square purple icon for the app (correct) or a large purple rectangle (wrong) [Where problems could occur] * Due to being a base system library then images and icons might fail to load across the operating system, or be incorrectly scaled * The patch could be insufficient to fix the problem as described [Other Info] * This patch has been applied upstream, and I have been running a patched installation for several weeks without issue --- original description below --- System: Ubuntu MATE 17.10 64bit Kernel: 4.13.0-16-generic indicator-applet-complete: 1.18.0 It appears that some icons on the indicator applet complete cannot scale well. I tried this on multiple computers and fresh installations, and I can reproduce it 100% of the times. Icon on attached screenshot is from synology cloudstation drive. As a side note, same icon scales well on Ubuntu 17.10 (gnome session), Kubuntu 17.10, and Ubuntu-Mate 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-indicator/+bug/1733301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Update Released
The verification of the Stable Release Update for gnome-shell-extension- desktop-icons 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-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: [SRU]Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in OEM Priority Project: Triaged Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] * When user edit and save a file in Desktop, the file icon will disappear, and the file is still there, it's bad experience for user. * Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. [Test Plan] * Edit and save a file in Desktop. $ echo "abc" > ~/a.log $ gedit ~/a.log [Where problems could occur] * It is low risk, cause I just check the fileItem in source code before call it, or else it prompt 'fileItem is undefined'. [Other Info] OS: Ubuntu 20.04.3 gnome-shell: 3.36.9 gnome-shell-extension-desktop-icons: 20.04.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing
This bug was fixed in the package gnome-shell-extension-desktop-icons - 20.04.0-3~ubuntu20.04.6 --- gnome-shell-extension-desktop-icons (20.04.0-3~ubuntu20.04.6) focal; urgency=medium * Check fileItem before using it. (LP: #1883174) -- Bin Li Thu, 18 Nov 2021 10:48:34 +0800 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: [SRU]Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in OEM Priority Project: Triaged Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] * When user edit and save a file in Desktop, the file icon will disappear, and the file is still there, it's bad experience for user. * Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. [Test Plan] * Edit and save a file in Desktop. $ echo "abc" > ~/a.log $ gedit ~/a.log [Where problems could occur] * It is low risk, cause I just check the fileItem in source code before call it, or else it prompt 'fileItem is undefined'. [Other Info] OS: Ubuntu 20.04.3 gnome-shell: 3.36.9 gnome-shell-extension-desktop-icons: 20.04.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing
This bug was fixed in the package gnome-shell-extension-desktop-icons - 20.04.0+git20200908-5ubuntu0.3 --- gnome-shell-extension-desktop-icons (20.04.0+git20200908-5ubuntu0.3) hirsute; urgency=medium * Check fileItem before using it. (LP: #1883174) -- Bin Li Thu, 18 Nov 2021 10:48:34 +0800 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: [SRU]Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in OEM Priority Project: Triaged Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] * When user edit and save a file in Desktop, the file icon will disappear, and the file is still there, it's bad experience for user. * Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. [Test Plan] * Edit and save a file in Desktop. $ echo "abc" > ~/a.log $ gedit ~/a.log [Where problems could occur] * It is low risk, cause I just check the fileItem in source code before call it, or else it prompt 'fileItem is undefined'. [Other Info] OS: Ubuntu 20.04.3 gnome-shell: 3.36.9 gnome-shell-extension-desktop-icons: 20.04.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883174] Re: [SRU]Some (or all) desktop icons are missing
Marking the development task as invalid - gnome-shell-extension-desktop- icons no longer exists in impish and beyond. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: [SRU]Some (or all) desktop icons are missing Status in gnome-shell-extension-desktop-icons: Unknown Status in OEM Priority Project: Triaged Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] * When user edit and save a file in Desktop, the file icon will disappear, and the file is still there, it's bad experience for user. * Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. [Test Plan] * Edit and save a file in Desktop. $ echo "abc" > ~/a.log $ gedit ~/a.log [Where problems could occur] * It is low risk, cause I just check the fileItem in source code before call it, or else it prompt 'fileItem is undefined'. [Other Info] OS: Ubuntu 20.04.3 gnome-shell: 3.36.9 gnome-shell-extension-desktop-icons: 20.04.0-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885344] Re: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel)
Confirmed, using PPA kelebek333/nvidia-legacy with GT218M (NVS2100M) (Kubuntu 21.04 with kernel 5.11.0-41-generic). Thank you to Andrea (andrea-amoroso81) Thank you to Butterfly (kelebek333) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1885344 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel) Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Bug description: Nvidia kernel module fails to build with linux kernel 5.6.0. Exits with error code 2. Description: Ubuntu 20.04 LTS Release: 20.04 linux-image-unsigned-5.6.0-1018-oem: Installed: 5.6.0-1018.18 Candidate: 5.6.0-1018.18 Version table: *** 5.6.0-1018.18 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.6.0-1018-oem Date: Sat Jun 27 02:15:51 2020 DuplicateSignature: dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25: error: implicit declaration of function ‘drm_pci_init’; did you mean ‘drm_mm_init’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-04-24 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1885344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952107] Autopkgtest regression report (evolution-data-server/3.36.5-0ubuntu2)
All autopkgtests for the newly accepted evolution-data-server (3.36.5-0ubuntu2) for focal have finished running. The following regressions have been reported in tests triggered by the package: evolution-data-server/3.36.5-0ubuntu2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#evolution-data-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Committed Status in evolution-data-server source package in Impish: Fix Committed Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I can still confirm bug. Fully updated Ubuntu 20.10 - thunderbird 1:91.3.1+build1-0ubuntu0.21.10.2 - mutter 40.5-1ubuntu3~21.10.1 But after commenting "export MOZ_ENABLE_WAYLAND=1" like suggested in comment #18 problem stops. All is working fine now. -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
** Changed in: ubuntu-settings (Ubuntu Jammy) Status: New => Confirmed ** Changed in: ubuntu-settings (Ubuntu Impish) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in initramfs-tools package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in initramfs-tools source package in Impish: New Status in ubuntu-settings source package in Impish: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Status in ubuntu-settings source package in Jammy: Confirmed Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
The attached debdiff fixes this issue in ubuntu-settings (and restores the 21.04.3 changes that were previously missing). Packages have been built and tested in the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-settings ** Patch added: "1-1950214.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1950214/+attachment/5546073/+files/1-1950214.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in initramfs-tools package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in initramfs-tools source package in Impish: New Status in ubuntu-settings source package in Impish: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Status in ubuntu-settings source package in Jammy: Confirmed Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1953014] Re: Return code for unsolicited arping is 1 instead of 0
** Also affects: iputils (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: iputils (Ubuntu Focal) Status: New => Confirmed ** Changed in: iputils (Ubuntu Focal) Importance: Undecided => Low ** Changed in: iputils (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1953014 Title: Return code for unsolicited arping is 1 instead of 0 Status in iputils package in Ubuntu: Confirmed Status in iputils source package in Focal: Confirmed Bug description: When running a gratuitous / unsolicited arp via "arping -U" on Ubuntu Focal a return code of 1 is given, instead of always 0 (as there is no arp reply expected). Focal: --- cut --- # arping -U -c1 -I eth0 127.0.0.1; echo "ReturnCode: $?" ARPING 127.0.0.1 from 127.0.0.1 eth0 Sent 1 probes (1 broadcast(s)) Received 0 response(s) ReturnCode: 1 # arping -V arping from iputils s20190709 --- cut --- see corresponding source at https://github.com/iputils/iputils/blob/13e00847176aa23683d68fce1d17ffb523510946/arping.c#L302. On Ubuntu Bionic this worked fine (and also does on Ubuntu Hirsute again BTW): --- cut --- arping -U -c 1 -I eth0 127.0.0.1; echo "ReturnCode: $?" ARPING 127.0.0.1 from 127.0.0.1 eth0 Sent 1 probes (1 broadcast(s)) Received 0 response(s) ReturnCode: 0 # arping -V arping utility, iputils-s20161105 --- cut --- see corresponding source for that version at https://github.com/iputils/iputils/blob/bffc0e957b98d626ab4cea218c89251201425442/arping.c#L329 or for the version on Hirsute at https://github.com/iputils/iputils/blob/cc16da6b574ce6637f3e6e9ab3c1a728663006ff/arping.c#L302 As you can see by looking at the source arping always statically returns a "0" for unsolicited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1953014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1953400] Re: hutdown not completly working
Hello Thank you I ran the command this morning but it did not work I got a failed message. That I can reset the credentials by removing the file So what happens is I shut down and I see the prompts of everything shutting on down. Then the screen goes blank but my laptop light stays on. I tried waiting 90 seconds for the proper shutdown of anything in the background and nothing happened. On December 6, 2021 7:40:56 p.m. Chris Guiver <1953...@bugs.launchpad.net> wrote: > 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 1953400 > > 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. > > ** Package changed: ubuntu => gnome-shell (Ubuntu) > > ** Summary changed: > > - hutdown not completly working > + shutdown not working from GNOME > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953400 > > Title: > shutdown not working from GNOME > > Status in gnome-shell package in Ubuntu: > New > > Bug description: > Upon using ubuntu 22.04 with latest updates. > > shutdown via gnome does shutdown but the power light stays on on > laptop. So I have to hold the button down for ten seconds. > > oddly enough > shutdown works in terminal correctly. > sudo shutdown -h now > works > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1953400/+subscriptions -- 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/1953400 Title: shutdown not working from GNOME Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953527] [NEW] Display Issue
Public bug reported: One issue I have is being unable to display my screen on a tv through hdmi port despite ensuring all settings on both devices is proper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 7 11:24:28 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-09-25 (72 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1953527 Title: Display Issue Status in gnome-shell package in Ubuntu: New Bug description: One issue I have is being unable to display my screen on a tv through hdmi port despite ensuring all settings on both devices is proper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 7 11:24:28 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-09-25 (72 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/1953527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891476] Re: gtkmm3.0 ftbfs in focal
Hello Matthias, or anyone else affected, Accepted gtkmm3.0 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtkmm3.0/3.24.2-1ubuntu0.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- 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. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtkmm3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1891476 Title: gtkmm3.0 ftbfs in focal Status in gtkmm3.0 package in Ubuntu: Invalid Status in gtkmm3.0 source package in Focal: Fix Committed Bug description: seen in a focal test rebuild, all architctures: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19795016 g++ -std=c++11 -DHAVE_CONFIG_H -I.. -I../gdk -I../gtk -pthread -pthread -I/usr/include/atkmm-1.6 -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/gtk-3.0/unix-print -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DDEMOCODEDIR=\"""\" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -DGLIBMM_DISABLE_DEPRECATED -DGIOMM_DISABLE_DEPRECATED -DGTKMM_DISABLE_DEPRECATED -DGDKMM_DISABLE_DEPRECATED -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o gtk-demo/gtkmm_demo-example_appwindow.o `test -f 'gtk-demo/example_appwindow.cc' || echo './'`gtk-demo/example_appwindow.cc gtk-demo/demowindow.cc:54:1: error: ‘demo_columns’ function uses ‘auto’ type specifier without trailing return type 54 | const auto& demo_columns() | ^ gtk-demo/demowindow.cc:54:1: note: deduced return type only available with ‘-std=c++14’ or ‘-std=gnu++14’ make[4]: *** [Makefile:733: gtk-demo/gtkmm_demo-demowindow.o] Error 1 make[4]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkmm3.0/+bug/1891476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953525] [NEW] debian control should express a package dependency on ubuntu-advantage-tools
Public bug reported: ./softwareproperties/gtk/utils.py relies on presence of ua command delivered by ubuntu-advantage-tools. This deb should probably express at least a Recommends on ubuntu-advantage-tools. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1953525 Title: debian control should express a package dependency on ubuntu- advantage-tools Status in software-properties package in Ubuntu: New Bug description: ./softwareproperties/gtk/utils.py relies on presence of ua command delivered by ubuntu-advantage-tools. This deb should probably express at least a Recommends on ubuntu-advantage-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1953525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1953400] Re: shutdown not working from GNOME
Hi Daniel Thank you for the prompt feedback. Unfortunately I do not really know exactly what you're talking about. When I do the shutdown feature, I see the proper shutdown prompts. But then eventually my computer screen shuts off but my computer light on my power button stays on. And I can still hear the hard drive spinning. If I can say one thing that might help you guys. I think half of these problems I'm having are your kernel. The standby feature not working correctly, was fixed by someone else using a different kernel. Also the blank screen function not working right can be fixed by a kernel downgrade. I imagine this can too. Hope that gives you some insight as to what's going on. Steve On December 6, 2021 8:50:51 p.m. Daniel van Vugt <1953...@bugs.launchpad.net> wrote: > Also it is fairly common for some background jobs to still be running on > shutdown. The system waits up to 90 seconds for those to complete. To > see what they are you can usually press Escape. > > ** Changed in: gnome-shell (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953400 > > Title: > shutdown not working from GNOME > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Upon using ubuntu 22.04 with latest updates. > > shutdown via gnome does shutdown but the power light stays on on > laptop. So I have to hold the button down for ten seconds. > > oddly enough > shutdown works in terminal correctly. > sudo shutdown -h now > works > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1953400/+subscriptions -- 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/1953400 Title: shutdown not working from GNOME Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951738] Re: [SRU] libreoffice 7.2.3 for impish
This bug was fixed in the package libreoffice - 1:7.2.3-0ubuntu0.21.10.1
---
libreoffice (1:7.2.3-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1951738)
* Bump yaru source to "2021-11-10"
libreoffice (1:7.2.2-1) unstable; urgency=medium
* LibreOffice 7.2.2 final release (identical to rc2)
* upload to unstable
* debian/liblibreoffice-java.lintian-overrides,
debian/libreoffice-dev-common.lintian-overrides: override bogus
repeated-path-segment
* debian/control.in: s/the the/the/
* debian/libreoffice-core{,-nogui}.lintian-overrides: remove, obsolete
-- Rico Tzschichholz Thu, 25 Nov 2021 15:44:17
+0100
** Changed in: libreoffice (Ubuntu Impish)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1951738
Title:
[SRU] libreoffice 7.2.3 for impish
Status in libreoffice package in Ubuntu:
New
Status in libreoffice source package in Impish:
Fix Released
Bug description:
[Impact]
* LibreOffice 7.2.3 is in its third bugfix release of the 7.2 line:
https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.3_release
* Version 7.2.2 is currently released in impish. For a list of fixed bugs
compared to 7.2.2 see the list of bugs fixed in the release candidates of 7.2.3
(that's a total of 112 bugs):
https://wiki.documentfoundation.org/Releases/7.2.3/RC1#List_of_fixed_bugs
https://wiki.documentfoundation.org/Releases/7.2.3/RC2#List_of_fixed_bugs
* Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU
a minor release rather than cherry-pick selected bug fixes.
[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_72/1116/
* 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.
* [amd64]
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211121_122557_220e4@/log.gz
* [arm64]
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211121_140906_e9b32@/log.gz
* [armhf]
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211121_135011_ebc4d@/log.gz
* [ppc64el]
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211121_121636_a621c@/log.gz
* [s390x]
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211121_120225_a0cce@/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 minor release with a total of 112 bug fixes always carries the
potential for introducing regressions, even though it is a bugfix-only
release, meaning that no new features were added, and no existing
features were removed.
* A combination of autopkgtests and careful smoke testing as
described above should provide reasonable confidence that no
regressions sneaked in.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951738/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951738] Update Released
The verification of the Stable Release Update for libreoffice 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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1951738 Title: [SRU] libreoffice 7.2.3 for impish Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Impish: Fix Released Bug description: [Impact] * LibreOffice 7.2.3 is in its third bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.3_release * Version 7.2.2 is currently released in impish. For a list of fixed bugs compared to 7.2.2 see the list of bugs fixed in the release candidates of 7.2.3 (that's a total of 112 bugs): https://wiki.documentfoundation.org/Releases/7.2.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_72/1116/ * 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. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211121_122557_220e4@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211121_140906_e9b32@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211121_135011_ebc4d@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211121_121636_a621c@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211121_120225_a0cce@/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 minor release with a total of 112 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
No more crashes with firmware https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/snapshot/linux-firmware-20211027.tar.gz and kernel 5.15.6. -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
While the issue is annoying there are workarounds, selecting manually being one for example, it's also something upstream milestoned for 0.68 pending libglib overflow handling changes, we are tagging as rls-ff- notfixing because we don't believe it requires special Ubuntu handling ** Tags removed: rls-jj-incoming ** Tags added: rls-jj-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output Status in MATE Desktop: New Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed (or use Live session) 2. Launch MATE Terminal 3. Enable infinite history (Edit - Profile Preferences - Scrolling, Scrollback - Unlimited) 4. Execute command with long output such as `journalctl | cat` 5. Select Edit - Select All (or press ++), then Edit - Copy (or press ++) 6. Open Pluma text editor and paste just copied terminal output Expected results: * whole terminal output is copied - staring by `user@host:~$ journalctl | cat` and ending by `user@host:~$` Actual results: * only last 15 lines were copied (depends on terminal size) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 1 17:35:47 2021 LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Changed in: hplip (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: hplip (Ubuntu Impish) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: hplip (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: hplip (Ubuntu Bionic) Assignee: (unassigned) => William Wilson (jawn-smith) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: Won't Fix Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
Seems an hardware enablement issue, while it would be nice to fix it's not something the desktop team can commit to work on at this point so I'm tagging it rls-ff-notfixing ** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing -- 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/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953507] Re: jammy live - on adjusting display config; one display is unsuable blocky-mess
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1953507 ** Tags added: iso-testing -- 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/1953507 Title: jammy live - on adjusting display config; one display is unsuable blocky-mess Status in xorg package in Ubuntu: New Bug description: ubuntu jammy daily (canary build) live test on - dell optiplex 960 (this is my primary machine; so is normally used for entry of data & not doing the QA-testing). on adjusting the displays to match my setup (six displays; two high & three across; this box uses two in the middle with middle on top row & middle on bottom row).. the top display is still useable, but the bottom is not. This boxes are not perfectly aligned as not all my displays are the exact same size; so top display is slightly to right of bottom display the bottom resembles a digital TV with bad signal, mostly blocky & parts of it flashing (very quickly). it doesn't match the attached picture (as viewable on this box anyway.. my top display; which was LEFT prior to alignment is perfectly readable). ** actual my top display is usable, bottom is not (blocky warped picture) ** expected on adjust displays to match my config; both displays remain usable & readable. ** notes likely related to graphics card & not GNOME. If I recall correctly; this box has an older video card used as it had 2x DVI connections my screens use. My usual install on this box is jammy; but I usually use LXQt/Lubuntu and I don't experience issues.. I also have installed Xubuntu/Xfce & Ubuntu/GNOME so can test the installed OS (where I don't believe I have issue), but my install is somewhat old (artful install upgraded every six months ~30-36 hours after each release) thus is likely heavily modified. ** Picture comments My top display is ~perfect (vertical white bar to left of ubuntu-dock- items I'd not expect, but the color-blocks to the left of the 'install/firefox/thunderbird/files` is NOT visible; only a vertical WHITE bar a few pixels wide to left of the dock appears' rest of top display is perfect. My bottom display is nothing like picture; it's unusable. A mixture of black/white boxes with red/purple bits which would be the picture warped into blocky-components. When I type, I get reactions on this display with the picture changing (mostly the black & white portions which flash, the red/purple bits which are warped indri picture appear to remain static). My phone/camera isn't working, but I've taken a photograph. I didn't anticipate issues in this QA-test (it's past 1AM now) otherwise I'd not have run this QA-test now. ** further comments this is likely a duplicate... I experience this type of reaction on other boxes; likely radeon related but I've yet to look & can't even remember which video card exists in this box (I don't experience issues with the display configuration of the box with identical card to this, but it relates to display setup/config... my other box with this card is landscape+portrait I believe and doesn't have one display above the other; ie. d780; I get these issues when one display is above the other - and only with single orientation (swap top/bottom and issues don't exist)) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 7 13:52:56 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211206) MachineType: Dell Inc. OptiPlex 960 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2011 dmi.bios.release: 10.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name:
[Desktop-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+
Targetting to Impish and Jammy as apparently ubuntu-settings lost the 21.04.3 changes in 21.10.1 (which was based on 21.04.2). ** Also affects: ubuntu-meta (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: ubuntu-settings (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: Fix Released => New ** Changed in: ubuntu-meta (Ubuntu Impish) Status: New => Fix Released -- 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/1922266 Title: eth0 interface name change fails on Pi 3/3+ Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-meta source package in Hirsute: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Status in ubuntu-meta source package in Impish: Fix Released Status in ubuntu-settings source package in Impish: New Status in ubuntu-meta source package in Jammy: Fix Released Status in ubuntu-settings source package in Jammy: New Bug description: The netplan configuration in ubuntu-raspi-settings (and more widely, the network-config in the gadget used on the server images) fails to rename the internal ethernet interface on Pi 3B and 3B+ models from "en" to "eth0". In the netplan case this is because the driver matching logic doesn't handle space-separate driver matches (although the underlying networkd system does); in the cloud-init case it simply refuses to rename interfaces that aren't matched by full MAC address. The intended fix is to stop attempting to do this via netplan or cloud-init, and simply handle this via a networkd .link file in ubuntu-raspi-settings. This will require an update to the relevant seeds as this package is currently only pulled into ubuntu-desktop- raspi, not ubuntu-server-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1922266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
Adding ubuntu-settings as that's where the override for the raspi will be added ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in initramfs-tools package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: New Status in initramfs-tools source package in Impish: New Status in ubuntu-settings source package in Impish: New Status in initramfs-tools source package in Jammy: Confirmed Status in ubuntu-settings source package in Jammy: New Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923672] Re: [FFe] Provide access to GPIO to default user
Targetting to Impish and Jammy as apparently ubuntu-settings lost the 21.04.3 changes in 21.10.1 (which was based on 21.04.2). ** Also affects: ubuntu-settings (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: ubuntu-settings (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-settings (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: Fix Released => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1923672 Title: [FFe] Provide access to GPIO to default user Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Hirsute: Fix Released Status in ubuntu-settings source package in Impish: New Status in ubuntu-settings source package in Jammy: New Bug description: At present, access to the GPIO pins is provided to the dialout group by the udev rules from the rpi.gpio-common package. However, rpi.gpio is a single GPIO library, and the device(s) it provides access to are not specific to it. Moreover, the interface used is deprecated and the /dev/gpiochip* interface is now the favoured mechanism for controlling the GPIO pins. The choice of the dialout group appears reasonable (historically it's used to provide access to the serial ports, and indeed the serial ports are part of the GPIO header on Raspberry Pi devices), but the rules should be extended to cover the modern /dev/gpiochip* devices, the related /dev/spidev* and /dev/i2c-* devices, and should be placed in a central location (i.e. ubuntu-raspi-settings) rather than in a specific GPIO library (like rpi.gpio). Related to this is LP: #1923363 which seeks to ensure equal access across images (the default user is currently granted "dialout" group membership on the pi server images, but not the desktop ones). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1923672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953507] [NEW] jammy live - on adjusting display config; one display is unsuable blocky-mess
Public bug reported: ubuntu jammy daily (canary build) live test on - dell optiplex 960 (this is my primary machine; so is normally used for entry of data & not doing the QA-testing). on adjusting the displays to match my setup (six displays; two high & three across; this box uses two in the middle with middle on top row & middle on bottom row).. the top display is still useable, but the bottom is not. This boxes are not perfectly aligned as not all my displays are the exact same size; so top display is slightly to right of bottom display the bottom resembles a digital TV with bad signal, mostly blocky & parts of it flashing (very quickly). it doesn't match the attached picture (as viewable on this box anyway.. my top display; which was LEFT prior to alignment is perfectly readable). ** actual my top display is usable, bottom is not (blocky warped picture) ** expected on adjust displays to match my config; both displays remain usable & readable. ** notes likely related to graphics card & not GNOME. If I recall correctly; this box has an older video card used as it had 2x DVI connections my screens use. My usual install on this box is jammy; but I usually use LXQt/Lubuntu and I don't experience issues.. I also have installed Xubuntu/Xfce & Ubuntu/GNOME so can test the installed OS (where I don't believe I have issue), but my install is somewhat old (artful install upgraded every six months ~30-36 hours after each release) thus is likely heavily modified. ** Picture comments My top display is ~perfect (vertical white bar to left of ubuntu-dock- items I'd not expect, but the color-blocks to the left of the 'install/firefox/thunderbird/files` is NOT visible; only a vertical WHITE bar a few pixels wide to left of the dock appears' rest of top display is perfect. My bottom display is nothing like picture; it's unusable. A mixture of black/white boxes with red/purple bits which would be the picture warped into blocky-components. When I type, I get reactions on this display with the picture changing (mostly the black & white portions which flash, the red/purple bits which are warped indri picture appear to remain static). My phone/camera isn't working, but I've taken a photograph. I didn't anticipate issues in this QA-test (it's past 1AM now) otherwise I'd not have run this QA-test now. ** further comments this is likely a duplicate... I experience this type of reaction on other boxes; likely radeon related but I've yet to look & can't even remember which video card exists in this box (I don't experience issues with the display configuration of the box with identical card to this, but it relates to display setup/config... my other box with this card is landscape+portrait I believe and doesn't have one display above the other; ie. d780; I get these issues when one display is above the other - and only with single orientation (swap top/bottom and issues don't exist)) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465+canary3.3 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 7 13:52:56 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211206) MachineType: Dell Inc. OptiPlex 960 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs maybe-ubiquity --- quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2011 dmi.bios.release: 10.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0F428D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 1701283234 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/05/2011:br10.0:svnDellInc.:pnOptiPlex960:pvr:sku:rvnDellInc.:rn0F428D:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1942951] Re: devhelp doesn't display any help pages
** Changed in: webkit2gtk (Debian) Status: Incomplete => Fix Released -- 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/1942951 Title: devhelp doesn't display any help pages Status in webkit2gtk package in Ubuntu: Triaged Status in webkit2gtk package in Debian: Fix Released Bug description: webkit2gtk 2.33.3-1ubuntu3 Test Case - 1. sudo apt install devhelp libgtk-3-doc 2. Open devhelp and click the GTK+ 3 Reference Manual link in the left sidebar. 3. The manual should show in the main view area. What Happens The main viewing area stays blank. Other Info -- I manually installed webkit2gtk from Ubuntu 21.04 and Devhelp worked normally again. The Epiphany web browser works fine with the broken webkit2gtk version. Ubuntu's packaging diverges slightly from Debian's. The changelog mentions some dependency changes and disabling lto. I haven't done any further investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1942951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Funnily, after disabling the Ubuntu Dock (have not yet logged out and in again) and unplugging my cable, there was no crash. Then again, the crashes are not consistent so I'll try again. This interferes with my work so much that I cannot test this constantly. -- 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/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug has been persisting since I've bought an external monitor for my laptop and started using Wayland (first on Ubuntu 20.04) until today (Ubuntu 21.10). It isn't consistent, but it occurs about 90% of the time when I'm on Wayland. On Xorg, this has never occurred. When I unplug my USB-C monitor from my laptop, the laptop screen freezes for a while before presenting me with the login screen. When I log back in, all my open applications have been shut down. I assume Mutter crashes, taking the entire session with it. Dmesg doesn't seem to contain anything useful. A lot of other people seem to have this problem (see https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1733127), but all have been asked to file their own bug reports, so here I am. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-04-01 (613 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish third-party-packages Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-05 (61 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-12-01T17:24:37.722144 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949637] Re: Libreoffice crash
Well, the problem reappeared this morning :(. -- 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/1949637 Title: Libreoffice crash Status in libreoffice package in Ubuntu: Confirmed Bug description: Libreoffice crashed on startup: sven@:~/$ libreoffice terminate called after throwing an instance of 'com::sun::star::lang::IllegalArgumentException' Unspecified Application Error I've removed Libreoffice completely, installed it again via the Software-Center and it crashes again. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice 1:7.2.2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 3 21:25:16 2021 InstallationDate: Installed on 2019-10-03 (762 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) SourcePackage: libreoffice UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
