[Desktop-packages] [Bug 1930119] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1930119 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: i am install chromium browser but show some unwanted error ProblemType: Package DistroRelease: Ubuntu 21.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.11.0-1008.8-raspi 5.11.12 Uname: Linux 5.11.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: chromium-browser:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue May 25 19:57:47 2021 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 ImageMediaBuild: 20210421 Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1930119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930119] [NEW] package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
Public bug reported: i am install chromium browser but show some unwanted error ProblemType: Package DistroRelease: Ubuntu 21.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.11.0-1008.8-raspi 5.11.12 Uname: Linux 5.11.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: chromium-browser:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue May 25 19:57:47 2021 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 ImageMediaBuild: 20210421 Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image hirsute raspi-image -- 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/1930119 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: i am install chromium browser but show some unwanted error ProblemType: Package DistroRelease: Ubuntu 21.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.11.0-1008.8-raspi 5.11.12 Uname: Linux 5.11.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: chromium-browser:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue May 25 19:57:47 2021 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 ImageMediaBuild: 20210421 Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1930119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921764] Re: [radeon] Bug affichage.
[Expired for xserver-xorg-video-ati (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1921764 Title: [radeon] Bug affichage. Status in xserver-xorg-video-ati package in Ubuntu: Expired Bug description: Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18 Uname: Linux 4.15.0-140-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 29 17:55:52 2021 DistUpgraded: 2021-03-27 13:26:19,628 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Juniper XT [Radeon HD 5770] [174b:e147] InstallationDate: Installed on 2021-03-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. P35-DS4 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-140-generic root=UUID=040b03c4-747a-4dce-8e7a-5cbea40e1985 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2021-03-27 (2 days ago) dmi.bios.date: 05/11/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: P35-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/11/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Mar 29 17:47:30 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech M315/M235 MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1921764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930104] Re: GNOME 40 (GDM) prevents GNOME Screensaver from locking
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1930104 Title: GNOME 40 (GDM) prevents GNOME Screensaver from locking Status in gnome-screensaver package in Ubuntu: New Bug description: WORK IN PROGRESS - GIT PR to be done Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock- screen. GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME Screensaver previously utilised. This prevents GNOME Screensaver from working i.e. provide its locking capability. To resolve this requires a patch to kill the GDM spawned process releasing the dbus grab. All of this is explained in the dep3 headers of the debdiff patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1930104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930112] [NEW] Error When Shutting Down via GUI- Xubuntu 21.04
Public bug reported: I get an error when I try to shutdown via the GUI, screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 28 19:59:00 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Desktop) [1028:085a] InstallationDate: Installed on 2021-05-27 (1 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. OptiPlex 7060 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c7908293-5a44-4112-b804-867efc7801ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0NC2VH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd05/05/2021:br1.12:svnDellInc.:pnOptiPlex7060:pvr:rvnDellInc.:rn0NC2VH:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7060 dmi.product.sku: 085A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu ** Attachment added: "Screenshot_2021-05-28_20-04-08.png" https://bugs.launchpad.net/bugs/1930112/+attachment/5500947/+files/Screenshot_2021-05-28_20-04-08.png -- 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/1930112 Title: Error When Shutting Down via GUI- Xubuntu 21.04 Status in xorg package in Ubuntu: New Bug description: I get an error when I try to shutdown via the GUI, screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 28 19:59:00 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Desktop) [1028:085a] InstallationDate: Installed on 2021-05-27 (1 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. OptiPlex 7060 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c7908293-5a44-4112-b804-867efc7801ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0NC2VH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd05/05/2021:br1.12:svnDellInc.:pnOptiPlex7060:pvr:rvnDellInc.:rn0NC2VH:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7060 dmi.product.sku: 085A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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
[Desktop-packages] [Bug 1930104] Re: GNOME 40 (GDM) prevents GNOME Screensaver from locking
** Description changed: + WORK IN PROGRESS - GIT PR to be done + Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock- screen. GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME Screensaver previously utilised. This prevents GNOME Screensaver from working i.e. provide its locking capability. To resolve this requires a patch to kill the GDM spawned process releasing the dbus grab. All of this is explained in the dep3 headers of the debdiff patch attached -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1930104 Title: GNOME 40 (GDM) prevents GNOME Screensaver from locking Status in gnome-screensaver package in Ubuntu: New Bug description: WORK IN PROGRESS - GIT PR to be done Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock- screen. GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME Screensaver previously utilised. This prevents GNOME Screensaver from working i.e. provide its locking capability. To resolve this requires a patch to kill the GDM spawned process releasing the dbus grab. All of this is explained in the dep3 headers of the debdiff patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1930104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1215882]
*** Bug 1713077 has been marked as a duplicate of this bug. ***
--
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/1215882
Title:
Emails are silently discarded on 554 reply to STARTTLS
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
It seems that emails are silently discarded when the remote SMTP
server replies with an error on STARTTLS. Here is an example smtp log
created with NSPR_LOG_MODULES='smtp:5,timestamp':
2013-08-23 11:10:25.548708 UTC - 43480896[7fe10164b370]: SMTP Connecting to:
mail.trialphaenergy.com
2013-08-23 11:10:26.513993 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:26.514026 UTC - 43480896[7fe10164b370]: SMTP Response: 220
mail.trialphaenergy.com Microsoft ESMTP MAIL Service ready at Fri, 23 Aug 2013
04:10:25 -0700
2013-08-23 11:10:26.514047 UTC - 43480896[7fe10164b370]: SMTP entering state:
14
2013-08-23 11:10:26.514069 UTC - 43480896[7fe10164b370]: SMTP Send: EHLO
[10.11.206.9]
2013-08-23 11:10:27.144751 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144791 UTC - 43480896[7fe10164b370]: SMTP Response:
250-mail.trialphaenergy.com Hello [10.11.10.19]
2013-08-23 11:10:27.144808 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144817 UTC - 43480896[7fe10164b370]: SMTP Response:
250-SIZE
2013-08-23 11:10:27.144828 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144839 UTC - 43480896[7fe10164b370]: SMTP Response:
250-PIPELINING
2013-08-23 11:10:27.144846 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144851 UTC - 43480896[7fe10164b370]: SMTP Response:
250-DSN
2013-08-23 11:10:27.144857 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144862 UTC - 43480896[7fe10164b370]: SMTP Response:
250-ENHANCEDSTATUSCODES
2013-08-23 11:10:27.144868 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144885 UTC - 43480896[7fe10164b370]: SMTP Response:
250-STARTTLS
2013-08-23 11:10:27.144889 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144893 UTC - 43480896[7fe10164b370]: SMTP Response:
250-AUTH NTLM
2013-08-23 11:10:27.144897 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144900 UTC - 43480896[7fe10164b370]: SMTP Response:
250-8BITMIME
2013-08-23 11:10:27.144904 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144920 UTC - 43480896[7fe10164b370]: SMTP Response:
250-BINARYMIME
2013-08-23 11:10:27.144926 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.144931 UTC - 43480896[7fe10164b370]: SMTP Response: 250
CHUNKING
2013-08-23 11:10:27.144936 UTC - 43480896[7fe10164b370]: SMTP entering state:
4
2013-08-23 11:10:27.144961 UTC - 43480896[7fe10164b370]: SMTP entering state:
21
2013-08-23 11:10:27.144968 UTC - 43480896[7fe10164b370]: SMTP Send: STARTTLS
2013-08-23 11:10:27.757848 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
2013-08-23 11:10:27.757881 UTC - 43480896[7fe10164b370]: SMTP Response: 554
Policy violation. Email Session ID: {521742ED-1-F0B0B0A-}
2013-08-23 11:10:27.757893 UTC - 43480896[7fe10164b370]: SMTP entering state:
19
2013-08-23 11:10:27.757900 UTC - 43480896[7fe10164b370]: SMTP entering state:
21
2013-08-23 11:10:27.757905 UTC - 43480896[7fe10164b370]: SMTP Send: QUIT
2013-08-23 11:10:27.757915 UTC - 43480896[7fe10164b370]: SMTP entering state: 0
The UI, however, gives no indication of failure and closes the compose window
after the apparent successful submission to the smtp server.
If the user has not configured a Sent folder this results in data loss. Even
if the user has configured a sent folder, he receives no indication that the
email has not been sent.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikratio 2425 F pulseaudio
BuildID: 20130803220711
Channel: Unavailable
Date: Fri Aug 23 13:05:30 2013
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-07-30 (23 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PrefSources:
prefs.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
[Desktop-packages] [Bug 1930104] Re: GNOME 40 (GDM) prevents GNOME Screensaver from locking
** Patch added: "gnome40gdm.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1930104/+attachment/5500946/+files/gnome40gdm.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1930104 Title: GNOME 40 (GDM) prevents GNOME Screensaver from locking Status in gnome-screensaver package in Ubuntu: New Bug description: Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock- screen. GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME Screensaver previously utilised. This prevents GNOME Screensaver from working i.e. provide its locking capability. To resolve this requires a patch to kill the GDM spawned process releasing the dbus grab. All of this is explained in the dep3 headers of the debdiff patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1930104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930104] [NEW] GNOME 40 (GDM) prevents GNOME Screensaver from locking
Public bug reported: Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock- screen. GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME Screensaver previously utilised. This prevents GNOME Screensaver from working i.e. provide its locking capability. To resolve this requires a patch to kill the GDM spawned process releasing the dbus grab. All of this is explained in the dep3 headers of the debdiff patch attached ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Assignee: fossfreedom (fossfreedom) Status: New ** Changed in: gnome-screensaver (Ubuntu) Assignee: (unassigned) => fossfreedom (fossfreedom) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1930104 Title: GNOME 40 (GDM) prevents GNOME Screensaver from locking Status in gnome-screensaver package in Ubuntu: New Bug description: Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock- screen. GNOME40 with GDM now grabs the Screensaver dbus entry that GNOME Screensaver previously utilised. This prevents GNOME Screensaver from working i.e. provide its locking capability. To resolve this requires a patch to kill the GDM spawned process releasing the dbus grab. All of this is explained in the dep3 headers of the debdiff patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1930104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849478] Re: [snap] (experimental) pipewire support not available
Relevant output from pw-dump when sharing the entire screen (which
remains black). The interesting bit is ["state": "suspended"]:
{
"id": 34,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"pipewire.protocol": "protocol-native",
"pipewire.sec.pid": 5394,
"pipewire.sec.uid": 1000,
"pipewire.sec.gid": 1000,
"pipewire.sec.label": "unconfined",
"module.id": 2,
"object.id": 34,
"log.level": 0,
"clock.power-of-two-quantum": true,
"default.clock.rate": 48000,
"default.clock.quantum": 1024,
"default.clock.min-quantum": 32,
"default.clock.max-quantum": 8192,
"default.video.width": 640,
"default.video.height": 480,
"default.video.rate.num": 25,
"default.video.rate.denom": 1,
"link.max-buffers": 64,
"mem.warn-mlock": false,
"mem.allow-mlock": true,
"cpu.max-align": 32,
"application.name": "gnome-shell",
"application.process.binary": "gnome-shell",
"application.language": "fr_FR.UTF-8",
"application.process.id": 5394,
"application.process.user": "osomon",
"application.process.host": "dantian",
"window.x11.display": ":0",
"core.version": "0.3.24",
"core.name": "pipewire-osomon-5394",
"pipewire.access": "unrestricted"
}
}
},
{
"id": 33,
"type": "PipeWire:Interface:Node",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"max-input-ports": 0,
"max-output-ports": 1,
"change-mask": [ "input-ports", "output-ports", "state", "props",
"params" ],
"n-input-ports": 0,
"n-output-ports": 1,
"state": "suspended",
"error": null,
"props": {
"media.name": "meta-screen-cast-src",
"stream.is-live": true,
"node.name": "gnome-shell",
"node.driver": true,
"media.class": "Stream/Output/Video",
"client.id": 34,
"object.id": 33
},
"params": {
}
}
},
{
"id": 35,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"direction": "output",
"change-mask": [ "props", "params" ],
"props": {
"port.id": 0,
"port.direction": "out",
"port.name": "out_0",
"node.id": 33,
"object.id": 35
},
"params": {
"EnumFormat": [
{
"mediaType": "video",
"mediaSubtype": "raw",
"format": "BGRx",
"size": { "width": 1920, "height": 1080 },
"framerate": { "num": 0, "denom": 1 },
"maxFramerate": { "default": { "num": 7864385, "denom": 131072 },
"min": { "num": 1, "denom": 1 }, "max": { "num": 7864385, "denom": 131072 } }
}
],
"Meta": [
{
"type": "Busy",
"size": 8
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ]
}
}
},
{
"id": 39,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"pipewire.protocol": "protocol-native",
"pipewire.sec.pid": 6827,
"pipewire.sec.uid": 1000,
"pipewire.sec.gid": 1000,
"pipewire.sec.label": "unconfined",
"module.id": 2,
"object.id": 39,
"pipewire.access.portal.app_id": "snap.chromium",
"pipewire.access.portal.media_roles": 0,
"log.level": 0,
"clock.power-of-two-quantum": true,
"default.clock.rate": 48000,
"default.clock.quantum": 1024,
"default.clock.min-quantum": 32,
"default.clock.max-quantum": 8192,
"default.video.width": 640,
"default.video.height": 480,
"default.video.rate.num": 25,
"default.video.rate.denom": 1,
"link.max-buffers": 64,
"mem.warn-mlock": false,
"mem.allow-mlock": true,
"cpu.max-align": 32,
"application.name": "xdg-desktop-portal",
"application.process.binary": "xdg-desktop-portal",
"application.language": "fr_FR.UTF-8",
"application.process.id": 6827,
"application.process.user": "osomon",
"application.process.host": "dantian",
"window.x11.display": ":0",
"core.version": "0.3.24",
"core.name": "pipewire-osomon-6827",
"pipewire.access": "portal"
}
}
},
--
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/1849478
Title:
[snap] (experimental) pipewire support not
[Desktop-packages] [Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
** Description changed: + [ Impact ] + On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the - available scaling options in the gnome-control-center (version: - 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, - 300, and 400%. This is insufficient as 200% is too small and 300% is too - large. The missing fractional scaling options are dealt with in bug - #1687246. However, the currently available experimental feature to - enable fractional scaling (provided in the bug description of #1687246) - does not solve the problem on my machine: + available scaling options in the gnome-control-center display settings + are limited to 100, 200, 300, and 400%. This is insufficient as 200% is + too small and 300% is too large. The missing fractional scaling options + are dealt with in bug #1687246. However, the currently available + experimental feature to enable fractional scaling (provided in the bug + description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." - ProblemType: Bug - DistroRelease: Ubuntu 18.10 + [ Test case ] + + In a setup with a display with HighDPi resolution (higher than 2880x1800) + - Open gnome-control-center display panel + - Scaling should show 5 level buttons to select + - Selecting higher values will show all the selectable values closer to the chosen one + - Any value could be used from 100% up to 400% (maximum varies on resolution) + + [ Regression potential ] + + Control center won't show any scaling value, or scaling value may be + wrong. + + --- + + ProblemType: BugDistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) - InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) - SourcePackage: gnome-control-center + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gnome-control-center (Ubuntu Hirsute) Status: Triaged => In Progress ** Changed in: gnome-control-center (Ubuntu Focal) Status: Triaged => In Progress -- 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/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: In Progress Status in gnome-control-center source package in Hirsute: In Progress Bug description: [ Impact ] On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246,
[Desktop-packages] [Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
While I'm fixing this upstream to show all the values and we're SRUing it to ubuntu stable versions, I've made a ppa for hisute (21.04) and focal (20.04) so you can test it (packages are building right now, so may take some moments): https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4565/ Note: since it's preferable not to change design in a SRU, the values will be still limited to 5 and will shoe exactly like before, but now selecting higher values, more scaling values will be visible and selectable. ** Also affects: gnome-control-center (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu Hirsute) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu Hirsute) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gnome-control-center (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu Focal) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu Focal) 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Focal: In Progress Status in gnome-control-center source package in Hirsute: In Progress Bug description: [ Impact ] On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." [ Test case ] In a setup with a display with HighDPi resolution (higher than 2880x1800) - Open gnome-control-center display panel - Scaling should show 5 level buttons to select - Selecting higher values will show all the selectable values closer to the chosen one - Any value could be used from 100% up to 400% (maximum varies on resolution) [ Regression potential ] Control center won't show any scaling value, or scaling value may be wrong. --- ProblemType: BugDistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930101] [NEW] gnome-shell calendar week numbers may not be vertically centered
Public bug reported: [ Impact ] Week numbers in gnome shell calendar are not vertically centered, with some fonts configurations (as in [1]). [ Test case ] 1. Open the gnome-shell calendar 2. Ensure that week numbers are vertically centered [ Regression potential ] Week numbers have wrong padding [1] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1415 ** Affects: yaru-theme (Ubuntu) Importance: Low 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 yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1930101 Title: gnome-shell calendar week numbers may not be vertically centered Status in yaru-theme package in Ubuntu: In Progress Bug description: [ Impact ] Week numbers in gnome shell calendar are not vertically centered, with some fonts configurations (as in [1]). [ Test case ] 1. Open the gnome-shell calendar 2. Ensure that week numbers are vertically centered [ Regression potential ] Week numbers have wrong padding [1] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1930101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921929] Re: Cancelling an ongoing verification via Escape key doesn't work
Hitting escape to cancel authentication works promptly now ❯ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.9-0ubuntu0.20.04.1 Candidato: 3.36.9-0ubuntu0.20.04.1 Tabella versione: *** 3.36.9-0ubuntu0.20.04.1 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1921929 Title: Cancelling an ongoing verification via Escape key doesn't work Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] When an identification is in progress, we can't cancel the user verification via Escape key [ Test case ] - Start authenticating an user (using a wrong password may make this easier to trigger) - Hit Escape - Authentication is cancelled and user can put PIN / password again [ Regression potential ] Authentication fails even if it should not, user authentication may lead to user to see the user lists under gdm when not expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
Tested with another user with no enrolled prints, and login and locking operations work fine. ❯ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.9-0ubuntu0.20.04.1 Candidato: 3.36.9-0ubuntu0.20.04.1 Tabella versione: *** 3.36.9-0ubuntu0.20.04.1 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages Also the autopkg tests regressions have been fixed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] This bug didn't affect current focal, but we still prefer to test it to ensure we're not regressing while fixing LP: #1865838. This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. [ Test case ] - In a system with a fingerprint reader supported by fprintd: Try to login in GDM using password authentication with an user that has NO enrolled fingerprints - Logging in should be possible, and so unlocking the screen [ Regression potential ] Impossible to login with authentication methods that expose them as unavailable. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921963] Re: SRU 3.36.9
Chris, as said the change we did in yaru is just applying to gnome-shell code, reflecting gnome-shell upstream code changes so putting it in different bug wouldn't be correct in this case. However I'm doing that. Also, I can confirm gnome-shell 3.36.9 as verified here ❯ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.9-0ubuntu0.20.04.1 Candidato: 3.36.9-0ubuntu0.20.04.1 Tabella versione: *** 3.36.9-0ubuntu0.20.04.1 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1921963 Title: SRU 3.36.9 Status in gnome-shell package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in yaru-theme source package in Focal: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Login a11y changed and so the usage of icons for notifications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929304] Re: file-roller / gnome archive manager fails to extract
apologies for the delay in replying. i have gnome archive manager 3.38.0 | fedora 34 | gnome 40.0.1 | wayland i face the exact same issue on ubuntu 20.04.2 | gnome 3.36.8 | X11 i download the file from the above posted links, right click & in the context menu the 1st option is extract here so i click on that & i get a new folder with the filename on it but the folder is empty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1929304 Title: file-roller / gnome archive manager fails to extract Status in file-roller package in Ubuntu: Incomplete Bug description: problem occurs with : a) ubuntu 20.04.2 | gnome version 3.36.8 | X11 b) fedora 34 | gnome 40.0.1 | wayland the latest version of gnome archive manager which is 3.36.3 fails to extract a .gz file which it used to do earlier. here are 2 links to 2 separate versions of hard disk sentinel linux version : 1. https://www.hdsentinel.com/hdslin/hdsentinel-018c.gz 2. https://www.hdsentinel.com/hdslin/hdsentinel-019c-x64.gz when i try to extract both the above mentioned files by right clicking & then extract here all i get is an empty folder with nothing extracted in it. if i open the gnome archive manager 3.36.3 from the applications menu & then try to extract the 1st file hard disk sentinel version 018c the extraction is successful. but if i open the gnome archive manager 3.36.3 from the applications menu & then try to extract the 2nd file hard disk sentinel version 019c it only makes a copy of the .gz file. the earlier version of gnome archive manager which is default / built-in the ubuntu 20.04.2 iso did not have this problem it is only after the update that the gnome archive manager fails to perform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1929304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
I had the same situation, first on ubuntu 20.04 and now still on ubuntu 20.10. I have USB keyboard nad usb mouse. I am using mapping for my USB mouse (btnx-config library) so I can map my button as keyboard keys, I was noticing small freezes but I though it was library problem. But later I wanted to create a simple keylogger from python keyboard library and simple script which always when I press d it also press r in system keyboard. When I did it many times, my computer freeze for few seconds, even minute and this warning occurs in syslog. Is it going to be solve in 21.04? -- 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/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working
❯ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.9-0ubuntu0.20.04.1 Candidato: 3.36.9-0ubuntu0.20.04.1 Tabella versione: *** 3.36.9-0ubuntu0.20.04.1 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages Only one worker is running as expected (after various relogin cycles) ps aux |grep gdm-session-worker root9195 0.0 0.0 312484 9700 ?Sl mag27 0:00 gdm-session-worker [pam/gdm-password] ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915066 Title: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in gnome-shell source package in Groovy: Fix Committed Bug description: [ Test case ] In the user session lockscreen (gdm login screen is fine): - Lock the screen - Hit Enter - Hit Escape - Repeat Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing after unlocked) gdm workers should not be running (a part the one used for logging in). Fingerprint unlocking is particularly hit by this as the service may prevent further authentication to happen until the PAM module times out. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 [ Regression potential ] Authenticating at login screen or at unlock screen stops working after wrong credentials have been used once or the request has been cancelled via escape key. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915066/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915174] Re: Fingerprint enrollment error stops user to be able to enroll again
Confirmed working, errors will be handled properly and will be possible to enroll a new finger afterwards. ❯ apt-cache policy gnome-control-center gnome-control-center: Installato: 1:3.36.5-0ubuntu2 Candidato: 1:3.36.5-0ubuntu2 Tabella versione: *** 1:3.36.5-0ubuntu2 400 400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.5-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:3.36.1-1ubuntu5 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1915174 Title: Fingerprint enrollment error stops user to be able to enroll again Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Bug description: [ Impact ] An error during enrollment prevents other enrollment to happen. [ Test case ] With a real fingerprint device (harder) or with fprintd mock runner: https://gitlab.freedesktop.org/3v1n0/fprintd-mock-runner/ 1. Enroll a finger 2. Cause the enrollment to fail (unplug the device if possible or enroll a previously enrolled finger if the device supports it) 3. Go back 4. Select a finger again and be able to enroll it 5. Enrollment should start [ Regression potential ] Dialog won't allow user to show the fingers enrolled or enroll at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930091] [NEW] Totem (videos) doesn't correctly activate hardware accelleration in gstreamer
Public bug reported: If I play videos (mp4) with totem in Intel graphics (i965) Haswell Chip the hardware acelleration is not completly activated in gstreamer. In intel-gpu-tools (command intel_gpu_top) it shows, that only the Engine "Render/3D" is activated but not the Engine "Videos" and "Blitter" in the driver. So the cpu consumption is markable higher if I play the same video with gstreamer plaver "gst-play-1.0". With gst-play-1.0 the Engine "Video" and "Blitter" is sometimes additional activated to the Engine "Render/3D" and the consumption in Render/3D is reduced in comparison to play the video with totem! It seems the failure lies in: 0:00:00.491871465 19021 0x563257eee100 WARN totem bacon-video-widget.c:2098:bvw_update_tags: Pipeline sent audio tags update with no changes (totem:19021): Gtk-WARNING **: 18:25:27.922: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale) In program "parole" (another video player with gstreamer) the vaapi driver is used correctly In debug-mode for totem for gstreamer there are shown several warning messages in the terminal. terminal messages (with totem): tux@tux-Aspire-V5-573G:~/Videos$ tux@tux-Aspire-V5-573G:~/Videos$ tux@tux-Aspire-V5-573G:~/Videos$ totem --gst-debug-level=1 Test-TS_in_100sec_h264.mp4 (totem:18959): Gtk-WARNING **: 18:23:02.053: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale) tux@tux-Aspire-V5-573G:~/Videos$ tux@tux-Aspire-V5-573G:~/Videos$ tux@tux-Aspire-V5-573G:~/Videos$ totem --gst-debug-level=2 Test-TS_in_100sec_h264.mp4 0:00:00.255306411 19021 0x563257eee100 WARN basesrc gstbasesrc.c:3600:gst_base_src_start_complete: pad not activated yet 0:00:00.255651516 19021 0x563257eee100 WARN basesrc gstbasesrc.c:3600:gst_base_src_start_complete: pad not activated yet 0:00:00.283533162 19021 0x563258fe0360 WARN qtdemux qtdemux_types.c:239:qtdemux_type_get: unknown QuickTime node type tmcd 0:00:00.283570302 19021 0x563258fe0360 WARN qtdemux qtdemux_types.c:239:qtdemux_type_get: unknown QuickTime node type pasp 0:00:00.283593896 19021 0x563258fe0360 WARN qtdemux qtdemux_types.c:239:qtdemux_type_get: unknown QuickTime node type sgpd 0:00:00.283607809 19021 0x563258fe0360 WARN qtdemux qtdemux_types.c:239:qtdemux_type_get: unknown QuickTime node type sbgp 0:00:00.283619727 19021 0x563258fe0360 WARN qtdemux qtdemux_types.c:239:qtdemux_type_get: unknown QuickTime node type nmhd 0:00:00.283630403 19021 0x563258fe0360 WARN qtdemux qtdemux_types.c:239:qtdemux_type_get: unknown QuickTime node type tmcd 0:00:00.283689023 19021 0x563258fe0360 WARN qtdemux qtdemux.c:3237:qtdemux_parse_trex: failed to find fragment defaults for stream 1 0:00:00.283822449 19021 0x563258fe0360 WARN qtdemux qtdemux.c:3237:qtdemux_parse_trex: failed to find fragment defaults for stream 2 0:00:00.283936255 19021 0x563258fe0360 WARN qtdemux qtdemux.c:3237:qtdemux_parse_trex: failed to find fragment defaults for stream 3 0:00:00.491871465 19021 0x563257eee100 WARN totem bacon-video-widget.c:2098:bvw_update_tags: Pipeline sent audio tags update with no changes (totem:19021): Gtk-WARNING **: 18:25:27.922: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale) 0:01:56.879677733 19021 0x7f760c008460 WARN libav gstavauddec.c:628:gst_ffmpegauddec_drain: send packet failed, could not drain decoder 0:01:58.021585797 19021 0x563258489b30 WARN pulse pulsesink.c:702:gst_pulsering_stream_underflow_cb: Got underflow tux@tux-Aspire-V5-573G:~/Videos$ terminal messages with gst.play-1.0: tux@tux-Aspire-V5-573G:~/Videos$ tux@tux-Aspire-V5-573G:~/Videos$ tux@tux-Aspire-V5-573G:~/Videos$ gst-play-1.0 --gst-debug-level=1 Test-TS_in_100sec_h264.mp4 Geben Sie »k« ein, um die Liste der Tastenkombinationen zu sehen. Momentan wird /home/tux/Videos/Test-TS_in_100sec_h264.mp4 wiedergegeben Redistribute latency... Redistribute latency... 0:01:57.5 / 0:01:57.6 Das Ende der Wiedergabeliste wurde erreicht. tux@tux-Aspire-V5-573G:~/Videos$ gst-play-1.0 --gst-debug-level=2 Test-TS_in_100sec_h264.mp4 Geben Sie »k« ein, um die Liste der Tastenkombinationen zu sehen. Momentan wird /home/tux/Videos/Test-TS_in_100sec_h264.mp4 wiedergegeben 0:00:00.029009130 19190 0x5600d5b774f0 WARN basesrc gstbasesrc.c:3600:gst_base_src_start_complete: pad not activated yet 0:00:00.029496474 19190 0x5600d5b774f0 WARN basesrc gstbasesrc.c:3600:gst_base_src_start_complete: pad not activated yet 0:00:00.044690597 19190 0x5600d5b7bb00 WARN qtdemux qtdemux_types.c:239:qtdemux_type_get: unknown QuickTime node type tmcd 0:00:00.044725770
[Desktop-packages] [Bug 1930090] [NEW] Sometimes doubleclick to open folders is not working
Public bug reported: I'm using Ubuntu 20.04 (64 bit, Desktop) and sometimes the doubleclick to open folders is not working correctly. Its not the mouse, cause I use the same mouse on a windows pc and it works without any problems. Its also not the doubleclick speed, I'm very sure about that, even if i can't prove. But I'm using a PC for over 20 years and never got that problem in the past 10 years, only with Ubuntu. So I think there's something wrong, cause its very annyoing if you have to work and go through many different folders and then every 5. - 10. folder that problem occurs. I posted this question in a ubuntu users forum and others said that they have that problem, too. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1930090 Title: Sometimes doubleclick to open folders is not working Status in nautilus package in Ubuntu: New Bug description: I'm using Ubuntu 20.04 (64 bit, Desktop) and sometimes the doubleclick to open folders is not working correctly. Its not the mouse, cause I use the same mouse on a windows pc and it works without any problems. Its also not the doubleclick speed, I'm very sure about that, even if i can't prove. But I'm using a PC for over 20 years and never got that problem in the past 10 years, only with Ubuntu. So I think there's something wrong, cause its very annyoing if you have to work and go through many different folders and then every 5. - 10. folder that problem occurs. I posted this question in a ubuntu users forum and others said that they have that problem, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1930090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928867] Re: System freeze on bulk rename
Thanks, the journal doesn't really include details but it seems a shell issue ** Package changed: nautilus (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1928867 Title: System freeze on bulk rename Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930085] [NEW] Does not detect hotplugged storage device
Public bug reported: when the system boots for first time then it works fine but after several mounting and un mounting it won't work like this only,then again i have to restart the system so it can detect my device. Thank you . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: udisks2 2.9.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.telegram-desktop.rules 70-snap.opera.rules 70-snap.obs-studio.rules 70-snap.gimp.rules 70-snap.discord.rules 70-snap.whatsie.rules 70-snap.zoom-client.rules 70-snap.snap-store.rules 70-snap.snapd.rules 70-snap.vlc.rules 70-snap.spotify.rules 70-snap.guiscrcpy.rules Date: Fri May 28 21:33:06 2021 HotplugNewDevices: /dev/sdb /dev/sdb1 HotplugNewMounts: InstallationDate: Installed on 2021-05-20 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Inspiron 14 5408 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=bf3b5835-4218-4d8f-93f3-c14286792c98 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: Does not detect hotplugged storage device UDisksDump: Error: command ['udisksctl', 'dump'] failed with exit code 1: Error connecting to the udisks daemon: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying UdisksMonitorError: Error connecting to the udisks daemon: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying UdisksMonitorLog: UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.3 dmi.board.name: 0W5NTH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.3:bd08/14/2020:br1.4:svnDellInc.:pnInspiron145408:pvr:rvnDellInc.:rn0W5NTH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5408 dmi.product.sku: 09E8 dmi.sys.vendor: Dell Inc. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1930085 Title: Does not detect hotplugged storage device Status in udisks2 package in Ubuntu: New Bug description: when the system boots for first time then it works fine but after several mounting and un mounting it won't work like this only,then again i have to restart the system so it can detect my device. Thank you . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: udisks2 2.9.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.telegram-desktop.rules 70-snap.opera.rules 70-snap.obs-studio.rules 70-snap.gimp.rules 70-snap.discord.rules 70-snap.whatsie.rules 70-snap.zoom-client.rules 70-snap.snap-store.rules 70-snap.snapd.rules 70-snap.vlc.rules 70-snap.spotify.rules 70-snap.guiscrcpy.rules Date: Fri May 28 21:33:06 2021 HotplugNewDevices: /dev/sdb /dev/sdb1 HotplugNewMounts: InstallationDate: Installed on 2021-05-20 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Inspiron 14 5408 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=bf3b5835-4218-4d8f-93f3-c14286792c98 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: Does not detect hotplugged storage device UDisksDump: Error: command ['udisksctl', 'dump'] failed with exit code 1: Error connecting to the udisks daemon: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying UdisksMonitorError: Error connecting to the udisks daemon: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying UdisksMonitorLog: UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.3 dmi.board.name: 0W5NTH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Well. My installation of Ubuntu 20.04 is one week old + all the updates and it is still happening occasionally. I just did what I did a year ago and I can reproduce the bug again and again. See attachment for a screenshot I did a few minutes ago. ** Attachment added: "Screenshot from 2021-05-28 17-57-22.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5500920/+files/Screenshot%20from%202021-05-28%2017-57-22.png -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926771] Re: [SRU] Hard dependency on desktop-file-utils not declared
** Description changed: + [Impact] + + This bug will cause installation issues once LP #1911432 SRU Process + complete. + + [Test Case] + + * checkout the ubuntu/master branch on wslu GitHub or launchpad repository; + * Run the autopktest with command "autopkgtest path/to/folder -- null" in Ubuntu 20.04 on WSL1 and WSL2. + * View the result of the test, it should be passed with 7 Windows Explorer open and 3 webpage open on the default browser. + + [Regression Potential] + + The potential regressions would be a result of badly generated + ~/.config/wslu/, or a badly merged package. + + [Original Bug Report] + Context: Manual upgrade (via updating sources.list, not do-release-upgrade) of Windows Store version of Ubuntu 20.04 to 20.10 failed. Expected: wslu declares all required dependencies as mandatory dependencies (Depends:). Actual: wslu's post-installation script requires desktop-file-utils, but wslu declares desktop-file-utils as a recommended dependency (Recommends:). Attempting to install wslu 3.2.1-0ubuntu1.1 without desktop-file-utils installed results in the following error: - E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up wslu (3.2.1-0ubuntu1.1) ... /var/lib/dpkg/info/wslu.postinst: 13: desktop-file-install: not found dpkg: error processing package wslu (--configure): - installed wslu package post-installation script subprocess returned error exit status 127 + installed wslu package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of ubuntu-wsl: - ubuntu-wsl depends on wslu; however: - Package wslu is not configured yet. - + ubuntu-wsl depends on wslu; however: + Package wslu is not configured yet. $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy wslu wslu: - Installed: 3.2.1-0ubuntu1.1 - Candidate: 3.2.1-0ubuntu1.1 - Version table: - *** 3.2.1-0ubuntu1.1 500 - 500 https://atl.mirrors.clouvider.net/ubuntu groovy-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 3.2.1-0ubuntu1 500 - 500 https://atl.mirrors.clouvider.net/ubuntu groovy/main amd64 Packages + Installed: 3.2.1-0ubuntu1.1 + Candidate: 3.2.1-0ubuntu1.1 + Version table: + *** 3.2.1-0ubuntu1.1 500 + 500 https://atl.mirrors.clouvider.net/ubuntu groovy-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 3.2.1-0ubuntu1 500 + 500 https://atl.mirrors.clouvider.net/ubuntu groovy/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1926771 Title: [SRU] Hard dependency on desktop-file-utils not declared Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Focal: New Status in wslu source package in Hirsute: New Status in wslu source package in Impish: Fix Released Bug description: [Impact] This bug will cause installation issues once LP #1911432 SRU Process complete. [Test Case] * checkout the ubuntu/master branch on wslu GitHub or launchpad repository; * Run the autopktest with command "autopkgtest path/to/folder -- null" in Ubuntu 20.04 on WSL1 and WSL2. * View the result of the test, it should be passed with 7 Windows Explorer open and 3 webpage open on the default browser. [Regression Potential] The potential regressions would be a result of badly generated ~/.config/wslu/, or a badly merged package. [Original Bug Report] Context: Manual upgrade (via updating sources.list, not do-release-upgrade) of Windows Store version of Ubuntu 20.04 to 20.10 failed. Expected: wslu declares all required dependencies as mandatory dependencies (Depends:). Actual: wslu's post-installation script requires desktop-file-utils, but wslu declares desktop-file-utils as a recommended dependency (Recommends:). Attempting to install wslu 3.2.1-0ubuntu1.1 without desktop-file-utils installed results in the following error: E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up wslu (3.2.1-0ubuntu1.1) ... /var/lib/dpkg/info/wslu.postinst: 13: desktop-file-install: not found dpkg: error processing package wslu (--configure): installed wslu package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of ubuntu-wsl: ubuntu-wsl depends on wslu; however: Package wslu is not configured yet. $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy wslu wslu: Installed: 3.2.1-0ubuntu1.1 Candidate: 3.2.1-0ubuntu1.1 Version table: *** 3.2.1-0ubuntu1.1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.1-0ubuntu1 500 500
[Desktop-packages] [Bug 1926771] Re: Hard dependency on desktop-file-utils not declared
** Also affects: wslu (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Impish) Importance: Undecided Assignee: Patrick Wu (callmepk) Status: Fix Released ** Summary changed: - Hard dependency on desktop-file-utils not declared + [SRU] Hard dependency on desktop-file-utils not declared -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1926771 Title: [SRU] Hard dependency on desktop-file-utils not declared Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Focal: New Status in wslu source package in Hirsute: New Status in wslu source package in Impish: Fix Released Bug description: Context: Manual upgrade (via updating sources.list, not do-release-upgrade) of Windows Store version of Ubuntu 20.04 to 20.10 failed. Expected: wslu declares all required dependencies as mandatory dependencies (Depends:). Actual: wslu's post-installation script requires desktop-file-utils, but wslu declares desktop-file-utils as a recommended dependency (Recommends:). Attempting to install wslu 3.2.1-0ubuntu1.1 without desktop-file-utils installed results in the following error: E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up wslu (3.2.1-0ubuntu1.1) ... /var/lib/dpkg/info/wslu.postinst: 13: desktop-file-install: not found dpkg: error processing package wslu (--configure): installed wslu package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of ubuntu-wsl: ubuntu-wsl depends on wslu; however: Package wslu is not configured yet. $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy wslu wslu: Installed: 3.2.1-0ubuntu1.1 Candidate: 3.2.1-0ubuntu1.1 Version table: *** 3.2.1-0ubuntu1.1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.1-0ubuntu1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1926771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1388491]
(In reply to BogdanB from comment #23) > Roland, please mark this bug as resolved. > I will mark as Verified later, it ok now. Thanks for fixing. Thanks for testing. This bug caused a regression for notes and patterns. I fell in my own trap. In my unit tests, my test sample started in A1, i.e. a special case. I've found the problem and I'll submit a patch after https://gerrit.libreoffice.org/c/core/+/116073/9 is merged. After, this regression is fixed, I'll set bugs 68976, 71058, 142065, 142201 together to RESOLVED FIXED. -- 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/1388491 Title: [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects other cells Status in LibreOffice: In Progress Status in libreoffice package in Ubuntu: Fix Committed Bug description: Step to reproduce: 1. Open the attached ods file. 2. Select I12 to L16 and cut this region (Ctrl+X). (This bug doesn't occur with copy) 3. Select I5 and open Paste Special dialog (Shift+Ctrl+V). 4. Enable "Transpose" option and Click "OK" Then, values of some cells in C9 to E10, which are not related to blank cells are changed: C9: =C3/SUM(C$3:C$6) -> K7/SUM(C$3:C$6) D9: =D3/SUM(D$3:D$6) -> L7/SUM(D$3:D6) E9: =E3/SUM(E$3:E$6) -> M7/SUM(E$3:E$6) C10: =C4/SUM(C$3:C$6) -> K8/SUM(C$3:C$6) D10: =D4/SUM(D$3:D$6) -> L8/SUM(D$3:D6) E10: =E4/SUM(E$3:E$6) -> M8/SUM(E$3:E$6) My environment is Ubuntu 14.04 LibreOffice 4.2.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1388491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923505] Re: thunderbird 78.9.0 FTBFS on ppc64el
Gee, I wonder what's up with ci.d.net; it's basically dead for ppc64el for thunderbird. I'll try to take a look at this on the Debian side when I have some time. -- 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/1923505 Title: thunderbird 78.9.0 FTBFS on ppc64el Status in thunderbird package in Ubuntu: Triaged Bug description: The build hangs forever when compiling the webrender rust crate (see https://launchpad.net/ubuntu/+source/thunderbird/1:78.9.0+build2-0ubuntu3/+build/21368163). I'm attaching the full build log for future reference. This happens when building with rustc 1.50.0+dfsg1+llvm-0ubuntu4 and 1.50.0+dfsg1+llvm-0ubuntu5 (the latter is the version currently in the hirsute release pocket). The build completes when building with rustc 1.50.0+dfsg1+llvm-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1923505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929999] [NEW] [SRU] libreoffice 6.4.7.2.M1 for Focal
Public bug reported: [Impact] * LibreOffice 6.4.7.2.M1 is a bug-fix release of the 6.4 line: It receives important bug-fixes on top of the 6.4 branch which is EOL since November 30, 2020. Currently maintained by Andras Timar for France's MIMO (https://blog.documentfoundation.org/blog/2013/06/17/the-document-foundation-welcomes-frances-mimo-in-the-advisory-board/) * Version 6.4.7 is currently released in focal. https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-6-4 (that's a total of ?? bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/12419370/+listing-archive-extra * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ?? bug fixes always carries the potential for introducing regressions, even though it is a bug-fix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: Undecided Assignee: Rico Tzschichholz (ricotz) Status: New ** Affects: libreoffice (Ubuntu Focal) Importance: Undecided Assignee: Rico Tzschichholz (ricotz) Status: New ** Also affects: libreoffice (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu Focal) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/192 Title: [SRU] libreoffice 6.4.7.2.M1 for Focal Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Focal: New Bug description: [Impact] * LibreOffice 6.4.7.2.M1 is a bug-fix release of the 6.4 line: It receives important bug-fixes on top of the 6.4 branch which is EOL since November 30, 2020. Currently maintained by Andras Timar for France's MIMO (https://blog.documentfoundation.org/blog/2013/06/17/the-document-foundation-welcomes-frances-mimo-in-the-advisory-board/) * Version 6.4.7 is currently released in focal. https://cgit.freedesktop.org/libreoffice/core/log/?h=distro/mimo/mimo-6-4 (that's a total of ?? bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/12419370/+listing-archive-extra * [amd64] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ?? bug fixes always carries the potential for introducing regressions, even though it is a bug-fix- only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829665] Re: Network Manager and upower not starting, libhogweed error
Thank you for your bug report, is that still an issue in newer versions? ** Changed in: nettle (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1829665 Title: Network Manager and upower not starting, libhogweed error Status in nettle package in Ubuntu: Incomplete Bug description: After updating Lubuntu 18.10 to 19.04, NetworkManager and upower no longer start. After a bit of digging it shows the source to be libhogweed4 v3.4.1-1. The error is: relocation error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: symbol nettle_rsa_sec_decrypt version HOGWEED_4 not defined in file libhogweed.so.4 with link time reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1829665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925775] Re: SRU the current 3.36.1 stable update
Using 3.36.1-0ubuntu1 the account are working as expected ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1925775 Title: SRU the current 3.36.1 stable update Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some API documentation fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try adding online account in a GNOME session, ensure the service is correctly enabled in application, for example that a google accounts are picked up in gnome-calendar and evolution. * Regression potential The changes are in API documentation so nothing specific to check, if there is an issue it would be from a toolchain regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923505] Re: thunderbird 78.9.0 FTBFS on ppc64el
According to https://buildd.debian.org/status/logs.php?pkg=thunderbird=ppc64el=sid, Debian is not affected by the same build failure. -- 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/1923505 Title: thunderbird 78.9.0 FTBFS on ppc64el Status in thunderbird package in Ubuntu: Triaged Bug description: The build hangs forever when compiling the webrender rust crate (see https://launchpad.net/ubuntu/+source/thunderbird/1:78.9.0+build2-0ubuntu3/+build/21368163). I'm attaching the full build log for future reference. This happens when building with rustc 1.50.0+dfsg1+llvm-0ubuntu4 and 1.50.0+dfsg1+llvm-0ubuntu5 (the latter is the version currently in the hirsute release pocket). The build completes when building with rustc 1.50.0+dfsg1+llvm-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1923505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922729] Re: SRU the current 3.36.2 stable update
Sorry the description of the testing done in the previous comment was entered in the wrong tab. The 3.36.2-0ubuntu1 update works as expected, yelp is able to browse the ubuntu user documentation, including playing videos. Trying to open and browse the documentation in a few applications (eog, evince, file- roller) also works without issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1922729 Title: SRU the current 3.36.2 stable update Status in yelp package in Ubuntu: Fix Released Status in yelp source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some translation updates and bugfixes https://gitlab.gnome.org/GNOME/yelp/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that browsing documentation from different GNOME softwares still work correctly, including the desktop user guide * Regression potential The update has changes around the handling of local document, make sure to test those and try editing to see that the browser is handling it correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1922729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925795] Re: SRU the current 0.20.4 stable update
The 0.20.4-0ubuntu1 update works as expected, accessing the keyring is working. Trying to open a protected pdf in evince the password is correctly stored and re-used after trying to open the document again. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1925795 Title: SRU the current 0.20.4 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922729] Re: SRU the current 3.36.2 stable update
The 3.36.2-0ubuntu1 update works as expected, accessing the keyring is working. Trying to open a protected pdf in evince the password is correctly stored and re-used after trying to open the document again. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1922729 Title: SRU the current 3.36.2 stable update Status in yelp package in Ubuntu: Fix Released Status in yelp source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some translation updates and bugfixes https://gitlab.gnome.org/GNOME/yelp/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that browsing documentation from different GNOME softwares still work correctly, including the desktop user guide * Regression potential The update has changes around the handling of local document, make sure to test those and try editing to see that the browser is handling it correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1922729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926843] Re: online accounts integration with fb isn't working
Confirmed that using 3.38.1-1ubuntu1.1 facebook isn't listed, other provides are still available and keep working ** Tags removed: verification-needed verification-needed-focal verification-needed-hirsute ** Tags added: verification-done verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Committed Status in gnome-online-accounts source package in Hirsute: Fix Committed Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
The focal SRU has been reuploaded merging the fixes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
Oh, I see now that you comment on the other bug, already I will merge the changes ** Changed in: pulseaudio (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: pulseaudio (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
So what are the next steps then @osomon? Thanks! -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt
Closing since it's an old issue with no report in 8 years also not likely Mathieu is still working on it at this point ** Changed in: network-manager (Ubuntu) Status: Triaged => 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/1197712 Title: 0.9.8.0-0ubuntu13 is causing conf prompt Status in network-manager package in Ubuntu: Invalid Bug description: Got a conf promt. not sure why =) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929598] Re: Firefox rfuses to start YouTube display
** Changed in: firefox (Ubuntu) Status: Incomplete => New -- 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/1929598 Title: Firefox rfuses to start YouTube display Status in firefox package in Ubuntu: New Bug description: Firefox starts to build the buffer, but is does not display anything. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 88.0.1+build1-0ubuntu0.21.04.2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bertadmin 4040 F pulseaudio /dev/snd/pcmC1D0p: bertadmin 4040 F...m pulseaudio /dev/snd/controlC0: bertadmin 4040 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue May 25 14:25:12 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2019-11-30 (542 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev enp7s0 proto dhcp metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 192.168.1.0/24 dev enp7s0 proto kernel scope link src 192.168.1.106 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=88.0.1/20210504152106 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-03-24 (61 days ago) dmi.bios.date: 07/18/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.10 dmi.board.name: B450M-HDV R4.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.:bvrP3.10:bd07/18/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1929598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
Thanks for the work, there is already a SRU in the queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=pulseaudio Do you want to include your changes and do another upload since it hasn't been accepted yet or should we wait for the other SRU to clear out first? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Merge proposal linked: https://code.launchpad.net/~os369510/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/403448 -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
@Timo, I guess you could get passed if adding "--oomable" ** Also affects: plainbox-provider-checkbox Importance: Undecided Status: New -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
** Tags removed: verification-needed -- 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/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Committed Status in jsunit source package in Bionic: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
I was able to reproduce it on my RKL, but the reason was bad RAM. After swapping it to another otherwise identical set, it works fine. The reproducer here was running 'stress-ng --stack 0' -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929224] Re: Scanning issue with Ubuntu 18.04 and HPLIP version 3.21.2
Update: I have done some more test. The issue occurs also with resolution 600 (not only 1200 as stated earlier). The issue is related to resolution/width/height scanimage --mode color --format jpeg --resolution 600 -x 128 -y 87 -> Application transferred too few lines -x 128 -y 88 -> OK -x 129 -y 88 -> OK -x 129 -y 89 -> OK -x 130 -y 89 -> OK -x 130 -y 90 -> Application transferred too few lines scanimage --mode color --format jpeg --resolution 1200 -x 128 -y 87 -> Application transferred too few lines -x 128 -y 88 -> Application transferred too few lines -x 129 -y 88 -> Application transferred too few lines -x 129 -y 89 -> OK -x 130 -y 89 -> OK -x 130 -y 90 -> Application transferred too few lines -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1929224 Title: Scanning issue with Ubuntu 18.04 and HPLIP version 3.21.2 Status in hplip package in Ubuntu: New Bug description: Hello HPLIP team, Since some days I have an HP Smart Tank Plus 555 printer connected to Ubuntu 18.04 with HPLIP installed. Everything works fine so far, but I have an issue with scanning. The images are not scanned correctly with highest resolution 1200 dpi (lower resolutions are working fine) My system configuration is Ubuntu 18.04 with most recent updates HPLIP version 3.21.2, scan utility version 2.2 HP Smart Tank Plus 555 firmware version POSPPWPP1N001.2051B.00 The HP printer/scanner is connected via USB I scan the image with: scanimage --mode color --resolution 1200 --format jpeg -l 0 -t 0 -x 88 -y 129 > image.jpeg scanimage terminates with the error message „Application transfered too few scanlines“ The scanned image has indeed missing pixels at the end of the file/image. The issue occures only with 1200 dpi, not with 600 dpi or 300 dpi. Since I hade no issue in the past with my former HP printer/scanner or lower resolutions I believe this issue is very likely related to HPLIP and/or the HP Smart Tank Plus 555 device. Would be great if one of the developers could take care of this issue and hopefully provide a bug fix. Best regards, Helmut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1929224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
``` Mar 3 18:07:02 kernel: [ 4935.420223] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:07:16 kernel: [ 4949.440656] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:08:11 kernel: [ 5004.462545] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:09:14 kernel: [ 5066.643244] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:09:34 kernel: [ 5087.214632] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:26 kernel: [10538.987863] gnome-terminal- invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:28 kernel: [10541.043501] gnome-terminal- invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:45 kernel: [10558.082088] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:49 kernel: [10562.058290] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:14 kernel: [10586.699020] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:35 kernel: [10608.175575] gnome-shell invoked oom-killer: gfp_mask=0x0(), order=0, oom_score_adj=0 Mar 3 19:41:55 kernel: [10627.942562] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:55 kernel: [10628.294303] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:42:12 kernel: [10645.292252] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:42:43 kernel: [10675.670335] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:06 gnome-shell[1691]: GNOME Shell crashed with signal 6 Mar 3 19:43:15 kernel: [10708.155220] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:31 kernel: [10724.420148] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:32 kernel: [10725.336522] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:36 kernel: [10729.101114] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:44 kernel: [10737.358855] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:44:09 kernel: [10761.733283] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:44:31 kernel: [10783.687545] pool-gnome-shel invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:45:23 /usr/lib/gdm3/gdm-x-session[1425]: (EE) Caught signal 6 (Aborted). Server aborting ``` Does not make sense to me, I don't think it's DM/WM issue but tool issue. -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
[Desktop-packages] [Bug 1929915] [NEW] "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt-sudo'")
Public bug reported: Release: Kubuntu Groovy (also affects focal, hirsute) SW, version: software-properties-qt, 0.99.3.1 (for groovy but also affects version on focal) How to reproduce: 1) Launch Discover. 2) Search for (or scroll to) 'software sources', select the 'Software Sources' from the search result. 3) Click on 'Launch'. Expected: The application launches, possibly asking for admin password. Actual: Does not launch (on groovy). On focal, launches with error (Snapshot attached). However, if we try to access software sources from 'Settings', it launches properly. When launched from terminal, it was seen that discover was trying to use `lxqt-sudo` and failing since it was not installed. Error message as below. `kf.kio.gui: "Could not find the program 'lxqt-sudo'"` Whereas when we access 'Software Sources' from 'Settings', it is using `kdesu`. Message as below. `org.kde.kdesu: Daemon not safe (not sgid), not using it.`. Inspite of 'Daemon not safe...' error, the software sources launches and able to make changes. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-qt 0.99.3.1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 28 11:41:34 2021 InstallationDate: Installed on 2021-05-28 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal groovy hirsute impish ** Tags added: focal hirsute impish ** Summary changed: - "Software Sources" fails to launch from Discover when trying lauch from applicatins list (kf.kio.gui: "Could not find the program 'lxqt-sudo'") + "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt-sudo'") -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1929915 Title: "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt- sudo'") Status in software-properties package in Ubuntu: New Bug description: Release: Kubuntu Groovy (also affects focal, hirsute) SW, version: software-properties-qt, 0.99.3.1 (for groovy but also affects version on focal) How to reproduce: 1) Launch Discover. 2) Search for (or scroll to) 'software sources', select the 'Software Sources' from the search result. 3) Click on 'Launch'. Expected: The application launches, possibly asking for admin password. Actual: Does not launch (on groovy). On focal, launches with error (Snapshot attached). However, if we try to access software sources from 'Settings', it launches properly. When launched from terminal, it was seen that discover was trying to use `lxqt-sudo` and failing since it was not installed. Error message as below. `kf.kio.gui: "Could not find the program 'lxqt-sudo'"` Whereas when we access 'Software Sources' from 'Settings', it is using `kdesu`. Message as below. `org.kde.kdesu: Daemon not safe (not sgid), not using it.`. Inspite of 'Daemon not safe...' error, the software sources launches and able to make changes. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-qt 0.99.3.1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 28 11:41:34 2021 InstallationDate: Installed on 2021-05-28 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1929915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928867] Re: System freeze on bulk rename
Screenshot just before reproducing the bug also attached. ** Attachment added: "Screenshot from 2021-05-28 08-53-00.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1928867/+attachment/5500829/+files/Screenshot%20from%202021-05-28%2008-53-00.png -- 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/1928867 Title: System freeze on bulk rename Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1928867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928867] Re: System freeze on bulk rename
journalctl log from past one hour attached. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1928867/+attachment/5500828/+files/journalctl.log -- 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/1928867 Title: System freeze on bulk rename Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1928867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
