[Desktop-packages] [Bug 1927940] Re: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1927940 Title: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: It's a notebook with internal audio and HDMI. The sound card cant be used at all. Pulse audio only shows "Dummy Output". Adding "options snd-hda-intel model=generic" to "/etc/modprobe.d/alsa- base.conf" shows at least the HDMI out. But internal analogue output still won't appear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 11:55:50 2021 InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: HW-13.3-BI-X133GRX210-040-A dmi.board.asset.tag: OEM default string inject dmi.board.name: LINCPLUS dmi.board.vendor: LINCPLUS dmi.board.version: 1.0 dmi.chassis.asset.tag: OEM default string inject dmi.chassis.type: 10 dmi.chassis.vendor: OEM default string inject dmi.chassis.version: OEM default string inject dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrHW-13.3-BI-X133GRX210-040-A:bd01/06/2021:br5.13:svnLINCPLUS:pnLINCPLUSP1:pvrOEMdefaultstringinject:rvnLINCPLUS:rnLINCPLUS:rvr1.0:cvnOEMdefaultstringinject:ct10:cvrOEMdefaultstringinject: dmi.product.family: TVE1315E dmi.product.name: LINCPLUS P1 dmi.product.sku: 1315E20201113001 dmi.product.version: OEM default string inject dmi.sys.vendor: LINCPLUS modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-05-10T11:51:26.728974 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04
*** This bug is a duplicate of bug 1969243 *** https://bugs.launchpad.net/bugs/1969243 Have the same problem only X11 session . GPU AMD -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969254 Title: wayland session not longer an option after recent update on Ubuntu 22.04 Status in gnome-session package in Ubuntu: Confirmed Bug description: After some recent update to Ubuntu 22.04 dev, X11 is selected by default and there is no longer the option to select the display protocol at login. It seems I am not the only affected: https://askubuntu.com/questions/1402671/ubuntu-no-gear-for- waylaland-x11 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-session 42.0-1ubuntu2 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 22:20:35 2022 InstallationDate: Installed on 2022-02-02 (72 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 993407] Re: install-info can fail to install due to syntax errors in /etc/environment
In my case I checked the '/etc/environment' file and noticed I had a variable from cloudflared named 'CLOUDFLARED_OPTS' and the value of that variable was not quoted. Simply quoting the value of 'CLOUDFLARED_OPTS' resolved the issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/993407 Title: install-info can fail to install due to syntax errors in /etc/environment Status in texinfo package in Ubuntu: Confirmed Bug description: The package install-info sources /etc/environment and will fail to install if there are any configuration errors in that file. This seems to happen a fair bit. As an example see bug 984562 or the invalid bug reports about texinfo: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=INVALID&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.tag=apport- package&field.tags_combinator=ANY&field.status_upstream-empty- marker=1&field.upstream_target=&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/993407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 946171] Re: Authentication dialog window loses focus easily - Ubuntu 12.04
This bug appears again in Ubuntu 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. https://bugs.launchpad.net/bugs/946171 Title: Authentication dialog window loses focus easily - Ubuntu 12.04 Status in policykit-gnome: Won't Fix Status in policykit-1-gnome package in Ubuntu: Fix Released Status in policykit-1-gnome source package in Precise: Fix Released Status in policykit-1-gnome source package in Quantal: Fix Released Status in policykit-1-gnome package in Debian: Fix Released Bug description: [SRU Request] [Impact] The policykit authentication dialog sometimes comes up unfocused, which causes users to type in their password into other applications. [Test Case] 1- Install Precise 2- Log into Unity2d (not 3d, is visible with metacity) 3- Install Synaptic 4- Open Synaptic, authenticate, right lick on launcher to keep synaptic icon there 5- Click on Synaptic icon in launcher and see if policykit authentication dialog comes up unfocused. May take a few tries. [Regression potential] A regression in this code would most likely prevent the authentication window from showing up at all, which would be easy to spot and fix. This is a fresh install of Precise from the beta1 alternate CD, but the problem has been occurring in earlier versions. I originally installed Oneiric and upgraded before the alpha 1 release. When using an application that needs administrative access, I notice that the password dialog box loses focus easily, and I can end up typing the password in places where it's easily visible. Examples are a nautilus search area, terminal window or draft email. Mostly I'm using Gnome fallback, though I've observed the same behaviour in Unity 2D as well. I'm still not clear what is causing the loss of focus. Sometimes it's because I've clicked on something else, but not always. Nor does the dialog always lose focus. An authentication box called by explicitly typing "gksu" doesn't lose focus. The screen dims as well, which is not happening with the other dialogs. I'm not sure what the proper package to report against is, so feel free to move to wherever it's appropriate. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.94-0ubuntu1 Architecture: i386 Date: Sun Mar 4 21:41:22 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-gnome/+bug/946171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 433851] Re: Authentication dialog doesn't get focus
This bug appears again in Ubuntu 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. https://bugs.launchpad.net/bugs/433851 Title: Authentication dialog doesn't get focus Status in PolicyKit GNOME: Expired Status in policykit-1-gnome package in Ubuntu: Triaged Status in software-center package in Ubuntu: Invalid Bug description: Binary package hint: software-store When I click on "install", an authentication dialog appears. Many times it does not get focus, so I have to manually click on it before being able to enter my password. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1-gnome/+bug/433851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969875] Re: "No package to remove" error when attempting to uninstall
*** This bug is a duplicate of bug 1969303 *** https://bugs.launchpad.net/bugs/1969303 ** This bug has been marked a duplicate of bug 1969303 "No package to remove" error when attempting to uninstall -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1969875 Title: "No package to remove" error when attempting to uninstall Status in gnome-software package in Ubuntu: New Bug description: Ubuntu Software It does not allow me to uninstall any program. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 00:15:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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-software/+bug/1969875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969875] Re: "No package to remove" error when attempting to uninstall
** Package changed: gnome-shell (Ubuntu) => gnome-software (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1969875 Title: "No package to remove" error when attempting to uninstall Status in gnome-software package in Ubuntu: New Bug description: Ubuntu Software It does not allow me to uninstall any program. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 00:15:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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-software/+bug/1969875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969875] [NEW] "No package to remove" error when attempting to uninstall
Public bug reported: Ubuntu Software It does not allow me to uninstall any program. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 00:15:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969875 Title: "No package to remove" error when attempting to uninstall Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu Software It does not allow me to uninstall any program. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 00:15:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1969875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969874] [NEW] Bluetooth Mouse and Keyboard drop connections when Laptop using battery
Public bug reported: Bluetooth Mouse and Keyboard drop connections when Laptop using battery (power discconnected). Keyboard and mouse work correctly when laptop is powered by mains power. May be related to suspend/resume. Symptoms: - Mouse and keyboard don't work. - Mouse and keyboard bluetooth association cannot be removed rand e-connected. - Mouse and keyboard are detected (sometimes) with different device names. The following does NOT fix the problem:: - Connect laptop power; - In Bluetooth settings Turn Bluetooth off, then on again Rebooting allows devices to be configured again, and connect correctly. Ubuntu version: Ubuntu 21.10 Kernel: 5.13.0-39-generic Package: bluez 5.60-0ubuntu2.2 When working the keyboard and mouse appear with: root@silver:/home/paul# bluetoothctl devices Device D2:91:D2:B9:6B:9D Logi POP Keys Device D1:8F:A4:4B:1B:F9 Logi POP Mouse When not working, the devices show up as: Device D2:91:D2:B9:6B:9D Logi POP @ Device D1:8F:A4:4B:1B:F9 Logi POP @ This devices are: - https://www.logitech.com/en-au/products/mice/pop-wireless-mouse.910-006515.html - https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-010578.html I know that the devices both work with a Windows 10 desktop. Bluetooth Device Details When working.. root@silver:/home/paul# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 20:68:9D:64:8A:FC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1801269 acl:99624 sco:0 events:560 errors:0 TX bytes:8612 acl:173 sco:0 commands:227 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'silver' Class: 0x7c010c Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969874 Title: Bluetooth Mouse and Keyboard drop connections when Laptop using battery Status in bluez package in Ubuntu: New Bug description: Bluetooth Mouse and Keyboard drop connections when Laptop using battery (power discconnected). Keyboard and mouse work correctly when laptop is powered by mains power. May be related to suspend/resume. Symptoms: - Mouse and keyboard don't work. - Mouse and keyboard bluetooth association cannot be removed rand e-connected. - Mouse and keyboard are detected (sometimes) with different device names. The following does NOT fix the problem:: - Connect laptop power; - In Bluetooth settings Turn Bluetooth off, then on again Rebooting allows devices to be configured again, and connect correctly. Ubuntu version: Ubuntu 21.10 Kernel: 5.13.0-39-generic Package: bluez 5.60-0ubuntu2.2 When working the keyboard and mouse appear with: root@silver:/home/paul# bluetoothctl devices Device D2:91:D2:B9:6B:9D Logi POP Keys Device D1:8F:A4:4B:1B:F9 Logi POP Mouse When not working, the devices show up as: Device D2:91:D2:B9:6B:9D Logi POP @ Device D1:8F:A4:4B:1B:F9 Logi POP @ This devices are: - https://www.logitech.com/en-au/products/mice/pop-wireless-mouse.910-006515.html - https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-010578.html I know that the devices both work with a Windows 10 desktop. Bluetooth Device Details When working.. root@silver:/home/paul# hciconfig -a hci0: Type: Primary Bus: USB BD Address: 20:68:9D:64:8A:FC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1801269 acl:99624 sco:0 events:560 errors:0 TX bytes:8612 acl:173 sco:0 commands:227 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'silver' Class: 0x7c010c Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-pa
[Desktop-packages] [Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04
*** This bug is a duplicate of bug 1969243 *** https://bugs.launchpad.net/bugs/1969243 I just did a fresh install of the official release 22.04 LTS image today, and hit this problem. No gear, and it defaults to X11, whether I have just the NVIDIA GPU enabled, or both the Intel integrated GPU and the NVIDIA discrete GPU enabled in hybrid mode. I had previously installed a nightly build of 22.04 LTS (beta) last week, and had the gear as an option, and was able to use Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969254 Title: wayland session not longer an option after recent update on Ubuntu 22.04 Status in gnome-session package in Ubuntu: Confirmed Bug description: After some recent update to Ubuntu 22.04 dev, X11 is selected by default and there is no longer the option to select the display protocol at login. It seems I am not the only affected: https://askubuntu.com/questions/1402671/ubuntu-no-gear-for- waylaland-x11 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-session 42.0-1ubuntu2 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 22:20:35 2022 InstallationDate: Installed on 2022-02-02 (72 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to jammy on 2022-03-18 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix
The attached Xorg logs are from March 8th so not recent enough... While the problem is happening please run this command to collect a newer log: journalctl -b0 > journal.txt and attach the resulting text file here. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Incomplete ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1969834 Title: artifacts (many short horizontal lines) on laptop with hybrid graphix Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: artifacts (many short horizontal lines) see https://youtu.be/SQOOp0bd0LE artifacts only on display (screen capture is clear) i have laptop with hybrid graphix (intel nvidia) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.16.13-051613-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Apr 21 22:06:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] InstallationDate: Installed on 2022-02-28 (52 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.dmic_detect=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.release: 3.16 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.310 dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1969834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More he
[Desktop-packages] [Bug 1748177] Re: Recurring crash during updates package libinput10:i386 1.6.3-1ubuntu1~16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should r
*** This bug is a duplicate of bug 1969787 *** https://bugs.launchpad.net/bugs/1969787 ** This bug is no longer a duplicate of bug 1737543 package libinput10:i386 1.6.3-1ubuntu1~16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ** This bug has been marked a duplicate of bug 1969787 package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1748177 Title: Recurring crash during updates package libinput10:i386 1.6.3-1ubuntu1~16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libinput package in Ubuntu: New Bug description: Recurring ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libinput10:i386 1.6.3-1ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39 Uname: Linux 3.13.0-96-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Thu Feb 1 17:38:45 2018 DuplicateSignature: package:libinput10:i386:1.6.3-1ubuntu1~16.04.1 Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ... dpkg: error processing package libinput10:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-04-07 (671 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libinput Title: package libinput10:i386 1.6.3-1ubuntu1~16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2016-09-21 (505 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1748177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510 (Ubuntu) -- 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/1969834 Title: artifacts (many short horizontal lines) on laptop with hybrid graphix Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: artifacts (many short horizontal lines) see https://youtu.be/SQOOp0bd0LE artifacts only on display (screen capture is clear) i have laptop with hybrid graphix (intel nvidia) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.16.13-051613-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Apr 21 22:06:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] InstallationDate: Installed on 2022-02-28 (52 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.dmic_detect=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.release: 3.16 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.310 dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1969834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969816] Re: Display dimming despite setting being turned off
On some laptops there are two settings that dim the display so you need to disable both. Please try: Settings > Power > Automatic Screen Brightness = OFF Settings > Power > Dim Screen = OFF ** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1969816 Title: Display dimming despite setting being turned off Status in gnome-control-center package in Ubuntu: Incomplete Bug description: The display is dimming after a few seconds of "inactivity" despite turning off the setting to dim the display. This seems to occur on any power setting and a reboot did not solve the problem. This makes activities such as reading difficult as the display becomes harder to read and I have to interact with the computer more than necessary to keep the screen bright. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.14.0-1033.36-oem 5.14.21 Uname: Linux 5.14.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 09:56:56 2022 DistUpgraded: 2022-04-21 09:33:57,457 DEBUG failed to SystemLock() (E:Could not get lock /var/lib/dpkg/lock. It is held by process 55177 (dpkg), W:Be aware that removing the lock file is not a solution and may break your system., E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a7d] InstallationDate: Installed on 2022-03-29 (23 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 14 5410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1033-oem root=UUID=65a9ddc2-0f7d-4b2c-8228-d1f755668bf9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) dmi.bios.date: 02/15/2022 dmi.bios.release: 2.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.1 dmi.board.name: 0XPW9D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.1:bd02/15/2022:br2.7:svnDellInc.:pnInspiron145410:pvr:rvnDellInc.:rn0XPW9D:rvrA00:cvnDellInc.:ct10:cvr:sku0A7D: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5410 dmi.product.sku: 0A7D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969637] Re: lookup table appears bottom left of application
** Bug watch added: Debian Bug tracker #1009996 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009996 ** Also affects: im-config (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009996 Importance: Unknown Status: Unknown ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Summary changed: - lookup table appears bottom left of application + lookup table appears bottom left of application (x11) ** Tags added: regression-release x11 ** Summary changed: - lookup table appears bottom left of application (x11) + IBus lookup table appears bottom left of application (x11) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: IBus lookup table appears bottom left of application (x11) Status in ibus: Fix Released Status in gnome-settings-daemon package in Ubuntu: New Status in im-config package in Ubuntu: New Status in im-config package in Debian: Unknown Status in openSUSE: Unknown Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969820] Re: Wayland doesn't work after updating, eventhough in conf WaylandEnable is true
*** This bug is a duplicate of bug 1968929 *** https://bugs.launchpad.net/bugs/1968929 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1968929, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) ** This bug has been marked a duplicate of bug 1968929 Missing Wayland login option on NVIDIA systems -- 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/1969820 Title: Wayland doesn't work after updating, eventhough in conf WaylandEnable is true Status in gdm3 package in Ubuntu: New Bug description: I have been working on Ubuntu 21.04 and Wayland worked just fine. But after updating to 22.04 Beta and now 22.04 LTS Wayland just stopped working. I tried install it, but it doesn't work either. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 00:52:41 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-12 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-13 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969838] Re: Ubuntu-dock does not work when using Turkish Language
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1687 https://github.com/micheleg/dash-to-dock/issues/1687 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1687 Importance: Unknown Status: Unknown ** Tags added: jammy ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1969838 Title: Ubuntu-dock does not work when using Turkish Language Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Ubuntu dock doesn't work when Turkish language is selected. Issue on dash-to-dock's github: https://github.com/micheleg/dash-to- dock/issues/1687 Ubuntu version: Ubuntu 22.04 LTS gnome-shell-extension-ubuntu-dock version: 72~ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1969838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969782] Re: action-middle-click-titlebar 'toggle-maximize-vertically' instead does 'toggle-maximize'
*** This bug is a duplicate of bug 1698083 *** https://bugs.launchpad.net/bugs/1698083 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1698083, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1698083 Maximize vertically/horizontally doesn't work (in some apps) -- 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/1969782 Title: action-middle-click-titlebar 'toggle-maximize-vertically' instead does 'toggle-maximize' Status in gnome-shell package in Ubuntu: New Bug description: Simply, configuring the middle mouse button in dconf-editor to maximize a window vertically when its title bar is middle-clicked, causes the window instead to maximize fully. In dconf-editor, the setting is /org/gnome/desktop/wm/preferences/action-middle-click-titlebar. The misbehaving setting is 'toggle-maximize-vertically'. The 'toggle-maximize' setting works correctly. Ubuntu 20.04.4 gnome-shell 3.36.9-0ubuntu0.20.04.2 Expected behavior: Configuring the middle mouse button to maximize vertically would cause the window to maximize vertically. Behavior: Configuring the middle mouse button to maximize vertically instead causes the window to maximize fully, i.e., both vertically and horizontally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 21 06:50:07 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-09 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) 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/1969782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969558] Re: Dragging one edge of a modal dialog moves the opposite edge
Canonical and myself are not part of the GNOME design team. Although we do sometimes deviate from upstream designs for Ubuntu, this particular issue has never come up before that I can recall. If you would like to make GNOME design suggestions then maybe try opening an upstream issue: https://gitlab.gnome.org/GNOME/gnome- shell/issues -- 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/1969558 Title: Dragging one edge of a modal dialog moves the opposite edge Status in gnome-shell package in Ubuntu: Invalid Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
** Summary changed: - totem unable to play bbb mp4: "The specified movie could not be found" + Totem unable to play video: "The specified movie could not be found" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969767] Re: totem crashes when attempting to play mp4 files
If you launch totem from a Terminal, do you get the same error as bug 1969512? ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969767 Title: totem crashes when attempting to play mp4 files Status in totem package in Ubuntu: Incomplete Bug description: I can add and display a directory of .mp4 files in totem but when attempting to play any of them totem will crash. Any attempts to restart totem fail with the window not appearing at all. After several attempts to restart I can add an .mp4 file but any attempt to play it results in the described sequence repeating with sometimes the window not appearing, sometimes I can navigate to a local file and sometimes the above error is displayed as soon as totem's window is displayed. These reports have appeared on errors.ubuntu.com which relate to the most recent crashes: https://errors.ubuntu.com/oops/383cc642-c157-11ec-8afa-fa163e993415 https://errors.ubuntu.com/oops/37f3e83a-c157-11ec-a3c9-fa163ef35206 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 10:53:17 2022 InstallationDate: Installed on 2022-04-02 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1969767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xwayland (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961747] Re: [nvidia] Black screen (with grey squares) after resume from sleep
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1876632, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- 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/1961747 Title: [nvidia] Black screen (with grey squares) after resume from sleep Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Problem: Screen is black when resuming from sleep. Only a few grey squares are shown. Software: Latest Ubuntu 22.04 (updated 21st of february). Nvidia 495 drivers. Update: Tested again with 22.04 reinstalled as of 12th of April. This gave me Nvidia 510.60 drivers. Same problem. Hardware: Ryzen 5900x, Nvidia 3080ti GPU. Configuration: Wayland at login screen. Analysis: Maybe Video RAM is purged during sleep and then it is not restored when resuming. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965557] Re: Holding the "X" window button in the overview crashes gnome-shell
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-42.1 fixed-upstream ** Package changed: gnome-shell (Ubuntu) => mutter (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/1965557 Title: Holding the "X" window button in the overview crashes gnome-shell Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: I have updated Ubuntu 22.04 today and now when I press key and then "X" on any program and Ubuntu crashes and then login window appears. I can reproduce this problem any time on any program. I don't know if I collected info correctly. I did: ubuntu-bug gnome-shell [ 40.489188] u22 gnome-shell[3770]: ** [ 40.489188] u22 gnome-shell[3770]: Clutter:ERROR:../clutter/clutter/clutter-actor.c:1275:clutter_actor_set_mapped: assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self)) [ 40.489188] u22 gnome-shell[3770]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-actor.c:1275:clutter_actor_set_mapped: assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self)) [ 40.489188] u22 gnome-shell[3770]: GNOME Shell crashed with signal 6 [ 40.489188] u22 gnome-shell[3770]: == Stack trace for context 0x5646b3729180 == [ 40.489743] u22 gnome-shell[3770]: #0 5646b5c09468 i resource:///org/gnome/shell/ui/windowPreview.js:370 (353e696062e0 @ 12) [ 40.489743] u22 gnome-shell[3770]: #1 7fff3283f9a0 b resource:///org/gnome/shell/ui/environment.js:132 (995e4ecc4c0 @ 98) [ 40.489743] u22 gnome-shell[3770]: #2 7fff3283fa60 b resource:///org/gnome/shell/ui/environment.js:219 (995e4ecc830 @ 14) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 16:40:32 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-16 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967452] Re: [nvidia] When resume from suspend, monitor keep blinking and don't show the whole desktop.
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 ** This bug is no longer a duplicate of bug 1961747 [nvidia] Black screen (with grey squares) after resume from sleep ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- 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/1967452 Title: [nvidia] When resume from suspend, monitor keep blinking and don't show the whole desktop. Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Reproduce steps] 1. Install jammy beta. 2. Install nvidia-driver by ubuntu-driver install 3. Suspend the system by clicking the button at the upper right corner. [Expected result] Should re-enter to desktop. [Actual result] Screen keep blinking and don't show the desktop screen. According to reaction of the system, it seems to login already, I can press ctrl+alt+del to pop out a logout menu. [Info] OS version: Ubuntu Jammy Jellyfish (development branch) Device: HP Z2 Mini G5 workstation CID: 202008-28179 Wayland in use. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 23:27:12 2022 InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xwayland 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/1967452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967219] Re: Wayland: Cursor is 90° rotated on rotated screen
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-42.1 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967219 Title: Wayland: Cursor is 90° rotated on rotated screen Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: I have a multi-screen setup with one of the displays being rotated (Portrait Right in Displays settings). Since upgrading to Jammy the cursor gets 90° rotated after being moved from a landscape to the rotated screen. This seems to be happening only in Overview or if cursor is hovered over the desktop. Hovering cursor over the application window (e.g. Terminal) would reset the rotation; however, after being moved back to the landscape screen, the cursor gets rotated again (but now in an opposite direction). This doesn't happen on Xorg and it wasn't happening on impish (wayland). This doesn't happen if desktop icons NG extension is enabled. Steps to reproduce: 1) Disable DING extension. 2) Set up two screens, (1) being rotated and (2) in normal Landscape position. 3) Move cursor to (2), it should be in normal position. 4) Move cursor to (1). Expected: the cursor is in normal position. Actual: the cursor is rotated 90° CW. 5) Open the application, move it to (1), hover the cursor over it. The cursor would go back to the normal position again. 6) Move the cursor to (2) Expected: the cursor is in normal position. Actual: the cursor is rotated 90° CCW. As in the previous case, hovering cursor over the application window fixes it's rotation. Additional notes: sometimes the dead cursor copy stays near the screen edge after cursor is being moved to a different screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 31 08:23:17 2022 InstallationDate: Installed on 2019-04-17 (1078 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
Snap version built via snapcraft at https://github.com/3v1n0/notify- send-test-snap/commits/46b035b ** Description changed: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. - [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] - Build the test snap: - git clone https://github.com/3v1n0/notify-send-test-snap - snapcraft prime - snap try prime + Build the test snap (or install it from the attached files to this bug): + git clone https://github.com/3v1n0/notify-send-test-snap + snapcraft prime + snap try prime Check that icons are shown when launching: - notify-send-test-snap - notify-send-test-snap.image-path + notify-send-test-snap + notify-send-test-snap.image-path - Running them with G_MESSAGES_DEBUG=all should provide translation - logging + Ensure that desktop entry is correctly sent, monitoring the dbus + session: + + In a terminal: +dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" + + In the other: +notify-send-test-snap.desktop-entry +notify-send-test-snap.desktop-entry-explicit-id +notify-send-test-snap.desktop-entry-explicit-file-name +notify-send-test-snap.desktop-entry-explicit-path +notify-send-test-snap.desktop-entry-explicit-uri +notify-send-test-snap.desktop-entry-explicit-snapped-uri + + The + `desktop-entry` value sent to dbus should be either: +- A `notify-send-test-snap_`-prefixed desktop ID +- A .desktop file path (readable from both inside and outside the snap) +- A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file ** Also affects: libnotify (Ubuntu Jammy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: libnotify (Ubuntu Focal) Importance: Undecided Status: New ** Attachment added: "notify-send-test-snap_0+git.46b035b_amd64.snap" https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5582259/+files/notify-send-test-snap_0+git.46b035b_amd64.snap ** Description changed: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime + To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) + snap install --dangerous notify-send-test-snap_*.snap + Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path Ensure that desktop entry is correctly sent, monitoring the dbus session: - In a terminal: -dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" + In a terminal: + dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" - In the other: -notify-send-test-snap.desktop-entry -notify-send-test-snap.desktop-entry-explicit-id -notify-send-test-snap.desktop-entry-explicit-file-name -notify-send-test-snap.desktop-entry-explicit-path -notify-send-test-snap.desktop-entry-explicit-uri -notify-send-test-snap.desktop-entry-explicit-snapped-uri + In the other: + notify-send-test-snap.desktop-entry + notify-send-test-snap.desktop-entry-explicit-id + notify-send-test-snap.desktop-entry-explicit-file-name + notify-send-test-snap.desktop-entry-explicit-path + notify-send-test-snap.desktop-entry-explicit-uri + notify-send-test-snap.desktop-entry-explicit-snapped-uri - The - `desktop-entry` value sent to dbus should be either: -- A `notify-send-test-snap_`-prefixed desktop ID -- A .desktop file path (readable from both inside and outside the snap) -- A .desktop file uri (readable from both inside and outside the snap) + The + `desktop-entry` value sent to dbus should be either: + - A `notify-send-test-snap_`-prefixed desktop ID + - A .desktop file path (readable from both inside and outside the snap) + - A .desktop file
[Desktop-packages] [Bug 1969530] Re: gjs-console error on gnome-extension prefs (Ubuntu 22.04)
** Attachment removed: "_usr_bin_gjs-console.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1969530/+attachment/5581525/+files/_usr_bin_gjs-console.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1969530 Title: gjs-console error on gnome-extension prefs (Ubuntu 22.04) Status in gjs package in Ubuntu: New Bug description: gjs-console error reported everytime opening a gnome-extension settings prefs on Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gjs 1.72.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 00:25:33 2022 InstallationDate: Installed on 2022-04-18 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220418) SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1969530/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
Updated and now I can't reproduce. Looks like some update made it go away. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
Looking at dbus-x11, I think it would still be possible to have it running without it, but I feel it would need to tune the systemd units a bit to get dbus running. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Invalid Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964122] Re: Cannot connect to router with admin page over TLS v1.0
haproxy 2.0 doesn't like private key that is not strong enough (only 1024 bits). I generated new certificate for key that has 2048 bits just to find that this certificate is accepted but TLSv1.0 was removed from haproxy or some SSL library, haproxy 2.0.13 cannot connect to the old router...:-( haproxy cannot connect to the router and reports error 503 - Service unavailable. This is a script to generate new certificate, inspired by https://gist.github.com/yuezhu/47b15b4b8e944221861ccf7d7f5868f5 $ cat gen-new-pem.sh #!/bin/sh FNAME="firewall" DAYS=370 NUMBITS=2048 # Generate a unique private key (KEY) openssl genrsa -out $FNAME.key $NUMBITS # Generating a Certificate Signing Request (CSR) openssl req -new -key $FNAME.key -out $FNAME.csr # Creating a Self-Signed Certificate (CRT) openssl x509 -req -days $DAYS -in $FNAME.csr -signkey $FNAME.key -out $FNAME.crt # Append KEY and CRT to mydomain.pem cat $FNAME.key $FNAME.crt > $FNAME.pem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964122 Title: Cannot connect to router with admin page over TLS v1.0 Status in firefox package in Ubuntu: Won't Fix Bug description: firefox-97.0.2+linuxmint1+tricia I cannot connect to web interface of my old router that is on local LAN. It supports only TLS v1.0 and support for TLS v1.0 & 1.1 was removed in Firefox v97... I know I should replace my router with some better device, I already tried several times but new devices had other issues, I always returned back to my old router... I do not think that it is real security risk to have TLS v1.0 interface on local LAN... Any idea how to connect to a device with TLS v1.0? Any idea for a workaround? Maybe some proxy, or other browser, etc... I already tried Chromium browser but it is the same, I cannot connect with TLSv1.0. Do I really need to run old PC with W2k to manage my router?? ;-) --- https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox- did-not-connect?as=u&utm_source=inproduct#w_tls-version-unsupported Note: The option to enable TLS 1.0 and 1.1 has been removed from the error page in Firefox version 97. --- Router supports TLS v1.0 only: $ curl -v -s --tlsv1.0 https://192.168.222.1:445 * Rebuilt URL to: https://192.168.222.1:445/ * Trying 192.168.222.1... * TCP_NODELAY set * Connected to 192.168.222.1 (192.168.222.1) port 445 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.0 (OUT), TLS handshake, Client hello (1): * TLSv1.0 (IN), TLS handshake, Server hello (2): * TLSv1.0 (IN), TLS handshake, Certificate (11): * TLSv1.0 (OUT), TLS alert, Server hello (2): * SSL certificate problem: self signed certificate * stopped the pause stream! * Closing connection 0 $ curl -v -s --tlsv1.1 https://192.168.222.1:445 * Rebuilt URL to: https://192.168.222.1:445/ * Trying 192.168.222.1... * TCP_NODELAY set * Connected to 192.168.222.1 (192.168.222.1) port 445 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.1 (OUT), TLS handshake, Client hello (1): * TLSv1.1 (IN), TLS handshake, Server hello (2): * TLSv1.1 (OUT), TLS alert, Server hello (2): * error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol * stopped the pause stream! * Closing connection 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969855] [NEW] Livepatch status icon does not appear in top bar
Public bug reported: Today I enabled Livepatch and have confirmed it is active. The option to 'Show Livepatch status in the top bar' in the Software & Updates application is checked but I do not have the status icon that I have when running Ubuntu 18.04 and 20.04. I have rebooted my laptop and have checked in both Xorg and Wayland sessions but the icon fails to appear. When in use I do see the relevant icons for HexChat, Transmission and IRCCloud in this area. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-appindicator 42-2~fakesync1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 22:55:27 2022 InstallationDate: Installed on 2022-04-02 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: canonical-livepatch-client Importance: Undecided Status: New ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Also affects: canonical-livepatch-client Importance: Undecided Status: New ** Description changed: Today I enabled Livepatch and have confirmed it is active. The option to 'Show Livepatch status in the top bar' in the Software & Updates application is checked but I do not have the status icon that I have when running Ubuntu 18.04 and 20.04. I have rebooted my laptop and have checked in both Xorg and Wayland sessions but the icon fails to appear. + + When in use I do see the relevant icons for HexChat, Transmission and + IRCCloud in this area. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-appindicator 42-2~fakesync1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 22:55:27 2022 InstallationDate: Installed on 2022-04-02 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1969855 Title: Livepatch status icon does not appear in top bar Status in Canonical Livepatch Client: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: Today I enabled Livepatch and have confirmed it is active. The option to 'Show Livepatch status in the top bar' in the Software & Updates application is checked but I do not have the status icon that I have when running Ubuntu 18.04 and 20.04. I have rebooted my laptop and have checked in both Xorg and Wayland sessions but the icon fails to appear. When in use I do see the relevant icons for HexChat, Transmission and IRCCloud in this area. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-appindicator 42-2~fakesync1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 22:55:27 2022 InstallationDate: Installed on 2022-04-02 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/1969855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969842] Re: No font available after installing in user space
** Package changed: ubuntu => libreoffice (Ubuntu) ** Tags added: focal snap -- 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/1969842 Title: No font available after installing in user space Status in libreoffice package in Ubuntu: New Bug description: I can't find the installed "Ecofont Vera Sans" under LibreOffice (7.3.2.2) in Ubuntu (20.04.4 LTS). --- $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 --- LibreOffice (snap snapcraft.io) Version: 7.3.2.2 / LibreOffice Community Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528 CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: it-IT (en_US.UTF-8); UI: en-US Calc: threaded --- Ecofont Vera Sans Download page: https://www.fonts4free.net/ecofont-vera-sans-font.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969842] [NEW] No font available after installing in user space
You have been subscribed to a public bug: I can't find the installed "Ecofont Vera Sans" under LibreOffice (7.3.2.2) in Ubuntu (20.04.4 LTS). --- $ lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 --- LibreOffice (snap snapcraft.io) Version: 7.3.2.2 / LibreOffice Community Build ID: 454130fadb9a820d3728b86ccb63c8f359d70528 CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: it-IT (en_US.UTF-8); UI: en-US Calc: threaded --- Ecofont Vera Sans Download page: https://www.fonts4free.net/ecofont-vera-sans-font.html ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- No font available after installing in user space https://bugs.launchpad.net/bugs/1969842 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice 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 1969274] Re: openvpn client no longer connects in 22.04
Ubuntu 22.04 LTS ** Attachment added: "Screenshot from 2022-04-21 22-26-12.png" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+attachment/5582218/+files/Screenshot%20from%202022-04-21%2022-26-12.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 Status in network-manager-openvpn package in Ubuntu: New Bug description: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969274] Re: openvpn client no longer connects in 22.04
The result of this failure from $ sudo tail -f /var/log/syslog ** Attachment added: "Screenshot from 2022-04-21 22-20-26.png" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+attachment/5582217/+files/Screenshot%20from%202022-04-21%2022-20-26.png ** Changed in: network-manager-openvpn (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 Status in network-manager-openvpn package in Ubuntu: New Bug description: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969274] Re: openvpn client no longer connects in 22.04
Hello, I also encounter this problem after upgrade from Ubuntu 21.10 to 22.04. 1. I setup openvpn server on my router (Asus AX88U) at home. 2. I exported the config to *.ovpn file and imported that to openvpn client via gnome-network-manager; I did same on my smartphone. 2. Being outside home, I use 4G connection and click VPN Connect in the right upper corner menu. 3. There is a message pop-up in the notification area that "Activation of network connection failed" 4. it worked perfectly in 21.10 and it works now on my Galaxy S20+. ** Attachment added: "Screenshot from 2022-04-21 22-16-01.png" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+attachment/5582216/+files/Screenshot%20from%202022-04-21%2022-16-01.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969274 Title: openvpn client no longer connects in 22.04 Status in network-manager-openvpn package in Ubuntu: New Bug description: Client no longer connects. previous version had no problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 15:09:56 2022 InstallationDate: Installed on 2022-04-15 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969834] Re: artifacts (many short horizontal lines) on laptop with hybrid graphix
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1969834 Title: artifacts (many short horizontal lines) on laptop with hybrid graphix Status in xorg package in Ubuntu: New Bug description: artifacts (many short horizontal lines) see https://youtu.be/SQOOp0bd0LE artifacts only on display (screen capture is clear) i have laptop with hybrid graphix (intel nvidia) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.16.13-051613-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Apr 21 22:06:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] InstallationDate: Installed on 2022-02-28 (52 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.dmic_detect=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.release: 3.16 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.310 dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969834/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964122] Re: Cannot connect to router with admin page over TLS v1.0
I installed Mint 20.3 (Ubuntu 20.04) to new desktop PC. haproxy was upgraded to 2.0.13 and it doesn't work with configuration that was written for haproxy 1.8.8. The problem is with certificate file, haproxy reports problem with configuration file, with line "bind". haproxy cannot find SSL certificate (unable to load SSL certificate from PEM file)... I spent hour on this issue and so far I do not know what is wrong and how to fix it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964122 Title: Cannot connect to router with admin page over TLS v1.0 Status in firefox package in Ubuntu: Won't Fix Bug description: firefox-97.0.2+linuxmint1+tricia I cannot connect to web interface of my old router that is on local LAN. It supports only TLS v1.0 and support for TLS v1.0 & 1.1 was removed in Firefox v97... I know I should replace my router with some better device, I already tried several times but new devices had other issues, I always returned back to my old router... I do not think that it is real security risk to have TLS v1.0 interface on local LAN... Any idea how to connect to a device with TLS v1.0? Any idea for a workaround? Maybe some proxy, or other browser, etc... I already tried Chromium browser but it is the same, I cannot connect with TLSv1.0. Do I really need to run old PC with W2k to manage my router?? ;-) --- https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox- did-not-connect?as=u&utm_source=inproduct#w_tls-version-unsupported Note: The option to enable TLS 1.0 and 1.1 has been removed from the error page in Firefox version 97. --- Router supports TLS v1.0 only: $ curl -v -s --tlsv1.0 https://192.168.222.1:445 * Rebuilt URL to: https://192.168.222.1:445/ * Trying 192.168.222.1... * TCP_NODELAY set * Connected to 192.168.222.1 (192.168.222.1) port 445 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.0 (OUT), TLS handshake, Client hello (1): * TLSv1.0 (IN), TLS handshake, Server hello (2): * TLSv1.0 (IN), TLS handshake, Certificate (11): * TLSv1.0 (OUT), TLS alert, Server hello (2): * SSL certificate problem: self signed certificate * stopped the pause stream! * Closing connection 0 $ curl -v -s --tlsv1.1 https://192.168.222.1:445 * Rebuilt URL to: https://192.168.222.1:445/ * Trying 192.168.222.1... * TCP_NODELAY set * Connected to 192.168.222.1 (192.168.222.1) port 445 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.1 (OUT), TLS handshake, Client hello (1): * TLSv1.1 (IN), TLS handshake, Server hello (2): * TLSv1.1 (OUT), TLS alert, Server hello (2): * error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol * stopped the pause stream! * Closing connection 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969619] Re: RDP Sharing appears on by default in jammy
** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center: Unknown Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Jammy: Fix Committed Bug description: Impact == 1. It looks like RDP Sharing is turned on but it is not. 2. To actually turn on RDP Sharing, you would need to turn it off then turn it on. This bugfix fixes it so that it correctly shown as off by default and turning it on works. Test Case = 0. Start with a clean Ubuntu 22.04 install. Or you can create a new user and log in as the new user. 1. Open the Settings app. 2. In the left sidebar, click Sharing. The switch at the top of the page needs to be off. 3. Turn the switch on. Then click Remote Desktop and turn it on. 4. Close the Settings app. 5. Open the Settings app and verify that Sharing is on and Remote Desktop is on. 6. Close the Settings app. 7. From a terminal, run systemctl --user status gnome-remote-sharing.service It should show the service as active (running) and a line at the bottom should say RDP server started 8. Then run systemctl --user stop gnome-remote-sharing.service 9. Open the Settings app. It should show that Remote Desktop sharing is off. 10. Turn on Sharing and turn on Remote Desktop sharing. 11. Run systemctl --user status gnome-remote-sharing.service It should show the service as active (running) and a line at the bottom should say RDP server started What Could Go Wrong === This is a minimal fix proposed upstream. The original implementation was insufficient. The bugfix will allow Remote Desktop to be turned on and work correctly from the beginning. More Details To simplify this bug report, I removed a lot of troubleshooting details that can still be seen with the "See full activity log" link Just opening the Sharing panel flips the gsettings key org.gnome.desktop.remote-desktop.rdp enable to true and apparently tries to start RDP sharing. RDP sharing doesn't work because the TLS keys weren't set yet. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969834] [NEW] artifacts (many short horizontal lines) on laptop with hybrid graphix
You have been subscribed to a public bug: artifacts (many short horizontal lines) see https://youtu.be/SQOOp0bd0LE artifacts only on display (screen capture is clear) i have laptop with hybrid graphix (intel nvidia) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.16.13-051613-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1) ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Apr 21 22:06:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:12eb] InstallationDate: Installed on 2022-02-28 (52 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.16.13-051613-generic root=UUID=98fc789e-6997-4a4b-b741-da24a1b635ca ro quiet splash modprode.blacklist=nouveau snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.dmic_detect=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2022 dmi.bios.release: 3.16 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.310 dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.310:bd01/13/2022:br3.16:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kubuntu resolution ubuntu -- artifacts (many short horizontal lines) on laptop with hybrid graphix https://bugs.launchpad.net/bugs/1969834 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1969838] Re: Ubuntu-dock does not work when using Turkish Language
** Attachment added: "Desktop when Turkish Language is selected" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969838/+attachment/5582212/+files/Ekran%20G%C3%B6r%C3%BCnt%C3%BCs%C3%BC%20-%202022-04-21%2022-08-43.png -- 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/1969838 Title: Ubuntu-dock does not work when using Turkish Language Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu dock doesn't work when Turkish language is selected. Issue on dash-to-dock's github: https://github.com/micheleg/dash-to- dock/issues/1687 Ubuntu version: Ubuntu 22.04 LTS gnome-shell-extension-ubuntu-dock version: 72~ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969838] [NEW] Ubuntu-dock does not work when using Turkish Language
Public bug reported: Ubuntu dock doesn't work when Turkish language is selected. Issue on dash-to-dock's github: https://github.com/micheleg/dash-to- dock/issues/1687 Ubuntu version: Ubuntu 22.04 LTS gnome-shell-extension-ubuntu-dock version: 72~ubuntu5 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Ubuntu-dock not working when using Turkish Language + Ubuntu-dock does not work when using Turkish Language -- 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/1969838 Title: Ubuntu-dock does not work when using Turkish Language Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu dock doesn't work when Turkish language is selected. Issue on dash-to-dock's github: https://github.com/micheleg/dash-to- dock/issues/1687 Ubuntu version: Ubuntu 22.04 LTS gnome-shell-extension-ubuntu-dock version: 72~ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
Just an additional info: The issue also presents when Take a Picture is selected in Profile image change. Using Cheese (with Logitech C270), selecting 640x480 resolution provides good picture. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in cheese package in Ubuntu: In Progress Status in cheese source package in Jammy: In Progress Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1967843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-package
[Desktop-packages] [Bug 1969821] [NEW] File uploading sort by modified makes the window crash in browsers
Public bug reported: Ubuntu 22.04 @ 21/04/2022 with kernel 5.15.0-25-generic uploading a file somewhere from a browser (tested Firefox & chromium snap) sorting the files by 'modified' makes the upload window crash (not the whole browser) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gnome 42.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 20:07:48 2022 SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: Ubuntu 22.04 @ 21/04/2022 with kernel 5.15.0-25-generic uploading a file somewhere from a browser (tested Firefox & chromium snap) - sorting the filed by 'modified' makes the upload window crash (not the whole browser) + sorting the files by 'modified' makes the upload window crash (not the whole browser) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gnome 42.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 20:07:48 2022 SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1969821 Title: File uploading sort by modified makes the window crash in browsers Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 @ 21/04/2022 with kernel 5.15.0-25-generic uploading a file somewhere from a browser (tested Firefox & chromium snap) sorting the files by 'modified' makes the upload window crash (not the whole browser) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gnome 42.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 20:07:48 2022 SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/1969821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949183] Re: Cheese screenshot white screen and video freezes
Maybe related upstream? https://gitlab.gnome.org/GNOME/cheese/-/issues/139 ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #139 https://gitlab.gnome.org/GNOME/cheese/-/issues/139 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1949183 Title: Cheese screenshot white screen and video freezes Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch with kernel 5.13.0-19-generic on wayland and Xorg When taking webcam pictures with cheese on wayland and xorg, it takes the picture but gives me a few seconds of white screen after the shot When taking a webcam video it takes a freezed picture instead of a video and has problems to push the stop recording button --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1949183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961747] Re: [nvidia] Black screen (with grey squares) after resume from sleep
I updated my system today. I added this file: # cat /etc/modprobe.d/nvidia-power-management.conf options nvidia NVreg_PreserveVideoMemoryAllocations=1 Now, for the first time ever, it seems Wayland with Nvidia proprietary drivers work, including suspend and resume. I think I did not have to do anything else than the above, but I'm not 100% sure. -- 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/1961747 Title: [nvidia] Black screen (with grey squares) after resume from sleep Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Problem: Screen is black when resuming from sleep. Only a few grey squares are shown. Software: Latest Ubuntu 22.04 (updated 21st of february). Nvidia 495 drivers. Update: Tested again with 22.04 reinstalled as of 12th of April. This gave me Nvidia 510.60 drivers. Same problem. Hardware: Ryzen 5900x, Nvidia 3080ti GPU. Configuration: Wayland at login screen. Analysis: Maybe Video RAM is purged during sleep and then it is not restored when resuming. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949183] Re: Cheese screenshot white screen and video freezes [wayland]
** Description changed: Ubuntu 22.04 development branch with kernel 5.13.0-19-generic on wayland + and Xorg - When taking webcam pictures with cheese on wayland, it takes the picture + When taking webcam pictures with cheese on wayland and xorg, it takes the picture but gives me a few seconds of white screen after the shot When taking a webcam video it takes a freezed picture instead of a video and has problems to push the stop recording button - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: - cheese3.38.0-4 - cheese-common 3.38.0-4 + cheese3.38.0-4 + cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter - Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera - Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - --- + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter + Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera + Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: Notebook N7x0WU Package: cheese 3.38.0-4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: - cheese3.38.0-4 - cheese-common 3.38.0-4 + cheese3.38.0-4 + cheese-common 3.38.0-4 Tags: wayland-session jammy gstreamer-error Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter - Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera - Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter + Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera + Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ** Summary changed: - Cheese screenshot white screen and video freezes [wayland] + Cheese screenshot white screen and video freezes -- You received this bug notificat
[Desktop-packages] [Bug 1969820] [NEW] Wayland doesn't work after updating, eventhough in conf WaylandEnable is true
Public bug reported: I have been working on Ubuntu 21.04 and Wayland worked just fine. But after updating to 22.04 Beta and now 22.04 LTS Wayland just stopped working. I tried install it, but it doesn't work either. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 00:52:41 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-12 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-13 (8 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/1969820 Title: Wayland doesn't work after updating, eventhough in conf WaylandEnable is true Status in gnome-shell package in Ubuntu: New Bug description: I have been working on Ubuntu 21.04 and Wayland worked just fine. But after updating to 22.04 Beta and now 22.04 LTS Wayland just stopped working. I tried install it, but it doesn't work either. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 00:52:41 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-12 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-13 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886322] Re: Unable to move all selected files on desktop
@Sergio: It's already closed as regards ding. What's open is the original gnome-shell-extension-desktop-icons package for Ubuntu 20.04. -- 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/1886322 Title: Unable to move all selected files on desktop Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: Hi, This bug started to happen like 1-2 months ago, and as I remember I didn't do any customizations like installing any external plugins and etc, but I have some stuff already like custom icons, shell, theme... but it worked normaly before. What is happening is that when I select more than 1 file on desktop, no matter which file it is (folder, .txt, image.. anything), and when I try to move around desktop from one place to another, it will move only 1 file and not the rest. So, unable to move selected files on desktop (drag and drop using cursor's rectangle). Its simple issue, no need for video or screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:18:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221] InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: MSI MS-7693 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1886322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969816] [NEW] Display dimming despite setting being turned off
Public bug reported: The display is dimming after a few seconds of "inactivity" despite turning off the setting to dim the display. This seems to occur on any power setting and a reboot did not solve the problem. This makes activities such as reading difficult as the display becomes harder to read and I have to interact with the computer more than necessary to keep the screen bright. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.14.0-1033.36-oem 5.14.21 Uname: Linux 5.14.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 09:56:56 2022 DistUpgraded: 2022-04-21 09:33:57,457 DEBUG failed to SystemLock() (E:Could not get lock /var/lib/dpkg/lock. It is held by process 55177 (dpkg), W:Be aware that removing the lock file is not a solution and may break your system., E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a7d] InstallationDate: Installed on 2022-03-29 (23 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 14 5410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1033-oem root=UUID=65a9ddc2-0f7d-4b2c-8228-d1f755668bf9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) dmi.bios.date: 02/15/2022 dmi.bios.release: 2.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.1 dmi.board.name: 0XPW9D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.1:bd02/15/2022:br2.7:svnDellInc.:pnInspiron145410:pvr:rvnDellInc.:rn0XPW9D:rvrA00:cvnDellInc.:ct10:cvr:sku0A7D: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5410 dmi.product.sku: 0A7D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969816 Title: Display dimming despite setting being turned off Status in xorg package in Ubuntu: New Bug description: The display is dimming after a few seconds of "inactivity" despite turning off the setting to dim the display. This seems to occur on any power setting and a reboot did not solve the problem. This makes activities such as reading difficult as the display becomes harder to read and I have to interact with the computer more than necessary to keep the screen bright. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.14.0-1033.36-oem 5.14.21 Uname: Linux 5.14.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 09:56:56 2022 DistUpgraded: 2022-04-21 09:33:57,457 DEBUG failed to SystemLock() (E:Could not get lock /var/lib/dpkg/lock. It is held by process 55177 (dpkg), W:Be aware that removing the lock file is not a solution and may break your system., E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a78] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a7d] InstallationDate: Installed on 2022-03-29 (23 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron 14 5410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1033-oem root=UUID=65a9ddc2-0f7d-4b2c-8228-d1f755668bf9 ro quiet spl
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: plasma-browser-integration (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969637] Re: lookup table appears bottom left of application
On 2022-04-21 12:44, Ikuya Awashiro wrote: > It must be caused by bottom two commits. > > https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/e2d268eb00f06f497b2f62ae9f3b6e7e1fe4bd9e > https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/c8981ef0b1e915e89c79e301080541baef0f9fa9 > > $ gsettings get org.gnome.desktop.interface gtk-im-module > '' > $ gsettings set org.gnome.desktop.interface gtk-im-module 'ibus' > > This command works as expected immediately. Hmm.. Previously that value was controlled dynamically. It defaulted to "gtk-im-context-simple", but as soon as some ibus IM was present in the list of input sources (or the OSK was enabled) the value switched automatically to "ibus". That's why it worked fine without setting GTK_IM_MODULE=ibus explicitly, and we could prevent im-config from doing anything in case of a GNOME desktop. > But according to commit messages, it is not intended for GNOME 42. Do you understand what their intention actually is? > And I don't know why Fedora 36 works so great. Is GTK_IM_MODULE unset there? I have noticed that the upstream ibus maintainer (who is a Fedora guy) frequently advises users to set GTK_IM_MODULE=ibus. He seems to consider that to be a normal measure on x11 and not a workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Status in openSUSE: Unknown Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886322] Re: Unable to move all selected files on desktop
This should be already fixed. Can we close this? -- 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/1886322 Title: Unable to move all selected files on desktop Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: Hi, This bug started to happen like 1-2 months ago, and as I remember I didn't do any customizations like installing any external plugins and etc, but I have some stuff already like custom icons, shell, theme... but it worked normaly before. What is happening is that when I select more than 1 file on desktop, no matter which file it is (folder, .txt, image.. anything), and when I try to move around desktop from one place to another, it will move only 1 file and not the rest. So, unable to move selected files on desktop (drag and drop using cursor's rectangle). Its simple issue, no need for video or screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:18:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221] InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: MSI MS-7693 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1886322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
Turns out that Ubiquity was removing dbus-x11 (was included in it's remove list), so I've removed it from Ubiquity's package remove list and released Ubuntu Unity 22.04 (didn't find any issues after that): https://twitter.com/ubuntu_unity/status/1517174884576935936 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Invalid Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947115] Re: VAAPI / HW-acceleration not working Snap-packaged Firefox
Pardon me, I didn't see your comment. I attached the output when viewing a video on Youtube ** Attachment added: "moz_log_platformDecoderModule5.log" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947115/+attachment/5582152/+files/moz_log_platformDecoderModule5.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947115 Title: VAAPI / HW-acceleration not working Snap-packaged Firefox Status in firefox package in Ubuntu: Fix Released Bug description: I just installed Ubuntu 21.10, which packages Firefox in snap in contrary to the old .deb package way. Now neither of my laptops (with snap packaged firefox and Ubuntu 21.10) can play videos hardware accelerated using VAAPI anymore. This means my laptops get hotter and use battery faster. It was working perfectly in Ubuntu 21.04. I can see that the about:config has stayed untouched since the upgrade, so I have my doubts that this is related to an updated about:config. vainfo shows full support (nothing appears broken) and I am also able to play videos in VLC using hardware acceleration, VAAPI. The reason why I can see it is not using VAAPI is intel_gpu_top. In previous versions of Ubuntu with Firefox, I could monitor the video decoder when watching videos in Firefox. Before the upgrade it was always utilized. Now it only shows that the GPU is being used, so the video decoder is not in use. I can't see any switch in the Application/Firefox menu regarding allowing access to video decoding hardware, so I am wondering if it simply cannot access that part of the GPU inside a snap environment? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947115] Re: VAAPI / HW-acceleration not working Snap-packaged Firefox
On my other laptop which uses the iHD driver, it is also not working troels@spectre:~$ vainfo libva info: VA-API version 1.14.0 libva info: User environment variable requested driver 'iHD' libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.14 (libva 2.12.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 () vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI On both computers, intel_gpu_top shows that the "video" engine is not being used at all. In Ubuntu 21.10, they were perfectly capable of using the hardware decoder with firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947115 Title: VAAPI / HW-acceleration not working Snap-packaged Firefox Status in firefox package in Ubuntu: Fix Released Bug description: I just installed Ubuntu 21.10, which packages Firefox in snap in contrary to the old .deb package way. Now neither of my laptops (with snap packaged firefox and Ubuntu 21.10) can play videos hardware accelerated using VAAPI anymore. This means my laptops get hotter and use battery faster. It was working perfectly in Ubuntu 21.04. I can see that the about:config has stayed untouched since the upgrade, so I have my doubts that this is related to an updated about:config. vainfo shows full support (nothing appears broken) and I am also able to play videos in VLC using hardware acceleration, VAAPI. The reason why I can see it is not using VAAPI is intel_gpu_top. In previous versions of Ubuntu with Firefox, I could monitor the video decoder when watching videos in Firefox. Before the upgrade it was always utilized. Now it only shows that the GPU is being used, so the video decoder is not in use. I can't see any switch in the Application/Firefox menu regarding allowing access to video decoding hardware, so I am wondering if it simply cannot access that part of the GPU inside a snap environment? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969808] Re: [BPO] libreoffice 7.2.6 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Focal) Importance: Undecided => Medium -- 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/1969808 Title: [BPO] libreoffice 7.2.6 for focal Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release * This source packages matches the proposed SRU for impish handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1963279 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.1.7 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1950467 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.6-0ubuntu0.21.10.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1492/ * 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] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * 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 52 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/1969808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947115] Re: VAAPI / HW-acceleration not working Snap-packaged Firefox
The gnome platform snap, which the firefox snap relies on for libva drivers, comes with both drivers (i965 and iHD): $ ls -1 /snap/gnome-3-38-2004/current/usr/lib/x86_64-linux-gnu/dri/ | grep _drv_video.so i965_drv_video.so iHD_drv_video.so nouveau_drv_video.so r600_drv_video.so radeonsi_drv_video.so Can you share the output of: MOZ_LOG="PlatformDecoderModule:5" snap run firefox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947115 Title: VAAPI / HW-acceleration not working Snap-packaged Firefox Status in firefox package in Ubuntu: Fix Released Bug description: I just installed Ubuntu 21.10, which packages Firefox in snap in contrary to the old .deb package way. Now neither of my laptops (with snap packaged firefox and Ubuntu 21.10) can play videos hardware accelerated using VAAPI anymore. This means my laptops get hotter and use battery faster. It was working perfectly in Ubuntu 21.04. I can see that the about:config has stayed untouched since the upgrade, so I have my doubts that this is related to an updated about:config. vainfo shows full support (nothing appears broken) and I am also able to play videos in VLC using hardware acceleration, VAAPI. The reason why I can see it is not using VAAPI is intel_gpu_top. In previous versions of Ubuntu with Firefox, I could monitor the video decoder when watching videos in Firefox. Before the upgrade it was always utilized. Now it only shows that the GPU is being used, so the video decoder is not in use. I can't see any switch in the Application/Firefox menu regarding allowing access to video decoding hardware, so I am wondering if it simply cannot access that part of the GPU inside a snap environment? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969808] Re: [BPO] libreoffice 7.2.6 for focal
Packaging changes are available at https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/focal-7.2 -- 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/1969808 Title: [BPO] libreoffice 7.2.6 for focal Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release * This source packages matches the proposed SRU for impish handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1963279 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.1.7 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1950467 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.6-0ubuntu0.21.10.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1492/ * 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] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * 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 52 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/1969808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969808] [NEW] [BPO] libreoffice 7.2.6 for focal
Public bug reported: [Impact] * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release * This source packages matches the proposed SRU for impish handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1963279 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.1.7 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1950467 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.6-0ubuntu0.21.10.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1492/ * 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] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * 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 52 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. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu Focal) Importance: Medium Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Also affects: libreoffice (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Focal) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- 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/1969808 Title: [BPO] libreoffice 7.2.6 for focal Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release * This source packages matches the proposed SRU for impish handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1963279 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages * Previous backport of 7.1.7 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1950467 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.6-0ubuntu0.21.10.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1492/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
[Desktop-packages] [Bug 1947115] Re: VAAPI / HW-acceleration not working Snap-packaged Firefox
It does not work again on Ubuntu 22.04 LTS with i965. I am not sure whether i965_drv_video.so is packaged with the snap or not. If I do: ``` troels@troels-ThinkPad-X230-Tablet:~$ LIBVA_DRIVER_NAME=i965 vainfo libva info: VA-API version 1.14.0 libva info: User environment variable requested driver 'i965' libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.14 (libva 2.12.0) vainfo: Driver version: Intel i965 driver for Intel(R) Ivybridge Mobile - 2.4.1 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD ``` However, if it force the iHD driver: ``` troels@troels-ThinkPad-X230-Tablet:~$ LIBVA_DRIVER_NAME=iHD vainfo libva info: VA-API version 1.14.0 libva info: User environment variable requested driver 'iHD' libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 vaInitialize failed with error code 1 (operation failed),exit ``` So my computer does not work with the iHD driver, that I think the snap comes packaged with. Maybe I by mistake in Ubuntu 21.10 was using the normal packaged version of Firefox, which enabled me to use the i965 VA driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1947115 Title: VAAPI / HW-acceleration not working Snap-packaged Firefox Status in firefox package in Ubuntu: Fix Released Bug description: I just installed Ubuntu 21.10, which packages Firefox in snap in contrary to the old .deb package way. Now neither of my laptops (with snap packaged firefox and Ubuntu 21.10) can play videos hardware accelerated using VAAPI anymore. This means my laptops get hotter and use battery faster. It was working perfectly in Ubuntu 21.04. I can see that the about:config has stayed untouched since the upgrade, so I have my doubts that this is related to an updated about:config. vainfo shows full support (nothing appears broken) and I am also able to play videos in VLC using hardware acceleration, VAAPI. The reason why I can see it is not using VAAPI is intel_gpu_top. In previous versions of Ubuntu with Firefox, I could monitor the video decoder when watching videos in Firefox. Before the upgrade it was always utilized. Now it only shows that the GPU is being used, so the video decoder is not in use. I can't see any switch in the Application/Firefox menu regarding allowing access to video decoding hardware, so I am wondering if it simply cannot access that part of the GPU inside a snap environment? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969637] Re: lookup table appears bottom left of application
Launchpad has imported 7 comments from the remote bug at https://bugzilla.opensuse.org/show_bug.cgi?id=1197873. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-03-31T13:04:44+00:00 Hillwood Yang wrote: Created attachment 857578 on gnome ternimal Triggering conditions: Update Tumbleweed to version 20220323+ or fresh install with gnome. Cursor can not follow on Firefox and Gnome terminal. Reply at: https://bugs.launchpad.net/ubuntu/+source/im- config/+bug/1969637/comments/0 On 2022-03-31T13:06:33+00:00 Hillwood Yang wrote: Created attachment 857579 on firefox Reply at: https://bugs.launchpad.net/ubuntu/+source/im- config/+bug/1969637/comments/1 On 2022-04-06T14:46:58+00:00 Ftake wrote: Does this problem still reproduce with GNOME 42? Which session type do you use? GNOME Wayland or GNOME X11? It looks like IBus is working with xim protocol. Reply at: https://bugs.launchpad.net/ubuntu/+source/im- config/+bug/1969637/comments/2 On 2022-04-14T06:04:12+00:00 Hillwood Yang wrote: (In reply to Fuminobu Takeyama from comment #2) > Does this problem still reproduce with GNOME 42? > Which session type do you use? GNOME Wayland or GNOME X11? > > It looks like IBus is working with xim protocol. Yep, and it only reproduces on GNOME 42. It works fine on Gnome 41. GNOME 42 Wayland is invaild on my system. I do not test on Wayland. Reply at: https://bugs.launchpad.net/ubuntu/+source/im- config/+bug/1969637/comments/3 On 2022-04-14T14:33:02+00:00 Ftake wrote: GTK_IM_MODULE is not specified now. So maybe GTK X11 applications uses xim, which does not support showing candidate window under the cursor. Note that GTK_IM_MODULE should not be set under GNOME wayland session because it now use Wayland input method protocol instead of GTK IM Module. We have to find out why GTK_IM_MODULE is not set even for X11 sessions. Reply at: https://bugs.launchpad.net/ubuntu/+source/im- config/+bug/1969637/comments/4 On 2022-04-14T14:59:02+00:00 Ftake wrote: This change might be related https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/276 Reply at: https://bugs.launchpad.net/ubuntu/+source/im- config/+bug/1969637/comments/5 On 2022-04-21T15:11:25+00:00 Ftake wrote: Ubuntu launchpad (a workaround available): https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1969637 Reply at: https://bugs.launchpad.net/ubuntu/+source/im- config/+bug/1969637/comments/13 ** Changed in: opensuse Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Status in openSUSE: Unknown Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969637] Re: lookup table appears bottom left of application
** Bug watch added: bugzilla.opensuse.org/ #1197873 https://bugzilla.opensuse.org/show_bug.cgi?id=1197873 ** Also affects: opensuse via https://bugzilla.opensuse.org/show_bug.cgi?id=1197873 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Status in openSUSE: Unknown Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969804] Re: unable to authenticate some appllications for sudo access in jammy
Workaround... using sudo pkexec /usr/bin/grub-customizer or pkexec /usr/bin/grub-customizer allows the command to run after correct password is entered ** Also 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/1969804 Title: unable to authenticate some appllications for sudo access in jammy Status in grub-customizer package in Ubuntu: Invalid Status in software-properties package in Ubuntu: New Bug description: VirtualBox Version 6.1.34 r150636 (Qt5.6.2) machine running Kubuntu (upgraded from Impish to Jammy via "pkexec do-release-upgrade -m desktop -f DistUpgradeViewKDE -d" command at 11:21 21 apr 2022 UTC Ubuntu 22.04 LTS (Kubuntu) grub-customizer version 5.1.0-3build1 expected: application asked for password to authorize for sudo (root) privileges to run then for it to run... happened: administrator level account is unable to authorize application to run. same type of reaction to issue #1965439 for software-properties-qt which also happens here screen shot attached with terminals open and the error message with attempted bug report collection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-customizer/+bug/1969804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** Also affects: plasma-browser-integration (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: New Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969797] [NEW] tree: command not found
Public bug reported: this package should suggest package "tree" to be installed. /usr/sbin/alsa-info: line 661: tree: command not found log: $ sudo alsa-info ALSA Information Script v 0.5.1 This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci aplay amixer alsactl rpm, dpkg /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See '/usr/sbin/alsa-info --help' for command line options. /usr/sbin/alsa-info: line 661: tree: command not found /usr/sbin/alsa-info: line 661: tree: command not found /usr/sbin/alsa-info: line 661: tree: command not found Automatically upload ALSA information to www.alsa-project.org? [y/N] : n Your ALSA information is in /tmp/alsa-info.txt.nTN6DqVchT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-utils 1.2.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 16:39:18 2022 InstallationDate: Installed on 2022-04-14 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1969797 Title: tree: command not found Status in alsa-utils package in Ubuntu: New Bug description: this package should suggest package "tree" to be installed. /usr/sbin/alsa-info: line 661: tree: command not found log: $ sudo alsa-info ALSA Information Script v 0.5.1 This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci aplay amixer alsactl rpm, dpkg /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See '/usr/sbin/alsa-info --help' for command line options. /usr/sbin/alsa-info: line 661: tree: command not found /usr/sbin/alsa-info: line 661: tree: command not found /usr/sbin/alsa-info: line 661: tree: command not found Automatically upload ALSA information to www.alsa-project.org? [y/N] : n Your ALSA information is in /tmp/alsa-info.txt.nTN6DqVchT ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-utils 1.2.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 16:39:18 2022 InstallationDate: Installed on 2022-04-14 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1969797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969787] [NEW] package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: No idea ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libinput-bin 1.15.5-1ubuntu0.3 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 AptOrdering: libinput10:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Thu Apr 21 16:01:58 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libinput-bin:1.15.5-1ubuntu0.3 Unpacking libinput10:amd64 (1.15.5-1ubuntu0.3) over (1.15.5-1ubuntu0.2) ... dpkg: error processing package libinput-bin (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY TU116 [GeForce GTX 1650 SUPER] [196e:1350] InstallationDate: Installed on 2021-09-22 (211 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic root=UUID=5c263473-36e2-410e-95e7-1174764ce9f8 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libinput Title: package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1969787 Title: package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libinput package in Ubuntu: New Bug description: No idea ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libinput-bin 1.15.5-1ubuntu0.3 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 AptOrdering: libinput10:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Thu Apr 21 16:01:58 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libinput-bin:1.15.5-1ubuntu0.3 Unpacking libinput10:amd64 (1.15.5-1ubuntu0.3) over (1.15.5-1ubuntu0.2) ... dpkg: error processing package libinput-bin (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY TU116 [GeForce GTX 1650 SUPER] [196e:1350] InstallationDate: Installed on 2021-09-22 (211 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine:
[Desktop-packages] [Bug 1969782] [NEW] action-middle-click-titlebar 'toggle-maximize-vertically' instead does 'toggle-maximize'
Public bug reported: Simply, configuring the middle mouse button in dconf-editor to maximize a window vertically when its title bar is middle-clicked, causes the window instead to maximize fully. In dconf-editor, the setting is /org/gnome/desktop/wm/preferences/action-middle-click-titlebar. The misbehaving setting is 'toggle-maximize-vertically'. The 'toggle-maximize' setting works correctly. Ubuntu 20.04.4 gnome-shell 3.36.9-0ubuntu0.20.04.2 Expected behavior: Configuring the middle mouse button to maximize vertically would cause the window to maximize vertically. Behavior: Configuring the middle mouse button to maximize vertically instead causes the window to maximize fully, i.e., both vertically and horizontally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 21 06:50:07 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-09 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) 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/1969782 Title: action-middle-click-titlebar 'toggle-maximize-vertically' instead does 'toggle-maximize' Status in gnome-shell package in Ubuntu: New Bug description: Simply, configuring the middle mouse button in dconf-editor to maximize a window vertically when its title bar is middle-clicked, causes the window instead to maximize fully. In dconf-editor, the setting is /org/gnome/desktop/wm/preferences/action-middle-click-titlebar. The misbehaving setting is 'toggle-maximize-vertically'. The 'toggle-maximize' setting works correctly. Ubuntu 20.04.4 gnome-shell 3.36.9-0ubuntu0.20.04.2 Expected behavior: Configuring the middle mouse button to maximize vertically would cause the window to maximize vertically. Behavior: Configuring the middle mouse button to maximize vertically instead causes the window to maximize fully, i.e., both vertically and horizontally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 21 06:50:07 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-09 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) 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/1969782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** Description changed: (initially reported at https://forum.snapcraft.io/t/chrome-gnome-shell- does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] - Use Extension manager to install gnome extensions - https://flathub.org/apps/details/com.mattjakeman.ExtensionManager + If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. + + sudo apt install gnome-shell-extension-manager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969619] Re: RDP Sharing appears on by default in jammy
** Changed in: gnome-control-center (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center: Unknown Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Jammy: Fix Committed Bug description: Impact == 1. It looks like RDP Sharing is turned on but it is not. 2. To actually turn on RDP Sharing, you would need to turn it off then turn it on. This bugfix fixes it so that it correctly shown as off by default and turning it on works. Test Case = 0. Start with a clean Ubuntu 22.04 install. Or you can create a new user and log in as the new user. 1. Open the Settings app. 2. In the left sidebar, click Sharing. The switch at the top of the page needs to be off. 3. Turn the switch on. Then click Remote Desktop and turn it on. 4. Close the Settings app. 5. Open the Settings app and verify that Sharing is on and Remote Desktop is on. 6. Close the Settings app. 7. From a terminal, run systemctl --user status gnome-remote-sharing.service It should show the service as active (running) and a line at the bottom should say RDP server started 8. Then run systemctl --user stop gnome-remote-sharing.service 9. Open the Settings app. It should show that Remote Desktop sharing is off. 10. Turn on Sharing and turn on Remote Desktop sharing. 11. Run systemctl --user status gnome-remote-sharing.service It should show the service as active (running) and a line at the bottom should say RDP server started What Could Go Wrong === This is a minimal fix proposed upstream. The original implementation was insufficient. The bugfix will allow Remote Desktop to be turned on and work correctly from the beginning. More Details To simplify this bug report, I removed a lot of troubleshooting details that can still be seen with the "See full activity log" link Just opening the Sharing panel flips the gsettings key org.gnome.desktop.remote-desktop.rdp enable to true and apparently tries to start RDP sharing. RDP sharing doesn't work because the TLS keys weren't set yet. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
[Workaround] Use Extension manager to install gnome extensions https://flathub.org/apps/details/com.mattjakeman.ExtensionManager ** Description changed: (initially reported at https://forum.snapcraft.io/t/chrome-gnome-shell- does-not-work-with-chromium-snap/3377) See attached screenshot. + + [Workaround] + Use Extension manager to install gnome extensions + https://flathub.org/apps/details/com.mattjakeman.ExtensionManager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] Use Extension manager to install gnome extensions https://flathub.org/apps/details/com.mattjakeman.ExtensionManager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall
** Changed in: gnome-software (Ubuntu) Milestone: None => ubuntu-22.04.1 ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall Status in GNOME Software: Unknown Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any application If you want to uninstall a software, there is an error message : "no package to remove" No problem to uninstall this same software with synaptic for example To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
I can confirm that this issue is still present in Ubuntu 22.04. Extensions can only be installed manually now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
** No longer affects: unity (Ubuntu) ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Invalid Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840] Re: Spell checking more than one language in Firefox
** Bug watch added: Mozilla Bugzilla #1073827 https://bugzilla.mozilla.org/show_bug.cgi?id=1073827 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
The default for a site you haven't visited is to match the language of the document or the edit control. If you change the dictionaries manually, they should be remembered for the site, so this should only be a problem the first time you visit a site. I think it's worth discussing whether we should change this behaviour when the user has explicitly enabled multiple dictionaries at the same time, but I think that would best be done either in a new bug or maybe one of the existing bugs above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
Yes, I wrote about this in https://bugzilla.mozilla.org/show_bug.cgi?id=1073827#c40 See also https://bugzilla.mozilla.org/show_bug.cgi?id=1073827#c33 I think the priority of choosing dictionaries should be discussed in that ticket -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
> that means I can only type English emails? You can type in any language, but only English dictionary will be enabled for such pages. You will have to manually enable multiple dictionaries via spellchecker context menu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
I often even mix multiple languages in the same text, for various reasons. In a multi-language context, this is quite common. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
When I wrote "can type", I meant of course with the spellchecker working in the language, assuming I have the right dictionary installed, without the spellchecker trying to tell me that **all** my _words_ are _wrong_ and _everything_ has a _red_ _underline_, which is _quite_ _annoying_. (Underline for illustration of the effect.) It would be quite a pity to do all this work in this bug, and then the spellchecker still assumes English, just because Gmail or Yahoo Mail or RoundCube or whatever web app is in English. How would RoundCube know which language I am writing the email in? I write emails (and text in webapps) in multiple languages, so this logic as stated in comment 38 would render the fix here moot in such situations and keep the spellchecker broken for all languages but one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
(In reply to Alexander Gavrilov from comment #36) > Has the about:config → spellchecker.dictionary setting been adapted to > support multiple dictionaries? In my tests setting it to something > comma-separated like "ru,en-US" does nothing. We first try to match the element or document language and then use this preference. So if we think the input is in en-US, and en-US is in the list of dictionaries in "spellchecker.dictionary", we'll only enable the en-US dictionary. If there's no match on the element or document, then all of the dictionaries in the pref are used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
> element or document language ... is ... en-US ..., we'll only enable the en-US dictionary So, if Gmail or Yahoo or RoundCube document was set to "en-US", that means I can only type English emails? Doesn't that counter the purpose of this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
I just did a fresh install (again) of Ubuntu Unity 22.04 (an iso I built just now) and it looks like dbus-x11 was not installed by default and installing it without touching gnome-session (and then rebooting) fixed the issue (I didn't install or remove any another packages). This works with both GDM and lightdm. Looks like gnome-session wasn't causing the issue and dbus-x11 was getting installed when installing gnome-session's old version, which is why it started working after installing the old version of gnome-session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: totem unable to play bbb mp4: "The specified movie could not be found"
** Changed in: totem (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: totem unable to play bbb mp4: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969637] Re: lookup table appears bottom left of application
Hi Gunnar, thank you for your testing! It is my current analysis: It must be caused by bottom two commits. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/e2d268eb00f06f497b2f62ae9f3b6e7e1fe4bd9e https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/c8981ef0b1e915e89c79e301080541baef0f9fa9 $ gsettings get org.gnome.desktop.interface gtk-im-module '' $ gsettings set org.gnome.desktop.interface gtk-im-module 'ibus' This command works as expected immediately. But according to commit messages, it is not intended for GNOME 42. And I don't know why Fedora 36 works so great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
** Also affects: gdm3 (Ubuntu Jammy) Importance: High Status: In Progress ** Changed in: gdm3 (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- 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/1968929 Title: Missing Wayland login option on NVIDIA systems Status in OEM Priority Project: New Status in gdm3 package in Ubuntu: In Progress Status in gdm3 source package in Jammy: In Progress Bug description: Impact - Systems using Nvidia graphics drivers should have an option to use Wayland but Xorg should be the default. Hybrid systems using Nvidia graphics drivers should use Wayland by default. Test Case - Create a new user (since existing users can choose their own session). Restart your system after applying the update. Select your name on the login screen. A gear button should appear in the lower right of the screen. Click the gear button. Ubuntu should be selected. If you are using a system with only an Nvidia graphics card (so your system is not a hybrid), there should be an Ubuntu on Wayland option. Otherwise, there should be an Ubuntu on Xorg option. What Could Go Wrong --- Hybrid systems should actually be using the Intel graphics for to run GNOME Shell so that's why it should be safe to use Wayland by default. There are some suspend & resume issues, an issue with gsync, etc. which is why Nvidia are requesting that we don't enable Wayland by default for systems that are only using the Nvidia graphics driver. We do still make it available in case someone really wants to try without needing to edit system files. Before last week, we were actually using Wayland by default for Nvidia systems so this upload returns most systems back to that status quo. Priority This is a high priority for the Desktop and OEM Teams and it's requested that this update be available as soon as possible after release. The desktop live session defaults to Xorg not Wayland so this doesn't impact that session at all. We are not going to delay the release to get this fix on the Ubuntu 22.04 desktop ISO. Original Bug Report --- I'm using Ubuntu 22.04 on a Dell G15 5511 laptop that have an NVIDIA 3060 GPU. I saw in the last update in the gdm3 package that Wayland will be disabled in machines with hybrid graphics. The question is: In this laptop I can enable optimus to use Intel and sometimes NVIDIA or keep only on NVIDIA (I use this option). So even it's detected two GPUs the Intel one is unused. I think the problem could extend for people with a desktop with an integrated intel GPU and a discrete NVIDIA GPU, since both will be present in the system. So maybe will be necessary to check with more accuracy to check if there are two GPUs, but only one is being used or have a documented option to force the enablement of Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: totem unable to play bbb mp4: "The specified movie could not be found"
Hmm, some interesting updates here. Firstly, here's the output from totem when run with "G_MESSAGES_DEBUG=all": (totem:38425): GLib-GIO-DEBUG: 11:13:06.494: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (totem:38425): dconf-DEBUG: 11:13:06.495: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.503: watch_established: "/org/gnome/Totem/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:06.530: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.530: watch_fast: "/org/gnome/desktop/peripherals/mouse/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.530: watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.531: watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.531: watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.531: watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.531: watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.531: watch_fast: "/org/gnome/desktop/a11y/interface/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:06.532: watch_established: "/org/gnome/desktop/interface/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:06.532: watch_established: "/org/gnome/desktop/peripherals/mouse/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:06.534: watch_established: "/org/gnome/desktop/sound/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:06.534: watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:06.534: watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:06.535: watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:06.535: watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:06.535: watch_established: "/org/gnome/desktop/a11y/interface/" (establishing: 1) (totem:38425): GLib-GIO-DEBUG: 11:13:06.678: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (totem:38425): GLib-DEBUG: 11:13:06.793: unsetenv() is not thread-safe and should not be used after threads are created (totem:38425): Gtk-DEBUG: 11:13:06.793: Connecting to session manager (totem:38425): Handy-DEBUG: 11:13:06.797: Trying to initialize portal (totem:38425): dconf-DEBUG: 11:13:07.282: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 1) (totem:38425): dconf-DEBUG: 11:13:07.282: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:07.283: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) (totem:38425): dconf-DEBUG: 11:13:07.549: watch_fast: "/org/gnome/desktop/thumbnailers/" (establishing: 0, active: 0) (totem:38425): dconf-DEBUG: 11:13:07.550: watch_established: "/org/gnome/desktop/thumbnailers/" (establishing: 1) (totem:38425): GLib-GIO-DEBUG: 11:13:07.559: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals (totem:38425): GLib-GIO-DEBUG: 11:13:07.569: _g_io_module_get_default: Found default implementation networkmanager (GNetworkMonitorNM) for ‘gio-network-monitor’ (totem:38425): dconf-DEBUG: 11:13:07.570: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:38425): dconf-DEBUG: 11:13:07.570: unwatch_fast: "/org/gnome/Totem/" (active: 3, establishing: 0) (totem:38425): GLib-GIO-DEBUG: 11:13:07.630: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’ (totem:38425): dconf-DEBUG: 11:13:07.813: change_fast (totem:38425): dconf-DEBUG: 11:13:07.815: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:38425): dconf-DEBUG: 11:13:07.816: unwatch_fast: "/org/gnome/Totem/" (active: 3, establishing: 0) (totem:38425): dconf-DEBUG: 11:13:07.816: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 2) (totem:38425): dconf-DEBUG: 11:13:07.834: watch_fast: "/org/gnome/Totem/" (establishing: 0, active: 3) (totem:38425): dconf-DEBUG: 11:13:07.862: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 1) (totem:38425): Totem-DEBUG: 11:13:08.657: TotemGrilo: Pausing videos thumbnailing (totem:38425): Totem-DEBUG: 11:13:08.675: totem_playlist_add_one_mrl (): big_buck_bunny_720p_surround.mp4 (null) (null) (null) 0 false (totem:38425): Totem-DEBUG: 11:13:08.719: Adding popup busy for reason opening file (totem:38425): Totem-DEBUG: 11:13:08.721: emitting PlaybackStatus change (totem:38425): Totem-DEBUG: 11:13:08.721: Not enabling offline save, as
[Desktop-packages] [Bug 1969767] [NEW] totem crashes when attempting to play mp4 files
Public bug reported: I can add and display a directory of .mp4 files in totem but when attempting to play any of them totem will crash. Any attempts to restart totem fail with the window not appearing at all. After several attempts to restart I can add an .mp4 file but any attempt to play it results in the described sequence repeating with sometimes the window not appearing, sometimes I can navigate to a local file and sometimes the above error is displayed as soon as totem's window is displayed. These reports have appeared on errors.ubuntu.com which relate to the most recent crashes: https://errors.ubuntu.com/oops/383cc642-c157-11ec-8afa-fa163e993415 https://errors.ubuntu.com/oops/37f3e83a-c157-11ec-a3c9-fa163ef35206 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 10:53:17 2022 InstallationDate: Installed on 2022-04-02 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969767 Title: totem crashes when attempting to play mp4 files Status in totem package in Ubuntu: New Bug description: I can add and display a directory of .mp4 files in totem but when attempting to play any of them totem will crash. Any attempts to restart totem fail with the window not appearing at all. After several attempts to restart I can add an .mp4 file but any attempt to play it results in the described sequence repeating with sometimes the window not appearing, sometimes I can navigate to a local file and sometimes the above error is displayed as soon as totem's window is displayed. These reports have appeared on errors.ubuntu.com which relate to the most recent crashes: https://errors.ubuntu.com/oops/383cc642-c157-11ec-8afa-fa163e993415 https://errors.ubuntu.com/oops/37f3e83a-c157-11ec-a3c9-fa163ef35206 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 10:53:17 2022 InstallationDate: Installed on 2022-04-02 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1969767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Re: Google Contacts API Deprecated
Fit it to work on Focal, one has to also backport this commit in EDS https://gitlab.gnome.org/GNOME/evolution-data- server/-/commit/adbd6fc07033b639a990467009bce416b87ef855 -- 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: Confirmed Status in evolution-data-server source package in Focal: Confirmed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released 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 1969619] Re: RDP Sharing appears on by default in jammy
** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center: Unknown Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Jammy: In Progress Bug description: Impact == 1. It looks like RDP Sharing is turned on but it is not. 2. To actually turn on RDP Sharing, you would need to turn it off then turn it on. This bugfix fixes it so that it correctly shown as off by default and turning it on works. Test Case = 0. Start with a clean Ubuntu 22.04 install. Or you can create a new user and log in as the new user. 1. Open the Settings app. 2. In the left sidebar, click Sharing. The switch at the top of the page needs to be off. 3. Turn the switch on. Then click Remote Desktop and turn it on. 4. Close the Settings app. 5. Open the Settings app and verify that Sharing is on and Remote Desktop is on. 6. Close the Settings app. 7. From a terminal, run systemctl --user status gnome-remote-sharing.service It should show the service as active (running) and a line at the bottom should say RDP server started 8. Then run systemctl --user stop gnome-remote-sharing.service 9. Open the Settings app. It should show that Remote Desktop sharing is off. 10. Turn on Sharing and turn on Remote Desktop sharing. 11. Run systemctl --user status gnome-remote-sharing.service It should show the service as active (running) and a line at the bottom should say RDP server started What Could Go Wrong === This is a minimal fix proposed upstream. The original implementation was insufficient. The bugfix will allow Remote Desktop to be turned on and work correctly from the beginning. More Details To simplify this bug report, I removed a lot of troubleshooting details that can still be seen with the "See full activity log" link Just opening the Sharing panel flips the gsettings key org.gnome.desktop.remote-desktop.rdp enable to true and apparently tries to start RDP sharing. RDP sharing doesn't work because the TLS keys weren't set yet. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969558] Re: Dragging one edge of a modal dialog moves the opposite edge
That's right, this becomes quite visible with Extension settings as they can be quite lengthy and the default window size it often too small. I am not sure I agree with the design choice but I believe that this is outside of the scope of this bug report so I'm happy for this report to be closed since the system behaves as intended. I will leave it to you and the design team to decide if you want to revisit this design choise in the future or not. -- 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/1969558 Title: Dragging one edge of a modal dialog moves the opposite edge Status in gnome-shell package in Ubuntu: Invalid Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969637] Re: lookup table appears bottom left of application
I tested on Debian testing too, and there it's even worse in Xorg sessions: When using gedit, I couldn't input using IBus IMs at all. Also there it helps to set GTK_IM_MODULSE=ibus. So I drafted a merge request with a possible im-config fix (or workaround): https://salsa.debian.org/input-method-team/im-config/-/merge_requests/15 But before doing anything I want to talk with some Debian folks. I'll submit a Debian bug report later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969512] Re: totem unable to play bbb mp4: "The specified movie could not be found"
We download and try to play locally (see item 12 in http://iso.qa.ubuntu.com/qatracker/milestones/432/builds/247134/testcases/1747/results for an example). I'll try and get some DEBUG output this morning (I can state it's definitely not crashing though; the error message simply appears and totem remains open, without playing anything, until closed). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: totem unable to play bbb mp4: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Incomplete Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969753] [NEW] gnome-power-statistics graph labels hard to read in dark mode
Public bug reported: I am running with Ubuntu set to dark mode. The graph labels on gnome- power-statistics are black on dark grey, which is very hard to read. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 11:20:41 2022 InstallationDate: Installed on 2022-03-17 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screenshot showing the problem" https://bugs.launchpad.net/bugs/1969753/+attachment/5582023/+files/Screenshot%20from%202022-04-21%2011-21-10.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1969753 Title: gnome-power-statistics graph labels hard to read in dark mode Status in gnome-power-manager package in Ubuntu: New Bug description: I am running with Ubuntu set to dark mode. The graph labels on gnome- power-statistics are black on dark grey, which is very hard to read. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 11:20:41 2022 InstallationDate: Installed on 2022-03-17 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1969753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966091] Re: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic
Also with new 5.13.0-40-generic the issue is still available for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1966091 Title: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a recent update to linux-image-5.13.0-37-generic, I started experiencing random noises about every five seconds. After rebooting into linux-image-5.13.0-35-generic, the noises were gone. Some details that I've noticed: 1. When launching pulseaudio manually, not as a daemon, the problem disappears. 2. If I set the log-level in /etc/pulse/daemon.conf to debug and reload it, the log has a lot of: Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Which roughly correspond with the noises. 3. The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa force-reload" doesn't seem to help. Only a kernel downgrade does. 4. This happens both in Firefox (where I first noticed it) as well as in Totem and in system sounds. 5. I tried to report the bug using "ubuntu-bug audio", but it showed me six inputs of which three looked the same, and for each of them it told me that it pulseaudio wasn't configured to use it. I'm ready to collect logs and other info within the next days. Additional Info $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal $ apt-cache policy linux-image-generic-hwe-20.04 linux-image-generic-hwe-20.04: Installed: 5.13.0.37.42~20.04.22 Candidate: 5.13.0.37.42~20.04.22 Version table: *** 5.13.0.37.42~20.04.22 500 500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages 500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
So you can minimize this window and then have working Unity. If you close it, your session ends. This window belongs to a process of /usr/libexec/gnome-session-failed ** Attachment added: "jammy-error-moved-aside.png" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+attachment/5582021/+files/jammy-error-moved-aside.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
Confirm (in KVM machines) that Unity works fine from gdm3 under Impish, but a fresh VM of Jammy doesn't work with either lightdm or gdm for me. I get to see a quick glimpse of the Unity desktop, then this fullscreen splash error shows up "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. All extensions have been disabled as a precaution." Since it refers to extensions, I presume this is a part of GNOME Shell. However... if you use the keyboard shortcut to left-split the window (ctrl-super-left) ... you can see the Unity desktop is running. (I first tried ctrl-alt-t to summon a terminal above it but the window is always- on-top, I saw it lose focus though.) ** Attachment added: "jammy-gnome-shell-error.png" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+attachment/5582020/+files/jammy-gnome-shell-error.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968635] Re: Chromium window empty
*** This bug is a duplicate of bug 1966108 ***
https://bugs.launchpad.net/bugs/1966108
** This bug has been marked a duplicate of bug 1966108
Chromium snap on Jammy system with nvidia-510 does not start
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1968635
Title:
Chromium window empty
Status in chromium-browser package in Ubuntu:
New
Bug description:
The browser starts, but the entire user interface apart from the
window's border is missing.
This is what gets displayed when the browser is started via CLI:
Gtk-Message: 00:45:30.672: Failed to load module "canberra-gtk-module"
Gtk-Message: 00:45:30.673: Failed to load module "canberra-gtk-module"
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open nvidia-drm:
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so:
cannot open shared object file: Permission denied (search paths
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: nvidia-drm
MESA-LOADER: failed to open kms_swrast:
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/kms_swrast_dri.so:
cannot open shared object file: Permission denied (search paths
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast:
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so:
cannot open shared object file: Permission denied (search paths
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
failed to load swrast driver
[740332:740418:0412/004535.002377:ERROR:udev_watcher.cc(98)] Failed to begin
udev enumeration.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 00:43:30 2022
InstallationDate: Installed on 2022-02-23 (47 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Snap.ChromeDriverVersion: ChromeDriver 100.0.4896.75
(d9568d04d7dd79269c5a655d7ada69650c5a8336-refs/branch-heads/4896@{#1007})
Snap.ChromiumVersion: Chromium 100.0.4896.75 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968635/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969709] Re: libreoffice font selection unusably slow
** Also affects: fontconfig (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in fontconfig package in Ubuntu: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures. The CPU jumps to 100% and the whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. The only thing that works is disabling font previews. I have downgraded to 7.2 for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
