[Desktop-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
Alright, there's no need to wait for a fix here. Mainly because there's no one to verify a fix anymore. ** No longer affects: bluez (Ubuntu Jammy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] No verifiable test case yet. Will ask the community for testing, and if it fails then consider reverting the fix. [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Confirmed ** Changed in: linux-hwe-5.19 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Rishabraju, Boot into your BIOS screen (DEL or F2). Select your drive. When the GRUB menu opens, select Advanced Features. You should then see a list of available kernels. Select 5.19.0-32-generic (the later kernels are broken. After you sign in, open the Audio setting, select HDMI hardware, and then test the speakers. -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2014976] Re: CUPS doesnt work anymore with my HP Printer
This bug was fixed in the package libppd - 2:2.0~rc1-0ubuntu1 --- libppd (2:2.0~rc1-0ubuntu1) lunar; urgency=medium * New upstream release 2.0rc1. - PPD generator sets default color mode when printer attrs say "auto" now (LP: #2014976). - ppdLoadAttributes() finds the default page size also by size dimensions now (LP: #2013131). * Removed patches as these fixes are included upstream. * Updated libppd2.symbols. -- Till Kamppeter Wed, 12 Apr 2023 00:12:27 +0200 ** Changed in: libppd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2014976 Title: CUPS doesnt work anymore with my HP Printer Status in cups-browsed package in Ubuntu: In Progress Status in libppd package in Ubuntu: Fix Released Bug description: With 22.10, the autogenerated PPD has much more info inside then with 23.10. My printer needs about 5 Minutes now to start printing and prints only black and white, no colour. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 2 00:57:13 2023 InstallationDate: Installed on 2022-10-13 (170 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0b4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (1 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2014976/+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 2015373] Re: massive yellow screen color corruption
*** This bug is a duplicate of bug 1969959 *** https://bugs.launchpad.net/bugs/1969959 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1969959, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - massive yellow screen color corruption + [nouveau] massive yellow screen color corruption ** This bug has been marked a duplicate of bug 1969959 [nouveau] Weird colors after startup (Ubuntu 22.04) ** Tags added: nouveau -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015373 Title: [nouveau] massive yellow screen color corruption Status in linux package in Ubuntu: New Bug description: using the "try ubuntu" feature, this is what the entire experience looks like (see the 2nd attached image in comment #2). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470.2 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 5 15:37:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] [1458:402b] LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.40 dmi.board.name: A320M Pro4 R2.0 dmi.board.vendor: ASRock 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.:bvrP7.40:bd10/26/2022:br5.17:svnToBeFilledByO.E.M.:pnA320MPro4R2.0:pvrToBeFilledByO.E.M.:rvnASRock:rnA320MPro4R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A320M Pro4 R2.0 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015373/+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 2015880] Re: Update mozjs102 to 102.10.0
This bug was fixed in the package mozjs102 - 102.10.0-1 --- mozjs102 (102.10.0-1) unstable; urgency=high * New upstream release (LP: #2015880) - CVE-2023-29536: Invalid free from JavaScript code - CVE-2023-29548: Incorrect optimization result on ARM64 - CVE-2023-29550: Memory safety bugs - CVE-2023-29535: Potential Memory Corruption following Garbage Collector compaction -- Jeremy Bícha Mon, 10 Apr 2023 19:48:42 -0400 ** Changed in: mozjs102 (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-29535 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-29536 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-29548 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-29550 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs102 in Ubuntu. https://bugs.launchpad.net/bugs/2015880 Title: Update mozjs102 to 102.10.0 Status in mozjs102 package in Ubuntu: Fix Released Bug description: Impact -- Several security bug fixes Filing tracker bug since we are late in the Ubuntu 23.04 release cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs102/+bug/2015880/+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 2015952] Re: libgusb-dev is missing libjson-glib-dev dependency
** Tags added: rls-ll-tracking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/2015952 Title: libgusb-dev is missing libjson-glib-dev dependency Status in libgusb package in Ubuntu: In Progress Bug description: Packages depending on libgusb-dev are broken right now, for example libfprint: Determining dependency 'gusb' with pkg-config executable '/usr/bin/pkg-config' env[PKG_CONFIG_PATH]: Called `/usr/bin/pkg-config --modversion gusb` -> 1 stderr: Package json-glib-1.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `json-glib-1.0.pc' to the PKG_CONFIG_PATH environment variable Package 'json-glib-1.0', required by 'gusb', not found In practice we're missing this change: - https://salsa.debian.org/efi-team/libgusb/-/commit/0b82db8fc0333e9d16e3e0eb9c7fa77b6d47f34c While also https://salsa.debian.org/efi- team/libgusb/-/commit/d234a8ca7dde5c8d2b0b031270156ea4933e7724 would be nice to be included to prevent this to happen again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgusb/+bug/2015952/+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 2015952] Re: libgusb-dev is missing libjson-glib-dev dependency
This is fixed in the attached patch, including the two mentioned commits ** Patch added: "libgusb_0.4.5-1ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/libgusb/+bug/2015952/+attachment/5663177/+files/libgusb_0.4.5-1ubuntu1.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/2015952 Title: libgusb-dev is missing libjson-glib-dev dependency Status in libgusb package in Ubuntu: In Progress Bug description: Packages depending on libgusb-dev are broken right now, for example libfprint: Determining dependency 'gusb' with pkg-config executable '/usr/bin/pkg-config' env[PKG_CONFIG_PATH]: Called `/usr/bin/pkg-config --modversion gusb` -> 1 stderr: Package json-glib-1.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `json-glib-1.0.pc' to the PKG_CONFIG_PATH environment variable Package 'json-glib-1.0', required by 'gusb', not found In practice we're missing this change: - https://salsa.debian.org/efi-team/libgusb/-/commit/0b82db8fc0333e9d16e3e0eb9c7fa77b6d47f34c While also https://salsa.debian.org/efi- team/libgusb/-/commit/d234a8ca7dde5c8d2b0b031270156ea4933e7724 would be nice to be included to prevent this to happen again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgusb/+bug/2015952/+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 2015952] [NEW] libgusb-dev is missing libjson-glib-dev dependency
Public bug reported: Packages depending on libgusb-dev are broken right now, for example libfprint: Determining dependency 'gusb' with pkg-config executable '/usr/bin/pkg-config' env[PKG_CONFIG_PATH]: Called `/usr/bin/pkg-config --modversion gusb` -> 1 stderr: Package json-glib-1.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `json-glib-1.0.pc' to the PKG_CONFIG_PATH environment variable Package 'json-glib-1.0', required by 'gusb', not found In practice we're missing this change: - https://salsa.debian.org/efi-team/libgusb/-/commit/0b82db8fc0333e9d16e3e0eb9c7fa77b6d47f34c While also https://salsa.debian.org/efi- team/libgusb/-/commit/d234a8ca7dde5c8d2b0b031270156ea4933e7724 would be nice to be included to prevent this to happen again. ** Affects: libgusb (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/2015952 Title: libgusb-dev is missing libjson-glib-dev dependency Status in libgusb package in Ubuntu: In Progress Bug description: Packages depending on libgusb-dev are broken right now, for example libfprint: Determining dependency 'gusb' with pkg-config executable '/usr/bin/pkg-config' env[PKG_CONFIG_PATH]: Called `/usr/bin/pkg-config --modversion gusb` -> 1 stderr: Package json-glib-1.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `json-glib-1.0.pc' to the PKG_CONFIG_PATH environment variable Package 'json-glib-1.0', required by 'gusb', not found In practice we're missing this change: - https://salsa.debian.org/efi-team/libgusb/-/commit/0b82db8fc0333e9d16e3e0eb9c7fa77b6d47f34c While also https://salsa.debian.org/efi- team/libgusb/-/commit/d234a8ca7dde5c8d2b0b031270156ea4933e7724 would be nice to be included to prevent this to happen again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgusb/+bug/2015952/+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 2015183] Re: Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.
Tracking in https://errors.ubuntu.com/problem/64e3f2e18d0341d9671739f096085c0310725018 ** Description changed: - I don't experience crashes but valgrind gnome-shell reports: + https://errors.ubuntu.com/problem/64e3f2e18d0341d9671739f096085c0310725018 ==33999== Invalid read of size 8 ==33999==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (gtype.c:4164) ==33999==by 0x4D149EA: g_object_set_data (gobject.c:4242) ==33999==by 0x363DCFD9: free_fetch_user_request (act-user-manager.c:1717) ==33999==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C382AB: reply_cb (gdbusproxy.c:2571) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C28801: g_dbus_connection_call_done (gdbusconnection.c:5885) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BCE64C: complete_in_idle_cb (gtask.c:1323) ==33999== Address 0xb966c30 is 0 bytes inside a block of size 64 free'd ==33999==at 0x484620F: free (vg_replace_malloc.c:872) ==33999==by 0x4D2C66B: g_type_free_instance (gtype.c:2062) ==33999==by 0x4D1A0A6: UnknownInlinedFun (gobject.c:1556) ==33999==by 0x4D1A0A6: g_object_notify (gobject.c:1602) ==33999==by 0x363E3519: UnknownInlinedFun (act-user.c:562) ==33999==by 0x363E3519: UnknownInlinedFun (act-user.c:557) ==33999==by 0x363E3519: _act_user_update_from_object_path (act-user.c:1346) ==33999==by 0x363E3C3F: fetch_user_incrementally (act-user-manager.c:1804) ==33999==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C382AB: reply_cb (gdbusproxy.c:2571) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C28801: g_dbus_connection_call_done (gdbusconnection.c:5885) ==33999== Block was alloc'd at ==33999==at 0x4848A13: calloc (vg_replace_malloc.c:1328) ==33999==by 0x4DB5550: g_malloc0 (gmem.c:163) ==33999==by 0x4D31B7C: g_type_create_instance (gtype.c:1965) ==33999==by 0x4D1920F: g_object_new_internal (gobject.c:2246) ==33999==by 0x4D1A7B7: g_object_new_with_properties (gobject.c:2409) ==33999==by 0x4D1B560: g_object_new (gobject.c:2055) ==33999==by 0x363DE5F1: create_new_user (act-user-manager.c:707) ==33999==by 0x363E41D8: act_user_manager_get_user (act-user-manager.c:1896) ==33999==by 0x5DDE8B5: ffi_call_unix64 (unix64.S:104) ==33999==by 0x5DDB34C: ffi_call_int.lto_priv.0 (ffi64.c:673) ==33999==by 0x5DDDF32: ffi_call (ffi64.c:710) ==33999==by 0x4F28BD8: Gjs::Function::invoke(JSContext*, JS::CallArgs const&, JS::Handle, _GIArgument*) (function.cpp:995) - ==33999== - + ==33999== ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: accountsservice 22.08.8-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 4 14:29:55 2023 InstallationDate: Installed on 2022-11-28 (126 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015183 Title: Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192) Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/64e3f2e18d0341d9671739f096085c0310725018 ==33999== Invalid read of size 8 ==33999==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (gtype.c:4164) ==33999==by 0x4D149EA: g_object_set_data (gobject.c:4242) ==33999==by 0x363DCFD9: free_fetch_user_request (act-user-manager.c:1717) ==33999==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C382AB: reply_cb
[Desktop-packages] [Bug 2015950] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_set_data:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished
*** This bug is a duplicate of bug 2015183 *** https://bugs.launchpad.net/bugs/2015183 ** This bug has been marked a duplicate of bug 2015183 Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192) -- 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/2015950 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_fundamentally_a:g_object_set_data:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished Status in gnome-shell package in Ubuntu: New 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 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/64e3f2e18d0341d9671739f096085c0310725018 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015950/+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 2015951] Re: /usr/bin/gnome-shell:5:XInternAtom:get_property:meta_input_settings_x11_set_tap_button_map:settings_device_set_uint_setting:settings_set_uint_setting
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 ** This bug has been marked a duplicate of bug 2014986 gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] -- 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/2015951 Title: /usr/bin/gnome- shell:5:XInternAtom:get_property:meta_input_settings_x11_set_tap_button_map:settings_device_set_uint_setting:settings_set_uint_setting Status in gnome-shell package in Ubuntu: New 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 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/9a8ce95b940e7ec15d62e85de24b3c098acf03c9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015951/+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 2015183] Re: Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: accountsservice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015183 Title: Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192) Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/64e3f2e18d0341d9671739f096085c0310725018 ==33999== Invalid read of size 8 ==33999==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (gtype.c:4164) ==33999==by 0x4D149EA: g_object_set_data (gobject.c:4242) ==33999==by 0x363DCFD9: free_fetch_user_request (act-user-manager.c:1717) ==33999==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C382AB: reply_cb (gdbusproxy.c:2571) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C28801: g_dbus_connection_call_done (gdbusconnection.c:5885) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BCE64C: complete_in_idle_cb (gtask.c:1323) ==33999== Address 0xb966c30 is 0 bytes inside a block of size 64 free'd ==33999==at 0x484620F: free (vg_replace_malloc.c:872) ==33999==by 0x4D2C66B: g_type_free_instance (gtype.c:2062) ==33999==by 0x4D1A0A6: UnknownInlinedFun (gobject.c:1556) ==33999==by 0x4D1A0A6: g_object_notify (gobject.c:1602) ==33999==by 0x363E3519: UnknownInlinedFun (act-user.c:562) ==33999==by 0x363E3519: UnknownInlinedFun (act-user.c:557) ==33999==by 0x363E3519: _act_user_update_from_object_path (act-user.c:1346) ==33999==by 0x363E3C3F: fetch_user_incrementally (act-user-manager.c:1804) ==33999==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C382AB: reply_cb (gdbusproxy.c:2571) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C28801: g_dbus_connection_call_done (gdbusconnection.c:5885) ==33999== Block was alloc'd at ==33999==at 0x4848A13: calloc (vg_replace_malloc.c:1328) ==33999==by 0x4DB5550: g_malloc0 (gmem.c:163) ==33999==by 0x4D31B7C: g_type_create_instance (gtype.c:1965) ==33999==by 0x4D1920F: g_object_new_internal (gobject.c:2246) ==33999==by 0x4D1A7B7: g_object_new_with_properties (gobject.c:2409) ==33999==by 0x4D1B560: g_object_new (gobject.c:2055) ==33999==by 0x363DE5F1: create_new_user (act-user-manager.c:707) ==33999==by 0x363E41D8: act_user_manager_get_user (act-user-manager.c:1896) ==33999==by 0x5DDE8B5: ffi_call_unix64 (unix64.S:104) ==33999==by 0x5DDB34C: ffi_call_int.lto_priv.0 (ffi64.c:673) ==33999==by 0x5DDDF32: ffi_call (ffi64.c:710) ==33999==by 0x4F28BD8: Gjs::Function::invoke(JSContext*, JS::CallArgs const&, JS::Handle, _GIArgument*) (function.cpp:995) ==33999== ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: accountsservice 22.08.8-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 4 14:29:55 2023 InstallationDate: Installed on 2022-11-28 (126 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2015183/+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 2015951] [NEW] /usr/bin/gnome-shell:5:XInternAtom:get_property:meta_input_settings_x11_set_tap_button_map:settings_device_set_uint_setting:settings_set_uint_setting
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/9a8ce95b940e7ec15d62e85de24b3c098acf03c9 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2015951 Title: /usr/bin/gnome- shell:5:XInternAtom:get_property:meta_input_settings_x11_set_tap_button_map:settings_device_set_uint_setting:settings_set_uint_setting Status in gnome-shell package in Ubuntu: New 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 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/9a8ce95b940e7ec15d62e85de24b3c098acf03c9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015951/+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 1968614] Re: gnome-shell crashed with SIGSEGV in meta_input_device_x11_reset_scroll_info()
** Tags added: lunar -- 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/1968614 Title: gnome-shell crashed with SIGSEGV in meta_input_device_x11_reset_scroll_info() Status in gnome-shell package in Ubuntu: Confirmed Bug description: I don't know, was using beta, something crashed, asked me to report, so here I am. I don't know why I need to specify any further details given that I have no clue what crashed at all. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 21:58:17 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-04-10 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968614/+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 2015950] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_set_data:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished
*** This bug is a duplicate of bug 2015183 *** https://bugs.launchpad.net/bugs/2015183 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/64e3f2e18d0341d9671739f096085c0310725018 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2015950 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_fundamentally_a:g_object_set_data:free_fetch_user_request:fetch_user_incrementally:on_find_user_by_name_finished Status in gnome-shell package in Ubuntu: New 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 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/64e3f2e18d0341d9671739f096085c0310725018 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015950/+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 1864215] Re: Please add webp loader to gdk-pixbuf
** Changed in: gdk-pixbuf (Baltix) Assignee: (unassigned) => Mantas Kriaučiūnas (mantas) ** Also affects: webp-pixbuf-loader (Baltix) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webp-pixbuf-loader in Ubuntu. https://bugs.launchpad.net/bugs/1864215 Title: Please add webp loader to gdk-pixbuf Status in gdk-pixbuf: Fix Released Status in webp-pixbuf-loader package in Ubuntu: Fix Released Status in gdk-pixbuf package in Baltix: Triaged Status in webp-pixbuf-loader package in Baltix: New Status in webp-pixbuf-loader package in Debian: Fix Released Bug description: Attempting to load a webp image -- for instance, https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp or https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" error. Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in libwebp, but isn't this really a gdk-pixbuf issue? If it really does belong to libwebp, my apologies, please dup this bug to 1407644 (I'm confident it doesn't belong to eog since I don't use that program; I have other programs that use libgdk-pixbuf). You can probably use eog to test this, or run /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp (I assume the loader would mention webp if there was a loader for it). I have these packages installed in addition to libgdk-pixbuf2.0-0: libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the format: $ file /tmp/FKK78W.jpg.webp /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1200x533, Scaling: [none]x[none], YUV color, decoders should clamp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Fri Feb 21 08:48:36 2020 InstallationDate: Installed on 2019-10-10 (133 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 2015947] Re: apt gives tons of errors when doing an update on the repositories. GPT keys are all screwed up
*** This bug is a duplicate of bug 2012287 *** https://bugs.launchpad.net/bugs/2012287 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 #2012287, 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/2015947/+attachment/5663141/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2015947/+attachment/5663143/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2015947/+attachment/5663144/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 2012287 GNOME Characters search provider for GNOME Shell 44 crashes ** 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/2015947 Title: apt gives tons of errors when doing an update on the repositories. GPT keys are all screwed up Status in gjs package in Ubuntu: New Bug description: I went to do an sudo apt update, and it threw tons of errors related to GPT keys. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gjs 1.76.0-1 Uname: Linux 6.2.0-19-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 20:27:57 2023 ExecutablePath: /usr/bin/gjs-console ExecutableTimestamp: 1679921159 ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters --gapplication-service ProcCwd: /home/peter ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gjs UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2015947/+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 2015948] [NEW] GNOME Character shows no emoji
Public bug reported: Emoji list is empty after gjs update ** Affects: gnome-characters (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2015948 Title: GNOME Character shows no emoji Status in gnome-characters package in Ubuntu: In Progress Bug description: Emoji list is empty after gjs update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2015948/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can also confirm #25 not working for me but #44 did on Ubuntu 22.04 and Google Chrome Version 112.0.5615.49 (Official Build) beta (64-bit) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** Changed in: gjs (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: New Status in Spidermonkey Javascript engine: Invalid Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Invalid Status in mozjs102 package in Ubuntu: Invalid Status in mozjs91 package in Ubuntu: Invalid Status in gnome-shell package in Fedora: Confirmed Bug description: https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
** Changed in: gjs (Ubuntu) Status: New => Fix Committed ** Changed in: gjs (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in gjs package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 2012978] Re: Memory leak
** Changed in: gjs (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak Status in gjs package in Ubuntu: Fix Committed Status in gjs source package in Jammy: Triaged Bug description: High Memory Usage 3.1gb in 2h after reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
** Changed in: tracker-miners (Ubuntu Jammy) Status: New => In Progress ** Changed in: tracker-miners (Ubuntu Kinetic) Status: New => In Progress ** Changed in: tracker-miners (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: tracker-miners (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: tracker-miners (Ubuntu Jammy) Assignee: (unassigned) => Denison Barbosa (justdenis) ** Changed in: tracker-miners (Ubuntu Kinetic) Assignee: (unassigned) => Denison Barbosa (justdenis) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Jammy: New Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: New Status in tracker-miners source package in Kinetic: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. ## Original description ## Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this
[Desktop-packages] [Bug 2006500] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported()
This bug was fixed in the package gnome-control-center - 1:44.0-1ubuntu5 --- gnome-control-center (1:44.0-1ubuntu5) lunar; urgency=medium * Cherry-pick a few fixes from upstream gnome-44 branch: - ad0cc232: keyboard:Fix cancel button issue - 03fcffdd: datetime: Fix NTP switch getting out of sync. - aa7a6b09: sharing: Fix network row visible name bug - 39afc8a3: display/night-light: Disconnect config manager changed handler (LP: #2006500) - 2956cd68: display/night-light: Don't leak config manager proxy -- Amin Bandali Tue, 11 Apr 2023 16:43:49 -0400 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2006500 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_manager_get_night_light_supported() Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/c917df7aa152ef3144e7356e4290c799e31475b3 gnome-control-center crashed when i try change refresh rate to other value than 60 Hz. Its crash after I tap keep changes ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 7 19:59:50 2023 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2023-02-07 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) JournalErrors: lut 07 19:59:50 hostname kernel: show_signal_msg: 4 callbacks suppressed ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55a5f2b496d4:mov(%rdi),%rax PC (0x55a5f2b496d4) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2006500/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)
** Also affects: gjs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1991709 Title: gnome-shell memory leak (when Ubuntu AppIndicators is enabled) Status in GNOME Shell: New Status in gjs package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Bug description: over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled extensions: gnome-extensions list --enabled ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com other info: lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 22:35:24 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-03 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 2012978] Re: Memory leak
** Package changed: gnome-shell (Ubuntu) => gjs (Ubuntu) ** Changed in: gjs (Ubuntu) Status: Incomplete => In Progress ** Changed in: gjs (Ubuntu) Importance: Undecided => High ** Changed in: gjs (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gjs (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gjs (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2012978 Title: Memory leak Status in gjs package in Ubuntu: In Progress Status in gjs source package in Jammy: Triaged Bug description: High Memory Usage 3.1gb in 2h after reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 22:46:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-25 (366 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+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 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
** Summary changed: - [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] + gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] ** No longer affects: nvidia-graphics-drivers-525 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 2015706] Re: Automatic time-zone detection does not work
This bug was fixed in the package geocode-glib - 3.26.3-6 --- geocode-glib (3.26.3-6) unstable; urgency=medium * Cherry-pick patch to fix geolocation in Initial Setup, Clocks (Closes: #1034158) (LP: #2015706) * Have the library package depend on the -common package -- Jeremy Bicha Mon, 10 Apr 2023 08:58:39 -0400 ** Changed in: geocode-glib (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geocode-glib in Ubuntu. https://bugs.launchpad.net/bugs/2015706 Title: Automatic time-zone detection does not work Status in geocode-glib package in Ubuntu: Fix Released Status in geocode-glib package in Debian: Unknown Bug description: Whenever gsd-datetime attempts to query the location, the following lines appear in journalctl: Apr 09 17:38:11 prescott gsd-datetime[13578]: g_bytes_unref_to_data: assertion 'size != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_file_set_contents_full: assertion 'contents != NULL || length == 0' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_task_return_error: assertion 'error != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: GTask 0x562ac7384890 (source object: 0x562ac6d73480, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. After doing some debugging, I have found that the issue is fixed by applying this commit from upstream: https://gitlab.gnome.org/GNOME/geocode- glib/-/commit/72285d203963c118a05f810016b584210663ae80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geocode-glib/+bug/2015706/+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 2015129] Re: gstreamer 1.22.1 bugfix release
** Also affects: gstreamer-editing-services1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gstreamer-editing-services1.0 (Ubuntu) Status: New => Fix Committed ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015129 Title: gstreamer 1.22.1 bugfix release Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Committed Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Committed Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: Impact -- This is a stable bugfix release See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2015129/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
I need to deploy the machine from scratch each time I access it, so I won't be able to run that command in the same install. I tried reproducing again from scratch, but this time "switch user" immediately aborted w/o generating a gnome-shell crash. I'm not sure what was different - I do know that the nvidia driver I was using has been updated in the distro, so at least that had changed. Re: nouveau_dri.so - I realized that I'd only installed the nvidia driver packages and not the "full stack" - i.e. nvidia-driver-525 and dependencies. Perhaps I was running with an unsupported config the first time. I tried installing that stack and reproducing again, but this time I saw no problem doing "switch user" at all. At that point my reservation expired and I was unable to collect logs from this session. Next I'll try to do this all over again, making sure to install both nvidia-driver-525 linux-modules-nvidia-525-generic and see if I can reproduce. -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.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:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 2015928] Re: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1
** Changed in: gst-plugins-base1.0 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015928 Title: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1 Status in gst-plugins-base: New Status in gst-plugins-base1.0 package in Ubuntu: In Progress Bug description: gst-plugins-base1.0 fails to build on Ubuntu 23.04 because of a build test failure. This appears to have been triggered by the removal of the slice allocator in glib 2.76. I have reported the issue upstream to gstreamer now. https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.22.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2015928/+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 1971168]
The patch is sent, but it seems that there were some changes in the maintainers of xdg-desktop-portal-gnome, so I suspect that it will need some time until it is merged upstream... :-( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168]
Last activity was three weeks ago, how are we looking wrt a fix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 2015129] Re: gstreamer 1.22.1 bugfix release
This bug was fixed in the package gst-plugins-good1.0 - 1.22.1-1ubuntu1
---
gst-plugins-good1.0 (1.22.1-1ubuntu1) lunar; urgency=medium
* Merge from Debian (LP: #2015129. Remaining changes:
+ Import plugins from -bad that are needed for main applications.
- jpegformat
- camerabin (+ basecamerabinsrc + photography)
+ Add a library package containing the shared library and a -dev package for
compiling against it. Add Breaks and Replaces against the plugins packages
which formerly contained files shipped here.
+ Add 'pluginsdir' variable to our added pcfile for compatibility with
some external software
+ debian/control{,.in}: Update Vcs-* for Ubuntu
+ Don't require libqt5waylandclient5-dev Build-Depends on i386
+ Don't build the Qt6 plugin on i386 since Qt6 isn't built there
on Ubuntu yet
gst-plugins-good1.0 (1.22.1-1) experimental; urgency=medium
* Team upload
* New upstream bugfix release
gst-plugins-good1.0 (1.22.0-5) unstable; urgency=medium
* Team upload
* Disable the qt5/qt6 elements on architectures where Qt5/Qt6 are not
building
-- Jeremy Bicha Tue, 04 Apr 2023 08:53:41 -0400
** Changed in: gst-plugins-good1.0 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2015129
Title:
gstreamer 1.22.1 bugfix release
Status in gst-plugins-bad1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
Triaged
Status in gst-plugins-good1.0 package in Ubuntu:
Fix Released
Status in gstreamer1.0 package in Ubuntu:
Fix Released
Bug description:
Impact
--
This is a stable bugfix release
See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2015129/+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 2007379] Update Released
The verification of the Stable Release Update for im-config has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/2007379 Title: Set GTK_IM_MODULE in Ubuntu on Xorg sessions Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Jammy: Fix Released Status in im-config source package in Kinetic: Won't Fix Status in im-config package in Debian: Fix Released Bug description: [ Impact ] gnome-settings-daemon underwent a code refactoring before the release of version 42 as regards the IBus integration on x11. Initially there was the striking bug #1969637, but also with that one fixed, an issue due to the refactoring remains. These steps illustrate the problem: * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you only can input latin letters * Log out and log in again * Find that you now can input Chinese as expected The need for the last relogin is an inconvenience and a regression compared to how it worked before gnome-settings-daemon 42. The proposed upload makes im-config set the GTK_IM_MODULE variable to 'ibus' for Ubuntu on Xorg sessions, which makes it work as smoothly as it did previously. [ Test Plan ] * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Install im-config from jammy-proposed * Reboot and log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you instantly can input Chinese Post-release: After the new version has been moved to jammy-updates and propagated, be attentive to the crash stats at errors.ubuntu.com. If a significant increase of crashes happens, which can be assumed to be related to this change, a reversal should be considered. [ Where problems could occur ] This means that we — again — make im-config interfere with the IM configuration on GNOME desktops. Via bug #1893551 we kind of did the opposite in order to reduce the frequency of ibus crashes. But the situation now is different: - This is more narrow-scoped and limited to x11 - The upstream GNOME code has undergone significant changes - The measure is greenlighted by the upstream IBus maintainer (I think Fedora does it too) But with that said, I'm going to be attentive to the frequency of ibus crashes going forward. [ Other Info ] I prefer to skip kinetic for these reasons: - Not so much time left before EOL - Low importance - A jammy user with an IBus IM already set up, and who upgrades to kinetic, won't encounter a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/2007379/+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 2007379] Re: Set GTK_IM_MODULE in Ubuntu on Xorg sessions
This bug was fixed in the package im-config - 0.50-2ubuntu22.04.1 --- im-config (0.50-2ubuntu22.04.1) jammy; urgency=medium * Set GTK_IM_MODULE in Ubuntu on Xorg sessions (LP: #2007379) -- Gunnar Hjalmarsson Wed, 15 Feb 2023 12:52:03 +0100 ** Changed in: im-config (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/2007379 Title: Set GTK_IM_MODULE in Ubuntu on Xorg sessions Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Jammy: Fix Released Status in im-config source package in Kinetic: Won't Fix Status in im-config package in Debian: Fix Released Bug description: [ Impact ] gnome-settings-daemon underwent a code refactoring before the release of version 42 as regards the IBus integration on x11. Initially there was the striking bug #1969637, but also with that one fixed, an issue due to the refactoring remains. These steps illustrate the problem: * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you only can input latin letters * Log out and log in again * Find that you now can input Chinese as expected The need for the last relogin is an inconvenience and a regression compared to how it worked before gnome-settings-daemon 42. The proposed upload makes im-config set the GTK_IM_MODULE variable to 'ibus' for Ubuntu on Xorg sessions, which makes it work as smoothly as it did previously. [ Test Plan ] * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Install im-config from jammy-proposed * Reboot and log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you instantly can input Chinese Post-release: After the new version has been moved to jammy-updates and propagated, be attentive to the crash stats at errors.ubuntu.com. If a significant increase of crashes happens, which can be assumed to be related to this change, a reversal should be considered. [ Where problems could occur ] This means that we — again — make im-config interfere with the IM configuration on GNOME desktops. Via bug #1893551 we kind of did the opposite in order to reduce the frequency of ibus crashes. But the situation now is different: - This is more narrow-scoped and limited to x11 - The upstream GNOME code has undergone significant changes - The measure is greenlighted by the upstream IBus maintainer (I think Fedora does it too) But with that said, I'm going to be attentive to the frequency of ibus crashes going forward. [ Other Info ] I prefer to skip kinetic for these reasons: - Not so much time left before EOL - Low importance - A jammy user with an IBus IM already set up, and who upgrades to kinetic, won't encounter a problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/2007379/+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 2015928] Re: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1
** Changed in: gst-plugins-base Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015928 Title: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1 Status in gst-plugins-base: New Status in gst-plugins-base1.0 package in Ubuntu: Triaged Bug description: gst-plugins-base1.0 fails to build on Ubuntu 23.04 because of a build test failure. This appears to have been triggered by the removal of the slice allocator in glib 2.76. I have reported the issue upstream to gstreamer now. https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.22.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2015928/+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 2015928] [NEW] gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1
Public bug reported: gst-plugins-base1.0 fails to build on Ubuntu 23.04 because of a build test failure. This appears to have been triggered by the removal of the slice allocator in glib 2.76. I have reported the issue upstream to gstreamer now. https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.22.1-1 ** Affects: gst-plugins-base Importance: Unknown Status: Unknown ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs lunar update-excuse ** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #2480 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2480 ** Also affects: gst-plugins-base via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2480 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015928 Title: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1 Status in gst-plugins-base: Unknown Status in gst-plugins-base1.0 package in Ubuntu: Triaged Bug description: gst-plugins-base1.0 fails to build on Ubuntu 23.04 because of a build test failure. This appears to have been triggered by the removal of the slice allocator in glib 2.76. I have reported the issue upstream to gstreamer now. https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.22.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2015928/+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 2015923] [NEW] jammy: enable GTK4 build for webkit2gtk
*** This bug is a security vulnerability *** Public security bug reported: When you update Ubuntu 22.04 LTS with webkit2gtk 2.40, please consider enabling the GTK4 build (webkitgtk-6.0). This would be useful for snapping GTK4 apps that use webkit. The most prominent example is epiphany. On the other hand, enabling the GTK4 build will lengthen the build time. The Ubuntu 22.04 LTS webkit2gtk package is building itself twice, once for 4.0 (gtk3 + libsoup2) and once for 4.1 (gtk3+ libsoup3). This request is for a third build: 6.0 (gtk4 + libsoup3). I'm marking as Security since the Security Team does most of the webkit2gtk uploads for Ubuntu stable releases. ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2015923 Title: jammy: enable GTK4 build for webkit2gtk Status in webkit2gtk package in Ubuntu: New Bug description: When you update Ubuntu 22.04 LTS with webkit2gtk 2.40, please consider enabling the GTK4 build (webkitgtk-6.0). This would be useful for snapping GTK4 apps that use webkit. The most prominent example is epiphany. On the other hand, enabling the GTK4 build will lengthen the build time. The Ubuntu 22.04 LTS webkit2gtk package is building itself twice, once for 4.0 (gtk3 + libsoup2) and once for 4.1 (gtk3+ libsoup3). This request is for a third build: 6.0 (gtk4 + libsoup3). I'm marking as Security since the Security Team does most of the webkit2gtk uploads for Ubuntu stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2015923/+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 1958019]
On my Legion Slim 7 Gen 7 16ARHA7 Same issue on Debian 12 Testing on Kernel 6.1.0-7 if this is a kernel issue, i hope it gets fixed soon and the distro maintainers can patch this sooner rather than later. Heres my audio info dump: root@Lavavex-Legion:~# aplay --list-devices List of PLAYBACK Hardware Devices card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 3: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 root@Lavavex-Legion:~# ls /dev/snd -al total 0 drwxr-xr-x 3 root root 360 Apr 10 22:23 . drwxr-xr-x 19 root root 3800 Apr 10 22:23 .. drwxr-xr-x 2 root root 120 Apr 10 22:23 by-path crw-rw+ 1 root audio 116, 3 Apr 10 22:23 controlC0 crw-rw+ 1 root audio 116, 9 Apr 10 22:23 controlC1 crw-rw+ 1 root audio 116, 10 Apr 10 22:23 controlC2 crw-rw+ 1 root audio 116, 14 Apr 10 22:23 controlC3 crw-rw+ 1 root audio 116, 6 Apr 10 22:23 hwC1D0 crw-rw+ 1 root audio 116, 8 Apr 10 22:23 hwC2D0 crw-rw+ 1 root audio 116, 13 Apr 10 22:23 hwC3D0 crw-rw+ 1 root audio 116, 2 Apr 10 22:23 pcmC0D0c crw-rw+ 1 root audio 116, 4 Apr 10 22:23 pcmC1D3p crw-rw+ 1 root audio 116, 5 Apr 10 22:23 pcmC1D7p crw-rw+ 1 root audio 116, 7 Apr 10 22:23 pcmC2D3p crw-rw+ 1 root audio 116, 12 Apr 10 22:23 pcmC3D0c crw-rw+ 1 root audio 116, 11 Apr 10 22:31 pcmC3D0p crw-rw+ 1 root audio 116, 1 Apr 10 22:23 seq crw-rw+ 1 root audio 116, 33 Apr 10 22:23 timer root@Lavavex-Legion:~# cat /proc/asound/pcm 00-00: DMIC capture dmic-hifi-0 : : capture 1 01-03: HDMI 0 : HDMI 0 : playback 1 01-07: HDMI 1 : HDMI 1 : playback 1 02-03: HDMI 0 : HDMI 0 : playback 1 03-00: ALC287 Analog : ALC287 Analog : playback 1 : capture 1 root@Lavavex-Legion:~# cat /proc/asound/cards 0 [acp6x ]: acp6x - acp6x LENOVO-82UG-LegionS716ARHA7-LNVNB161216 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xc0b0 irq 79 2 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xc06c8000 irq 80 3 [Generic_1 ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xc06c irq 81 -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6
[Desktop-packages] [Bug 1939941] Re: Drop down menu issues
*** This bug is a duplicate of bug 1940417 *** https://bugs.launchpad.net/bugs/1940417 I am also experiencing this problem on Thunderbird 102.9.0. I do not experience this problem with Firefox, only Thunderbird, hence noting it on this ticket, not the dup. If I run Thunderbird from the commandline (with or without MOZ_ENABLE_WAYLAND=1, per that other bug linked above), the menus function as normal, whereas launching with Synapse (0.2.99.4) results in the problem described here immediately on startup. I am on Ubuntu 22.04.2 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1939941 Title: Drop down menu issues Status in firefox package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I found that about a month or so ago that I was having problems with dropdown menus in Thunderbird where they would not respond when I clicked on them. I managed to get around this by using the arrow keys but I would also have issues with the thunderbird icon in the icon tray not responding if I suspended the computer with Thunderbird still open. Now I find that the drop down application menu in Firefox also doesn't work and when I click on it the menu flashes up very quickly but then disappears. Also sometimes drop down menus that I have opened continue to persist in the display even after I have shut down the program, so I don't think it is a problem just in Mozilla products. I have reported the bug to Mozilla however just in case. Thanks. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 14 13:19:47 2021 DistUpgraded: 2021-05-17 16:32:46,967 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05bd] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [1028:05bd] InstallationDate: Installed on 2021-03-06 (160 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude E6440 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i3o8fa@/vmlinuz-5.11.0-25-generic root=ZFS=rpool/ROOT/ubuntu_i3o8fa ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-17 (88 days ago) dmi.bios.date: 06/13/2019 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd06/13/2019:br65.24:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.sku: 05BD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1939941/+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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Guys i have the same problem...and i installed ubuntu 4-5 hours ago so ye sad. Can anyone tell me what to do? I need that hdmi audio output cause my laptop display is busted and i use hdmi to connect to a monitor to do things. I downloaded the latest ubuntu version currently available. assist me please... -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 1993881] Re: shotwell does not support file format WebP
This bug was fixed in the package shotwell - 0.30.18-0ubuntu1 --- shotwell (0.30.18-0ubuntu1) lunar; urgency=medium * New upstream bugfix release - Add missing value to saturation slider - Use libportal for "Set as Desktop Background" feature like Nautilus does * debian/control: Build-Depend on libportal-gtk3-dev * Depend on xdg-desktop-portal-gnome | xdg-desktop-portal-backend for "Set as Desktop Background" * debian/control: Build-Depend on libwebp-dev * Bump required libgevi2-dev to 0.12.0-2~, required for webp support * List webp-pixbuf-loader in Depends, not Build-Depends (Closes: #1034010) * Cherry-pick patch to fix build with vala 0.56.6 (Closes: #1034011) * Cherry-pick 2 more patches required for webp support to work (LP: #1993881) -- Jeremy Bicha Thu, 06 Apr 2023 09:56:00 -0400 ** Changed in: shotwell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1993881 Title: shotwell does not support file format WebP Status in shotwell package in Ubuntu: Fix Released Bug description: Try open a file in WebP format: shotwell displays a small window with a message stating: Shotwell does not support the file format of .webp corrado@corrado-n7-kinetic:~$ apt policy shotwell shotwell: Installed: 0.30.16-1ubuntu2 Candidate: 0.30.16-1ubuntu2 Version table: *** 0.30.16-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n7-kinetic:~$ inxi -Sx System: Host: corrado-n7-kinetic Kernel: 5.19.0-21-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu) corrado@corrado-n7-kinetic:~$ ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: shotwell 0.30.16-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 09:14:18 2022 InstallationDate: Installed on 2022-10-21 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1993881/+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 2015777] Re: Fix build for screen-resolution-extra 0.18.2 on Lunar
** Tags added: ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/2015777 Title: Fix build for screen-resolution-extra 0.18.2 on Lunar Status in screen-resolution-extra package in Ubuntu: In Progress Bug description: Build failure: https://launchpad.net/ubuntu/+archive/test- rebuild-20230324-lunar/+build/25796978. The attached patch fixes the build: https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/25972961. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/2015777/+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 2015800] Re: Blank screen after inactivity when set to Never
I confirm that turning off "Dim Screen" fixes the issue! Thanks Jeremy! ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/2015800 Title: Blank screen after inactivity when set to Never Status in gnome-control-center package in Ubuntu: Invalid Bug description: OS: 23.04 g-c-c: 44.0-1ubuntu4 My laptop is plugged into the charger and indicates that it is charging. In gnome-control-center, I have the "Screen Blank" setting set to Never. Also, "Automatic Suspend" is set to only happen when on battery power. So perhaps even though the battery charger icon indicates it's charging, maybe g-c-c thinks it's not? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015800/+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 2015887] Re: VPN private key is visible
Please report this for the network-manager debian package, the snappy- hwe-snaps is only for the network-manager snap package. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: snappy-hwe-snaps Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2015887 Title: VPN private key is visible Status in snappy-hwe-snaps: Invalid Status in network-manager package in Ubuntu: New Bug description: When importing a configuration from .ovpn file, I select "Store the password only for this user" for Private key in Network Manager's GUI. It then works as expected, great job! What I did not expect though, is possibility of seeing the Private key at any time afterwards (actually, the same issue applies to Password in Wi-Fi Security settings). The problem is, that this key is confidential and may only be used by our sysadmin at work, and I'm not allowed to know it, but still, I need to be able to connect to remote desktop in his absence, so the key should be stored somewhere in an encrypted format. I'd appreciate an option, that allows to hide this key from end-user - a way to disable Show password check-boxes and buttons for Private key after VPN was added, otherwise I cannot use remote desktop feature on Ubuntu at my current work. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-hwe-snaps/+bug/2015887/+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 1832426] Re: "Program" is not responding when debugging in gdb
I'm also affected by this same bug mentioned by ekso in unreal with rider using other distributions that are based off of ubuntu, like for example pop-os (with gnome-shell installed, not the cosmic DE). I've created a forum post on the epicgames community forum about this issue as well here: https://forums.unrealengine.com/t/debugging-in-rider-on-ubuntu-linux-gnome-causes-editor-or-game-to-freeze-on-breakpoints-causing-no-mouse-to-appear/835140/2 As I said in the forum post: Perhaps there is a way to make gnome aware that an application is being debugged so that it doesn't force a dialog window with wait for a response or force quit "crash". Or perhaps make it so that the cursor still appears when such a dialog appears, allowing for other applications to become interact-able with the mouse? -- 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/1832426 Title: "Program" is not responding when debugging in gdb Status in gnome-shell package in Ubuntu: Confirmed Bug description: I believe this is a regression for bug 1740869: is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.04 Release: 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+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 2015756] Re: Update cheese to 44.0
This bug was fixed in the package cheese - 44.0-1 --- cheese (44.0-1) experimental; urgency=medium * New upstream bugfix release (LP: #2015756) -- Jeremy Bícha Mon, 10 Apr 2023 09:44:52 -0400 ** Changed in: cheese (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/2015756 Title: Update cheese to 44.0 Status in cheese package in Ubuntu: Fix Released Bug description: Impact -- This is a minor bugfix release https://gitlab.gnome.org/GNOME/cheese/-/compare/43.0...master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/2015756/+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 2015880] [NEW] Update mozjs102 to 102.10.0
Public bug reported: Impact -- Several security bug fixes Filing tracker bug since we are late in the Ubuntu 23.04 release cycle ** Affects: mozjs102 (Ubuntu) Importance: High Status: In Progress ** Tags: lunar upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs102 in Ubuntu. https://bugs.launchpad.net/bugs/2015880 Title: Update mozjs102 to 102.10.0 Status in mozjs102 package in Ubuntu: In Progress Bug description: Impact -- Several security bug fixes Filing tracker bug since we are late in the Ubuntu 23.04 release cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs102/+bug/2015880/+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 2015873] Re: Firefox does not open when clicked -- first time
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2015873 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note that your report contains no information relating to the release or flavour of Ubuntu that you are using or whether the .deb or snap version of Firefox is installed. Please run the given command. That will add the appropriate information to the bug report. Please then change the status of the bug report to 'New'. ** Package changed: ubuntu => firefox (Ubuntu) ** 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/2015873 Title: Firefox does not open when clicked -- first time Status in firefox package in Ubuntu: Incomplete Bug description: When clicking Firefox starter in the side bar, the browser does not load. The cursor changes into a running action but nothing happens. Close with the drop down menu and click the starter again does open the Firefox browser. First attempt to open the browser is failing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2015873/+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 2015873] [NEW] Firefox does not open when clicked -- first time
You have been subscribed to a public bug: When clicking Firefox starter in the side bar, the browser does not load. The cursor changes into a running action but nothing happens. Close with the drop down menu and click the starter again does open the Firefox browser. First attempt to open the browser is failing. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- Firefox does not open when clicked -- first time https://bugs.launchpad.net/bugs/2015873 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox 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 2015777] Re: Fix build for screen-resolution-extra 0.18.2 on Lunar
** Changed in: screen-resolution-extra (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/2015777 Title: Fix build for screen-resolution-extra 0.18.2 on Lunar Status in screen-resolution-extra package in Ubuntu: In Progress Bug description: Build failure: https://launchpad.net/ubuntu/+archive/test- rebuild-20230324-lunar/+build/25796978. The attached patch fixes the build: https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/25972961. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/2015777/+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 2015777] Re: Fix build for screen-resolution-extra 0.18.2 on Lunar
Uploaded. Thank you for your contribution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/2015777 Title: Fix build for screen-resolution-extra 0.18.2 on Lunar Status in screen-resolution-extra package in Ubuntu: In Progress Bug description: Build failure: https://launchpad.net/ubuntu/+archive/test- rebuild-20230324-lunar/+build/25796978. The attached patch fixes the build: https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/25972961. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/2015777/+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 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
Can give an example for testing? ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: Confirmed Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+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 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
I am also affected by this bug. This is my personal last barrier to switch over to chromium from chrome. As I make heavy use of PWAs for example for microsoft and google products plus community projects like exalidraw. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [snap] PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: New Bug description: I have recently converted from deb to snap package of chromium and progressive web applications (PWAs) launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+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 2015706] Re: Automatic time-zone detection does not work
** Changed in: geocode-glib (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geocode-glib in Ubuntu. https://bugs.launchpad.net/bugs/2015706 Title: Automatic time-zone detection does not work Status in geocode-glib package in Ubuntu: Fix Committed Status in geocode-glib package in Debian: Unknown Bug description: Whenever gsd-datetime attempts to query the location, the following lines appear in journalctl: Apr 09 17:38:11 prescott gsd-datetime[13578]: g_bytes_unref_to_data: assertion 'size != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_file_set_contents_full: assertion 'contents != NULL || length == 0' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: g_task_return_error: assertion 'error != NULL' failed Apr 09 17:38:11 prescott gsd-datetime[13578]: GTask 0x562ac7384890 (source object: 0x562ac6d73480, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program. After doing some debugging, I have found that the issue is fixed by applying this commit from upstream: https://gitlab.gnome.org/GNOME/geocode- glib/-/commit/72285d203963c118a05f810016b584210663ae80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geocode-glib/+bug/2015706/+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 1877559] Re: LibreOffice Impress crash on apply a transition effect to a slide
Launchpad has imported 3 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=154743. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2023-04-10T10:05:21+00:00 gdp77 wrote: Description: Libre Impress crashes each time I try to select some of the advanced slide transitions (vortex, honeycomp etc.) Steps to Reproduce: 1.Create any slideshow 2.try to add advanced slideshow transitions like vortex, honeycomp etc. 3.Impress crashes and takes with it my DE (cinnamon) which restarts. Actual Results: Tried disabling hardware acceleration, start in safe mode, disable anti-aliasing, set in soffice.sh the variable SAL_USE_VCLPLUGIN=gen, NOTHING works. my system specs: https://docs.google.com/document/d/1yYK4Rx4Mu- XeaO9YiiDxI79BS17ge_5pYAdPank6K84/edit?usp=sharing Expected Results: Transitions should be able to work without crashing. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: el-GR (en_US.UTF-8); UI: en-US Ubuntu package version: 4:7.5.2~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877559/comments/5 On 2023-04-10T10:41:58+00:00 gdp77 wrote: UPDATE: I tested on my laptop (Ryzen 5500u - same Linux Mint 21.1) and it worked fine. So I went back to my desktop (Ryzen 5800X3D + Radeon 5600XT + Linux Mint 21.1) I tried to install latest kernel (6.10) using mainline tool. The problem remained. Last resort was to try to update my mesa drivers using oibaf ppa (I use linux mint) So, up to now I was using mesa drivers *Mesa 23.0.0*-devel (git-64d584b 2022-12-05 jammy-oibaf-ppa). Had to updated them some months ago to resolve a graphical glitch with my desktop. I made a timeshift snapshot (mesa updates can be messy) and updated my mesa drivers to latest version *Mesa 23.1.0*-devel (git-4ac56e3 2023-04-09 jammy-oibaf-ppa). THAT WAS IT! Now all the transition effects work perfectly without crashing my system. So the problem was a combination of my GPU (Radeon 5600XT) + mesa drivers. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877559/comments/6 On 2023-04-11T09:45:03+00:00 Stephane-guillou-i wrote: Thank you for testing further and reporting back. Glad the issue is fixed! Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877559/comments/8 ** Changed in: df-libreoffice Status: Unknown => Invalid ** Changed in: df-libreoffice Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1877559 Title: LibreOffice Impress crash on apply a transition effect to a slide Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Expired Bug description: On a fresh install of Ubuntu 20.04, LibreOffice Impress crash when selecting transition effect to slides. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-impress 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 11:49:25 2020 InstallationDate: Installed on 2020-05-05 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1877559/+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 1968614] Re: gnome-shell crashed with SIGSEGV in meta_input_device_x11_reset_scroll_info()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1968614 Title: gnome-shell crashed with SIGSEGV in meta_input_device_x11_reset_scroll_info() Status in gnome-shell package in Ubuntu: Confirmed Bug description: I don't know, was using beta, something crashed, asked me to report, so here I am. I don't know why I need to specify any further details given that I have no clue what crashed at all. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 21:58:17 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-04-10 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 42.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968614/+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 2015345] Re: Intermittent problems with second monitor after xorg security updates
When problems start to occur, sometimes the "working" screen goes blank and forces me to log back in, as if the screen was locked. After disabling wayland in /etc/gdm3/custom.conf and rebooting, xrandr shows the "missing" screen, and I can manually force the system to use both screens using xrandr --output eDP-1 --auto --left-of DP-1-1 I tried the 6.2.10 mainline kernel using "ubuntu-mainline-kernel.sh -i v6.2.10" after installing ubuntu-mainline-kernel.sh from https://raw.githubusercontent.com/pimlie/ubuntu-mainline- kernel.sh/master/ubuntu-mainline-kernel.sh === Before manual command: xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected (normal left inverted right x axis y axis) 1920x1080 60.05 + 60.05 1680x1050 60.05 1400x1050 60.05 1600x900 60.05 1280x1024 60.05 1400x900 60.05 1280x960 60.05 1440x810 60.05 1368x768 60.05 1280x800 60.05 1280x720 60.05 1024x768 60.05 960x720 60.05 928x696 60.05 896x672 60.05 1024x576 60.05 960x600 60.05 960x540 60.05 800x600 60.05 840x525 60.05 864x486 60.05 700x525 60.05 800x450 60.05 640x512 60.05 700x450 60.05 640x480 60.05 720x405 60.05 684x384 60.05 640x360 60.05 512x384 60.05 512x288 60.05 480x270 60.05 400x300 60.05 432x243 60.05 320x240 60.05 360x202 60.05 320x180 60.05 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 1920x1080 60.00*+ 50.0059.94 1680x1050 59.95 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x800 59.81 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-2 disconnected (normal left inverted right x axis y axis) DP-1-3 disconnected (normal left inverted right x axis y axis) == After manual command: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 1920x1080 60.05*+ 60.05 1680x1050 60.05 1400x1050 60.05 1600x900 60.05 1280x1024 60.05 1400x900 60.05 1280x960 60.05 1440x810 60.05 1368x768 60.05 1280x800 60.05 1280x720 60.05 1024x768 60.05 960x720 60.05 928x696 60.05 896x672 60.05 1024x576 60.05 960x600 60.05 960x540 60.05 800x600 60.05 840x525 60.05 864x486 60.05 700x525 60.05 800x450 60.05 640x512 60.05 700x450 60.05 640x480 60.05 720x405 60.05 684x384 60.05 640x360 60.05 512x384 60.05 512x288 60.05 480x270 60.05 400x300 60.05 432x243 60.05 320x240 60.05 360x202 60.05 320x180 60.05 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-1-1 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 600mm x 340mm 1920x1080 60.00*+ 50.0059.94 1680x1050 59.95 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x800 59.81 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-2 disconnected (normal left inverted right x axis y axis) DP-1-3 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015345 Title: Intermittent problems with second monitor after xorg security updates Status in xorg package in Ubuntu: New Bug description: I am running Ubuntu 22.04.2 LTS on a Dell 5410 laptop. Typically it is connected to a Dell WD19 docking station with an attached monitor. I have been having issues with using two monitors at once since a recent security update to several xorg packages. Since the update of:
[Desktop-packages] [Bug 2015868] Re: flash to black on login
*** This bug is a duplicate of bug 1968614 *** https://bugs.launchpad.net/bugs/1968614 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 #1968614, 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/2015868/+attachment/5663003/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2015868/+attachment/5663006/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2015868/+attachment/5663007/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 1968614 gnome-shell crashed with SIGSEGV in meta_input_device_x11_reset_scroll_info() ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2015868 Title: flash to black on login Status in gnome-shell package in Ubuntu: New Bug description: I tried to click on a launcher, it appeared unresponsive, then flash to black, desktop reappears, and "send debug information" ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-20-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 12:58:55 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/derwin Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015868/+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 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors
** Tags added: rls-ll-incoming -- 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/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in gnome-shell package in Ubuntu: New Bug description: I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015861/+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 2015863] Re: authentication prompt does not respect monitor scaling when there are multiple monitors
** Tags added: rls-ll-incoming -- 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/2015863 Title: authentication prompt does not respect monitor scaling when there are multiple monitors Status in gnome-shell package in Ubuntu: New Bug description: When the graphical authentication prompt is displayed it follows the scaling of the primary monitor even if its displayed on another monitor with a different scaling factor. In the attached screenshot I've triggered the prompt on my external monitor which is at 100% scaling. The primary monitor on my laptop is using 200% scaling. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:13:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015863/+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 2015865] Re: window size changing randomly
** Tags added: rls-ll-incoming -- 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/2015865 Title: window size changing randomly Status in gnome-shell package in Ubuntu: New Bug description: When I create an additional window for an application the previous windows size changes abruptly and without any user action. Additionally, placement of new windows seems random and unpredictable. I've attached a video to demonstrate this when I launch gnome-console using `CTRL+ALT+T`. You can see sometimes it is full screen, other times its in the top left quadrant, and then when i spawn an additional window the previous window's size changes. I am experiencing the same behavior with Files. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:29:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015865/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
** Tags removed: need-amd64-retrace -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.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:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
** Attachment added: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+attachment/5663002/+files/CoreDump.gz ** Tags added: need-amd64-retrace -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.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:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+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 2015865] [NEW] window size changing randomly
Public bug reported: When I create an additional window for an application the previous windows size changes abruptly and without any user action. Additionally, placement of new windows seems random and unpredictable. I've attached a video to demonstrate this when I launch gnome-console using `CTRL+ALT+T`. You can see sometimes it is full screen, other times its in the top left quadrant, and then when i spawn an additional window the previous window's size changes. I am experiencing the same behavior with Files. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:29:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screencast from 2023-04-11 11-25-37.webm" https://bugs.launchpad.net/bugs/2015865/+attachment/5662974/+files/Screencast%20from%202023-04-11%2011-25-37.webm -- 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/2015865 Title: window size changing randomly Status in gnome-shell package in Ubuntu: New Bug description: When I create an additional window for an application the previous windows size changes abruptly and without any user action. Additionally, placement of new windows seems random and unpredictable. I've attached a video to demonstrate this when I launch gnome-console using `CTRL+ALT+T`. You can see sometimes it is full screen, other times its in the top left quadrant, and then when i spawn an additional window the previous window's size changes. I am experiencing the same behavior with Files. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:29:40 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015865/+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 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors
** Description changed: I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. - - - running lunar lobster and a wayland session - - Gnome 44.0 - - Lenovo ThinkPad X1 Carbon Gen 9 - - 11th Gen Intel® Core™ i7-1165G7 × 8 - - Intel® Xe Graphics (TGL GT2) - - Linux 6.2.0-19-generic ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in gnome-shell package in Ubuntu: New Bug description: I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015861/+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 2015864] [NEW] tiling only triggers if window is dragged from titlebar
Public bug reported: When you drag a window from the title bar title works as expected. However, if you use the "window action key" to drag a window from elsewhere tiling does not trigger. I've attached a screencast to show the issue. This works for the gnome half screen tiling so I would expect the same behaviour with the tiling assistant. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:18:36 2023 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) PackageArchitecture: all SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-tiling-assistant (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screencast from 2023-04-11 11-17-46.webm" https://bugs.launchpad.net/bugs/2015864/+attachment/5662970/+files/Screencast%20from%202023-04-11%2011-17-46.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-tiling-assistant in Ubuntu. https://bugs.launchpad.net/bugs/2015864 Title: tiling only triggers if window is dragged from titlebar Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: When you drag a window from the title bar title works as expected. However, if you use the "window action key" to drag a window from elsewhere tiling does not trigger. I've attached a screencast to show the issue. This works for the gnome half screen tiling so I would expect the same behaviour with the tiling assistant. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:18:36 2023 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) PackageArchitecture: all SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2015864/+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 2015863] [NEW] authentication prompt does not respect monitor scaling when there are multiple monitors
Public bug reported: When the graphical authentication prompt is displayed it follows the scaling of the primary monitor even if its displayed on another monitor with a different scaling factor. In the attached screenshot I've triggered the prompt on my external monitor which is at 100% scaling. The primary monitor on my laptop is using 200% scaling. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:13:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screenshot from 2023-04-11 11-05-28.png" https://bugs.launchpad.net/bugs/2015863/+attachment/5662963/+files/Screenshot%20from%202023-04-11%2011-05-28.png ** Summary changed: - authenitcation prompt does not respect monitor scaling + authentication prompt does not respect monitor scaling when there are multiple monitors -- 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/2015863 Title: authentication prompt does not respect monitor scaling when there are multiple monitors Status in gnome-shell package in Ubuntu: New Bug description: When the graphical authentication prompt is displayed it follows the scaling of the primary monitor even if its displayed on another monitor with a different scaling factor. In the attached screenshot I've triggered the prompt on my external monitor which is at 100% scaling. The primary monitor on my laptop is using 200% scaling. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:13:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015863/+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 2015861] [NEW] cursor does not track window when dragging between monitors with different scaling factors
Public bug reported: I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. - running lunar lobster and a wayland session - Gnome 44.0 - Lenovo ThinkPad X1 Carbon Gen 9 - 11th Gen Intel® Core™ i7-1165G7 × 8 - Intel® Xe Graphics (TGL GT2) - Linux 6.2.0-19-generic ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screencast from 2023-04-11 11-03-57.webm" https://bugs.launchpad.net/bugs/2015861/+attachment/5662945/+files/Screencast%20from%202023-04-11%2011-03-57.webm -- 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/2015861 Title: cursor does not track window when dragging between monitors with different scaling factors Status in gnome-shell package in Ubuntu: New Bug description: I have two screens. My laptop is using 200% scaling and the other external screen is using 100% scaling. When I drag windows between the monitors the cursor moves to unexpected locations when it moves onto another screen with a different scaling factor. I would expect the cursor to stay in the relative location when I started dragging the window. Hopefully this is clear the the attached screencast. - running lunar lobster and a wayland session - Gnome 44.0 - Lenovo ThinkPad X1 Carbon Gen 9 - 11th Gen Intel® Core™ i7-1165G7 × 8 - Intel® Xe Graphics (TGL GT2) - Linux 6.2.0-19-generic ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 11:04:51 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-05 (5 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404) RelatedPackageVersions: mutter-common 44.0-2ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015861/+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 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006981 Title: apport-gtk crashed with signal 5 in g_log_writer_default() Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: I can´t provide any other information other than what was collected. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:9017369:2023-02-10 20:09:56.662793636 -0300:2023-02-10 20:09:57.662793636 -0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash 640:1000:124:1463707:2023-02-10 20:09:58.698746919 -0300:2023-02-10 20:09:59.698746919 -0300:/var/crash/_usr_bin_kwin_x11.1000.crash 640:1000:124:633811:2023-02-10 20:09:59.986718177 -0300:2023-02-10 20:10:00.986718177 -0300:/var/crash/_usr_bin_xembedsniproxy.1000.crash 640:1000:124:653094:2023-02-10 20:10:01.258690357 -0300:2023-02-10 20:10:02.258690357 -0300:/var/crash/_usr_bin_gmenudbusmenuproxy.1000.crash 640:1000:124:990:2023-02-10 20:10:05.770595073 -0300:2023-02-10 20:10:06.770595073 -0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: KDE Date: Fri Feb 10 20:10:04 2023 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A Signal: 5 SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2006981/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
Also: https://salsa.debian.org/gnome-team/gjs/-/merge_requests/21 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Invalid ** Changed in: gnome-shell (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: gnome-shell (Ubuntu) Milestone: ubuntu-23.04 => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: New Status in Spidermonkey Javascript engine: Invalid Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in mozjs102 package in Ubuntu: Invalid Status in mozjs91 package in Ubuntu: Invalid Status in gnome-shell package in Fedora: Confirmed Bug description: https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+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 2015858] Re: Turn on the mobile network
*** This bug is a duplicate of bug 2012287 *** https://bugs.launchpad.net/bugs/2012287 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 #2012287, 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/2015858/+attachment/5662916/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2015858/+attachment/5662918/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2015858/+attachment/5662919/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 2012287 GNOME Characters search provider for GNOME Shell 44 crashes ** 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/2015858 Title: Turn on the mobile network Status in gjs package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gjs 1.75.90-1 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 11 09:27:20 2023 ExecutablePath: /usr/bin/gjs-console ExecutableTimestamp: 1678210639 ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters --gapplication-service ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gjs UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2015858/+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 2015782] Re: gnome-shell makes the system crash "Window manager warning: Overwriting existing binding of keysym 32 with keysym 32"
Also next time a crash happens, after rebooting please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - gnome-shell makes the system crash "Window manager warning: Overwriting existing binding of keysym 32 with keysym 32" + System crash -- 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/2015782 Title: System crash Status in Ubuntu: Incomplete Bug description: gnome-shell makes the system crash occasionally. Last time was after closing a youtube tab in firefox. Custom keyboard shorcuts are also not working sometimes. My system is Ubuntu 22.04.2 LTS Linux PC1 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC CPU: Ryzen 7 7700X RAM: 32 GB 6000 CL30 GPU: Nvidia 2060 Super MOBO: Asrock x670e Steel Legend ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 11:58:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-24 (44 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015782/+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 2015782] Re: gnome-shell makes the system crash "Window manager warning: Overwriting existing binding of keysym 32 with keysym 32"
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- 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/2015782 Title: System crash Status in Ubuntu: Incomplete Bug description: gnome-shell makes the system crash occasionally. Last time was after closing a youtube tab in firefox. Custom keyboard shorcuts are also not working sometimes. My system is Ubuntu 22.04.2 LTS Linux PC1 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC CPU: Ryzen 7 7700X RAM: 32 GB 6000 CL30 GPU: Nvidia 2060 Super MOBO: Asrock x670e Steel Legend ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 11:58:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-24 (44 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015782/+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 2015782] Re: gnome-shell makes the system crash "Window manager warning: Overwriting existing binding of keysym 32 with keysym 32"
That warning (bug 1857392) is not related to crashes. If you experience crashes then please follow: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/2015782 Title: System crash Status in Ubuntu: Incomplete Bug description: gnome-shell makes the system crash occasionally. Last time was after closing a youtube tab in firefox. Custom keyboard shorcuts are also not working sometimes. My system is Ubuntu 22.04.2 LTS Linux PC1 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC CPU: Ryzen 7 7700X RAM: 32 GB 6000 CL30 GPU: Nvidia 2060 Super MOBO: Asrock x670e Steel Legend ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 11:58:07 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-02-24 (44 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015782/+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 2015642] Re: gnome-shell crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 ** This bug is no longer a duplicate of private bug 2015547 ** This bug has been marked a duplicate of bug 2014986 [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] -- 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/2015642 Title: gnome-shell crashed with signal 5 in _XReply() Status in gnome-shell package in Ubuntu: New Bug description: - Gnome 44 - Kernel 6.2 - Gtx 1070 max-Q with nvidia 525 drivers ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 8 18:44:18 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-31 (7 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=pt_PT.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /lib/x86_64-linux-gnu/libX11.so.6 XInternAtom () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0 Title: gnome-shell crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015642/+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 2015647] Re: gnome-shell crashed with signal 5 in _XEventsQueued()
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 Duplicate of bug 2015027 (bug 2014986) ** This bug has been marked a duplicate of bug 2014986 [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] -- 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/2015647 Title: gnome-shell crashed with signal 5 in _XEventsQueued() Status in gnome-shell package in Ubuntu: Invalid Bug description: Crash happened upon boot. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 8 11:53:30 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-04 (34 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu3 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015647/+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 2008607] Re: if an item is selected the scrolling keeps jumping back to it without progressing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/2008607 Title: if an item is selected the scrolling keeps jumping back to it without progressing Status in nautilus package in Ubuntu: Confirmed Bug description: If an item is selected the scrolling jumps back to it sometimes. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 13:52:45 2023 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008607/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Recent Ubuntu 22.04.2 LTS, libgtk-4-common 4.6.6+ds-0ubuntu1, libgtk-3-common 3.24.33-1ubuntu2,vivaldi-stable 5.7.2921.65-1 'Save as' dialog now works as expected: focus is on filename keyboard entry, immediately closes dialog. BAD regression: Vivaldi window is frozen after that. Does not happen with other distros, cf https://forum.vivaldi.net/topic/85488/bug-saving-a-web-page-freezes-browser-window This is since about 1 week now. As I got used to mousing my way around the previous bug, I did not immediately notice the changed behaviour. Except the browser hang, of course. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Invalid Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1999924] Re: Unsupported buffer format 842094158 (NV12)
I'm told Chromium already worked around this, but for the record, proper NV12 support is in progress at https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2191 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: New => In Progress -- 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/124 Title: Unsupported buffer format 842094158 (NV12) Status in chromium-browser package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. OS: Ubuntu 22.10 Desktop: Wayland GPU: Intel AlderLake-S GT1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+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 1999924] Re: Unsupported buffer format 842094158 (NV12)
** Summary changed: - Unsupported buffer format 842094158 + Unsupported buffer format 842094158 (NV12) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/124 Title: Unsupported buffer format 842094158 (NV12) Status in chromium-browser package in Ubuntu: Confirmed Bug description: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. OS: Ubuntu 22.10 Desktop: Wayland GPU: Intel AlderLake-S GT1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
OK that didn't work. We can't usually handle crash files as attachments... Please report the crash file again by running: ubuntu-bug _usr_bin_gnome-shell.1002.crash or apport-cli _usr_bin_gnome-shell.1002.crash from the machine. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** No longer affects: mesa (Ubuntu) ** No longer affects: nvidia-graphics-drivers-525 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: Incomplete Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.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:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
** Information type changed from Public Security to Public -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 1994011] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_da
Also tracking in https://errors.ubuntu.com/problem/910a78997982c35fd72bc02352f051ef09f8b09e -- 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/1994011 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() Status in mutter package in Ubuntu: Fix Released 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 43.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/572031ecb97102a47da85c728ab7b98e918bb1bd contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1994011/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
** Tags removed: need-amd64-retrace -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.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:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+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 2015840] Re: /usr/bin/gnome-shell:11:g_strjoinv:init_secondary_gpu_data_gpu:init_secondary_gpu_data:create_renderer_gpu_data_gbm:meta_renderer_native_create_renderer_gpu_data
*** This bug is a duplicate of bug 1994011 *** https://bugs.launchpad.net/bugs/1994011 ** This bug has been marked a duplicate of bug 1994011 gnome-shell crashed with SIGSEGV in __strlen_avx2() from g_strjoinv() from init_secondary_gpu_data_gpu() from init_secondary_gpu_data() from create_renderer_gpu_data_gbm() -- 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/2015840 Title: /usr/bin/gnome- shell:11:g_strjoinv:init_secondary_gpu_data_gpu:init_secondary_gpu_data:create_renderer_gpu_data_gbm:meta_renderer_native_create_renderer_gpu_data Status in gnome-shell package in Ubuntu: New 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.5-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/910a78997982c35fd72bc02352f051ef09f8b09e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015840/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
Three observations: - Crashing in nouveau_dri.so which shouldn't be used at all when the proper Nvidia driver is installed. - Unexplained crashes in cogl_blit_framebuffer() is something I've seen before when working on Nvidia multi-GPU support. So that sounds relevant; https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2749 - The #1 gnome-shell crash in jammy (bug 1960590) is also Nvidia- specific but is not provably related yet... ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-525 (Ubuntu) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags added: need-amd64-retrace ** Tags added: multigpu nvidia wayland wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.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:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+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 2015840] [NEW] /usr/bin/gnome-shell:11:g_strjoinv:init_secondary_gpu_data_gpu:init_secondary_gpu_data:create_renderer_gpu_data_gbm:meta_renderer_native_create_renderer_gpu_data
*** This bug is a duplicate of bug 1994011 *** https://bugs.launchpad.net/bugs/1994011 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.5-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/910a78997982c35fd72bc02352f051ef09f8b09e 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal jammy -- 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/2015840 Title: /usr/bin/gnome- shell:11:g_strjoinv:init_secondary_gpu_data_gpu:init_secondary_gpu_data:create_renderer_gpu_data_gbm:meta_renderer_native_create_renderer_gpu_data Status in gnome-shell package in Ubuntu: New 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.5-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/910a78997982c35fd72bc02352f051ef09f8b09e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015840/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
We need the robots to retrace that properly, but what I can figure so far is: #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=139744913655232) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. [Current thread is 1 (Thread 0x7f18e5f005c0 (LWP 7141))] (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=139744913655232) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=139744913655232) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=139744913655232, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f18eb1c9476 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #4 0x561d62d507aa in ?? () #5 #6 __strlen_avx2_rtm () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #7 0x7f18d5f2192a in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #8 0x7f18d5f21567 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #9 0x7f18d62afed0 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #10 0x7f18d62ab825 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #11 0x7f18d62ad4c7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #12 0x7f18d61940da in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #13 0x7f18d617523f in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #14 0x7f18eae25cf2 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7f18eae22b3c in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #16 0x7f18eae22fee in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #17 0x7f18eae33c71 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #18 0x7f18eae1bc76 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #19 0x7f18eae4aeb2 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #20 0x7f18eae4b233 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #21 0x7f18eae4b4c6 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #22 0x7f18eae4bf4f in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #23 0x7f18eae53343 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #24 0x7f18ec109f80 in g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f18eae52e7b in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #26 0x7f18eae55e30 in cogl_blit_framebuffer () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #27 0x7f18eb695b4d in clutter_stage_view_before_swap_buffer () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-clutter-10.so.0 #28 0x7f18eb434803 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #29 0x7f18eb438f71 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #30 0x7f18eb52482b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #31 0x7f18eb696258 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-clutter-10.so.0 --Type for more, q to quit, c to continue without paging-- #32 0x7f18eb65eda9 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-clutter-10.so.0 #33 0x7f18ec10fd3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7f18ec1646c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7f18ec10f2b3 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f18eb47f909 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #37 0x561d62d4ff12 in ?? () #38 0x7f18eb1b0d90 in __libc_start_call_main ( main=main@entry=0x561d62d4fa70, argc=argc@entry=1, argv=argv@entry=0x7ffc73a73a48) at ../sysdeps/nptl/libc_start_call_main.h:58 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
