[Desktop-packages] [Bug 1963732] Re: xdg-desktop-portal crashed with SIGSEGV in g_mutex_lock()
*** This bug is a duplicate of bug 1958157 *** https://bugs.launchpad.net/bugs/1958157 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1958157, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1963732/+attachment/5565956/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1963732/+attachment/5565958/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1963732/+attachment/5565961/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1963732/+attachment/5565962/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1963732/+attachment/5565963/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1963732/+attachment/5565964/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1963732/+attachment/5565965/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1958157 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1963732 Title: xdg-desktop-portal crashed with SIGSEGV in g_mutex_lock() Status in xdg-desktop-portal package in Ubuntu: New Bug description: No idea what triggered this. Was using Firefox and an error dialog appeared. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.12.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Feb 28 23:41:47 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2021-03-31 (339 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210329) ProcCmdline: /usr/libexec/xdg-desktop-portal ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SegvAnalysis: Segfault happened at: 0x7f00f8863049 : lock xadd %eax,(%rdi) PC (0x7f00f8863049) ok source "%eax" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () () at /lib/x86_64-linux-gnu/libffi.so.8 Title: xdg-desktop-portal crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1963732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1962043] Re: libwacom9 : depends on : libwacom-common
Hello, today I tried to uninstall the libinput2 package, but I don't have this package installed on my raspberry pi. The package cannot even be installed - the package cannot be found. Best Regards Dne 28.02.2022 v 17:33 Sebastien Bacher napsal(a): > could you try to sudo apt remove libinput2? > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1962043 Title: libwacom9 : depends on : libwacom-common Status in libwacom package in Ubuntu: Confirmed Bug description: Broken denpendency on ARM64: (rpi4 @ ubuntu 22.04 test) libwacom9 : depend on: libwacom-common (= 2.1.0-2) but will be installed 1.12-1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwacom-common 1.12-1 ProcVersionSignature: Ubuntu 5.15.0-1002.2-raspi 5.15.12 Uname: Linux 5.15.0-1002-raspi aarch64 ApportVersion: 2.20.11-0ubuntu78 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Feb 23 21:03:57 2022 Dependencies: DistUpgraded: 2022-02-11 12:31:30,541 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: wireguard/1.0.20210606: added GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:7D:95:B4 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: libwacom UpgradeStatus: Upgraded to jammy on 2022-02-11 (12 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1962043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1962043] Re: libwacom9 : depends on : libwacom-common
Hello, my apt sources.list deb http://ports.ubuntu.com/ubuntu-ports/ jammy main universe deb http://ports.ubuntu.com/ubuntu-ports/ jammy-security universe main deb http://ports.ubuntu.com/ubuntu-ports/ jammy-updates universe main deb http://ports.ubuntu.com/ubuntu-ports/ jammy-backports universe main Best Regards Dne 28.02.2022 v 17:33 Sebastien Bacher napsal(a): > could you try to sudo apt remove libinput2? > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1962043 Title: libwacom9 : depends on : libwacom-common Status in libwacom package in Ubuntu: Confirmed Bug description: Broken denpendency on ARM64: (rpi4 @ ubuntu 22.04 test) libwacom9 : depend on: libwacom-common (= 2.1.0-2) but will be installed 1.12-1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwacom-common 1.12-1 ProcVersionSignature: Ubuntu 5.15.0-1002.2-raspi 5.15.12 Uname: Linux 5.15.0-1002-raspi aarch64 ApportVersion: 2.20.11-0ubuntu78 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Feb 23 21:03:57 2022 Dependencies: DistUpgraded: 2022-02-11 12:31:30,541 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: wireguard/1.0.20210606: added GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:7D:95:B4 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: libwacom UpgradeStatus: Upgraded to jammy on 2022-02-11 (12 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1962043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
How helpful to you would it be for me to install the .ddeb file and which of the traces would you want me to run again? Would I do the install via sudo dpkg -i or use synaptic or apt in some manner? Should I uninstall it after the traces? Obviously I would need to do the traces you want prior to falling back to the earlier release of the packages. I am running linux mint cinnamon x64 20.3 which is based on ubuntu focal. The updates were applied from a mirror of the focal updates repository, thus I contacted you when the problem arose. The desktop environment is cinnamon 5.2.7 here. I have some cinnamon applets installed and can provide you any details you deem appropriate. Have any similar reports been filed on this, or is this something that seems to manifest only on my particular system for some reason? Is my system or my usage of it uncommon enough that you have receive no other reports of a total inability to use programs such as I am encountering? Thank you again for your assistance in this matter. I trust backing this update out should solve the problem. Looking at the build date on the launchpad page I certainly would have been running them for almost two years on this system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Per the above dpkg search and looking at /var/cache/apt/archives I see the following: -rw-r--r-- 1 root root195976 Feb 16 05:54 gir1.2-gtk-3.0_3.24.20-0ubuntu1.1_amd64.deb -rw-r--r-- 1 root root 28756 Feb 16 05:54 gtk-update-icon-cache_3.24.20-0ubuntu1.1_amd64.deb -rw-r--r-- 1 root root 22380 Feb 16 05:54 libgail-3-0_3.24.20-0ubuntu1.1_amd64.deb -rw-r--r-- 1 root root 2620492 Feb 16 05:54 libgtk-3-0_3.24.20-0ubuntu1.1_amd64.deb -rw-r--r-- 1 root root 61884 Feb 16 05:54 libgtk-3-bin_3.24.20-0ubuntu1.1_amd64.deb -rw-r--r-- 1 root root234388 Feb 16 05:54 libgtk-3-common_3.24.20-0ubuntu1.1_all.deb So I should download the corresponding files from launchpad to a new directory and then issue the sudo dpkg -i *.deb command from there to replace the updated files on my system, correct? Should there be anything else I ought to do before issuing the sudo dpkg command? Should I take any action to ensure I don't accidentally "update" these files and get back into the same situation? I think I can "lock" them in synaptic and there may be other ways to accomplish the same thing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946525] Re: Removable media are not mounted automatically
Noob to Ubuntu... I have a similar problem with a U.S. Robotics USR5637 modem. lsusb and usb-devices both show the device, and dmesg shows it being recognized, however it does not show up in /dev as ttyACM*. Running 21.10 on a Raspberry Pi 4. The device works as expected with 20.04.3 LTS also on a Pi 4. I tried Henrik Dahle's work around of reinstalling fuse simply because he had luck with it, but no joy. The device is also not created with it installed during a reboot. lsusb: Bus 001 Device 008: ID 0baf:0303 U.S. Robotics USR5637 56K Faxmodem usb-devices: T: Bus=01 Lev=04 Prnt=06 Port=01 Cnt=01 Dev#= 8 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0baf ProdID=0303 Rev=02.00 S: Manufacturer=U.S.Robotics S: Product=USB Modem S: SerialNumber=002 C: #Ifs= 2 Cfg#= 2 Atr=80 MxPwr=360mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=(none) I: If#=0x1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none) dmesg: [ 127.376952] usb 1-1.2.4.1: new high-speed USB device number 7 using xhci_hcd [ 127.585699] usb 1-1.2.4.1: New USB device found, idVendor=0baf, idProduct=0303, bcdDevice= 2.00 [ 127.585739] usb 1-1.2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=10 [ 127.585757] usb 1-1.2.4.1: Product: USB Modem [ 127.585771] usb 1-1.2.4.1: Manufacturer: U.S.Robotics [ 127.585784] usb 1-1.2.4.1: SerialNumber: 002 [ 127.747138] kauditd_printk_skb: 518 callbacks suppressed [ 127.747159] audit: type=1400 audit(1646439492.316:597): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.1/busnum" pid=2810 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 127.747191] audit: type=1400 audit(1646439492.316:598): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/platform/scb/fd50.pcie/pci:00/:00:00.0/:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.1/devnum" pid=2810 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Removable media are not mounted automatically Status in udisks2 package in Ubuntu: Confirmed Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 471650] Re: system-config-printer can't find dbus module
Cf.: https://bugs.launchpad.net/ubuntu/+source/system-config- printer/+bug/1963723. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/471650 Title: system-config-printer can't find dbus module Status in cups package in Ubuntu: Expired Bug description: Binary package hint: cups Using the menus Admin/Printing hangs for a bit, then just dies silently. running from the command line: > rik@monk:~$ system-config-printer > Traceback (most recent call last): > File "/usr/share/system-config-printer/system-config-printer.py", line 30, in ? > import dbus > ImportError: No module named dbus i tried to manually check to see what sys.path is available, but don't really know what system-config-printer requires? rik@monk:~$ /usr/bin/env python Python 2.4.4 (#1, Nov 8 2008, 19:16:01) [GCC 4.3.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import dbus Traceback (most recent call last): File "", line 1, in ? ImportError: No module named dbus >>> import sys >>> sys.path ['', '/usr/local/lib/python24.zip', '/usr/local/lib/python2.4', '/usr/local/lib/python2.4/plat-linux2', '/usr/local/lib/python2.4/lib-tk', '/usr/local/lib/python2.4/lib-dynload', '/usr/local/lib/python2.4/site-packages', '/usr/local/lib/python2.4/site-packages/PIL'] ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 MachineType: LENOVO 2055W1W Package: cups 1.3.9-17ubuntu3.2 Papersize: letter PpdFiles: hp1200: HP LaserJet 1200 Foomatic/hpijs, hpijs 2.8.7 ProcCmdLine: root=UUID=7e2488f5-5963-409b-9069-39f19996edc8 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-16.55-generic SourcePackage: cups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/471650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963723] [NEW] Crash: 'No module named "dbus"'
Public bug reported: $ system-config-printer Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 29, in import dbus ModuleNotFoundError: No module named 'dbus' I have the problem on Linux Mint 20.3 Cinnamon, which is based upon Ubuntu 20.04; and/but a Mint developer advised me to report the problem here. $ apt list system-config-printer Listing... Done system-config-printer/focal-updates,focal-updates,now 1.5.12-0ubuntu1.1 all [installed] Cf. (among others?) ##1057256, 819053 ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: crash dbus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1963723 Title: Crash: 'No module named "dbus"' Status in system-config-printer package in Ubuntu: New Bug description: $ system-config-printer Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 29, in import dbus ModuleNotFoundError: No module named 'dbus' I have the problem on Linux Mint 20.3 Cinnamon, which is based upon Ubuntu 20.04; and/but a Mint developer advised me to report the problem here. $ apt list system-config-printer Listing... Done system-config-printer/focal-updates,focal-updates,now 1.5.12-0ubuntu1.1 all [installed] Cf. (among others?) ##1057256, 819053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1963723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
the segfault seems to be in the gtk menu code, do ypu have any special indicator or plugin installed? what desktop environment do you use? it would also help to get details on the backtrace if https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.32-4ubuntu4/+build/18229140/+files/libgtk2.0-0-dbgsym_2.24.32-4ubuntu4_amd64.ddeb was installed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.
Still crashes - albeit a bit differently now. Follow the directions and it crashes at the same point, but not everything closes - just the last two LibreOffice applications close (math and writer). -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
you can find the deb files on https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1/+build/19437463 check on your system the packages from that source using $ dpkg -l | grep 3.24.20-0ubuntu1.1 and download in a new directory the corresponding deb from the webpage, then install them using $ sudo dpkg -i *.deb in the directory where you downloaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
** Description changed: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] + system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok + system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok + + [PR] + https://github.com/tseliot/ubuntu-drivers-common/pull/68 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963712] [NEW] FFE: Switch from apt to apt_pkg bindings
Public bug reported: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
I was going to add a copy of the libgail-3-0 package that was working for me to my local repository to see if I could prepare to attempt to back out the update. I am having difficulty locating a copy of the package that was replaced. I have access to 3.24.18 in the main repository and the failing one in the updates, but a search for the one that was replaced has failed. I am looking for: libgail-3-0_3.24.20-0ubuntu1_amd64.deb This appears to no longer be available. Am I missing something? I am looking for advice on my next step to recover from this failure. Is the data available from the three back traces sufficient to isolate the part of the recent updates that needs to be backed out? If it is indeed libgail-3-0 should I back it out to the 3.24.18 version available in main? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963701] [NEW] [NVIDIA][Wayland] graphic target not able to reach
Public bug reported: [Steps to reproduce] 1. Have an I+N desktop. 2. Attach monitor to dGPU (nvidia) 3. install jammy daily build with enable third-party (to install nvidia-510) 4. dist-upgrade 5. reboot the system and make sure the system starts with Wayland [Expected result] System launch gdm login screen without problem [Actual result] System stuck with blackscreen [Other information] $ systemctl list-jobs JOB UNIT TYPE STATE 140 system-getty.slice start waiting 2 multi-user.targetstart waiting 1 graphical.target start waiting 165 plymouth-quit-wait.service start running 8 setvtrgb.service start waiting 110 systemd-update-utmp-runlevel.service start waiting 6 jobs listed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 [modified: lib/udev/rules.d/61-gdm.rules] ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 5 00:15:24 2022 InstallationDate: Installed on 2022-01-20 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220109) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-03-04T20:36:36.997559 ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy oem-priority originate-from-1956556 sutton -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: New Bug description: [Steps to reproduce] 1. Have an I+N desktop. 2. Attach monitor to dGPU (nvidia) 3. install jammy daily build with enable third-party (to install nvidia-510) 4. dist-upgrade 5. reboot the system and make sure the system starts with Wayland [Expected result] System launch gdm login screen without problem [Actual result] System stuck with blackscreen [Other information] $ systemctl list-jobs JOB UNIT TYPE STATE 140 system-getty.slice start waiting 2 multi-user.targetstart waiting 1 graphical.target start waiting 165 plymouth-quit-wait.service start running 8 setvtrgb.service start waiting 110 systemd-update-utmp-runlevel.service start waiting 6 jobs listed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 [modified: lib/udev/rules.d/61-gdm.rules] ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 5 00:15:24 2022 InstallationDate: Installed on 2022-01-20 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220109) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-03-04T20:36:36.997559 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944113]
(In reply to GeneC from comment #16) > Xcb is a not great workaround; at least for me on 4k monitor, it looks > pretty icky. Fonts render quite poorly. Another option is to use the more mature gtk3 VCL plugin by setting environment variable SAL_USE_VCLPLUGIN=gtk3 -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962021] Re: Make the deb package install the firefox snap
I just found it completely trashed my system on install. The reason was that I don't have snapd on my machine and installation attempted to install it, causing X to crash and login to reject my account because I'm not in 'nopasswdlogin' group. Reverting back to firefox=97.0.1+build1-0ubuntu1 and setting "apt-mark hold firefox" fixed the issue. -- 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/1962021 Title: Make the deb package install the firefox snap Status in firefox package in Ubuntu: In Progress Bug description: Canonical and Mozilla are working together to make the firefox snap the only supported package in Ubuntu, thus deprecating the deb package in the archive. This bug tracks the transformation of the firefox package in the archive into a transitional package that installs the snap, much like was done for chromium-browser in Ubuntu 19.10. There are a number of known problems and regressions with the snap compared to the deb (see https://bugzilla.mozilla.org/show_bug.cgi?id=snap and https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap), those are actively being worked on and will be addressed in due time, please refrain from using this bug to point them out. Instead, file separate bugs in the upstream bug tracker (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify this is about the snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Found yet another program with the same crash. To my untrained eyes the failure appears to start with gdk_display_open_default_libgtk_only in all three of these crashes. Is it possible that this crash impacts ALL gtk2 dependent programs? ** Attachment added: "gdb-gimp.txt" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+attachment/5565819/+files/gdb-gimp.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961565] Re: Package in bionic installs unnecessary build artifacts
This bug was fixed in the package chromium-browser - 99.0.4844.51-0ubuntu0.18.04.1 --- chromium-browser (99.0.4844.51-0ubuntu0.18.04.1) bionic; urgency=medium * Upstream release: 99.0.4844.51 - CVE-2022-0789: Heap buffer overflow in ANGLE. - CVE-2022-0790: Use after free in Cast UI. - CVE-2022-0791: Use after free in Omnibox. - CVE-2022-0792: Out of bounds read in ANGLE. - CVE-2022-0793: Use after free in Views. - CVE-2022-0794: Use after free in WebShare. - CVE-2022-0795: Type Confusion in Blink Layout. - CVE-2022-0796: Use after free in Media. - CVE-2022-0797: Out of bounds memory access in Mojo. - CVE-2022-0798: Use after free in MediaStream. - CVE-2022-0799: Insufficient policy enforcement in Installer. - CVE-2022-0800: Heap buffer overflow in Cast UI. - CVE-2022-0801: Inappropriate implementation in HTML parser. - CVE-2022-0802: Inappropriate implementation in Full screen mode. - CVE-2022-0803: Inappropriate implementation in Permissions. - CVE-2022-0804: Inappropriate implementation in Full screen mode. - CVE-2022-0805: Use after free in Browser Switcher. - CVE-2022-0806: Data leak in Canvas. - CVE-2022-0807: Inappropriate implementation in Autofill. - CVE-2022-0808: Use after free in Chrome OS Shell. - CVE-2022-0809: Out of bounds memory access in WebXR. * debian/rules: exclude unnecessary build artifacts (LP: #1961565) * debian/patches/arm64-no-pointer-authentication.patch: added * debian/patches/build-with-old-libva-missing-defines.patch: refreshed * debian/patches/build-with-old-libva-no-av1.patch: refreshed * debian/patches/configuration-directory.patch: refreshed * debian/patches/define__libc_malloc.patch: updated * debian/patches/gn-no-std-equal_to.patch: added * debian/patches/libaom-armhf-build-cpudetect.patch: refreshed * debian/patches/revert-sequence-checker-capability-name.patch: refreshed * debian/patches/search-credit.patch: refreshed * debian/patches/set-rpath-on-chromium-executables.patch: refreshed * debian/patches/suppress-newer-clang-warning-flags.patch: refreshed * debian/patches/use-clang-versioned.patch: refreshed * debian/patches/widevine-enable-version-string.patch: refreshed -- Olivier Tilloy Tue, 01 Mar 2022 21:43:44 +0100 ** Changed in: chromium-browser (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0789 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0790 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0791 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0792 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0793 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0794 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0795 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0796 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0797 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0798 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0799 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0800 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0801 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0802 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0803 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0804 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0805 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0806 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0807 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0808 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0809 -- 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/1961565 Title: Package in bionic installs unnecessary build artifacts Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser source package in Bionic: Fix Released Bug description: Not sure when this started happening, but today I noticed while testing chromium-browser 98.0.4758.102-0ubuntu0.18.04.1 that the chromium-browser binary package installs a lot of build artifacts that increase unnecessarily the size of the package. These artifacts include *.runtime_deps files, as well as binaries such as transport_security_state_generator or protozero_plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1961565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
@Chris: ok, we'll sort this out, and let you know, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in OEM Priority Project:
New
Status in iio-sensor-proxy package in Ubuntu:
Fix Committed
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963691] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1962761, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1963691/+attachment/5565804/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1963691/+attachment/5565806/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1963691/+attachment/5565810/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1963691/+attachment/5565811/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1963691/+attachment/5565812/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1963691/+attachment/5565813/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1963691/+attachment/5565814/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1962761 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1963691 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: New Bug description: I was working with another app/window and popped up an error window. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~beta-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 4 14:34:10 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2022-01-07 (55 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220106) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7ff61780a9a8 : cmp %rax,(%rbx) PC (0x7ff61780a9a8) ok source "%rax" ok destination "(%rbx)" (0x000a) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1963691/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024] Re: firefox fails to use the default profile from classic snaps
This error is extremely annoying, in my case I am using slack and chrome and it is also affected. -- 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/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Fix Released Status in snapd: Invalid Status in firefox package in Ubuntu: Fix Committed Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963684] [NEW] [20252, Intel Haswell HDMI, Digital Out, HDMI] Background noise or low volume
Public bug reported: Sound is too low when built_in speaker working. I hear low frequencies better. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: easear 1541 F pulseaudio /dev/snd/controlC0: easear 1541 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 4 15:36:39 2022 InstallationDate: Installed on 2022-02-28 (3 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20252, Intel Haswell HDMI, Digital Out, HDMI] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.release: 0.24 dmi.bios.vendor: LENOVO dmi.bios.version: 8ECN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Ginkgo 7A1 dmi.board.vendor: LENOVO dmi.board.version: 3194Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G710 dmi.ec.firmware.release: 0.16 dmi.modalias: dmi:bvnLENOVO:bvr8ECN24WW:bd09/26/2013:br0.24:efr0.16:svnLENOVO:pn20252:pvrLenovoG710:rvnLENOVO:rnGinkgo7A1:rvr3194Std:cvnLENOVO:ct10:cvrLenovoG710:skuLENOVO_MT_20252: dmi.product.family: IDEAPAD dmi.product.name: 20252 dmi.product.sku: LENOVO_MT_20252 dmi.product.version: Lenovo G710 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1963684 Title: [20252, Intel Haswell HDMI, Digital Out, HDMI] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: Sound is too low when built_in speaker working. I hear low frequencies better. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: easear 1541 F pulseaudio /dev/snd/controlC0: easear 1541 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 4 15:36:39 2022 InstallationDate: Installed on 2022-02-28 (3 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20252, Intel Haswell HDMI, Digital Out, HDMI] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.release: 0.24 dmi.bios.vendor: LENOVO dmi.bios.version: 8ECN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Ginkgo 7A1 dmi.board.vendor: LENOVO dmi.board.version: 3194Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G710 dmi.ec.firmware.release: 0.16 dmi.modalias: dmi:bvnLENOVO:bvr8ECN24WW:bd09/26/2013:br0.24:efr0.16:svnLENOVO:pn20252:pvrLenovoG710:rvnLENOVO:rnGinkgo7A1:rvr3194Std:cvnLENOVO:ct10:cvrLenovoG710:skuLENOVO_MT_20252: dmi.product.family: IDEAPAD dmi.product.name: 20252 dmi.product.sku: LENOVO_MT_20252 dmi.product.version: Lenovo G710 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1963684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932005] Re: nm-applet not showing in system tray
Hello all, I've upgraded to the latest 20.04.04 LTS, and network-manager is 1.22.10-1ubuntu2.3 nm-applet is still not showing in the system tray. After a little of tinkering, I believe the issue is with the system tray. I have tried loading flameshot that sits in the system tray, is also not showing. I've attach a screen shoot. I have tried uninstall indicator-notifications and ayatana-indicator- notifications and reinstalling them and no luck. I have switched to awesomewm and openbox with polybar and tint2 and the system tray work fine in those, except in mate enviroment. ** Attachment added: "systemtray.png" https://bugs.launchpad.net/ubuntu-mate/+bug/1932005/+attachment/5565781/+files/systemtray.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1932005 Title: nm-applet not showing in system tray Status in Ubuntu MATE: New Status in network-manager-applet package in Ubuntu: New Bug description: Hello all, I noticed this morning that the network options (i am not sure if it suppose to be nm-applet) is no longer showing in system tray and for a while now that KDE Connect indicator is not showing in the system tray. I am currently Ubuntu Mate 20.04 on a raspberry PI400 uname -a Linux pi400 5.4.0-1036-raspi #39-Ubuntu SMP PREEMPT Wed May 12 17:37:51 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal apt policy network-manager network-manager: Installed: 1.22.10-1ubuntu2.2 Candidate: 1.22.10-1ubuntu2.2 Version table: *** 1.22.10-1ubuntu2.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages Does anyone else have a similar issue? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1932005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] Re: Screencast not recording
Turned out that these 2 packages were missing in my host and are required for proper functionality: pipewire-media-session libpipewire-0.3-common After adding these and rebooting everything works finally! Please, close this ticket -- 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/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: New Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714763] Re: No way to disable system startup sound
I have found a specific way to stop this by getting visit https://betterscapeslv.com/ and learn a lot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1714763 Title: No way to disable system startup sound Status in libcanberra package in Ubuntu: New Bug description: Package gnome-session-canberra contains /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop file, which plays extremely annoying drum sound at every boot. This is a problem (at least for me, but I think for many others), and there is no way to disable this without changing package-provided files. Moreover, this package (gnome-session-canberra) couldn't be removed without breaking ubuntu-desktop package (I'll file separate bugreport for this). Propose: Create a way do disable those sounds in a user-available way. The simplest way I can propose is to mark /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop as conffile, which will keep user changes in this file during package upgrade. More user-friendly (visible) changes would be appreciated too, but conffile should, at least, give some way to manage loud 'blam-blam' at boot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session-canberra 0.30-3ubuntu1 [modified: usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop] ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Sun Sep 3 12:55:31 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (73 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: libcanberra UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1714763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
** Changed in: iio-sensor-proxy (Ubuntu)
Importance: Undecided => High
** Changed in: iio-sensor-proxy (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in iio-sensor-proxy package in Ubuntu:
Fix Committed
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962591] Re: [MIR] mozjs91
The package has been promoted to release by @doko on 2022-03-02 14:48:55 CET ** Changed in: mozjs91 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs91 in Ubuntu. https://bugs.launchpad.net/bugs/1962591 Title: [MIR] mozjs91 Status in mozjs91 package in Ubuntu: Fix Released Bug description: This is just a version bump based on the same sources that are in main already. gjs is the only dependency pulling in mozjs, so we should demote mozjs78 and promote mozjs91 instead. https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1683937 https://wiki.ubuntu.com/SecurityTeam/FAQ#mozjs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs91/+bug/1962591/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] Re: Screencast not recording
I got a bit further. gstreamer1.0-pipewire was installed but for some reason gstreamer did not pick it up. Even after reinstalling, it still was not listed as a gstreamer plugin. I had to physically remove the libgstpipewire so, restart streamer and then put it back. After that gstreamder picks the plugin and this error "no element pipewiresrc" occurs no more. However, recording still does not work properly The recording indicator appears, the file appears as well but has no content (0 size). journalctl log Mar 04 10:42:08 Development dbus-daemon[2781]: [session uid=1000 pid=2781] Activating service name='org.gnome.Shell.Screencast' requested by ':1.64' (uid=1000 pid=3358 comm="/usr/libexec/gsd-media-keys " label="unconfine> Mar 04 10:42:08 Development dbus-daemon[2781]: [session uid=1000 pid=2781] Successfully activated service 'org.gnome.Shell.Screencast' Mar 04 10:42:36 Development dbus-daemon[2781]: [session uid=1000 pid=2781] Activating service name='org.gnome.Shell.Screencast' requested by ':1.64' (uid=1000 pid=3358 comm="/usr/libexec/gsd-media-keys " label="unconfine> Mar 04 10:42:36 Development dbus-daemon[2781]: [session uid=1000 pid=2781] Successfully activated service 'org.gnome.Shell.Screencast' Mar 04 10:42:38 Development dbus-daemon[2781]: [session uid=1000 pid=2781] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.4' (uid=1000 pid=> Mar 04 10:42:38 Development systemd[2764]: Starting Tracker metadata extractor... Mar 04 10:42:38 Development dbus-daemon[2781]: [session uid=1000 pid=2781] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' Mar 04 10:42:38 Development systemd[2764]: Started Tracker metadata extractor. I cannot even stop the recording. It is stuck. -- 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/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: New Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts
Exactly, so at the moment only the following are affected: - impish - jammy I've added a few comments to the arctica-greeter repo and issued a pull request that basically reverts the commit that introduced the weakness. However this still needs to be reviewed by the maintainers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961857] Re: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r30
Hello. No news about this ? Computer being unusable, should I switch back to 18.04 or buy a new computer ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961857 Title: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_state() Status in compiz package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding compiz. This problem was most recently seen with package version 1:0.9.14.1+20.04.20200211-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/253612f74aa79d2e52b8f27505f04cb72de285c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] Re: Screencast not recording
But you are right gst-inspect-1.0 pipewiresrc No such element or plugin 'pipewiresrc' something is odd with my installation. I tried reinstalling the gstreamer1.0-pipewire but still the same. Will try think of something -- 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/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: New Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] Re: Screencast not recording
Similarly this does not work gst-launch-1.0 pipewiresrc ERROR: pipeline could not be constructed: no element "pipewiresrc" but it works on the VM -- 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/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: New Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] Re: Screencast not recording
I have found this little python script which also suffers from the same
issue.
When run as
GST_DEBUG=3 python gnome-screen-cast.py
I get the following output:
session path: /org/gnome/Mutter/ScreenCast/Session/u16
stream path: /org/gnome/Mutter/ScreenCast/Stream/u16
added
0:00:00.019493755 132581 0xecbd30 WARN GST_ELEMENT_FACTORY
gstelementfactory.c:701:gst_element_factory_make_with_properties: no such
element factory "pipewiresrc"!
0:00:00.019526231 132581 0xecbd30 ERROR GST_PIPELINE
gst/parse/grammar.y:851:priv_gst_parse_yyparse: no element "pipewiresrc"
0:00:00.020452889 132581 0xecbd30 ERROR GST_PIPELINE
gst/parse/grammar.y:939:priv_gst_parse_yyparse: link has no source
[sink=@0xf28d50]
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 232, in
maybe_handle_message
self._handler(*args, **kwargs)
File "/home/jakub/Downloads/gnome-screen-cast.py", line 82, in
on_pipewire_stream_added
pipeline = Gst.parse_launch('pipewiresrc path=%u ! %s videoconvert !
glimagesink'%(node_id, format_element))
gi.repository.GLib.GError: gst_parse_error: no element "pipewiresrc" (1)
Still complains about some missing element
** Attachment added: "gnome-screen-cast"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+attachment/5565631/+files/gnome-screen-cast.py
--
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/1963264
Title:
Screencast not recording
Status in gnome-shell package in Ubuntu:
New
Bug description:
When I press Ctrl+Shift+Alt+R, screencast indicator appears in the
indicator menu but disappears in about 2 seconds. No file is even
created under the Videos folder.
journalctl shows:
Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962]
Activating service name='org.gnome.Shell.Screencast' requested by ':1.62'
(uid=1000 pid=3311 comm="/usr/libexec/gsd-media->
Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962]
Successfully activated service 'org.gnome.Shell.Screencast'
Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962]
Activating service name='org.gnome.Shell.Screencast' requested by ':1.62'
(uid=1000 pid=3311 comm="/usr/libexec/gsd-media->
Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962]
Successfully activated service 'org.gnome.Shell.Screencast'
Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline:
Gst.ParseError: no element "pipewiresrc"
The issue is the Gst.ParseError.
Before upgrading to jammy (22.04), it used to work fine. Also, when
testing under qemu/KVM it works properly. It just doesn't work when
running directly on the PC.
What other logs can I provide?
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 3 15:41:44 2022
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-12 (660 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963264] Re: Screencast not recording
Yes, I do. Like I said, it works on my VM (almost the same installation) but not on the host. I am thinking about trying to build some older pipewire version just for testing. -- 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/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: New Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
> isn't that the real issue? is that an hardware or firmware bug? could
it be fixed rather than worked around in udev rules?
It's their hardware limitation that vendors are unable to handle.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in iio-sensor-proxy package in Ubuntu:
New
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963241] Re: [FFe] evince 42
** Description changed: - . + Why Needed + -- + The Ubuntu Desktop had a goal of including as much of GNOME 42 as possible in Ubuntu 22.04 LTS. (One major exception was where apps had switched to GTK4). + + The evince document viewer (PDFs and more) did not have earlier releases + in the 42 cycle and its Beta wasn't released until March 3, a week after + Feature Freeze. + + The Ubuntu Desktop Team commits to packaging the final evince 42 stable + release and working to fix any regressions introduced in the update. We + do have the ability to use a "really" version number in case we decide + we need to go back to the 41 version. + + What Changed + + https://gitlab.gnome.org/GNOME/evince/-/blob/42.beta/NEWS + + https://gitlab.gnome.org/GNOME/evince/-/compare/41.3...42.beta + + For this release I have reverted 2 commits that required a new version + of libarchive since that wasn't included in 22.04 LTS yet. + + Build Test + -- + Builds successfully + + Install Test + + $ sudo apt install ./../build-area/*ev*.deb + Reading package lists... Done + Building dependency tree... Done + Reading state information... Done + Note, selecting 'evince' instead of './../build-area/evince_42~beta-1_amd64.deb' + Note, selecting 'evince-common' instead of './../build-area/evince-common_42~beta-1_all.deb' + Note, selecting 'gir1.2-evince-3.0' instead of './../build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb' + Note, selecting 'libevdocument3-4' instead of './../build-area/libevdocument3-4_42~beta-1_amd64.deb' + Note, selecting 'libevview3-3' instead of './../build-area/libevview3-3_42~beta-1_amd64.deb' + The following packages were automatically installed and are no longer required: + libabsl20200923 libicu67 libpoppler115 + Use 'sudo apt autoremove' to remove them. + Suggested packages: + unrar + The following packages will be upgraded: + evince evince-common gir1.2-evince-3.0 libevdocument3-4 libevview3-3 + 5 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. + Need to get 0 B/821 kB of archives. + After this operation, 803 kB disk space will be freed. + Get:1 /home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb evince-common all 42~beta-1 [132 kB] + Get:2 /home/jeremy/devel/pkg-gnome/build-area/evince_42~beta-1_amd64.deb evince amd64 42~beta-1 [306 kB] + Get:3 /home/jeremy/devel/pkg-gnome/build-area/libevdocument3-4_42~beta-1_amd64.deb libevdocument3-4 amd64 42~beta-1 [204 kB] + Get:4 /home/jeremy/devel/pkg-gnome/build-area/libevview3-3_42~beta-1_amd64.deb libevview3-3 amd64 42~beta-1 [148 kB] + Get:5 /home/jeremy/devel/pkg-gnome/build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb gir1.2-evince-3.0 amd64 42~beta-1 [31.1 kB] + (Reading database ... 207369 files and directories currently installed.) + Preparing to unpack .../evince-common_42~beta-1_all.deb ... + Unpacking evince-common (42~beta-1) over (41.3-3) ... + Preparing to unpack .../evince_42~beta-1_amd64.deb ... + Unpacking evince (42~beta-1) over (41.3-3) ... + Preparing to unpack .../libevdocument3-4_42~beta-1_amd64.deb ... + Unpacking libevdocument3-4:amd64 (42~beta-1) over (41.3-3) ... + Preparing to unpack .../libevview3-3_42~beta-1_amd64.deb ... + Unpacking libevview3-3:amd64 (42~beta-1) over (41.3-3) ... + Preparing to unpack .../gir1.2-evince-3.0_42~beta-1_amd64.deb ... + Unpacking gir1.2-evince-3.0:amd64 (42~beta-1) over (41.3-3) ... + Setting up evince-common (42~beta-1) ... + Setting up libevdocument3-4:amd64 (42~beta-1) ... + Setting up libevview3-3:amd64 (42~beta-1) ... + Setting up evince (42~beta-1) ... + Setting up gir1.2-evince-3.0:amd64 (42~beta-1) ... + Processing triggers for desktop-file-utils (0.26-1ubuntu2) ... + Processing triggers for hicolor-icon-theme (0.17-2) ... + Processing triggers for gnome-menus (3.36.0-1ubuntu2) ... + Processing triggers for libglib2.0-0:amd64 (2.71.2-1) ... + Processing triggers for libc-bin (2.35-0ubuntu1) ... + Processing triggers for man-db (2.10.1-1) ... + Processing triggers for mailcap (3.70+nmu1ubuntu1) ... + N: Download is performed unsandboxed as root as file '/home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) + $ evince + + (runs ok) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1963241 Title: [FFe] evince 42 Status in evince package in Ubuntu: New Bug description: Why Needed -- The Ubuntu Desktop had a goal of including as much of GNOME 42 as possible in Ubuntu 22.04 LTS. (One major exception was where apps had switched to GTK4). The evince document viewer (PDFs and more) did not have earlier releases in the 42 cycle and its Beta wasn't released until March 3, a week after Feature Freeze. The Ubuntu Desktop Team commits to packaging the final evince 42 stable
[Desktop-packages] [Bug 1962283] Re: Ubuntu dock has a border
Oh, well a mix of them actually. But probably yaru is enough for current shell as well. -- 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/1962283 Title: Ubuntu dock has a border Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Ubuntu dock has a grey (gray) border. Confirmed on a couple of jammy machines. Seems to be a recent regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 25 13:40:40 2022 InstallationDate: Installed on 2021-11-05 (111 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock 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/1962283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963241] Re: [FFe] evince 42
** Tags added: jammy upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1963241 Title: [FFe] evince 42 Status in evince package in Ubuntu: New Bug description: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
That would mean that Jammy, a LTS, will not be able to make use of LTE modems on 2021 shipped ThinkPad ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
This is debdiff for iio-sensor-proxy for jammy, which is also based on
the same version in impish.
** Patch added: "iio-sensor-proxy_3.3-0ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5565596/+files/iio-sensor-proxy_3.3-0ubuntu4.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in iio-sensor-proxy package in Ubuntu:
New
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962818] Re: Jammy Jellyfish LightDM is frozen after long period of inactivity
Changing package to xfce-screensaver after additional troubleshooting: -apt remove xfce4-screensaver resolves the issue Appears that the frozen screen is a result of xfce4-screensaver not operating as expected and is not a LightDM issue ** Package changed: lightdm (Ubuntu) => xfce4-screensaver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1962818 Title: Jammy Jellyfish LightDM is frozen after long period of inactivity Status in xfce4-screensaver package in Ubuntu: New Bug description: Jammy Jellyfish LightDM is frozen after long period of inactivity Latest updates installed, has been happening since first install 2 weeks ago. Upon using the laptop after over night or coming back from work, the screen is frozen. I can move the mouse around but click is unresponsive. To resolve the issue, I ctrl+alt+f2 in order to log into a shell then restart the LightDM services. I am using an XFCE environment. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 xfce4-screensaver: Installed: 4.16.0-1 Candidate: 4.16.0-1 Version table: *** 4.16.0-1 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.30.0-0ubuntu5 Candidate: 1.30.0-0ubuntu5 Version table: *** 1.30.0-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (45 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: lightdm 1.30.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-16 (46 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: xfce4-screensaver 4.16.0-1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-18 (13 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1962818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Description changed:
- [Steps to reproduce]
- 1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
- 2. After the installation, press enter to reboot system
- 3. prime-select query
+ RTD3 is a nvidia GPU feature to support runtime suspend.
- [Expected result]
- on-demand
+ On-demand would be a X offloading feature.
- [Actual result]
- performance
+ They are independent, according to discussion on
+ https://github.com/tseliot/ubuntu-drivers-common/issues/55.
- ---
+ Some parts need to be adjusted, e.g.
- It's because ubiquity launches `ubuntu-drivers install --packages-list
- ...` in live system but install each package to target storage.
+ ```
+ # If we are dealing with NVIDIA PRIME, and runtimepm
+ # is supported, enable it
+ if (os.path.isfile('/run/nvidia_runtimepm_supported') and
+ os.path.isfile('/usr/bin/prime-select')):
+ print('Trying to select the on-demand PRIME profile')
+ try:
+ subprocess.call(['prime-select', 'on-demand'])
+ except:
+ pass
- When installing nvidia-prime, the preinst set "on" to "/etc/prime-
- discrete" which will be referred by gpu-manager. The gpu-manager will
- set to performance mode.
+ # Create the override file for gpu-manager
+ with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
+ f.write('# File created by ubuntu-drivers\n')
+ ```
- After confirming with Alberto on Mattermost, since we don't have a
- nvidia driver which lower than 450 version since focal.
-
- I think we are ok to switch to on-demand mode.
---
[Impact]
* Ubuntu will set GPU mode to performance as default which may use more power
* User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
* According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Test Plan]
* Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU
driver. After the installation, reboot the system. Execute "prime-select query"
should get "on-demand"
- * Old GPU (which supported by nvidia-390 only) will keep in performance
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
+ * Old GPU (which supported by nvidia-390 only) will keep in performance
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
* On non-laptop machine. Can set GPU mode to on-demand
* On laptop with GPU in runtime PM support list. Set GPU mode to on-demand
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
[Where problems could occur]
* With GPU supported RTD3 not able enable runtime PM on non-laptop. But
based on the Nvidia README, this case shall not happened.
[Other Info]
Changelogs:
nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)
[ Alberto Milone ]
* prime-select:
- Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
- on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
- Use bootvga detection when last_gfx_boot
is not available.
- Don't check the current profile when setting
a profile (LP: #1946476).
- Catch BrokenPipeError.
- Use bootvga detection when last_gfx_boot is
not available.
-
- nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
-
- [ Jeremy Szu ]
- * Set on-demand mode as default nvidia mode (LP: #1942307)
-
- [ Alberto Milone ]
- * prime-select:
- - Detect chassis type and enable RTD3 only
- on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
- RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
- is not available.
- - Don't check the current profile when setting
- a profile (LP: #1946476).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
Fix Released
Status in nvidia-prime source package in Focal:
Incomplete
Status in nvidia-prime source package in Hirsute:
Won't Fix
Bug description:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
# If we are dealing with NVIDIA PRIME, and runtimepm
# is supported, enable it
if (os.path.isfile('/run/nvidia_runtimepm_supported') and
os.path.isfile('/usr/bin/prime-select')):
print('Trying to select the on-demand PRIME profile')
try:
[Desktop-packages] [Bug 1963264] Re: Screencast not recording
Do you have gstreamer1.0-pipewire installed? -- 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/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: New Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
** Changed in: xorg-server (Ubuntu) Importance: Medium => Low -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in xorg-server package in Ubuntu: Fix Committed Status in xwayland package in Ubuntu: Fix Released Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1823516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. + --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. - - nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) - - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Description changed: - [Steps to reproduce] - 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. - 2. After the installation, press enter to reboot system - 3. prime-select query + As per LP: #1942307 we now set on-demand as the default. This however, + causes "prime-select on-demand", called by ubuntu-drivers, not to even + try to detect RTD3 and to enable it, since "on-demand" is already set. - [Expected result] - on-demand + We cannot make informed choices about RTD3 in the postinstallation + script of nvidia-prime, therefore we should simply drop the check that + prime-select makes to abort if the new profile is determined to be the + same as the current profile. - [Actual result] - performance - - --- - - It's because ubiquity launches `ubuntu-drivers install --packages-list - ...` in live system but install each package to target storage. - - When installing nvidia-prime, the preinst set "on" to "/etc/prime- - discrete" which will be referred by gpu-manager. The gpu-manager will - set to performance mode. - - After confirming with Alberto on Mattermost, since we don't have a - nvidia driver which lower than 450 version since focal. - - I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. - - nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) - - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in
[Desktop-packages] [Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- 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/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver Status in Mutter: Unknown Status in mutter package in Ubuntu: Incomplete Bug description: When an external display is connected to my laptop, running Ubuntu 22.04, the display is detected and I am sent to the login screen. After logging in again, the display is not running, although the primary laptop display works fine. The external monitor is looking for connection in that moment, which it never founds. The bug is tested on two Samsung monitors: S24R350FHUXEN and S22F350FHU. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-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 495.46 Wed Oct 27 16:31:33 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1) ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 13:25:04 2022 DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/495.46, 5.15.0-17-generic, x86_64: installed nvidia/495.46, 5.15.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:086f] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f] InstallationDate: Installed on 2021-09-09 (146 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
