[Desktop-packages] [Bug 1974181] Re: package libreoffice-common 1:7.3.3-0ubuntu0.22.04.1 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned er
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1974181 Title: package libreoffice-common 1:7.3.3-0ubuntu0.22.04.1 failed to install/upgrade: installed libreoffice-common package post- installation script subprocess returned error exit status 128 Status in libreoffice package in Ubuntu: Confirmed Bug description: check ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.3-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 16 11:34:57 2022 DuplicateSignature: package:libreoffice-common:1:7.3.3-0ubuntu0.22.04.1 Setting up libreoffice-common (1:7.3.3-0ubuntu0.22.04.1) ... Replacing config file /etc/libreoffice/registry/main.xcd with new version dpkg: error processing package libreoffice-common (--configure): installed libreoffice-common package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-common package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2022-05-04 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.3-0ubuntu0.22.04.1 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1974181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987196] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1
Relevant debug logging from DpkgTerminalLog.txt: ==> Installing the firefox snap error: cannot perform the following tasks: - 下载 snap "firefox" (1670)，来自频道 "stable" (unexpected EOF) This looks like a transient network error. Would you mind retrying? sudo apt reinstall firefox ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1987196 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 Status in firefox package in Ubuntu: Incomplete Bug description: I wait for a long time when updating the firrefox and then it crashed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pathogen 1440 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sun Aug 21 15:54:59 2022 ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 ForcedLayersAccel: False InstallationDate: Installed on 2021-11-10 (283 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.126.2 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.126.0/24 dev ens33 proto kernel scope link src 192.168.126.128 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to jammy on 2022-08-21 (0 days ago) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987224] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Relevant debug output from DpkgTerminalLog.txt: ==> Installing the firefox snap error: cannot perform the following tasks: - Download snap "firefox" (1670) from channel "stable" (Get https://canonical-lgw01.cdn.snapcraftcontent.com/download-origin/canonical-lgw01/3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk_1670.snap?interactive=1&token=1661126400_8c49199b3b580b188a988abffbbf25cd477d195f: read tcp 192.168.2.199:39844->185.125.190.27:443: read: connection reset by peer) This looks like a transient network failure. Would you mind retrying? sudo apt reinstall firefox ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1987224 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: Incomplete Bug description: Tryning to upgrade to the new ubuntu version fails ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1045.51-oem 5.14.21 Uname: Linux 5.14.0-1045-oem x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuri 2469 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sun Aug 21 22:45:24 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-01-17 (215 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.2.254 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.2.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.2.199 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-21 (0 days ago) dmi.bios.date: 06/09/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0C6CP1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd06/09/2022:br1.11:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn0C6CP1:rvrA01:cvnDellInc.:ct10:cvr:sku0A61: dmi.product.family: XPS dmi.product.name: XPS 15 9510 dmi.product.sku: 0A61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890593] Re: [nvidia] Boot freeze - can't get to login screen without unplugging HDMI first
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1890593 Title: [nvidia] Boot freeze - can't get to login screen without unplugging HDMI first Status in gdm3 package in Ubuntu: Expired Status in plymouth package in Ubuntu: Expired Bug description: Just installed ubuntu 20.04 and I am stuck on ubuntu with a spining logo. If I go to other tty and unplug the HDMI screens I can get to the login screen, Otherwise I cant. I did checked the md5sum of the iso before installing and its was correct. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .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 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 14:29:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T570 [17aa:2248] Subsystem: Lenovo GM108GLM [Quadro M520 Mobile] [17aa:2248] InstallationDate: Installed on 2020-08-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HCS0660M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=be1cbba6-c044-4d36-a6f4-fe872353a538 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET49W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HCS0660M dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET49W(1.39):bd05/08/2019:svnLENOVO:pn20HCS0660M:pvrThinkPadP51s:rvnLENOVO:rn20HCS0660M:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad THINKPAD P51S dmi.product.name: 20HCS0660M dmi.product.sku: LENOVO_MT_20HC_BU_Think_FM_ThinkPad THINKPAD P51S dmi.product.version: ThinkPad P51s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1890593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890593] Re: [nvidia] Boot freeze - can't get to login screen without unplugging HDMI first
[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: plymouth (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1890593 Title: [nvidia] Boot freeze - can't get to login screen without unplugging HDMI first Status in gdm3 package in Ubuntu: Expired Status in plymouth package in Ubuntu: Expired Bug description: Just installed ubuntu 20.04 and I am stuck on ubuntu with a spining logo. If I go to other tty and unplug the HDMI screens I can get to the login screen, Otherwise I cant. I did checked the md5sum of the iso before installing and its was correct. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .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 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 14:29:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T570 [17aa:2248] Subsystem: Lenovo GM108GLM [Quadro M520 Mobile] [17aa:2248] InstallationDate: Installed on 2020-08-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HCS0660M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=be1cbba6-c044-4d36-a6f4-fe872353a538 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET49W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HCS0660M dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET49W(1.39):bd05/08/2019:svnLENOVO:pn20HCS0660M:pvrThinkPadP51s:rvnLENOVO:rn20HCS0660M:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad THINKPAD P51S dmi.product.name: 20HCS0660M dmi.product.sku: LENOVO_MT_20HC_BU_Think_FM_ThinkPad THINKPAD P51S dmi.product.version: ThinkPad P51s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1890593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
See also: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1968#note_1275389 -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
Another duplicate (bug 1987174) shows the crash happening on a hybrid system with i915+nouveau. So it doesn't sound as related to AMDGPU as to hybrid systems in general (open source drivers). -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983175] Re: In Wayland, can't wake up monitor after it has gone black
No problem. The bug will automatically close after 2 months if no further comments are added. -- 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/1983175 Title: In Wayland, can't wake up monitor after it has gone black Status in mutter package in Ubuntu: Incomplete Bug description: Hi, sorry I don't know if it's about GDM or else. Ubuntu 22.04.1 LTS jammy Linux 5.15.0-41-generic x86_64 x86_64 ubuntu / wayland installed DE's are : ubuntu.desktop ubuntu-xorg.desktop My system is set to turn screen black after some minutes. And after some other minutes later, it locks the screen → no sleep nor hibernate involved ( even if sleep and hibernate are ok on that machine. ) On Xorg, after screen's gone black, any mouse or keyboard solicitation fires up again the screen, as expected. On Wayland, after screen's gone black, any mouse or keyboard solicitation just does nothing, screen stays black. BUT keyboard is not turned off : only thing that works for « waking up » the screen is key-combo [ ctrl ] + [ alt ] + [ F1 ] If of any interest : django@ASGARD:~$ sudo lshw -c video [sudo] Mot de passe de django : *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabricant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 nom logique: /dev/fb0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom fb configuration : depth=32 driver=i915 latency=0 resolution=1920,1080 ressources : irq:33 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d django@ASGARD:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973014] Re: gnome-shell crashes with SIGSEGV in libgbm.so.1.0.0 on resume or session change
Yes this sounds like bug 1969422. Next time please open a new bug of your own instead of commenting on closed bugs reported by someone else. -- 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/1973014 Title: gnome-shell crashes with SIGSEGV in libgbm.so.1.0.0 on resume or session change Status in gnome-shell package in Ubuntu: Expired Bug description: Trying to change session with ctrl-alt f1 or suspend-resume the computer systematically leads to a crash on my system : -First i can see the screen, but mouse an keyboard are not responsive. -Then many visual artifacts appear on my secondary monitor. -Then i get a new login prompt. After that in dmesg i can see errors such as : [ 6574.079637] gnome-shell[5525]: segfault at 55713299a720 ip 7f7c0af012e7 sp 7ffc8932bdb8 error 4 in libgbm.so.1.0.0[7f7c0af0+8000] [ 6574.079660] Code: 18 c3 90 f3 0f 1e fa 48 8b 07 ff a0 c0 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 a8 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 a0 b0 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 b8 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30 Uname: Linux 5.15.0-27-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 11 15:05:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-23 (1114 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987229] Re: 22.04 Cannot Restore Files from Backup
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. If you would prefer live chat support, you can find an IRC support channel for your flavor of Ubuntu here: https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: duplicity (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/duplicity/+question/702866 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1987229 Title: 22.04 Cannot Restore Files from Backup Status in duplicity package in Ubuntu: Invalid Bug description: My system upgraded to 22.04. I was having issues unable to boot. I created a backup of all my files in the Recovery Mode. Onto an external 500 GB Hard drive. I reformatted the hard drive and re-installed 22.04. Now going to Applications > Utilities > Backup. I select to Restore from a backup. And I receive this error: Failed to read duplicity-full-signatures. 20220818T155126Z.sigtar.gz: CRC check failed 0xc5eba518!=0xae357fd0 When I click Retry I get the same error. I searched for another backup restore application and found what looks like the same version of Backups used to create the back ups. When I click Restore From a Previous Backup. I select the 500 GB hard drive and type the Folder name containing the backups. I get the same error. I have searched community but only find things from version 17 or earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1987229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987229] [NEW] 22.04 Cannot Restore Files from Backup
Public bug reported: My system upgraded to 22.04. I was having issues unable to boot. I created a backup of all my files in the Recovery Mode. Onto an external 500 GB Hard drive. I reformatted the hard drive and re-installed 22.04. Now going to Applications > Utilities > Backup. I select to Restore from a backup. And I receive this error: Failed to read duplicity-full-signatures. 20220818T155126Z.sigtar.gz: CRC check failed 0xc5eba518!=0xae357fd0 When I click Retry I get the same error. I searched for another backup restore application and found what looks like the same version of Backups used to create the back ups. When I click Restore From a Previous Backup. I select the 500 GB hard drive and type the Folder name containing the backups. I get the same error. I have searched community but only find things from version 17 or earlier. ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1987229 Title: 22.04 Cannot Restore Files from Backup Status in duplicity package in Ubuntu: New Bug description: My system upgraded to 22.04. I was having issues unable to boot. I created a backup of all my files in the Recovery Mode. Onto an external 500 GB Hard drive. I reformatted the hard drive and re-installed 22.04. Now going to Applications > Utilities > Backup. I select to Restore from a backup. And I receive this error: Failed to read duplicity-full-signatures. 20220818T155126Z.sigtar.gz: CRC check failed 0xc5eba518!=0xae357fd0 When I click Retry I get the same error. I searched for another backup restore application and found what looks like the same version of Backups used to create the back ups. When I click Restore From a Previous Backup. I select the 500 GB hard drive and type the Folder name containing the backups. I get the same error. I have searched community but only find things from version 17 or earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1987229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987224] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1987224 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: Tryning to upgrade to the new ubuntu version fails ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1045.51-oem 5.14.21 Uname: Linux 5.14.0-1045-oem x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuri 2469 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sun Aug 21 22:45:24 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-01-17 (215 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.2.254 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.2.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.2.199 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-21 (0 days ago) dmi.bios.date: 06/09/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0C6CP1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd06/09/2022:br1.11:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn0C6CP1:rvrA01:cvnDellInc.:ct10:cvr:sku0A61: dmi.product.family: XPS dmi.product.name: XPS 15 9510 dmi.product.sku: 0A61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987224] [NEW] package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: Tryning to upgrade to the new ubuntu version fails ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1045.51-oem 5.14.21 Uname: Linux 5.14.0-1045-oem x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuri 2469 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sun Aug 21 22:45:24 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-01-17 (215 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.2.254 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.2.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.2.199 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-21 (0 days ago) dmi.bios.date: 06/09/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0C6CP1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd06/09/2022:br1.11:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn0C6CP1:rvrA01:cvnDellInc.:ct10:cvr:sku0A61: dmi.product.family: XPS dmi.product.name: XPS 15 9510 dmi.product.sku: 0A61 dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1987224 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: Tryning to upgrade to the new ubuntu version fails ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1045.51-oem 5.14.21 Uname: Linux 5.14.0-1045-oem x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuri 2469 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sun Aug 21 22:45:24 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-01-17 (215 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.2.254 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.2.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.2.199 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-21 (0 days ago) dmi.bios.date: 06/09/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0C6CP1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd06/09/2022:br1.11:svnDellInc.:pnXPS159510:pvr:rvnDellInc.:rn0C6CP1:rvrA01:cvnDellInc.:ct10:cvr:sku0A61: dmi.product.family: XPS dmi.product.name: XPS 15 9510 dmi.product.sku: 0A61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firef
[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
Indeed - I don't think it is useful to have such information displayed prominently when there is nothing that user's can do to affect this (in general) and so this will only cause alarm. Like Marc said, it is then not useful to display this without offering actionable tasks that a user an perform to increase their security, since then as jbicha suggested, some users will likely try and manually workaround these findings to 'increase' their security and potentially break their systems. Whilst it is commendable that GNOME is trying to perhaps raise security awareness for users, doing this in a way where users don't really have any control over the results is likely to cause more harm than good. So I agree, this should not be part of the standard gnome-control-center at this stage for Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently Status in gnome-control-center package in Ubuntu: Triaged Bug description: GNOME 43 added a new Device Security feature in the Settings app. You can access it in gnome-control-center 1:43~beta-1ubuntu1 1. Open the Settings app 2. Click Privacy then Device Security The Security Events aren't clickable. A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". There isn't anything an Ubuntu user can do to get to a higher security level from the Device Security screen. If a user attempts to get their system to a higher security level, I think they could break their system since this isn't something we currently support. Therefore, I think we ought to hide/disable the screen for Ubuntu 22.10. We can work towards better integrating this screen for Ubuntu in future releases. I'm attaching several screenshots although it's worth trying out the feature for yourself too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
Started happening to me as soon as I updated to Ubuntu 22.04.1. My locale is it_IT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987209] Re: gnome-shell (Wayland) crashes when screen locker activates (jj)
Test suggested by oria on IRC: try "nomodeset" in kernel parameter and try to reproduce the problem. After the reboot: ``` $ uname -a Linux flhpz4 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=/dev/mapper/vg0-system ro quiet splash vt.handoff=7 nomodeset ``` Remarks: 1. During the login, the choice "Ubuntu on Xorg" appears no longer (I don't know why). I can choose only "Openbox" or "Ubuntu". And I have chosen "Ubuntu" of course. 2. I have only one monitor which works (the HP monitor). The other monitor (Asus) is just ignored. And in this case, the automatic lock screen works correctly. I can find my running appli after a re-login. -- 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/1987209 Title: gnome-shell (Wayland) crashes when screen locker activates (jj) Status in gnome-shell package in Ubuntu: New Bug description: Hi, On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem with the automatic lock screen which doesn't lock my session but closes it (and all opened applications in my session are closed too of course). In fact, I think the session is not really closed but there is some crash of gnome shell (see below). Maybe it's important, I have *2* monitors (more convenient for my tired eyes): * HP 24er (24") * ASUS MX279 (27") Theses 2 monitors are connected via a HDMI port, each on a dedicated card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model cards "Radeon Pro WX 3100"). Here is my setting in "Privacy" > "Screen", to test quickly the automatic lock screen: ``` Blank Screen Delay: 1 minute Automatic Screen Lock: Automatic Screen Lock Delay: 30 seconds Lock Screen on Suspend: Show Notifications on Lock Screen: ``` Note: I have tested with a fresh and new Unix account, just created for the test (by `sudo adduser foo`) and the problem is present too. Below, you can see the output of the `journalctl -eb` where: 1. about ~13:02:50, screens begins to be blank, 2. about ~13:03:20, the automatic lock screen should start. As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault": ``` Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea from uid 1000 finished with success after 229ms Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd from uid 1000 finished with success after 235ms Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by gnome-shell. Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 ip 55a109404860 sp 7fff85039338 error 15 Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property match 'XRANDR_name'='DP-3' does not exist Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 processes of 1 users. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of process 37752 owned by '1000' RT at priority 5. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 processes of 1 users. Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 unknown[3805
[Desktop-packages] [Bug 1987209] Re: gnome-shell (Wayland) crashes when screen locker activates (jj)
** Tags added: amdgpu multimonitor -- 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/1987209 Title: gnome-shell (Wayland) crashes when screen locker activates (jj) Status in gnome-shell package in Ubuntu: New Bug description: Hi, On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem with the automatic lock screen which doesn't lock my session but closes it (and all opened applications in my session are closed too of course). In fact, I think the session is not really closed but there is some crash of gnome shell (see below). Maybe it's important, I have *2* monitors (more convenient for my tired eyes): * HP 24er (24") * ASUS MX279 (27") Theses 2 monitors are connected via a HDMI port, each on a dedicated card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model cards "Radeon Pro WX 3100"). Here is my setting in "Privacy" > "Screen", to test quickly the automatic lock screen: ``` Blank Screen Delay: 1 minute Automatic Screen Lock: Automatic Screen Lock Delay: 30 seconds Lock Screen on Suspend: Show Notifications on Lock Screen: ``` Note: I have tested with a fresh and new Unix account, just created for the test (by `sudo adduser foo`) and the problem is present too. Below, you can see the output of the `journalctl -eb` where: 1. about ~13:02:50, screens begins to be blank, 2. about ~13:03:20, the automatic lock screen should start. As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault": ``` Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea from uid 1000 finished with success after 229ms Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd from uid 1000 finished with success after 235ms Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by gnome-shell. Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 ip 55a109404860 sp 7fff85039338 error 15 Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property match 'XRANDR_name'='DP-3' does not exist Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 processes of 1 users. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of process 37752 owned by '1000' RT at priority 5. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 processes of 1 users. Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 unknown[38050]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 terminator[46053]: Error reading events from display: Connection reset by peer Aug 21 13:03:21 flhpz4 gsd-wacom[38078]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 firefox[46499]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 systemd[37743]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE Aug 21 13:03:21 flhpz4 systemd[37743]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE Aug 21 13:03:21 flhpz4 systemd[37743]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'. Aug 21 13:03:21 f
[Desktop-packages] [Bug 1987209] Re: gnome-shell (Wayland) crashes when screen locker activates (jj)
Hi, Tom Reynolds wrote: > gnome-shell (Wayland) reproducibly segfaults on this amd64 system > whenever the no-user-interaction timeout is reached and the screen > locker kicks in. Not reproducible on Xorg. This is perfectly summarized. FYI, the problem doesn't appear if I lock my session manually with "Windows-L". -- 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/1987209 Title: gnome-shell (Wayland) crashes when screen locker activates (jj) Status in gnome-shell package in Ubuntu: New Bug description: Hi, On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem with the automatic lock screen which doesn't lock my session but closes it (and all opened applications in my session are closed too of course). In fact, I think the session is not really closed but there is some crash of gnome shell (see below). Maybe it's important, I have *2* monitors (more convenient for my tired eyes): * HP 24er (24") * ASUS MX279 (27") Theses 2 monitors are connected via a HDMI port, each on a dedicated card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model cards "Radeon Pro WX 3100"). Here is my setting in "Privacy" > "Screen", to test quickly the automatic lock screen: ``` Blank Screen Delay: 1 minute Automatic Screen Lock: Automatic Screen Lock Delay: 30 seconds Lock Screen on Suspend: Show Notifications on Lock Screen: ``` Note: I have tested with a fresh and new Unix account, just created for the test (by `sudo adduser foo`) and the problem is present too. Below, you can see the output of the `journalctl -eb` where: 1. about ~13:02:50, screens begins to be blank, 2. about ~13:03:20, the automatic lock screen should start. As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault": ``` Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea from uid 1000 finished with success after 229ms Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd from uid 1000 finished with success after 235ms Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by gnome-shell. Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 ip 55a109404860 sp 7fff85039338 error 15 Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property match 'XRANDR_name'='DP-3' does not exist Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 processes of 1 users. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of process 37752 owned by '1000' RT at priority 5. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 processes of 1 users. Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 unknown[38050]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 terminator[46053]: Error reading events from display: Connection reset by peer Aug 21 13:03:21 flhpz4 gsd-wacom[38078]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 firefox[46499]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 systemd[37743]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited,
[Desktop-packages] [Bug 1987209] Re: gnome-shell (Wayland) crashes when screen locker activates (jj)
Summary from my IRC support session with francois-lafont: gnome-shell (Wayland) reproducibly segfaults on this amd64 system whenever the no-user-interaction timeout is reached and the screen locker kicks in. Not reproducible on Xorg. This is an amd64 Intel CPU, 2x AMD GPU system, recently upgraded to JJ. Related Oopses from this system (SegvAnalysis failed for all, no debug): https://errors.ubuntu.com/oops/a812c258-216f-11ed-9782-fa163e993415 https://errors.ubuntu.com/oops/a6ea9d2a-216f-11ed-b145-fa163ef35206 https://errors.ubuntu.com/oops/c94458b8-1def-11ed-9760-fa163e993415 https://errors.ubuntu.com/oops/5d6f040c-1dee-11ed-975f-fa163e993415 -- 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/1987209 Title: gnome-shell (Wayland) crashes when screen locker activates (jj) Status in gnome-shell package in Ubuntu: New Bug description: Hi, On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem with the automatic lock screen which doesn't lock my session but closes it (and all opened applications in my session are closed too of course). In fact, I think the session is not really closed but there is some crash of gnome shell (see below). Maybe it's important, I have *2* monitors (more convenient for my tired eyes): * HP 24er (24") * ASUS MX279 (27") Theses 2 monitors are connected via a HDMI port, each on a dedicated card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model cards "Radeon Pro WX 3100"). Here is my setting in "Privacy" > "Screen", to test quickly the automatic lock screen: ``` Blank Screen Delay: 1 minute Automatic Screen Lock: Automatic Screen Lock Delay: 30 seconds Lock Screen on Suspend: Show Notifications on Lock Screen: ``` Note: I have tested with a fresh and new Unix account, just created for the test (by `sudo adduser foo`) and the problem is present too. Below, you can see the output of the `journalctl -eb` where: 1. about ~13:02:50, screens begins to be blank, 2. about ~13:03:20, the automatic lock screen should start. As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault": ``` Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea from uid 1000 finished with success after 229ms Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd from uid 1000 finished with success after 235ms Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by gnome-shell. Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 ip 55a109404860 sp 7fff85039338 error 15 Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property match 'XRANDR_name'='DP-3' does not exist Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 processes of 1 users. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of process 37752 owned by '1000' RT at priority 5. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 processes of 1 users. Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 unknown[38050]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 terminator[46053]: Error reading
[Desktop-packages] [Bug 1987209] Re: gnome-shell crashes with Wayland when screen locker activates (jj)
** Summary changed: - Automatic lock screen doesn't lock my session but closes it because of a gnome-shell crash + gnome-shell crashes with Wayland when screen locker activates (jj) ** Summary changed: - gnome-shell crashes with Wayland when screen locker activates (jj) + gnome-shell (Wayland) crashes when screen locker activates (jj) -- 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/1987209 Title: gnome-shell (Wayland) crashes when screen locker activates (jj) Status in gnome-shell package in Ubuntu: New Bug description: Hi, On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem with the automatic lock screen which doesn't lock my session but closes it (and all opened applications in my session are closed too of course). In fact, I think the session is not really closed but there is some crash of gnome shell (see below). Maybe it's important, I have *2* monitors (more convenient for my tired eyes): * HP 24er (24") * ASUS MX279 (27") Theses 2 monitors are connected via a HDMI port, each on a dedicated card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model cards "Radeon Pro WX 3100"). Here is my setting in "Privacy" > "Screen", to test quickly the automatic lock screen: ``` Blank Screen Delay: 1 minute Automatic Screen Lock: Automatic Screen Lock Delay: 30 seconds Lock Screen on Suspend: Show Notifications on Lock Screen: ``` Note: I have tested with a fresh and new Unix account, just created for the test (by `sudo adduser foo`) and the problem is present too. Below, you can see the output of the `journalctl -eb` where: 1. about ~13:02:50, screens begins to be blank, 2. about ~13:03:20, the automatic lock screen should start. As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault": ``` Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea from uid 1000 finished with success after 229ms Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd from uid 1000 finished with success after 235ms Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by gnome-shell. Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 ip 55a109404860 sp 7fff85039338 error 15 Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property match 'XRANDR_name'='DP-3' does not exist Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 processes of 1 users. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of process 37752 owned by '1000' RT at priority 5. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 processes of 1 users. Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 unknown[38050]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 terminator[46053]: Error reading events from display: Connection reset by peer Aug 21 13:03:21 flhpz4 gsd-wacom[38078]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 firefox[46499]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 systemd[37743]: org.gnome.SettingsDaemon.Keyboard.service:
[Desktop-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
Solved by executing amixer -q -D pulse sset Master toggle https://askubuntu.com/a/1341471 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987209] Re: Automatic lock screen doesn't lock my session but closes it because of a gnome-shell crash
Same test here but where I have selected "Ubuntu on Xorg" before login, instead of "Ubuntu". The point is, in that case, my session is locked and I don't loose my session: ``` Aug 21 18:31:20 flhpz4 systemd[38118]: Reached target Exit the Session. Aug 21 18:31:20 flhpz4 systemd[1]: user@122.service: Deactivated successfully. Aug 21 18:31:20 flhpz4 systemd[1]: Stopped User Manager for UID 122. Aug 21 18:31:20 flhpz4 systemd[1]: user@122.service: Consumed 1.932s CPU time. Aug 21 18:31:20 flhpz4 systemd[1]: Stopping User Runtime Directory /run/user/122... Aug 21 18:31:20 flhpz4 systemd[1]: run-user-122.mount: Deactivated successfully. Aug 21 18:31:20 flhpz4 systemd[1]: user-runtime-dir@122.service: Deactivated successfully. Aug 21 18:31:20 flhpz4 systemd[1]: Stopped User Runtime Directory /run/user/122. Aug 21 18:31:20 flhpz4 systemd[1]: Removed slice User Slice of UID 122. Aug 21 18:31:20 flhpz4 systemd[1]: user-122.slice: Consumed 6.123s CPU time. Aug 21 18:31:31 flhpz4 sudo[39952]: pam_unix(sudo-i:session): session closed for user root Aug 21 18:31:35 flhpz4 systemd[1]: systemd-localed.service: Deactivated successfully. Aug 21 18:31:35 flhpz4 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Aug 21 18:31:35 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 18:31:38 flhpz4 sudo[39993]: flaf : TTY=pts/0 ; PWD=/home/flaf ; USER=root ; COMMAND=/usr/bin/tail -f /tmp/y.log Aug 21 18:31:38 flhpz4 sudo[39993]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Aug 21 18:31:49 flhpz4 geoclue[38294]: Service not used for 60 seconds. Shutting down.. Aug 21 18:31:49 flhpz4 systemd[1]: Started Run anacron jobs. Aug 21 18:31:49 flhpz4 systemd[1]: geoclue.service: Deactivated successfully. Aug 21 18:31:49 flhpz4 anacron[39996]: Anacron 2.3 started on 2022-08-21 Aug 21 18:31:49 flhpz4 anacron[39996]: Normal exit (0 jobs run) Aug 21 18:31:49 flhpz4 systemd[1]: anacron.service: Deactivated successfully. Aug 21 18:32:05 flhpz4 dbus-daemon[38525]: [session uid=1000 pid=38525] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.40' (uid=1000 pid=38825 comm="/usr/bin/gnome-shell " label="unconfined") Aug 21 18:32:05 flhpz4 systemd[38508]: Starting Virtual filesystem metadata service... Aug 21 18:32:05 flhpz4 dbus-daemon[38525]: [session uid=1000 pid=38525] Successfully activated service 'org.gtk.vfs.Metadata' Aug 21 18:32:05 flhpz4 systemd[38508]: Started Virtual filesystem metadata service. Aug 21 18:32:05 flhpz4 systemd[38508]: Started Application launched by gnome-session-binary. Aug 21 18:32:05 flhpz4 systemd[38508]: Started Application launched by gnome-session-binary. Aug 21 18:32:06 flhpz4 ubuntu-appindicat...@ubuntu.com[38825]: unable to update icon for software-update-available Aug 21 18:32:06 flhpz4 ubuntu-appindicat...@ubuntu.com[38825]: unable to update icon for livepatch Aug 21 18:33:05 flhpz4 systemd[38508]: Started Application launched by gnome-session-binary. Aug 21 18:33:10 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Allocate new frame buffer 1920x1080 Aug 21 18:33:10 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): => pitch 7680 bytes Aug 21 18:33:10 flhpz4 rtkit-daemon[1824]: Supervising 6 threads of 2 processes of 1 users. Aug 21 18:33:10 flhpz4 rtkit-daemon[1824]: Successfully made thread 40066 of process 38517 owned by '1000' RT at priority 5. Aug 21 18:33:10 flhpz4 rtkit-daemon[1824]: Supervising 7 threads of 2 processes of 1 users. Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): EDID vendor "HWP", prod id 13088 Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Using hsync ranges from config file Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Using vrefresh ranges from config file Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Printing DDC gathered Modelines: Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Aug 21 18:33:11 flhpz4 /usr/libexec/gdm-x-session[38563]: (II) AMDGPU(0): Modeline "720x576"x0.0 27.00 720 732 7
[Desktop-packages] [Bug 1987215] Re: nautilus crashed with SIGABRT
*** This bug is a duplicate of bug 1986985 *** https://bugs.launchpad.net/bugs/1986985 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 #1986985, 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/1987215/+attachment/5610492/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1987215/+attachment/5610494/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1987215/+attachment/5610497/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1987215/+attachment/5610498/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1987215/+attachment/5610499/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1987215/+attachment/5610500/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1987215/+attachment/5610501/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1986985 ** 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/1987215 Title: nautilus crashed with SIGABRT Status in nautilus package in Ubuntu: New Bug description: nautilus crashed with SIGABRT. This error report generates while logging. It also occurs when logging into unity session from mate session. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.22.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Thu Aug 18 22:55:15 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2022-08-13 (8 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220713) ProcCmdline: nautilus ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libepoxy.so.0 ?? () from /lib/x86_64-linux-gnu/libepoxy.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () from /lib/x86_64-linux-gnu/libGLdispatch.so.0 ?? () Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to kinetic on 2022-08-13 (8 days ago) UserGroups: N/A separator: usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987209] Re: Automatic lock screen doesn't lock my session but closes it because of a gnome-shell crash
FYI, here is the output of `journalctl -f` (run as root in tyy4) during the automatic lock screen of my session (of the user flaf) and the gnome-shell crash: ``` Aug 21 18:11:17 flhpz4 sudo[25344]: pam_unix(sudo:session): session closed for user root Aug 21 18:11:17 flhpz4 sudo[25348]: flaf : TTY=tty4 ; PWD=/home/flaf ; USER=root ; COMMAND=/sbin/mdadm --detail --test /dev/md126 Aug 21 18:11:17 flhpz4 sudo[25348]: pam_unix(sudo:session): session opened for user root(uid=0) by flaf(uid=1000) Aug 21 18:11:17 flhpz4 sudo[25348]: pam_unix(sudo:session): session closed for user root Aug 21 18:11:17 flhpz4 gnome-software[12398]: Failed to reload changed app filter: App filtering is globally disabled Aug 21 18:11:17 flhpz4 gnome-software[12398]: Failed to reload changed app filter: App filtering is globally disabled Aug 21 18:11:21 flhpz4 sudo[25400]: flaf : TTY=tty4 ; PWD=/root ; USER=root ; COMMAND=/bin/bash Aug 21 18:11:21 flhpz4 sudo[25400]: pam_unix(sudo-i:session): session opened for user root(uid=0) by flaf(uid=1000) Aug 21 18:11:37 flhpz4 geoclue[25036]: Service not used for 60 seconds. Shutting down.. Aug 21 18:11:37 flhpz4 systemd[1]: geoclue.service: Deactivated successfully. # # Begin of the automatic lock screen. # Aug 21 18:11:47 flhpz4 kernel: rfkill: input handler disabled Aug 21 18:11:47 flhpz4 kernel: gnome-shell[24900]: segfault at 56230aceaac6 ip 7f71b0ab42e7 sp 7fff330d9418 error 4 in libgbm.so.1.0.0[7f71b0ab3000+8000] Aug 21 18:11:47 flhpz4 kernel: Code: 18 c3 90 f3 0f 1e fa 48 8b 07 ff a0 c0 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 a8 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 a0 b0 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 b8 00 00 00 Aug 21 18:11:47 flhpz4 gsd-power[25102]: Error reading events from display: Broken pipe Aug 21 18:11:47 flhpz4 org.gnome.Shell.desktop[25002]: (EE) failed to read Wayland events: Broken pipe Aug 21 18:11:47 flhpz4 gsd-media-keys[25084]: Error reading events from display: Broken pipe Aug 21 18:11:47 flhpz4 gsd-wacom[25056]: Error reading events from display: Broken pipe Aug 21 18:11:47 flhpz4 gsd-keyboard[25058]: Error reading events from display: Broken pipe Aug 21 18:11:47 flhpz4 gnome-session[24880]: gnome-session-binary[24880]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 Aug 21 18:11:47 flhpz4 gnome-session-binary[24880]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 Aug 21 18:11:47 flhpz4 gnome-session[24880]: gnome-session-binary[24880]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1 Aug 21 18:11:47 flhpz4 gnome-session[24880]: gnome-session-binary[24880]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1 Aug 21 18:11:47 flhpz4 gnome-session[24880]: gnome-session-binary[24880]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1 Aug 21 18:11:47 flhpz4 gnome-session-binary[24880]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1 Aug 21 18:11:47 flhpz4 gnome-session-binary[24880]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1 Aug 21 18:11:47 flhpz4 gnome-session-binary[24880]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1 Aug 21 18:11:47 flhpz4 gnome-session[24880]: gnome-session-binary[24880]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Aug 21 18:11:47 flhpz4 gnome-session-binary[24880]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Aug 21 18:11:47 flhpz4 gnome-session-binary[24880]: Unrecoverable failure in required component org.gnome.Shell.desktop Aug 21 18:11:47 flhpz4 gsd-color[25057]: Error reading events from display: Broken pipe Aug 21 18:11:47 flhpz4 /usr/libexec/gdm-wayland-session[24879]: dbus-daemon[24879]: [session uid=122 pid=24879] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=122 pid=24880 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined") Aug 21 18:11:47 flhpz4 org.gnome.SettingsDaemon.Keyboard.desktop[25429]: Cannot open display: Aug 21 18:11:47 flhpz4 /usr/libexec/gdm-wayland-session[24879]: dbus-daemon[24879]: [session uid=122 pid=24879] Successfully activated service 'ca.desrt.dconf' Aug 21 18:11:47 flhpz4 kernel: rfkill: input handler enabled Aug 21 18:11:47 flhpz4 org.gnome.SettingsDaemon.Wacom.desktop[25425]: Cannot open display: Aug 21 18:11:47 flhpz4 gsd-color[12313]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Hewlett_Packard_HP_24er_3CM8010FLW_gdm_122 Aug 21 18:11:47 flhpz4 gsd-color[12313]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Ancor_Communications_Inc_MX279_E8LMRS026763_gdm_122 Aug 21 18:11:47 flhpz4 org.gnome.SettingsDaemon.MediaKeys.desktop[25428]: Cannot open display: Aug 21 18:11:47 flhpz4 org.gnome.SettingsDaemon.Power.
[Desktop-packages] [Bug 1987209] [NEW] Automatic lock screen doesn't lock my session but closes it because of a gnome-shell crash
Public bug reported: Hi, On my Ubuntu 22.04 (migrated from 20.04 few days ago), I have a problem with the automatic lock screen which doesn't lock my session but closes it (and all opened applications in my session are closed too of course). In fact, I think the session is not really closed but there is some crash of gnome shell (see below). Maybe it's important, I have *2* monitors (more convenient for my tired eyes): * HP 24er (24") * ASUS MX279 (27") Theses 2 monitors are connected via a HDMI port, each on a dedicated card "Radeon Pro WX 3100" (1 card per monitor, so I have 2 same model cards "Radeon Pro WX 3100"). Here is my setting in "Privacy" > "Screen", to test quickly the automatic lock screen: ``` Blank Screen Delay: 1 minute Automatic Screen Lock: Automatic Screen Lock Delay: 30 seconds Lock Screen on Suspend: Show Notifications on Lock Screen: ``` Note: I have tested with a fresh and new Unix account, just created for the test (by `sudo adduser foo`) and the problem is present too. Below, you can see the output of the `journalctl -eb` where: 1. about ~13:02:50, screens begins to be blank, 2. about ~13:03:20, the automatic lock screen should start. As you can see below, "Aug 21 13:03:19 => gnome-shell: segfault": ``` Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25167_acdeacea from uid 1000 finished with success after 229ms Aug 21 13:00:39 flhpz4 PackageKit[2197]: resolve transaction /25168_badabacd from uid 1000 finished with success after 235ms Aug 21 13:00:40 flhpz4 systemd[37743]: Started Application launched by gnome-shell. Aug 21 13:01:09 flhpz4 systemd[1]: systemd-timedated.service: Deactivated successfully. Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:02:58 flhpz4 update-notifier[43667]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Aug 21 13:03:19 flhpz4 gnome-shell[37898]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Aug 21 13:03:19 flhpz4 kernel: gnome-shell[37898]: segfault at 55a109404860 ip 55a109404860 sp 7fff85039338 error 15 Aug 21 13:03:20 flhpz4 kernel: Code: 00 00 21 00 00 00 00 00 00 00 69 6e 73 65 6e 73 69 74 69 76 65 00 00 00 00 00 6f 75 74 00 00 00 00 00 21 00 00 00 00 00 00 00 <00> 66 18 84 0d 7f 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 Aug 21 13:03:19 flhpz4 gsd-color[38044]: failed to find device: property match 'XRANDR_name'='DP-3' does not exist Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 7 threads of 3 processes of 1 users. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Successfully made thread 47682 of process 37752 owned by '1000' RT at priority 5. Aug 21 13:03:20 flhpz4 rtkit-daemon[1801]: Supervising 8 threads of 3 processes of 1 users. Aug 21 13:03:21 flhpz4 gnome-calendar[47524]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 evolution-alarm[38073]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 seahorse[47526]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38284]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 xdg-desktop-por[38239]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 unknown[38050]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 terminator[46053]: Error reading events from display: Connection reset by peer Aug 21 13:03:21 flhpz4 gsd-wacom[38078]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 firefox[46499]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 systemd[37743]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE Aug 21 13:03:21 flhpz4 systemd[37743]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE Aug 21 13:03:21 flhpz4 systemd[37743]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'. Aug 21 13:03:21 flhpz4 gsd-media-keys[38052]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 systemd[37743]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'. Aug 21 13:03:21 flhpz4 gsd-power[38053]: Error reading events from display: Broken pipe Aug 21 13:03:21 flhpz4 systemd[37743]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE Aug 21 13:03:21 flhpz4 system
[Desktop-packages] [Bug 1987045] Re: [BPO] libreoffice 7.3.5 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1987045 Title: [BPO] libreoffice 7.3.5 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981966 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.2.7 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973594 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.2.7 (EOL since June 12, 2022) is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.5-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1797/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/amd64/libr/libreoffice/20220819_142247_194f7@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/arm64/libr/libreoffice/20220819_165236_1d317@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/armhf/libr/libreoffice/20220819_173744_60f42@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/ppc64el/libr/libreoffice/20220819_152216_4dc5e@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-ppa/focal/s390x/libr/libreoffice/20220819_143225_3bdea@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 83 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987206] Re: [Latitude 3510, Realtek ALC3204, Black Headphone Out, Front] No sound at all
Can you please check description of issue. I have explained it in details. -- 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/1987206 Title: [Latitude 3510, Realtek ALC3204, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Whenever I try to connect my Headphone through 3.5mm jack pin then my system sound is not working. I tried with multiple sides and tested sound. But sound is not coming. Steps to reproduce : Start the machine. Then just plugin 3.5mm jack headphone to laptop. Then play any video and song. Sound is not coming through headphone. Steps which I tried at my end are : 1). Tried by removing the headphone to just check system sound- Then sound is working fine but when i connect to headphone then no sound. 2). I tried by chenging sound settings: connected the headphone again, then go to settings, then Sound Settings, then click on Inpput tab, then just selected option "Headphone Microphone - sof-hda-dsp", then headphone sound works. But this 2nd step I always need to do to make my headphone working on laptop. My expectation here is : My headphone should work whenever i connect it to my laptop. Also my headphone should work without doing 2nd step mentioned above. Waiting for your valuable and quick response. As this is very important feature for me to join important calls immediately without wasting time to do manual setup of sound settings every time. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: manoj 2483 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 18:44:30 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-08-11 (739 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofsklhdacard failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1600 F pulseaudio manoj 2483 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Latitude 3510, Realtek ALC3204, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0J6VTW dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd02/08/2022:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn0J6VTW:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3510 dmi.product.sku: 09ED dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-05-29T15:59:15.435030 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1987206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987206] [NEW] [Latitude 3510, Realtek ALC3204, Black Headphone Out, Front] No sound at all
Public bug reported: Whenever I try to connect my Headphone through 3.5mm jack pin then my system sound is not working. I tried with multiple sides and tested sound. But sound is not coming. Steps to reproduce : Start the machine. Then just plugin 3.5mm jack headphone to laptop. Then play any video and song. Sound is not coming through headphone. Steps which I tried at my end are : 1). Tried by removing the headphone to just check system sound- Then sound is working fine but when i connect to headphone then no sound. 2). I tried by chenging sound settings: connected the headphone again, then go to settings, then Sound Settings, then click on Inpput tab, then just selected option "Headphone Microphone - sof-hda-dsp", then headphone sound works. But this 2nd step I always need to do to make my headphone working on laptop. My expectation here is : My headphone should work whenever i connect it to my laptop. Also my headphone should work without doing 2nd step mentioned above. Waiting for your valuable and quick response. As this is very important feature for me to join important calls immediately without wasting time to do manual setup of sound settings every time. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-124.140~18.04.1-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: manoj 2483 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 18:44:30 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-08-11 (739 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofsklhdacard failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1600 F pulseaudio manoj 2483 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Latitude 3510, Realtek ALC3204, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0J6VTW dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd02/08/2022:svnDellInc.:pnLatitude3510:pvr:rvnDellInc.:rn0J6VTW:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3510 dmi.product.sku: 09ED dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-05-29T15:59:15.435030 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Attached is image for reference related to step Number 2 tried to resolve issue. Refer issue description for more ideas." https://bugs.launchpad.net/bugs/1987206/+attachment/5610472/+files/Screenshot%20from%202022-08-21%2019-05-49.png -- 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/1987206 Title: [Latitude 3510, Realtek ALC3204, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Whenever I try to connect my Headphone through 3.5mm jack pin then my system sound is not working. I tried with multiple sides and tested sound. But sound is not coming. Steps to reproduce : Start the machine. Then just plugin 3.5mm jack headphone to laptop. Then play any video and song. Sound is not coming through headphone. Steps which I tried at my end are : 1). Tried by removing the headphone to just check system sound- Then sound is working fine but when i connect to headphone then no sound. 2). I tried by chenging sound settings: connected the headphone again, then go to settings, then Sound Settings, then click on Inpput tab, then just selected option "Headphone Microphone - sof-hda-dsp", then headphone sound works. But this 2nd step I always need to do to make my headphone working on laptop. My expectation here is : My headphone should work whenever i connect it to my laptop. Also my headphone should work without doing 2nd step mentioned above. Waiting for your valuable and quick response. As this is very important feature for me to join important calls
[Desktop-packages] [Bug 1987201] Re: Screen blanking no longer works after Thunderbird "new email" alert
** Package changed: ubuntu => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1987201 Title: Screen blanking no longer works after Thunderbird "new email" alert Status in gdm3 package in Ubuntu: New Bug description: Screen blanking is enabled, set to 10 minutes. Works fine. Launch thunderbird, with option to display alert when new email arrives. After receiving new email, thunderbird displays alert. Following this, the 10-minute screen blanking no longer works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 06:04:34 2022 ExecutablePath: /usr/libexec/gdm-wayland-session InstallationDate: Installed on 2018-10-19 (1401 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: SHELL=/bin/zsh PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-08-19 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1987201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987201] [NEW] Screen blanking no longer works after Thunderbird "new email" alert
You have been subscribed to a public bug: Screen blanking is enabled, set to 10 minutes. Works fine. Launch thunderbird, with option to display alert when new email arrives. After receiving new email, thunderbird displays alert. Following this, the 10-minute screen blanking no longer works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 06:04:34 2022 ExecutablePath: /usr/libexec/gdm-wayland-session InstallationDate: Installed on 2018-10-19 (1401 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: SHELL=/bin/zsh PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-08-19 (1 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Screen blanking no longer works after Thunderbird "new email" alert https://bugs.launchpad.net/bugs/1987201 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987097] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
I had recently upgraded from 20.4 to 22.4, and this bug caused a lot of error messages to pop up and was requesting to report the bug. I saw an messages at the end of upgrade operation, which said that "Upgrade was successful but some packages upgrading failed" and firefox is one of them. Thanks for the bug reporting features and thanks for helping fix the bugs -- 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/1987097 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: Incomplete Bug description: during migration 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 1436 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Fri Aug 19 15:16:07 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-02-16 (183 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.0.254 dev enp9s0 proto static metric 100 169.254.0.0/16 dev enp9s0 scope link metric 1000 192.168.0.0/24 dev enp9s0 proto kernel scope link src 192.168.0.23 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-19 (0 days ago) dmi.bios.date: 04/18/2014 dmi.bios.release: 1.30 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd04/18/2014:br1.30:efr1.30:svnTOSHIBA:pnSATELLITES70t-A:pvrPSKN6E-01C00KFR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKN6E: dmi.product.family: Type1Family dmi.product.name: SATELLITE S70t-A dmi.product.sku: PSKN6E dmi.product.version: PSKN6E-01C00KFR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu
The bug is still there even include to Ubuntu 22.10 development branch. The crash arrive in the same conditions previously mentioned except that using X11 instead Wayland does not fix anything at all. Crash arrive in both case ! it's time for this bug to disappear ... -- 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/1934579 Title: Nautilus crashes when opening places from the dock contextmenu Status in nautilus package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987197] Re: package libfontconfig1:i386 2.13.1-4.2ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1987197 Title: package libfontconfig1:i386 2.13.1-4.2ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in fontconfig package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libfontconfig1:i386 2.13.1-4.2ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 21 16:34:45 2022 DuplicateSignature: package:libfontconfig1:i386:2.13.1-4.2ubuntu5 Setting up libxss1:i386 (1:1.2.3-1build2) ... dpkg: error processing package libfontconfig1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-08-16 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: fontconfig Title: package libfontconfig1:i386 2.13.1-4.2ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1987197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987197] [NEW] package libfontconfig1:i386 2.13.1-4.2ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libfontconfig1:i386 2.13.1-4.2ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 21 16:34:45 2022 DuplicateSignature: package:libfontconfig1:i386:2.13.1-4.2ubuntu5 Setting up libxss1:i386 (1:1.2.3-1build2) ... dpkg: error processing package libfontconfig1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-08-16 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: fontconfig Title: package libfontconfig1:i386 2.13.1-4.2ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1987197 Title: package libfontconfig1:i386 2.13.1-4.2ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in fontconfig package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libfontconfig1:i386 2.13.1-4.2ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 21 16:34:45 2022 DuplicateSignature: package:libfontconfig1:i386:2.13.1-4.2ubuntu5 Setting up libxss1:i386 (1:1.2.3-1build2) ... dpkg: error processing package libfontconfig1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-08-16 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: fontconfig Title: package libfontconfig1:i386 2.13.1-4.2ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1987197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987196] [NEW] package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1
Public bug reported: I wait for a long time when updating the firrefox and then it crashed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pathogen 1440 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sun Aug 21 15:54:59 2022 ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 ForcedLayersAccel: False InstallationDate: Installed on 2021-11-10 (283 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.126.2 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.126.0/24 dev ens33 proto kernel scope link src 192.168.126.128 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to jammy on 2022-08-21 (0 days ago) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1987196 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 Status in firefox package in Ubuntu: New Bug description: I wait for a long time when updating the firrefox and then it crashed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pathogen 1440 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sun Aug 21 15:54:59 2022 ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 ForcedLayersAccel: False InstallationDate: Installed on 2021-11-10 (283 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.126.2 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.126.0/24 dev ens33 proto kernel scope link src 192.168.126.128 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to jammy on 2022-08-21 (0 days ago) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtu
