[Desktop-packages] [Bug 1313914] Re: Rhythmbox zeitgeist plugin doesn't activate when selected in Rhythmbox plugin preferences
Zeitgeist plugin has already been merged upstream in https://gitlab.gnome.org/GNOME/rhythmbox/merge_requests/18 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1313914 Title: Rhythmbox zeitgeist plugin doesn't activate when selected in Rhythmbox plugin preferences Status in Rhythmbox: Fix Released Status in rhythmbox package in Ubuntu: Triaged Bug description: When I open the Rhythmbox plugin's preferences dialog, and I click on the check-box for the zeitgeist plugin, an error icon is displayed instead of the regular check-box mark. Attached to this bug report there is a screenshot of the plugins dialog with the error for the zeitgeist plugin. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox-plugin-zeitgeist 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 28 22:40:36 2014 InstallationDate: Installed on 2014-04-23 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1313914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 917757] Re: cheese crashed with SIGSEGV in cheese_camera_set_device_by_dev_uuid()
** Changed in: cheese (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/917757 Title: cheese crashed with SIGSEGV in cheese_camera_set_device_by_dev_uuid() Status in Cheese: Fix Released Status in cheese package in Ubuntu: Fix Released Status in cheese package in Debian: Fix Released Bug description: cheese crashed after while start ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: cheese 3.3.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-9.16-generic-pae 3.2.1 Uname: Linux 3.2.0-9-generic-pae i686 ApportVersion: 1.90-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Tue Jan 17 18:04:06 2012 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120116) MachineType: Intel Corporation Calistoga & ICH7M Chipset ProcCmdline: cheese ProcEnviron: PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.3.3-0ubuntu2 cheese-common 3.3.3-0ubuntu2 SegvAnalysis: Segfault happened at: 0xb6c142cb:cmp%cl,(%edx) PC (0xb6c142cb) ok source "%cl" ok destination "(%edx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 cheese_camera_setup () from /usr/lib/i386-linux-gnu/libcheese.so.3 cheese_main_window_setup_camera () cheese_main_on_app_activate () g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: cheese crashed with SIGSEGV in cheese_camera_setup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/27/08 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: NAPA0001.86C.0059.D.0812271024 dmi.board.name: CAPELL VALLEY(NAPA) CRB dmi.board.vendor: Intel Corporation dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrNAPA0001.86C.0059.D.0812271024:bd12/27/08:svnIntelCorporation:pnCalistoga:pvrNotApplicable:rvnIntelCorporation:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Calistoga & ICH7M Chipset dmi.product.version: Not Applicable dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/917757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854147] Re: Xorg repeatedly crashes with SIGABRT
Thanks, that is the right log and it shows: dec 20 03:37:32 RooTBoX whoopsie[3823]: [03:37:32] Parsing /var/crash/_usr_lib_xorg_Xorg.1000.crash. dec 20 03:37:32 RooTBoX whoopsie[3823]: [03:37:32] Uploading /var/crash/_usr_lib_xorg_Xorg.1000.crash. But no other info about the crash. Maybe the crash was from the boot before that, so please also try: journalctl -b-2 > prevprevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854147 Title: Xorg repeatedly crashes with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 Several xorg crashes, unsure what have caused them https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46 https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1 https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:21:11 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01] InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857014] Re: Unable to paste files from Nautilus to the desktop
Pasting to the desktop also works for me in 19.10. Are you trying to paste a file with unusual permissions? ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1857014 Title: Unable to paste files from Nautilus to the desktop Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) Files app 1:3.34.1-1ubuntu1 3) Open Files app. Copy file. Right click on Desktop. Select paste. 4) Unable to paste the file to the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854147] Re: Xorg repeatedly crashes with SIGABRT
journal logs attached not sure about Xwayland, want me to test some time in wayland if i can reproduce? ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+attachment/5314234/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854147 Title: Xorg repeatedly crashes with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 Several xorg crashes, unsure what have caused them https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46 https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1 https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:21:11 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01] InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854147] Re: Xorg repeatedly crashes with SIGABRT
Next time (and every time) after a crash happens, on the very next boot please run: journalctl -b-1 > prevboot.txt and then send us the file 'prevboot.txt'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854147 Title: Xorg repeatedly crashes with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 Several xorg crashes, unsure what have caused them https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46 https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1 https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:21:11 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01] InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854147] Re: Xorg repeatedly crashes with SIGABRT
I also wonder why the 'Xorg' binary is crashing in the same session as 'Xwayland' problems being logged. Those two should never occur in the same session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854147 Title: Xorg repeatedly crashes with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 Several xorg crashes, unsure what have caused them https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46 https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1 https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:21:11 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01] InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854147] Re: Xorg repeatedly crashes with SIGABRT
Thanks again. Unfortunately it seems something strange is happening with your Xorg crashes and none are retraceable, all saying: "This problem failed to retrace because there was no crash signature after retracing." The only extra information we have from those crashes is: dec 04 20:24:34 pluto gnome-shell[21047]: Connection to xwayland lost which suggests it is Xwayland crashing. That reminds me, I think/wonder if upstream disabled Xwayland crash dumps in this version ** Summary changed: - Several xorg crashes + Xorg repeatedly crashes with SIGABRT -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854147 Title: Xorg repeatedly crashes with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 Several xorg crashes, unsure what have caused them https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46 https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1 https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:21:11 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01] InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854147] Re: Several xorg crashes
https://errors.ubuntu.com/user/cb36c5de1ffb50ae482d3229f8a2f70e727b96e656d23cc6d5028382d6e0be0a0d5d0534c9c092db38d15d6e49120078257f2f7842d480f0bb7db5d20caa84db -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854147 Title: Several xorg crashes Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 Several xorg crashes, unsure what have caused them https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46 https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1 https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:21:11 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01] InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854147] Re: Several xorg crashes
Thanks but that log does not show a crash. Please try following these instructions for your latest .crash files: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854147 Title: Several xorg crashes Status in xorg-server package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 Several xorg crashes, unsure what have caused them https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46 https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1 https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:21:11 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01] InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853835] Re: [snap] keepassxc browser integration does not work with chromium installed as a snap
*** This bug is a duplicate of bug 1741074 *** https://bugs.launchpad.net/bugs/1741074 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1853835 Title: [snap] keepassxc browser integration does not work with chromium installed as a snap Status in chromium-browser package in Ubuntu: Confirmed Bug description: After migrating to snap version of chromium in Ubuntu 19.10, I can no longer use KeePassXC-Browser extension: https://chrome.google.com/webstore/detail/keepassxc- browser/oboonakemofpalcgghocfoadofidjkkk Problem is described here: https://github.com/keepassxreboot /keepassxc-browser/issues/405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854147] Re: Several xorg crashes
Yes i have currently 3 xorg crashes and 1 gnome-shell one in /var/crash attached xorg.log ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+attachment/5314183/+files/Xorg.0.log ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854147 Title: Several xorg crashes Status in xorg-server package in Ubuntu: New Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 Several xorg crashes, unsure what have caused them https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46 https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1 https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:21:11 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01] InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313914] Re: Rhythmbox zeitgeist plugin doesn't activate when selected in Rhythmbox plugin preferences
** Changed in: rhythmbox Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1313914 Title: Rhythmbox zeitgeist plugin doesn't activate when selected in Rhythmbox plugin preferences Status in Rhythmbox: Fix Released Status in rhythmbox package in Ubuntu: Triaged Bug description: When I open the Rhythmbox plugin's preferences dialog, and I click on the check-box for the zeitgeist plugin, an error icon is displayed instead of the regular check-box mark. Attached to this bug report there is a screenshot of the plugins dialog with the error for the zeitgeist plugin. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox-plugin-zeitgeist 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 28 22:40:36 2014 InstallationDate: Installed on 2014-04-23 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1313914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857014] Re: Unable to paste files from Nautilus to the desktop
Curious. It works in Ubuntu 20.04. ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1857014 Title: Unable to paste files from Nautilus to the desktop Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Files app 1:3.34.1-1ubuntu1 3) Open Files app. Copy file. Right click on Desktop. Select paste. 4) Unable to paste the file to the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857037] Re: Update to 3.34.2 and SRU it
** Tags added: 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/1857037 Title: Update to 3.34.2 and SRU it Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: Confirmed Bug description: [ Description ] The second stable release in the 3.34 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Most of commits were already included in stable ubuntu release, as per git snapshot. However we've still various fixes in handling windows workspaces and focus, so ensure that there are no focus issues, especially with Java apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857037] Re: Update to 3.34.2 and SRU it
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: yaru-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857037 Title: Update to 3.34.2 and SRU it Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: Confirmed Bug description: [ Description ] The second stable release in the 3.34 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Most of commits were already included in stable ubuntu release, as per git snapshot. However we've still various fixes in handling windows workspaces and focus, so ensure that there are no focus issues, especially with Java apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Ariel, This bug is more about the screen not working. Please open a new bug for your laptop by running: ubuntu-bug libinput -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and screen - all in one) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Oct 1 00:53:26 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.0.0-29-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1021] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:180e] InstallationDate: Installed on 2019-09-27 (3 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GDX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Ariel, This bug is more about the screen not working. Please open a new bug for you laptop by running: ubuntu-bug libinput -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and screen - all in one) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Oct 1 00:53:26 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.0.0-29-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1021] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:180e] InstallationDate: Installed on 2019-09-27 (3 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GDX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857054] Re: after running several months the screen flickering starts
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- 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/1857054 Title: after running several months the screen flickering starts Status in Ubuntu: Won't Fix Bug description: after running several months the screen flickering starts. after uploading ubuntu freshly it runs for several months wihtout a problem, and the story starts again now observed in the last 3-4 years with ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 19 21:34:48 2019 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2019-03-17 (277 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=4285b974-ec80-403b-8d25-9e551a82132f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/11/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 19 19:10:28 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1857054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857055] Re: after running several months the screen flickering starts
*** This bug is a duplicate of bug 1857054 *** https://bugs.launchpad.net/bugs/1857054 ** This bug has been marked a duplicate of bug 1857054 after running several months the screen flickering starts -- 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/1857055 Title: after running several months the screen flickering starts Status in xorg package in Ubuntu: New Bug description: after running several months the screen flickering starts. after uploading ubuntu freshly it runs for several months wihtout a problem, and the story starts again now observed in the last 3-4 years with ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 19 21:34:48 2019 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2019-03-17 (277 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=4285b974-ec80-403b-8d25-9e551a82132f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/11/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 19 19:10:28 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1857055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
Tim, your issue in comment 26 is confusing to me. It looks like it's
caused by my patch in comment 6?
Specifically, it looks like subprocess.Popen returns a unicode string as
stdout for you. I can't reproduce locally, in either python2.7 or
python3.7:
>>> import subprocess
>>> subprocess.Popen([u'ls'],
>>> stdout=subprocess.PIPE).communicate()[0].decode('utf8')
The documentation for Popen says:
"If encoding or errors are specified, or text is true, the file objects stdin,
stdout and stderr are opened in text mode with the specified encoding and
errors, as described above in Frequently Used Arguments. The universal_newlines
argument is equivalent to text and is provided for backwards compatibility. By
default, file objects are opened in binary mode."
None of the arguments that would cause Popen to return a unicode string
seem to be passed to it by duplicity...?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1855736
Title:
Duplicity fails to start
Status in Duplicity:
Fix Committed
Status in duplicity package in Ubuntu:
Fix Committed
Bug description:
I am on 19.10. Duplicity crashes as soon as I try to start a backup,
as below. It was running fine on 19.04.
Traceback (innermost last):
File "/usr/bin/duplicity", line 107, in
with_tempdir(main)
File "/usr/bin/duplicity", line 93, in with_tempdir
fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in
main
action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200,
in ProcessCommandLine
globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in
get_backend
obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in
get_backend_object
return factory(pu)
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py",
line 81, in __init__
ensure_dbus()
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py",
line 37, in ensure_dbus
lines = output.split(u'\n')
TypeError: a bytes-like object is required, not 'str'
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()
** Changed in: grilo-plugins Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1856927 Title: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() Status in Grilo Plugins: Fix Released Status in grilo-plugins package in Ubuntu: Fix Committed Status in totem package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034 --- Test case: Fresh 20.04 install, updated Open totem What happens: segfault Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 19:51:40 2019 ExecutablePath: /usr/bin/totem ExecutableTimestamp: 1570435741 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcCmdline: /usr/bin/totem --gapplication-service ProcCwd: /home/doug ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax PC (0x7f76b92f6dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0 Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/grilo-plugins/+bug/1856927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856795] Re: X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5
Thanks. I can also confirm this bug running X2Go on Ubuntu 18.04 (Client / Remote). Appears to have been described also here: https://lists.x2go.org/pipermail/x2go-dev/2019-December/013260.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1856795 Title: X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5 Status in libssh package in Ubuntu: Confirmed Bug description: The recent CVE fix broke SCP support in libssh, which X2Go Client (x2goclient) relies on. Sessions now fail with error messages such as "SCP: Warning: status code 1 received: scp: ~username/.x2go/ssh: No such file or directory\n". (Also note the literal "\n" there, but I guess we don't really need to care about that.) The previous version worked fine and rolling the libssh4 package back fixes this issue, but also leaves users vulnerable to the fixed security issue in its scp implementation. I've been looking at the debdiff, but spotting the actual changes is very difficult due to the reformatting that was done at the same time. This degraded the patch(es) into one big blob. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838008] Re: [snap] cursor theme isn't respected
The KDE theme isn't supported because gtk-common-themes doesn't include the default KDE cursor theme. This MR fixes that: https://gitlab.gnome.org/Community/Ubuntu/gtk-common- themes/merge_requests/17 -- 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/1838008 Title: [snap] cursor theme isn't respected Status in chromium-browser package in Ubuntu: Confirmed Bug description: (initially reported at https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/85) When changing the cursor theme with gnome-tweaks, I can observe that some themes aren't respected in the chromium snap. This appears to be specific to chromium, other snaps like evince or gimp use the correct cursors. Yaru and Adwaita are fine, but Redglass or Whiteglass aren't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857054] [NEW] after running several months the screen flickering starts
Public bug reported: after running several months the screen flickering starts. after uploading ubuntu freshly it runs for several months wihtout a problem, and the story starts again now observed in the last 3-4 years with ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 19 21:34:48 2019 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2019-03-17 (277 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=4285b974-ec80-403b-8d25-9e551a82132f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/11/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 19 19:10:28 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1857054 Title: after running several months the screen flickering starts Status in xorg package in Ubuntu: New Bug description: after running several months the screen flickering starts. after uploading ubuntu freshly it runs for several months wihtout a problem, and the story starts again now observed in the last 3-4 years with ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 19 21:34:48 2019 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2019-03-17 (277 days ago) InstallationMedia: Ubuntu
[Desktop-packages] [Bug 1857055] [NEW] after running several months the screen flickering starts
Public bug reported: after running several months the screen flickering starts. after uploading ubuntu freshly it runs for several months wihtout a problem, and the story starts again now observed in the last 3-4 years with ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 19 21:34:48 2019 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2019-03-17 (277 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=4285b974-ec80-403b-8d25-9e551a82132f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/11/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 19 19:10:28 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1857055 Title: after running several months the screen flickering starts Status in xorg package in Ubuntu: New Bug description: after running several months the screen flickering starts. after uploading ubuntu freshly it runs for several months wihtout a problem, and the story starts again now observed in the last 3-4 years with ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 19 21:34:48 2019 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2019-03-17 (277 days ago) InstallationMedia: Ubuntu
[Desktop-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Hello, I've not been able to run the 5.5rc kernels. I downloaded modules / image / headers for the generic version and installed with dpkg -i each. The kernel appears in grub boot menu but does not succeed booting. I reverted to 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux regards -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend
Happens with the Dell XPS 9570 (Intel-Nvidia) as well on a fresh install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1853709 Title: lightdm does not greet or present login prompt when resuming from laptop suspend Status in lightdm package in Ubuntu: Confirmed Bug description: Expected result: when opening laptop lid the lock screen presents itself so I can unlock my session Actual result: the contents of my desktop are visible (windows, etc) and I can move my mouse cursor around but I cannot interact with the desktop session at all. Hovering over UI elements or clicking them has no effect. In order to get the login prompt I have to ctrl+alt+f1, login at the console, and run sudo systemctl restart lightdm, then I can login normally and resume whatever I was doing from before I closed the laptop lid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 23 09:08:32 2019 InstallationDate: Installed on 2019-11-09 (14 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848616] Re: LightDM crashes and logs me out when resuming from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1848616 Title: LightDM crashes and logs me out when resuming from suspend Status in lightdm package in Ubuntu: Confirmed Bug description: I close the laptop lid and let it suspend. On resume, the whole desktop is frozen for a while. Nothing works during this time, no CAPS LOCK indicator LED, neither TTY switching. Then the screen goes dark and I see the LightDM login screen. I was logged out. This is a regression, since it wasn't reproducible on Ubuntu 19.04. How reproducible? 100% of the time. I am not totally sure it was LightDM's fault. It is my best guess based on the behavior I witnessed. See logs. Potentially relevant specs: - Intel HD Graphics 400 (Braswell) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 17 21:52:19 2019 InstallationDate: Installed on 2019-10-17 (0 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1848616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1853709 Title: lightdm does not greet or present login prompt when resuming from laptop suspend Status in lightdm package in Ubuntu: Confirmed Bug description: Expected result: when opening laptop lid the lock screen presents itself so I can unlock my session Actual result: the contents of my desktop are visible (windows, etc) and I can move my mouse cursor around but I cannot interact with the desktop session at all. Hovering over UI elements or clicking them has no effect. In order to get the login prompt I have to ctrl+alt+f1, login at the console, and run sudo systemctl restart lightdm, then I can login normally and resume whatever I was doing from before I closed the laptop lid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 23 09:08:32 2019 InstallationDate: Installed on 2019-11-09 (14 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857027] Re: Bytes are not correctly converted to GygaBytes
Oh interesting!. Always thought it should have been this way, but I thought it wasn't standard. Thanks! -- 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/1857027 Title: Bytes are not correctly converted to GygaBytes Status in nautilus package in Ubuntu: Invalid Bug description: 6,230,444,800 bytes, are converted to 6.2GB, instead of 5.80GB This happens in the *folder view* and in the properties of the file ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 19 11:12:55 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-01-31 (321 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1857027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857038] Re: package gnome-control-center-shared-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in pac
Thank you for your bug report. The version listed suggested you tried to upgrade from trusty to bionic which isn't an official upgrade path, you need to upgrade through xenial first, closing that's not something Ubuntu is providing ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1857038 Title: package gnome-control-center-shared-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome- control-center-faces 1:3.28.2-0ubuntu0.18.04.2 Status in gnome-control-center package in Ubuntu: Invalid Bug description: I am trying to run gnome-control-center but keep getting an error stating 'Execution of "gnome-control-center" failed: Command not found.' I get this error after I click on the printer icon then click on "Printers". When I try to install "gnome-control-center" I get these: gnome-control-center : Depends: libcheese-gtk25 (>= 3.18.0) but it is not going to be installed Depends: libcheese8 (>= 3.18.0) but it is not going to be installed When I try to install these packages, this happens: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed As a result, I am unable to open gnome-control-center and therefore cannot install my Canon MX922 printer. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-control-center-shared-data (not installed) ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: gnome-control-center-shared-data:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Dec 19 10:37:14 2019 DpkgTerminalLog: Preparing to unpack .../gnome-control-center-shared-data_1%3a3.6.3-0ubuntu56.1_all.deb ... Unpacking gnome-control-center-shared-data (1:3.6.3-0ubuntu56.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/gnome-control-center-shared-data_1%3a3.6.3-0ubuntu56.1_all.deb (--unpack): trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.2 ErrorMessage: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.2 InstallationDate: Installed on 2018-08-31 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: gnome-control-center Title: package gnome-control-center-shared-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.2 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/1857038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853112] Re: Applications are closed when killing the Shell (like on a hang)
** Changed in: gnome-shell (Ubuntu Focal) Status: Triaged => In Progress -- 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/1853112 Title: Applications are closed when killing the Shell (like on a hang) Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Eoan: In Progress Status in gnome-shell source package in Focal: In Progress Bug description: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797820] Re: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamo
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1797820 Title: Xorg/Xwayland crashed with SIGSEGV in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_composite_clipped_region Status in xorg-server package in Ubuntu: Confirmed Bug description: Xwayland: https://errors.ubuntu.com/problem/f8ea9bb558676edbe2acec52b0f386ab1321fdaf Xorg: https://errors.ubuntu.com/problem/90ab0b3de538bdc1058e1af52156d870e04dd56e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1797820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853112] Re: Applications are closed when killing the Shell (like on a hang)
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/371252 -- 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/1853112 Title: Applications are closed when killing the Shell (like on a hang) Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Eoan: In Progress Status in gnome-shell source package in Focal: In Progress Bug description: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857037] Re: Update to 3.34.2 and SRU it
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/371252 -- 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/1857037 Title: Update to 3.34.2 and SRU it Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: New Bug description: [ Description ] The second stable release in the 3.34 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Most of commits were already included in stable ubuntu release, as per git snapshot. However we've still various fixes in handling windows workspaces and focus, so ensure that there are no focus issues, especially with Java apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853112] Re: Applications are closed when killing the Shell (like on a hang)
** Also affects: gnome-shell (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Eoan) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Eoan) Importance: Medium => High -- 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/1853112 Title: Applications are closed when killing the Shell (like on a hang) Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Eoan: In Progress Status in gnome-shell source package in Focal: Triaged Bug description: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857037] Re: Update to 3.34.2 and SRU it
** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: 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/1857037 Title: Update to 3.34.2 and SRU it Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: New Bug description: [ Description ] The second stable release in the 3.34 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Most of commits were already included in stable ubuntu release, as per git snapshot. However we've still various fixes in handling windows workspaces and focus, so ensure that there are no focus issues, especially with Java apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853112] Re: Applications are closed when killing the Shell (like on a hang)
** Tags added: fixed-in-3.34.2 fixed-upstream -- 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/1853112 Title: Applications are closed when killing the Shell (like on a hang) Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Focal: Triaged Bug description: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
This has been happening for a bit on a work computer that went through the built in update process to 19.10. I seem to have gotten some relief by purging the nvidia drivers and reinstalling. YMMV 1979 sudo apt purge nvidia-prime 1980 cat /var/log/prime-supported.log 1981 cat /var/log/gpu-manager.log 1982 nvidia-smi 1983 sudo apt purge nvidia* 1984 sudo apt update 1985 sudo apt install nvidia-driver-418 1986 sudo reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock Status in gnome-desktop: New Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
This has been happening for a bit on a work computer that went through the built in update process to 19.10. I seem to have gotten some relief by purging the nvidia drivers and reinstalling. YMMV 1979 sudo apt purge nvidia-prime 1980 cat /var/log/prime-supported.log 1981 cat /var/log/gpu-manager.log 1982 nvidia-smi 1983 sudo apt purge nvidia* 1984 sudo apt update 1985 sudo apt install nvidia-driver-418 1986 sudo reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock Status in gnome-desktop: New Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857038] [NEW] package gnome-control-center-shared-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in p
Public bug reported: I am trying to run gnome-control-center but keep getting an error stating 'Execution of "gnome-control-center" failed: Command not found.' I get this error after I click on the printer icon then click on "Printers". When I try to install "gnome-control-center" I get these: gnome-control-center : Depends: libcheese-gtk25 (>= 3.18.0) but it is not going to be installed Depends: libcheese8 (>= 3.18.0) but it is not going to be installed When I try to install these packages, this happens: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed As a result, I am unable to open gnome-control-center and therefore cannot install my Canon MX922 printer. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-control-center-shared-data (not installed) ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: gnome-control-center-shared-data:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Dec 19 10:37:14 2019 DpkgTerminalLog: Preparing to unpack .../gnome-control-center-shared-data_1%3a3.6.3-0ubuntu56.1_all.deb ... Unpacking gnome-control-center-shared-data (1:3.6.3-0ubuntu56.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/gnome-control-center-shared-data_1%3a3.6.3-0ubuntu56.1_all.deb (--unpack): trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.2 ErrorMessage: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.2 InstallationDate: Installed on 2018-08-31 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: gnome-control-center Title: package gnome-control-center-shared-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1857038 Title: package gnome-control-center-shared-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome- control-center-faces 1:3.28.2-0ubuntu0.18.04.2 Status in gnome-control-center package in Ubuntu: New Bug description: I am trying to run gnome-control-center but keep getting an error stating 'Execution of "gnome-control-center" failed: Command not found.' I get this error after I click on the printer icon then click on "Printers". When I try to install "gnome-control-center" I get these: gnome-control-center : Depends: libcheese-gtk25 (>= 3.18.0) but it is not going to be installed Depends: libcheese8 (>= 3.18.0) but it is not going to be installed When I try to install these packages, this happens: libcheese8 : Depends: gstreamer1.0-plugins-good (>= 0.11.0) but it is not going to be installed As a result, I am unable to open gnome-control-center and therefore cannot install my Canon MX922 printer. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-control-center-shared-data (not installed) ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: gnome-control-center-shared-data:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Dec 19 10:37:14 2019 DpkgTerminalLog: Preparing to unpack .../gnome-control-center-shared-data_1%3a3.6.3-0ubuntu56.1_all.deb ... Unpacking gnome-control-center-shared-data (1:3.6.3-0ubuntu56.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/gnome-control-center-shared-data_1%3a3.6.3-0ubuntu56.1_all.deb (--unpack): trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.2 ErrorMessage: trying to overwrite '/usr/share/pixmaps/faces/launch.jpg', which is also in package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.2 InstallationDate: Installed on 2018-08-31 (474 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details:
[Desktop-packages] [Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Bug description: GPU: NVIDIA GTX 1060 3GB Ubuntu: 19.04, Kernel Linux luky-pc 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux NVIDIA driver version: 418.56 Display settings: BenQ XL2411Z, 144Hz monitor, 1920x1080p I have noticed this strange behavior only on gnome-shell where the overall gnome-shell desktop VRAM usage was taking up to 1GB of GPU VRAM which does not happen on other desktops, or on Windows, happens after some hours of normal desktop usage Even the system RAM increases a lot during normal usage, but remains acceptable This behaviour can be observed by using "nvidia-smi" a tool from the NVIDIA proprietary driver gnome-shell VRAM usage on a cold start: 139MB, + 9 MB X.org VRAM usage on cold start: 48MB + 18MB Total: 214MB gnome-shell VRAM usage after some hours of normal usage: 445MB + 83 MB X.org VRAM usage after some hours of normal usage: 244MB + 18MB Total: 800MB On windows or other desktops the GPU VRAM usage remains the same --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.32.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856166] Re: NVS 5200M not supported by 435, but is recommended by ubuntu-drivers
** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1856166 Title: NVS 5200M not supported by 435, but is recommended by ubuntu-drivers Status in nvidia-graphics-drivers-430 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-435 package in Ubuntu: In Progress Bug description: I have a Dell Laptop with a NVS 5200M (0DFC) and wondered why ubuntu- drivers recommend the nvidia-driver-435 (and also the wrong driver 430). It won't work with these drivers. $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd0DFCsv1028sd0535bc03sc00i00 vendor : NVIDIA Corporation model: GF108GLM [NVS 5200M] driver : nvidia-340 - distro non-free driver : nvidia-driver-435 - distro non-free recommended driver : nvidia-driver-430 - distro non-free driver : nvidia-driver-390 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 I found the modalias in the packages nvidia-driver-435 and also in the package of the nvidia-driver-430. In the Nvidia READMEs you can find that the NVS 5200M (0DFC) is only supported up to 390. I opened an issue on https://github.com/tseliot/nvidia-graphics- drivers/issues/36 and tseliot told me it could be a parsing problem of the Nvidia READMEs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1856166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844222] Re: Wayland session overlaid by window when fullscreen SDL apps exits
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/376962 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1844222 Title: Wayland session overlaid by window when fullscreen SDL apps exits Status in Mutter: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: Seen on 18.04 and 19.10 [Impact] In the "Ubuntu Wayland" desktop [Test case] sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. [Regression Potential] Animations could stop on a window that has not been destroyed. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1844222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
A few more deja-dup issues: deja-dup (brings up GUI, I select backup...) Traceback (most recent call last): File "/usr/bin/duplicity", line 55, in from duplicity.dup_main import main ImportError: No module named duplicity.dup_main sudo deja-dup (brings up GUI, I select backup...) Traceback (most recent call last): File "/usr/bin/duplicity", line 31, in from future import standard_library ImportError: No module named future So: pip install future Requirement already satisfied: future in ./.local/lib/python2.7/site-packages (0.18.2) But isn't in python3 now? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/376962 -- 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/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/376962 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in mutter package in Ubuntu: In Progress Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846403] Re: gnome-shell sigsegv in meta_input_device_x11_get_current_tool -> meta_device_manager_x11_translate_event -> meta_clutter_backend_x11_translate_event -> meta_x11_ha
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/376962 -- 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/1846403 Title: gnome-shell sigsegv in meta_input_device_x11_get_current_tool -> meta_device_manager_x11_translate_event -> meta_clutter_backend_x11_translate_event -> meta_x11_handle_event -> handle_host_xevent Status in gnome-shell package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/9ed2d0f16e66799f511ef98bc6ad173a078bdc75 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857037] [NEW] Update to 3.34.2 and SRU it
Public bug reported: [ Description ] The second stable release in the 3.34 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Most of commits were already included in stable ubuntu release, as per git snapshot. However we've still various fixes in handling windows workspaces and focus, so ensure that there are no focus issues, especially with Java apps. ** Affects: gnome-shell (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/376962 -- 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/1857037 Title: Update to 3.34.2 and SRU it Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: [ Description ] The second stable release in the 3.34 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Most of commits were already included in stable ubuntu release, as per git snapshot. However we've still various fixes in handling windows workspaces and focus, so ensure that there are no focus issues, especially with Java apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
** Tags added: fixed-upstream ** Tags added: fixed-in-3.34.2 -- 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/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846403] Re: gnome-shell sigsegv in meta_input_device_x11_get_current_tool -> meta_device_manager_x11_translate_event -> meta_clutter_backend_x11_translate_event -> meta_x11_ha
** Tags added: fixed-upstream ** Tags added: fixed-in-3.34.2 -- 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/1846403 Title: gnome-shell sigsegv in meta_input_device_x11_get_current_tool -> meta_device_manager_x11_translate_event -> meta_clutter_backend_x11_translate_event -> meta_x11_handle_event -> handle_host_xevent Status in gnome-shell package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/9ed2d0f16e66799f511ef98bc6ad173a078bdc75 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()
The change fixing it is https://gitlab.gnome.org/GNOME/grilo- plugins/commit/46d7c0ed ** Also affects: grilo-plugins via https://gitlab.gnome.org/GNOME/grilo-plugins/issues/61 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1856927 Title: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() Status in Grilo Plugins: Unknown Status in grilo-plugins package in Ubuntu: Fix Committed Status in totem package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034 --- Test case: Fresh 20.04 install, updated Open totem What happens: segfault Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 19:51:40 2019 ExecutablePath: /usr/bin/totem ExecutableTimestamp: 1570435741 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcCmdline: /usr/bin/totem --gapplication-service ProcCwd: /home/doug ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax PC (0x7f76b92f6dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0 Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/grilo-plugins/+bug/1856927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
** Changed in: duplicity Importance: Medium => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()
Installing grilo-plugins-0.3-extra should workaround the issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1856927 Title: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() Status in Grilo Plugins: Unknown Status in grilo-plugins package in Ubuntu: Fix Committed Status in totem package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034 --- Test case: Fresh 20.04 install, updated Open totem What happens: segfault Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 19:51:40 2019 ExecutablePath: /usr/bin/totem ExecutableTimestamp: 1570435741 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcCmdline: /usr/bin/totem --gapplication-service ProcCwd: /home/doug ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax PC (0x7f76b92f6dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0 Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/grilo-plugins/+bug/1856927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()
The issue looks like https://gitlab.gnome.org/GNOME/grilo- plugins/issues/61 which is fixed in upstream git ** Bug watch added: gitlab.gnome.org/GNOME/grilo-plugins/issues #61 https://gitlab.gnome.org/GNOME/grilo-plugins/issues/61 ** Package changed: grilo (Ubuntu) => grilo-plugins (Ubuntu) ** Changed in: grilo-plugins (Ubuntu) Importance: Undecided => High ** Changed in: grilo-plugins (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: totem (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1856927 Title: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() Status in grilo-plugins package in Ubuntu: Fix Committed Status in totem package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034 --- Test case: Fresh 20.04 install, updated Open totem What happens: segfault Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 19:51:40 2019 ExecutablePath: /usr/bin/totem ExecutableTimestamp: 1570435741 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcCmdline: /usr/bin/totem --gapplication-service ProcCwd: /home/doug ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax PC (0x7f76b92f6dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0 Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1856927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857014] Re: Unable to paste files from Nautilus to the desktop
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1857014 Title: Unable to paste files from Nautilus to the desktop Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Files app 1:3.34.1-1ubuntu1 3) Open Files app. Copy file. Right click on Desktop. Select paste. 4) Unable to paste the file to the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857027] Re: Bytes are not correctly converted to GygaBytes
Thank you for your bug but what is displayed is correct, see https://en.wikipedia.org/wiki/Megabyte It would be 5.8GiB but 6.2GB is also correct ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1857027 Title: Bytes are not correctly converted to GygaBytes Status in nautilus package in Ubuntu: Invalid Bug description: 6,230,444,800 bytes, are converted to 6.2GB, instead of 5.80GB This happens in the *folder view* and in the properties of the file ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 19 11:12:55 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-01-31 (321 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1857027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
Thanks very much. I'm glad I was able to help a little by testing things. Have you any thoughts about why deja-dup fails as I reported in #26? Do I need to raise a separate report somewhere else? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857027] [NEW] Bytes are not correctly converted to GygaBytes
Public bug reported: 6,230,444,800 bytes, are converted to 6.2GB, instead of 5.80GB This happens in the *folder view* and in the properties of the file ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 19 11:12:55 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-01-31 (321 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot from 2019-12-19 11-21-32.png" https://bugs.launchpad.net/bugs/1857027/+attachment/5314052/+files/Screenshot%20from%202019-12-19%2011-21-32.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/1857027 Title: Bytes are not correctly converted to GygaBytes Status in nautilus package in Ubuntu: New Bug description: 6,230,444,800 bytes, are converted to 6.2GB, instead of 5.80GB This happens in the *folder view* and in the properties of the file ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 19 11:12:55 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2019-01-31 (321 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1857027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
The shebang points to python2 on all scripts. It was my fault. setup pointed to python3, duplicity pointed to python2. That caused all the problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
Which particular fix has been applied? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853774] Re: Keep track of upstream adwaita-icon-theme
It is not easy to implement this automatically, but we are already keeping an eye on adwaita icon theme ** Changed in: yaru-theme (Ubuntu) Status: Triaged => Invalid -- 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/1853774 Title: Keep track of upstream adwaita-icon-theme Status in Yaru Theme: New Status in yaru-theme package in Ubuntu: Invalid Bug description: Since Yaru is now syncing with upstream adwaita-gtk and gnome-shell themes, I think it would be a good idea to also keep an eye on upstream adwaita-icon-theme. adwaita-icon-theme mostly contains symbolic and action icons that correspond to code changes in gnome-shell, gnome-control-center and the rest of gnome apps. In every gnome development cycle, adwaita-icon-theme adds, fixes, or enhances its symbolic icons in order to reflect the code changes in the gnome stack. adwaita-icon-theme does not contain app icons since gnome apps ship their own icons. An example to elaborate: In the 3.34 development cycle, gnome added new battery icons in order to better represent the battery charge states: https://gitlab.gnome.org/GNOME/adwaita-icon-theme/issues/6 That has resulted in: 21 new battery icons in adwaita-icon-theme and moving the legacy battery icons to a legacy folder: https://gitlab.gnome.org/GNOME/adwaita-icon-theme/commit/377044f755c3ec994f661d787f50e633487b929d Code changes in gnome-shell to use the new icons, if available, and fall back to the existing icon names for compatibility with older icon themes: https://gitlab.gnome.org/GNOME/gnome-shell/commit/bd18313d125aa1873c21b9cce9bbf81a335e48b0 Without reflecting the new changes in Yaru*, gnome-shell would still be falling back to the legacy icons, and not showing a better charge state as a result. * https://github.com/ubuntu/yaru/issues/1482 Here is the gnome-stencils.svg as a reference: https://gitlab.gnome.org/GNOME/adwaita-icon-theme/blob/master/src/symbolic/gnome-stencils.svg To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1853774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855009] Re: autopkgtests all fail on s390x
autopkgtest analysis: the network-manager test on disco/ppc64el fails, being tracked in bug 1733321, and unrelated to this bug. -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
In my case, ASUS ZenBook Pro 15 UX580GE, Ubuntu 19.10, touchpad is unresponsive. I somehow made it work by installing xserver-xorg-input- libinput, xserver-xorg-input-evdev, xserver-xorg-input-mouse, but after rebooting it stops working again and can't find any solution anymore. Any tips on how to fix this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and screen - all in one) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Oct 1 00:53:26 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.0.0-29-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1021] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:180e] InstallationDate: Installed on 2019-09-27 (3 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GDX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
> I'm also effected by this bug on 18.04.3 (NetworkManager v1.10.14) please note that n-m version 1.10.14 never was released out of Bionic- proposed; instead smaller fixes were used to address specific bugs, and the latest NetworkManager version in Bionic-updates is 1.10.6-2ubuntu1.2. If you have version 1.10.14 installed, you should remove and reinstall it, or simply 'downgrade' it with apt to the latest released version. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857014] [NEW] Unable to paste files from Nautilus to the desktop
Public bug reported: 1) Ubuntu 19.10 2) Files app 1:3.34.1-1ubuntu1 3) Open Files app. Copy file. Right click on Desktop. Select paste. 4) Unable to paste the file to the desktop. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: 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/1857014 Title: Unable to paste files from Nautilus to the desktop Status in gnome-shell package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Files app 1:3.34.1-1ubuntu1 3) Open Files app. Copy file. Right click on Desktop. Select paste. 4) Unable to paste the file to the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845797]
It seems that there are some I2S amplifiers on the path to speakers and the BIOS has only limited initialization. I will try to gather information for C930 from Lenovo, too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828664] Re: [snap] Broken link in theme directory
@sean
The snap command (part of snapd) takes care of
~/snap/packagename/current/, anything below (including .themes) is
handled by the actual snap package. I would look into desktop extensions
added by snapcraft.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/1828664
Title:
[snap] Broken link in theme directory
Status in gnome-characters package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Invalid
Bug description:
Reproduce steps
---
1. $ snap install gnome-characters communitheme
2. logoff and select communitheme session at the greeter (probably needs a
reload of GDM or reboot, I'm running the wayland session but it also happened
of X)
3. $ snap run gnome-characters
Affected snaps:
gnome-characters
gnome-calculator
gnome-logs
gnome-system-monitor
libreoffice
evince
gnome-contacts
eog
Symptoms
I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which
broke at some point about two month ago. Screenshots are here:
https://askubuntu.com/q/1142291/40581
I found that ~/snap/gnome-characters/current/themes is a broken link
even when removing the respective snap folder for the app, removing
and then reinstalling the gnome-characters snap. This has worked
before, please take a look at this.
In the meantime I fixed this with the following commands, according
the the error message:
rm ~/snap/gnome-characters/current/.themes
cp -av /snap/communitheme/current/share/themes
~/snap/gnome-characters/current/.themes
Version
---
```
$ snap info {gnome-characters,communitheme} | grep -vE
"^(summary|license|contact|description|commands):"
name: gnome-characters
publisher: Canonical*
Characters is a simple utility application to find and
insert unusual characters.
- gnome-characters
snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
tracking: stable
refresh-date: heute um 04:19 CEST
channels:
stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
beta: ^
edge: v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
installed: v3.32.1+git1.2050bba(258) 15MB -
---
name: communitheme
publisher: Didier Roche (didrocks)
Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
package allows you to try out the theme on Ubuntu 18.04 LTS.
To try out the theme, install this package on Ubuntu 18.04 LTS, restart
your computer and select the "Ubuntu with communitheme snap" session from
the login screen.
More information is available at
https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
snap-id: Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
tracking: stable
refresh-date: 59 days ago, at 17:46 CET
channels:
stable:0.1 2019-03-13 (1768) 16MB -
candidate: ^
beta: ^
edge: 0.1 2019-05-08 (1799) 17MB -
installed: 0.1(1768) 16MB -
```
---
Further investigation
-
I'm also seeing broken links on an 19.04 machine where I'm not using
the Communitheme snap but the preinstalled Yaru packages. I'm trying
out the dark theme but all snaps launch with Adwaita instead.
```
$ snap list
Name Version Rev Tracking Publisher
Notes
android-studio 3.4.0.1875stablesnapcrafters
classic
canonical-livepatch 9.3.0 77stablecanonical*
-
core 16-2.38.1 6818 stablecanonical*
core
core18 20190409941 stablecanonical*
base
gedit3.30.2+git14.bed83e929 89stablecanonical*
-
gnome-3-26-1604 3.26.0.20190228 82stable/… canonical*
-
gnome-3-28-1804 3.28.0-10-gaa70833.aa70833 40stablecanonical*
-
gnome-calculator 3.32.1 406 stable/… canonical*
-
gnome-characters v3.32.1+git1.2050bba258 stablecanonical*
-
gnome-logs 3.32.0-4-ge8f3f37ca861stable/… canonical*
-
gtk-common-themes0.1-16-g2287c87 1198 stable/… canonical*
-
$ find snap/gnome-characters -xtype l
snap/gnome-characters/common/.cache/immodules/im-fcitx.so
snap/gnome-characters/common/.cache/immodules/im-wayland.so
snap/gnome-characters/common/.cache/immodules/im-broadway.so
snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
snap/gnome-characters/common/.cache/immodules/im-cedilla.so
snap/gnome-characters/common/.cache/immodules/im-ipa.so
snap/gnome-characters/common/.cache/immodules/im-xim.so
[Desktop-packages] [Bug 1828664] Re: [snap] Broken link in theme directory
@John
Which component is responsible for linking
~/snap/packagename/current/.themes? Is this a per snap functionality or
snapd that would produce this? Currently it's broken for at least the
snaps listed in the description.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/1828664
Title:
[snap] Broken link in theme directory
Status in gnome-characters package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Invalid
Bug description:
Reproduce steps
---
1. $ snap install gnome-characters communitheme
2. logoff and select communitheme session at the greeter (probably needs a
reload of GDM or reboot, I'm running the wayland session but it also happened
of X)
3. $ snap run gnome-characters
Affected snaps:
gnome-characters
gnome-calculator
gnome-logs
gnome-system-monitor
libreoffice
evince
gnome-contacts
eog
Symptoms
I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which
broke at some point about two month ago. Screenshots are here:
https://askubuntu.com/q/1142291/40581
I found that ~/snap/gnome-characters/current/themes is a broken link
even when removing the respective snap folder for the app, removing
and then reinstalling the gnome-characters snap. This has worked
before, please take a look at this.
In the meantime I fixed this with the following commands, according
the the error message:
rm ~/snap/gnome-characters/current/.themes
cp -av /snap/communitheme/current/share/themes
~/snap/gnome-characters/current/.themes
Version
---
```
$ snap info {gnome-characters,communitheme} | grep -vE
"^(summary|license|contact|description|commands):"
name: gnome-characters
publisher: Canonical*
Characters is a simple utility application to find and
insert unusual characters.
- gnome-characters
snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
tracking: stable
refresh-date: heute um 04:19 CEST
channels:
stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
beta: ^
edge: v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
installed: v3.32.1+git1.2050bba(258) 15MB -
---
name: communitheme
publisher: Didier Roche (didrocks)
Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
package allows you to try out the theme on Ubuntu 18.04 LTS.
To try out the theme, install this package on Ubuntu 18.04 LTS, restart
your computer and select the "Ubuntu with communitheme snap" session from
the login screen.
More information is available at
https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
snap-id: Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
tracking: stable
refresh-date: 59 days ago, at 17:46 CET
channels:
stable:0.1 2019-03-13 (1768) 16MB -
candidate: ^
beta: ^
edge: 0.1 2019-05-08 (1799) 17MB -
installed: 0.1(1768) 16MB -
```
---
Further investigation
-
I'm also seeing broken links on an 19.04 machine where I'm not using
the Communitheme snap but the preinstalled Yaru packages. I'm trying
out the dark theme but all snaps launch with Adwaita instead.
```
$ snap list
Name Version Rev Tracking Publisher
Notes
android-studio 3.4.0.1875stablesnapcrafters
classic
canonical-livepatch 9.3.0 77stablecanonical*
-
core 16-2.38.1 6818 stablecanonical*
core
core18 20190409941 stablecanonical*
base
gedit3.30.2+git14.bed83e929 89stablecanonical*
-
gnome-3-26-1604 3.26.0.20190228 82stable/… canonical*
-
gnome-3-28-1804 3.28.0-10-gaa70833.aa70833 40stablecanonical*
-
gnome-calculator 3.32.1 406 stable/… canonical*
-
gnome-characters v3.32.1+git1.2050bba258 stablecanonical*
-
gnome-logs 3.32.0-4-ge8f3f37ca861stable/… canonical*
-
gtk-common-themes0.1-16-g2287c87 1198 stable/… canonical*
-
$ find snap/gnome-characters -xtype l
snap/gnome-characters/common/.cache/immodules/im-fcitx.so
snap/gnome-characters/common/.cache/immodules/im-wayland.so
snap/gnome-characters/common/.cache/immodules/im-broadway.so
snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
snap/gnome-characters/common/.cache/immodules/im-cedilla.so
snap/gnome-characters/common/.cache/immodules/im-ipa.so
[Desktop-packages] [Bug 1065126]
*** Bug 1600471 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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: New Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1500282] Re: pixel scaling seems to be rounded to integers
Launchpad has imported 46 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1214470. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-10-14T02:19:54+00:00 Kai Mast wrote: User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 Build ID: 20151003161951 Steps to reproduce: Set the scaling vlaue in unity-control-center to a float value, e.g. 1.5. Actual results: Firefox adapts its highdpi settings to the value in unity-control- center. However, it will round the scale to the next higher value, e.g. 2.0. This means everything is much bigger than it should be. If I set devPixelsPerPx to 1.5 manually everything looks fine. So there must be some bug in firefox that is reading this value as an integer. Expected results: Firefox should use the actual floating point value. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1500282/comments/1 On 2015-10-14T02:21:15+00:00 Kai Mast wrote: (If somebody tells me where to look I might be able to submit a patch...) Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1500282/comments/2 On 2016-02-26T20:33:30+00:00 Moz-bugzilla-e wrote: Created attachment 8724197 patch to use actual gtk scaling Here is the patch which fixes this. It basically removes the rounding applied when reading the current DPI from gdk_screen_get_resolution(). I have tested this and it works as expected: the Xft/DPI value is read from XSETTINGS, returned in gdk_screen_get_resolution() and then correctly applied to the content rendering as well. This is consistent with the UI rendering, which already gets scaled correctly at all Xft/DPI values > 96. I hope this can be included. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1500282/comments/3 On 2016-02-26T20:39:18+00:00 Moz-bugzilla-e wrote: Further information: it seems that no-one ever questioned in the initial commit why "We want to set the default CSS to device pixel ratio as the closest _integer_ multiple, so round the ratio of actual dpi to CSS dpi (96)". This probably comes from the fact that GDK_SCALE and GDK_DPI_SCALE only accept integer values (and 0.5). There is no _technical_ requirement for this, though. https://developer.gnome.org/gtk3/unstable/GtkSettings.html#GtkSettings --gtk-xft-dpi accepts granularities of 1/1024th DPI. Also, the "component" of this bug should probably be changed to Gtk:Widget or seomthing else. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1500282/comments/4 On 2016-02-29T10:42:00+00:00 Stransky wrote: Yes, this scale (also editable by GDK_SCALE for debugging purposes) are intended to handle hi-res displays like retina. The DPI scale is just one part of it - the application is supposed to also provide hi-res graphics (pictures, icons, controls) for those modes. IIUC This is also a reason why it's integer scale - to easily scale bitmap images like icons or to provide hi-res icon set. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1500282/comments/5 On 2016-02-29T11:05:55+00:00 Moz-bugzilla-e wrote: But from my (limited) understanding, the problem is that the GDK_SCALE is not the value which is rounded here. As I see it, the DPI (referred to as font scaling, gtk-xft-dpi or Xft/DPI setting) operates independently from the "global" GDK_SCALE setting. If I am reading bug #1131978 correctly, both are used to determine the overall "scale" within Firefox. That is, the font scaling read from gdk_screen_get_resolution is not affected by GDK_SCALE (but maybe by GDK_DPI_SCALE?). In any case, it is obvious that the *UI* (is it called chrome?) part of Firefox scales correctly (as seen for example in the font size in about:settings and the tab font size), but the *content* part doesn't. After applying this patch, both scale consistently. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1500282/comments/6 On 2016-02-29T11:47:19+00:00 Stransky wrote: AFAIK the GDK_SCALE is here for debugging purpose only (if you want to emulate hi-res mode on a regular display so if you want to override the fedault) and it's involved unless user set it explicitly by hand (by gnome-tweaking-tool for instance). Reply at:
[Desktop-packages] [Bug 1756826] Re: hangs when remote search provider performs expensive operation
Confirmed working also with new calculator apt-cache policy gnome-calculator gnome-calculator: Installato: 1:3.28.2-1~ubuntu18.04.3 Candidato: 1:3.28.2-1~ubuntu18.04.3 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1756826 Title: hangs when remote search provider performs expensive operation Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in gnome-calculator source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: In Progress Status in gnome-software source package in Bionic: In Progress Status in nautilus source package in Bionic: In Progress Bug description: [ Impact ] Doing a search in the shell might lead to unresponsive processes that are not terminated when the search is cancelled or when the gnome- shell overlay is closed. [ Test case for GNOME-Shell and Nautilus ] 1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one) 2. Open gnome shell overlay (hit super, or got to activity) 3. Search for a short string (3 chars let's say) that matches many files you know you have 4. Close the overlay (press super again, hit escape twice) 5. The nautilus process should stop using CPU once the overlay is closed [ Test case for GNOME-Shell and GNOME-Calculator ] 1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one) 2. Open gnome shell overlay (hit super, or got to activity) 3. Type "10!!!" 4. Close the overlay (press super again, hit escape twice) 5. The gnome-calculator process should stop using CPU once the overlay is closed [ Regression Potential ] Nautilus search results returned are missing elements when continuously update the search string, gnome-calculator computations via the shell might not work as expected. I have a maildir for my mail. My computer's name is "nightingale", and this name is in the filenames in the maildir. I have a lot of email! When I search for "tilix" to start a terminal after logging in, Nautilus goes crazy consuming CPU. This is because I have to type "ti" to type "tilix" and "ti" is a substring of "nightingale". This is submitted as a search string to the nautilus search provider and apparently isn't cancelled when I close the entry - I checked the GError and it's NULL. A similar thing happens with the ctrl-f search in nautilus itself. We talked about this on IRC and I provided some traces and stuff. Linking to the log to avoid having to fetch those out into files. :-) https://irclogs.ubuntu.com/2018/03/14/%23ubuntu-desktop.html#t15:58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1756826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857005] Re: gnome-calculator fails to build with vala 0.40.17
It built ok. Build Architecture: amd64 Build Type: binary Build-Space: n/a Build-Time: 56 Distribution: bionic-amd64 Host Architecture: amd64 Install-Time: 105 Job: /data/GNOME/DEB-build-area/gnome-calculator_3.28.2-1~ubuntu18.04.3.dsc Lintian: pass Machine Architecture: amd64 Package: gnome-calculator Package-Time: 199 Source-Version: 1:3.28.2-1~ubuntu18.04.3 Space: n/a Status: successful Version: 1:3.28.2-1~ubuntu18.04.3 Finished at 2019-12-19T11:58:33Z ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1857005 Title: gnome-calculator fails to build with vala 0.40.17 Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-calculator source package in Bionic: Fix Committed Bug description: [ Impact ] Gnome calculator doesn't build in bionic-proposed valac -C --vapidir /<>/vapi --pkg posix --pkg posix /<>/vapi/mpfr.vapi /<>/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg gtksourceview-3.0 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' --pkg glib-2.0 --pkg gio-2.0 --color=always --directory lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 ../lib/mpfr-glue.vala ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala ../lib/equation-parser.vala ../lib/financial.vala ../lib/function-manager.vala ../lib/math-equation.vala ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala ../lib/equation-parser.vala:79.9-79.43: error: Assignment: Cannot convert from `GLib.List' to `GLib.List' this.token_list = token_list.copy(); ^^^ Compilation failed: 1 error(s), 0 warning(s) [ Test case ] sbuild it and... Should work [ Regression potential ] Possible refcount issue and so mem-leak. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1857005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853007]
i can confirm this behavior in Linux. i am running same version as reporter on debian unstable (bug 1602759). i would add that those files contain copies of sent emails. sometimes spotted even plain text where the sent email was encrypted. i tried running `thunderbird --verbose` but it did not help revealing more info. i tried `thunderbird -g` but thunderbird-dbgsym seems to be missing from debian. -- 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/1853007 Title: nsemail and nscopy files left in /tmp Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Triaged Bug description: thunderbird leaves nsemail and nscopy files in /tmp: # ls -l /tmp/ns* -rw--- 1 alistair alistair 5522 Nov 18 08:42 /tmp/nscopy-1.tmp -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nscopy-2.tmp -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nscopy-3.tmp -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nscopy.tmp -rw--- 1 alistair alistair 25790 Nov 15 09:26 /tmp/nsemail-10.eml -rw--- 1 alistair alistair 5840 Nov 15 09:28 /tmp/nsemail-11.eml -rw--- 1 alistair alistair 25442 Nov 15 09:29 /tmp/nsemail-12.eml -rw--- 1 alistair alistair 2838 Nov 15 09:29 /tmp/nsemail-13.eml -rw--- 1 alistair alistair 8556 Nov 15 10:10 /tmp/nsemail-14.eml -rw--- 1 alistair alistair 1659 Nov 15 10:32 /tmp/nsemail-15.eml -rw--- 1 alistair alistair 3240 Nov 15 10:47 /tmp/nsemail-16.eml -rw--- 1 alistair alistair 3260 Nov 15 10:57 /tmp/nsemail-17.eml -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml -rw--- 1 alistair alistair 4878 Nov 15 13:44 /tmp/nsemail-19.eml -rw--- 1 alistair alistair 21150 Nov 13 08:43 /tmp/nsemail-1.eml -rw--- 1 alistair alistair 2974 Nov 18 08:41 /tmp/nsemail-1.html -rw--- 1 alistair alistair 6328 Nov 15 13:45 /tmp/nsemail-20.eml -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml -rw--- 1 alistair alistair 2733 Nov 15 17:15 /tmp/nsemail-22.eml -rw--- 1 alistair alistair 53857 Nov 16 09:23 /tmp/nsemail-23.eml -rw--- 1 alistair alistair 89392 Nov 16 09:39 /tmp/nsemail-24.eml -rw--- 1 alistair alistair 80120 Nov 17 10:52 /tmp/nsemail-25.eml -rw--- 1 alistair alistair 6361 Nov 17 18:45 /tmp/nsemail-26.eml -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nsemail-27.eml -rw--- 1 alistair alistair 5522 Nov 18 08:41 /tmp/nsemail-28.eml -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nsemail-29.eml -rw--- 1 alistair alistair 29937 Nov 13 09:37 /tmp/nsemail-2.eml -rw--- 1 alistair alistair 5057 Nov 18 08:43 /tmp/nsemail-2.html -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nsemail-30.eml -rw--- 1 alistair alistair 2015 Nov 13 09:40 /tmp/nsemail-3.eml -rw--- 1 alistair alistair 4949 Nov 18 08:49 /tmp/nsemail-3.html -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml -rw--- 1 alistair alistair 59817 Nov 15 08:41 /tmp/nsemail-5.eml -rw--- 1 alistair alistair 9751 Nov 15 08:47 /tmp/nsemail-6.eml -rw--- 1 alistair alistair 2967 Nov 15 08:49 /tmp/nsemail-7.eml -rw--- 1 alistair alistair 2983 Nov 15 08:54 /tmp/nsemail-8.eml -rw--- 1 alistair alistair 19780 Nov 15 09:14 /tmp/nsemail-9.eml -rw--- 1 alistair alistair 27900 Nov 13 08:34 /tmp/nsemail.eml -rw--- 1 alistair alistair 1317 Nov 18 08:38 /tmp/nsemail.html -rw--- 1 alistair alistair 1115 Nov 18 08:41 /tmp/nsmail-1.tmp -rw--- 1 alistair alistair 2424 Nov 18 08:43 /tmp/nsmail-2.tmp -rw--- 1 alistair alistair 2000 Nov 18 08:49 /tmp/nsmail-3.tmp -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.1.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2211 F pulseaudio BuildID: 20191010144232 Channel: Unavailable Date: Mon Nov 18 08:50:15 2019 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback dns-search integrics.com InstallationDate: Installed on 2017-08-16 (823 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 1.0.0.1 dev wlp58s0 proto dhcp metric 600 1.0.0.0/21 dev wlp58s0 proto kernel scope link src 1.0.1.146 metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 NoProfiles: True ProcEnviron:
[Desktop-packages] [Bug 1828664] Re: [snap] Broken link in theme directory
It's unclear to me why you've added snapd to this bug. I'm setting it as
Invalid, but if you have a reasoning please explain it and set it back
to New so our triage picks it up again.
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/1828664
Title:
[snap] Broken link in theme directory
Status in gnome-characters package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Invalid
Bug description:
Reproduce steps
---
1. $ snap install gnome-characters communitheme
2. logoff and select communitheme session at the greeter (probably needs a
reload of GDM or reboot, I'm running the wayland session but it also happened
of X)
3. $ snap run gnome-characters
Affected snaps:
gnome-characters
gnome-calculator
gnome-logs
gnome-system-monitor
libreoffice
evince
gnome-contacts
eog
Symptoms
I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which
broke at some point about two month ago. Screenshots are here:
https://askubuntu.com/q/1142291/40581
I found that ~/snap/gnome-characters/current/themes is a broken link
even when removing the respective snap folder for the app, removing
and then reinstalling the gnome-characters snap. This has worked
before, please take a look at this.
In the meantime I fixed this with the following commands, according
the the error message:
rm ~/snap/gnome-characters/current/.themes
cp -av /snap/communitheme/current/share/themes
~/snap/gnome-characters/current/.themes
Version
---
```
$ snap info {gnome-characters,communitheme} | grep -vE
"^(summary|license|contact|description|commands):"
name: gnome-characters
publisher: Canonical*
Characters is a simple utility application to find and
insert unusual characters.
- gnome-characters
snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
tracking: stable
refresh-date: heute um 04:19 CEST
channels:
stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
beta: ^
edge: v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
installed: v3.32.1+git1.2050bba(258) 15MB -
---
name: communitheme
publisher: Didier Roche (didrocks)
Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
package allows you to try out the theme on Ubuntu 18.04 LTS.
To try out the theme, install this package on Ubuntu 18.04 LTS, restart
your computer and select the "Ubuntu with communitheme snap" session from
the login screen.
More information is available at
https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
snap-id: Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
tracking: stable
refresh-date: 59 days ago, at 17:46 CET
channels:
stable:0.1 2019-03-13 (1768) 16MB -
candidate: ^
beta: ^
edge: 0.1 2019-05-08 (1799) 17MB -
installed: 0.1(1768) 16MB -
```
---
Further investigation
-
I'm also seeing broken links on an 19.04 machine where I'm not using
the Communitheme snap but the preinstalled Yaru packages. I'm trying
out the dark theme but all snaps launch with Adwaita instead.
```
$ snap list
Name Version Rev Tracking Publisher
Notes
android-studio 3.4.0.1875stablesnapcrafters
classic
canonical-livepatch 9.3.0 77stablecanonical*
-
core 16-2.38.1 6818 stablecanonical*
core
core18 20190409941 stablecanonical*
base
gedit3.30.2+git14.bed83e929 89stablecanonical*
-
gnome-3-26-1604 3.26.0.20190228 82stable/… canonical*
-
gnome-3-28-1804 3.28.0-10-gaa70833.aa70833 40stablecanonical*
-
gnome-calculator 3.32.1 406 stable/… canonical*
-
gnome-characters v3.32.1+git1.2050bba258 stablecanonical*
-
gnome-logs 3.32.0-4-ge8f3f37ca861stable/… canonical*
-
gtk-common-themes0.1-16-g2287c87 1198 stable/… canonical*
-
$ find snap/gnome-characters -xtype l
snap/gnome-characters/common/.cache/immodules/im-fcitx.so
snap/gnome-characters/common/.cache/immodules/im-wayland.so
snap/gnome-characters/common/.cache/immodules/im-broadway.so
snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
snap/gnome-characters/common/.cache/immodules/im-cedilla.so
snap/gnome-characters/common/.cache/immodules/im-ipa.so
[Desktop-packages] [Bug 1638610]
*** Bug 1604720 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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1638610
Title:
Dependency of JavaScript objects is Misconfigured Browser Crashes.
Status in Mozilla Firefox:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Hey Team ,
The bug i want to mention here is a denial of service attack that will not
allow any kind of redirection on a page crafted by attacker where we have used
hyper-links(ahref).
The bug can be maliciously used by crafting an HTML file by an attacker and
then sending it to the victim clearly showing there is a hyper-link that
redirects to lets say (google.com) through status bar but it will not , instead
cause denial of service , browser's also hang up and Crashes.
I have tested it on the Very Latest Version of Ubuntu LTS Default Browser.
Reason:
The following script stops the page from being redirected:
window.onbeforeunload = function(){
//Unredirectable Page
setTimeout("window.location=document.location;",0);
}
Demo URL : http://hackies.in/Unredirect-Browsers-Test.html
Actual results:
It should redirect me to the new page , where as it don't redirect to
a new page and the browsers Hangs up.
Expected results:
So dependency of JavaScript objects(window.document) on Href attribute should
not be there.
Attached POC for References
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1638610/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853007]
*** Bug 1602759 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/1853007 Title: nsemail and nscopy files left in /tmp Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Triaged Bug description: thunderbird leaves nsemail and nscopy files in /tmp: # ls -l /tmp/ns* -rw--- 1 alistair alistair 5522 Nov 18 08:42 /tmp/nscopy-1.tmp -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nscopy-2.tmp -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nscopy-3.tmp -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nscopy.tmp -rw--- 1 alistair alistair 25790 Nov 15 09:26 /tmp/nsemail-10.eml -rw--- 1 alistair alistair 5840 Nov 15 09:28 /tmp/nsemail-11.eml -rw--- 1 alistair alistair 25442 Nov 15 09:29 /tmp/nsemail-12.eml -rw--- 1 alistair alistair 2838 Nov 15 09:29 /tmp/nsemail-13.eml -rw--- 1 alistair alistair 8556 Nov 15 10:10 /tmp/nsemail-14.eml -rw--- 1 alistair alistair 1659 Nov 15 10:32 /tmp/nsemail-15.eml -rw--- 1 alistair alistair 3240 Nov 15 10:47 /tmp/nsemail-16.eml -rw--- 1 alistair alistair 3260 Nov 15 10:57 /tmp/nsemail-17.eml -rw--- 1 alistair alistair 107975 Nov 15 13:43 /tmp/nsemail-18.eml -rw--- 1 alistair alistair 4878 Nov 15 13:44 /tmp/nsemail-19.eml -rw--- 1 alistair alistair 21150 Nov 13 08:43 /tmp/nsemail-1.eml -rw--- 1 alistair alistair 2974 Nov 18 08:41 /tmp/nsemail-1.html -rw--- 1 alistair alistair 6328 Nov 15 13:45 /tmp/nsemail-20.eml -rw--- 1 alistair alistair 134689 Nov 15 13:49 /tmp/nsemail-21.eml -rw--- 1 alistair alistair 2733 Nov 15 17:15 /tmp/nsemail-22.eml -rw--- 1 alistair alistair 53857 Nov 16 09:23 /tmp/nsemail-23.eml -rw--- 1 alistair alistair 89392 Nov 16 09:39 /tmp/nsemail-24.eml -rw--- 1 alistair alistair 80120 Nov 17 10:52 /tmp/nsemail-25.eml -rw--- 1 alistair alistair 6361 Nov 17 18:45 /tmp/nsemail-26.eml -rw--- 1 alistair alistair 3455 Nov 18 08:38 /tmp/nsemail-27.eml -rw--- 1 alistair alistair 5522 Nov 18 08:41 /tmp/nsemail-28.eml -rw--- 1 alistair alistair 8883 Nov 18 08:43 /tmp/nsemail-29.eml -rw--- 1 alistair alistair 29937 Nov 13 09:37 /tmp/nsemail-2.eml -rw--- 1 alistair alistair 5057 Nov 18 08:43 /tmp/nsemail-2.html -rw--- 1 alistair alistair 8311 Nov 18 08:49 /tmp/nsemail-30.eml -rw--- 1 alistair alistair 2015 Nov 13 09:40 /tmp/nsemail-3.eml -rw--- 1 alistair alistair 4949 Nov 18 08:49 /tmp/nsemail-3.html -rw--- 1 alistair alistair 183446 Nov 14 08:48 /tmp/nsemail-4.eml -rw--- 1 alistair alistair 59817 Nov 15 08:41 /tmp/nsemail-5.eml -rw--- 1 alistair alistair 9751 Nov 15 08:47 /tmp/nsemail-6.eml -rw--- 1 alistair alistair 2967 Nov 15 08:49 /tmp/nsemail-7.eml -rw--- 1 alistair alistair 2983 Nov 15 08:54 /tmp/nsemail-8.eml -rw--- 1 alistair alistair 19780 Nov 15 09:14 /tmp/nsemail-9.eml -rw--- 1 alistair alistair 27900 Nov 13 08:34 /tmp/nsemail.eml -rw--- 1 alistair alistair 1317 Nov 18 08:38 /tmp/nsemail.html -rw--- 1 alistair alistair 1115 Nov 18 08:41 /tmp/nsmail-1.tmp -rw--- 1 alistair alistair 2424 Nov 18 08:43 /tmp/nsmail-2.tmp -rw--- 1 alistair alistair 2000 Nov 18 08:49 /tmp/nsmail-3.tmp -rw--- 1 alistair alistair967 Nov 18 08:38 /tmp/nsmail.tmp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.1.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2211 F pulseaudio BuildID: 20191010144232 Channel: Unavailable Date: Mon Nov 18 08:50:15 2019 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback dns-search integrics.com InstallationDate: Installed on 2017-08-16 (823 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 1.0.0.1 dev wlp58s0 proto dhcp metric 600 1.0.0.0/21 dev wlp58s0 proto kernel scope link src 1.0.1.146 metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 NoProfiles: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to eoan on
[Desktop-packages] [Bug 1756826] Re: hangs when remote search provider performs expensive operation
Hello Iain, or anyone else affected, Accepted gnome-calculator into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- calculator/1:3.28.2-1~ubuntu18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-calculator (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1756826 Title: hangs when remote search provider performs expensive operation Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in gnome-calculator source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: In Progress Status in gnome-software source package in Bionic: In Progress Status in nautilus source package in Bionic: In Progress Bug description: [ Impact ] Doing a search in the shell might lead to unresponsive processes that are not terminated when the search is cancelled or when the gnome- shell overlay is closed. [ Test case for GNOME-Shell and Nautilus ] 1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one) 2. Open gnome shell overlay (hit super, or got to activity) 3. Search for a short string (3 chars let's say) that matches many files you know you have 4. Close the overlay (press super again, hit escape twice) 5. The nautilus process should stop using CPU once the overlay is closed [ Test case for GNOME-Shell and GNOME-Calculator ] 1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one) 2. Open gnome shell overlay (hit super, or got to activity) 3. Type "10!!!" 4. Close the overlay (press super again, hit escape twice) 5. The gnome-calculator process should stop using CPU once the overlay is closed [ Regression Potential ] Nautilus search results returned are missing elements when continuously update the search string, gnome-calculator computations via the shell might not work as expected. I have a maildir for my mail. My computer's name is "nightingale", and this name is in the filenames in the maildir. I have a lot of email! When I search for "tilix" to start a terminal after logging in, Nautilus goes crazy consuming CPU. This is because I have to type "ti" to type "tilix" and "ti" is a substring of "nightingale". This is submitted as a search string to the nautilus search provider and apparently isn't cancelled when I close the entry - I checked the GError and it's NULL. A similar thing happens with the ctrl-f search in nautilus itself. We talked about this on IRC and I provided some traces and stuff. Linking to the log to avoid having to fetch those out into files. :-) https://irclogs.ubuntu.com/2018/03/14/%23ubuntu-desktop.html#t15:58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1756826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo in Ubuntu. https://bugs.launchpad.net/bugs/1856927 Title: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() Status in grilo package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034 --- Test case: Fresh 20.04 install, updated Open totem What happens: segfault Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 19:51:40 2019 ExecutablePath: /usr/bin/totem ExecutableTimestamp: 1570435741 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcCmdline: /usr/bin/totem --gapplication-service ProcCwd: /home/doug ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax PC (0x7f76b92f6dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0 Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo/+bug/1856927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857005] Re: gnome-calculator fails to build with vala 0.40.17
Hello Marco, or anyone else affected, Accepted gnome-calculator into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- calculator/1:3.28.2-1~ubuntu18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-calculator (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1857005 Title: gnome-calculator fails to build with vala 0.40.17 Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-calculator source package in Bionic: Fix Committed Bug description: [ Impact ] Gnome calculator doesn't build in bionic-proposed valac -C --vapidir /<>/vapi --pkg posix --pkg posix /<>/vapi/mpfr.vapi /<>/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg gtksourceview-3.0 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' --pkg glib-2.0 --pkg gio-2.0 --color=always --directory lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 ../lib/mpfr-glue.vala ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala ../lib/equation-parser.vala ../lib/financial.vala ../lib/function-manager.vala ../lib/math-equation.vala ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala ../lib/equation-parser.vala:79.9-79.43: error: Assignment: Cannot convert from `GLib.List' to `GLib.List' this.token_list = token_list.copy(); ^^^ Compilation failed: 1 error(s), 0 warning(s) [ Test case ] sbuild it and... Should work [ Regression potential ] Possible refcount issue and so mem-leak. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1857005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756826] Re: hangs when remote search provider performs expensive operation
I want to mention to the release team, that the regression in gnome- calculator DOES NOT affect the other packages, so them can be considered verified and be sent to updates safely (not to block waiting for them), while only gnome-calculator needs an update. -- 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/1756826 Title: hangs when remote search provider performs expensive operation Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in gnome-calculator source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in gnome-software source package in Bionic: In Progress Status in nautilus source package in Bionic: In Progress Bug description: [ Impact ] Doing a search in the shell might lead to unresponsive processes that are not terminated when the search is cancelled or when the gnome- shell overlay is closed. [ Test case for GNOME-Shell and Nautilus ] 1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one) 2. Open gnome shell overlay (hit super, or got to activity) 3. Search for a short string (3 chars let's say) that matches many files you know you have 4. Close the overlay (press super again, hit escape twice) 5. The nautilus process should stop using CPU once the overlay is closed [ Test case for GNOME-Shell and GNOME-Calculator ] 1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one) 2. Open gnome shell overlay (hit super, or got to activity) 3. Type "10!!!" 4. Close the overlay (press super again, hit escape twice) 5. The gnome-calculator process should stop using CPU once the overlay is closed [ Regression Potential ] Nautilus search results returned are missing elements when continuously update the search string, gnome-calculator computations via the shell might not work as expected. I have a maildir for my mail. My computer's name is "nightingale", and this name is in the filenames in the maildir. I have a lot of email! When I search for "tilix" to start a terminal after logging in, Nautilus goes crazy consuming CPU. This is because I have to type "ti" to type "tilix" and "ti" is a substring of "nightingale". This is submitted as a search string to the nautilus search provider and apparently isn't cancelled when I close the entry - I checked the GError and it's NULL. A similar thing happens with the ctrl-f search in nautilus itself. We talked about this on IRC and I provided some traces and stuff. Linking to the log to avoid having to fetch those out into files. :-) https://irclogs.ubuntu.com/2018/03/14/%23ubuntu-desktop.html#t15:58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1756826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756826] Re: hangs when remote search provider performs expensive operation
So, I've verified this for: LANG=C apt-cache policy gnome-shell gnome-shell: Installed: 3.28.4-0ubuntu18.04.3 LANG=C apt-cache policy gnome-software gnome-software: Installed: 3.28.1-0ubuntu4.18.04.14 LANG=C apt-cache policy nautilus nautilus: Installed: 1:3.26.4-0~ubuntu18.04.5 HOWEVER... There's a regression in gnome-calculator 1:3.28.2-1~ubuntu18.04.2, but we've already uploaded a 1:3.28.2-1~ubuntu18.04.3 version in queue that fixes the issue. -- 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/1756826 Title: hangs when remote search provider performs expensive operation Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in gnome-calculator source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in gnome-software source package in Bionic: In Progress Status in nautilus source package in Bionic: In Progress Bug description: [ Impact ] Doing a search in the shell might lead to unresponsive processes that are not terminated when the search is cancelled or when the gnome- shell overlay is closed. [ Test case for GNOME-Shell and Nautilus ] 1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one) 2. Open gnome shell overlay (hit super, or got to activity) 3. Search for a short string (3 chars let's say) that matches many files you know you have 4. Close the overlay (press super again, hit escape twice) 5. The nautilus process should stop using CPU once the overlay is closed [ Test case for GNOME-Shell and GNOME-Calculator ] 1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one) 2. Open gnome shell overlay (hit super, or got to activity) 3. Type "10!!!" 4. Close the overlay (press super again, hit escape twice) 5. The gnome-calculator process should stop using CPU once the overlay is closed [ Regression Potential ] Nautilus search results returned are missing elements when continuously update the search string, gnome-calculator computations via the shell might not work as expected. I have a maildir for my mail. My computer's name is "nightingale", and this name is in the filenames in the maildir. I have a lot of email! When I search for "tilix" to start a terminal after logging in, Nautilus goes crazy consuming CPU. This is because I have to type "ti" to type "tilix" and "ti" is a substring of "nightingale". This is submitted as a search string to the nautilus search provider and apparently isn't cancelled when I close the entry - I checked the GError and it's NULL. A similar thing happens with the ctrl-f search in nautilus itself. We talked about this on IRC and I provided some traces and stuff. Linking to the log to avoid having to fetch those out into files. :-) https://irclogs.ubuntu.com/2018/03/14/%23ubuntu-desktop.html#t15:58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1756826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857005] [NEW] gnome-calculator fails to build with vala 0.40.17
Public bug reported: [ Impact ] Gnome calculator doesn't build in bionic-proposed valac -C --vapidir /<>/vapi --pkg posix --pkg posix /<>/vapi/mpfr.vapi /<>/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg gtksourceview-3.0 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' --pkg glib-2.0 --pkg gio-2.0 --color=always --directory lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 ../lib/mpfr-glue.vala ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala ../lib/equation-parser.vala ../lib/financial.vala ../lib/function-manager.vala ../lib/math-equation.vala ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala ../lib/equation-parser.vala:79.9-79.43: error: Assignment: Cannot convert from `GLib.List' to `GLib.List' this.token_list = token_list.copy(); ^^^ Compilation failed: 1 error(s), 0 warning(s) [ Test case ] sbuild it and... Should work [ Regression potential ] Possible refcount issue and so mem-leak. ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gnome-calculator (Ubuntu Bionic) Importance: Critical Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Description changed: - valac -C --vapidir /<>/vapi --pkg posix --pkg posix /<>/vapi/mpfr.vapi /<>/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg gtksourceview-3.0 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' --pkg glib-2.0 --pkg gio-2.0 --color=always --directory lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 ../lib/mpfr-glue.vala ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala ../lib/equation-parser.vala ../lib/financial.vala ../lib/function-manager.vala ../lib/math-equation.vala ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala + [ Impact ] + + Gnome calculator doesn't build in bionic-proposed + + + valac -C --vapidir /<>/vapi --pkg posix --pkg posix /<>/vapi/mpfr.vapi /<>/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg gtksourceview-3.0 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' --pkg glib-2.0 --pkg gio-2.0 --color=always --directory lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 ../lib/mpfr-glue.vala ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala ../lib/equation-parser.vala ../lib/financial.vala ../lib/function-manager.vala ../lib/math-equation.vala ../lib/math-function.vala ../lib/math-variables.vala ../lib/number.vala ../lib/serializer.vala ../lib/unit.vala ../lib/equation-parser.vala:79.9-79.43: error: Assignment: Cannot convert from `GLib.List' to `GLib.List' this.token_list = token_list.copy(); ^^^ Compilation failed: 1 error(s), 0 warning(s) + + [ Test case ] + + sbuild it and... Should work + + [ Regression potential ] + + Possible refcount issue and so mem-leak. ** Also affects: gnome-calculator (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-calculator (Ubuntu) Status: In Progress => Fix Released ** Changed in: gnome-calculator (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-calculator (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: gnome-calculator (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-calculator (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1857005 Title: gnome-calculator fails to build with vala 0.40.17 Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-calculator source package in Bionic: In Progress Bug description: [ Impact ] Gnome calculator doesn't build in bionic-proposed valac -C --vapidir /<>/vapi --pkg posix --pkg posix /<>/vapi/mpfr.vapi /<>/vapi/mpc.vapi --pkg libxml-2.0 --pkg libsoup-2.4 --pkg gtksourceview-3.0 --pkg gtk+-3.0 --pkg gobject-2.0 --target-glib ' 2.40.0' --pkg glib-2.0 --pkg gio-2.0 --color=always --directory lib/76b5a35@@calculator@sta --basedir ../lib --library calculator --header lib/calculator.h --vapi ../calculator.vapi --target-glib 2.40.0 ../lib/mpfr-glue.vala ../lib/currency.vala ../lib/equation.vala ../lib/equation-lexer.vala ../lib/equation-parser.vala ../lib/financial.vala ../lib/function-manager.vala ../lib/math-equation.vala ../lib/math-function.vala
[Desktop-packages] [Bug 662840]
Is this supported in the latest version or not yet? I would also like to put in a request that this be added it might seem uncommon in the English speaking world, but in many many countries, writing emails in multiple languages happens regularly, and in those countries, the thunderbird single-language spellcheck simply isn't adequate. Also, what's the point of labelling this as a duplicate and arguing about it if neither this nor the duplicate are getting addressed 9 years later? It sounds more like an attempt to brush it under the carpet than anything else. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 381017]
This issue is noticed on Windows 10 as well. Windows is updated. TB re-installed and still doesn't work. Tested a new User Account and still the same. -- 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/381017 Title: Cannot drag attachment from mail attachment pane to desktop Status in One Hundred Papercuts: Triaged Status in SeaMonkey: Confirmed Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Ubuntu 9.04 Gnome Desktop 2.26.1 Thunderbird 2.0.0.21 This is regression introduced in Jaunty as it works in Intrepid. Dragging an attachment from the attachment pane to the desktop give the following error: == Error while copying There was an error getting information about "fetch>UID>.voicemail>1784". The specified location is not supported == Mail account is IMAP. This error was shown to seb128 and asac. The expected behavior is that the file is copied to the destination onto which it is dragged. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/381017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
I ended up making an extension that tries to detect the language used in each input field, then switches the spell checking to the correct language for that field: https://addons.mozilla.org/da/firefox/addon /automatic-spelling-language/ However, this isn't quite the same as spell checking in multiple languages at the same time, so I still hope this bug gets addressed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1583849] Re: Firefox > 44 is broken on all big-endian architectures
Launchpad has imported 18 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1269654. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-05-03T07:56:04+00:00 Martin Husemann wrote: Probably same or similar underlying issue as bug 986328, I see flashing display and lots of "crash reporter logs": Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 0 (t=4.86961)|[25246][GFX1]: Unknown image format 0 (t=904.76)|[25242][GFX1]: coming from: #6 mozilla::gfx::GfxFormatToCairoFormat (format=format@entry=mozilla::gfx::SurfaceFormat::B8G8R8A8) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/HelpersCairo.h:163 #7 0xf3751e84 in GfxFormatToCairoFormat (format=mozilla::gfx::SurfaceFormat::B8G8R8A8) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/HelpersCairo.h:152 #8 mozilla::gfx::CreateSubImageForData (aData=, aRect=..., aStride=, aFormat=) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:283 #9 0xf37521fc in mozilla::gfx::GetCairoSurfaceForSourceSurface (aSurface=, aExistingOnly=aExistingOnly@entry=false, aSubImage=...) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:384 #10 0xf3752684 in mozilla::gfx::GfxPatternToCairoPattern (aPattern=..., aAlpha=, aTransform=...) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:507 #11 0xf3752efc in mozilla::gfx::DrawTargetCairo::DrawPattern (this=this@entry=0xdc662520, aPattern=..., aStrokeOptions=..., aOptions=..., aDrawType=aDrawType@entry=mozilla::gfx::DrawTargetCairo::DRAW_FILL, aPathBoundsClip=) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:961 #12 0xf3754d74 in mozilla::gfx::DrawTargetCairo::FillRect (this=0xdc662520, aRect=..., aPattern=..., aOptions=...) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/2d/DrawTargetCairo.cpp:1057 #13 0xf387c000 in gfxSurfaceDrawable::DrawInternal (this=this@entry=0xdda47100, aDrawTarget=aDrawTarget@entry=0xdc662520, aOp=aOp@entry=mozilla::gfx::CompositionOp::OP_OVER, aAntialiasMode=, aFillRect=..., aSamplingRect=..., aExtendMode=, aFilter=, aOpacity=, aTransform=...) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/thebes/gfxDrawable.cpp:106 #14 0xf387c23c in gfxSurfaceDrawable::Draw (this=this@entry=0xdda47100, aContext=aContext@entry=0xdc776e80, aFillRect=..., aExtendMode=aExtendMode@entry=mozilla::gfx::ExtendMode::CLAMP, aFilter=@0x81a8: mozilla::gfx::Filter::GOOD, aOpacity=, aTransform=...) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/thebes/gfxDrawable.cpp:77 #15 0xf38da684 in gfxUtils::DrawPixelSnapped (aContext=aContext@entry=0xdc776e80, aDrawable=, aImageSize=..., aRegion=..., aFormat=, aFilter=aFilter@entry=mozilla::gfx::Filter::GOOD, aImageFlags=, aOpacity=1) at /usr/pkgobj/www/firefox/work/firefox-46.0/gfx/thebes/gfxUtils.cpp:694 #16 0xf3910c7c in mozilla::image::imgFrame::Draw (this=0xe6f36480, aContext=aContext@entry=0xdc776e80, aRegion=..., aFilter=aFilter@entry=mozilla::gfx::Filter::GOOD, aImageFlags=aImageFlags@entry=96) at /usr/pkgobj/www/firefox/work/firefox-46.0/image/imgFrame.cpp:605 #17 0xf38eca9c in mozilla::image::RasterImage::DrawInternal(mozilla::image::DrawableFrameRef&&, gfxContext*, mozilla::gfx::IntSizeTyped const&, mozilla::image::ImageRegion const&, mozilla::gfx::Filter, unsigned int) (this=this@entry=0xdda42320, aFrameRef=aFrameRef@entry=, aContext=aContext@entry=0xdc776e80, aSize=..., aRegion=..., aFilter=aFilter@entry=mozilla::gfx::Filter::GOOD, aFlags=96) at /usr/pkgobj/www/firefox/work/firefox-46.0/image/RasterImage.cpp:1460 #18 0xf38ecc34 in mozilla::image::RasterImage::Draw (this=0xdda42320, aContext=0xdc776e80, aSize=..., aRegion=..., aWhichFrame=, aFilter=, aFlags=96) at /usr/pkgobj/www/firefox/work/firefox-46.0/image/RasterImage.cpp:1526 #19 0xf4bd1f54 in DrawImageInternal (aContext=..., aPresContext=aPresContext@entry=0xe09ac800, aImage=0xdda42320, aGraphicsFilter=aGraphicsFilter@entry=mozilla::gfx::Filter::GOOD, aDest=..., aFill=..., aAnchor=..., aDirty=..., aSVGContext=0x0, aImageFlags=96, aExtendMode=mozilla::gfx::ExtendMode::CLAMP) at /usr/pkgobj/www/firefox/work/firefox-46.0/layout/base/nsLayoutUtils.cpp:6467 #20 0xf4bd2dfc in nsLayoutUtils::DrawSingleImage (aContext=..., aPresContext=aPresContext@entry=0xe09ac800, aImage=aImage@entry=0xdda42320, aGraphicsFilter=, aDest=..., aDirty=...,
[Desktop-packages] [Bug 455130]
> Simply move "Sort by->Threaded/Unthreaded" options to the Threads submenu That would be great for usability! -- 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/455130 Title: Changing from threaded to unthreaded view should be doable from the View->Threads menu Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird I put a folder in thread view by going to View->Threads->Unread, however I was unable to figure out how to go back to normal. I ultimately had to google the answer, and found many forum posts from users with similar issues (eg http://www.linuxquestions.org/questions /linux-desktop-74/how-to-turn-off-threads-view-in-thunderbird- inbox.-477859/) It turns out that the way to do this is in a different option, Sort By. Sort By is already fairly long, so a much more intuitive place for threaded/unthreaded option would be in the threads submenu. ProblemType: Bug Architecture: amd64 Date: Sun Oct 18 20:29:42 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: thunderbird 2.0.0.23+build1+nobinonly-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: thunderbird Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/455130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843044]
If NSS was built with the FIPS options enabled (`./build.sh --enable- fips`), and is then used with a database set to FIPS mode (`modutil -fips true -dbdir dir`), then Firefox should automatically also go into FIPS mode. -- 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/1843044 Title: firefox crashes on a FIPS enabled machine Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since firefox with bundled nss is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
(In reply to Ryan VanderMeulen [:RyanVM] from comment #13) > Looks like this grafts cleanly to ESR68 - did you want to nominate it for > uplift? Yes, let's do it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846877]
(In reply to Jorg K (GMT+1) (PTO to 15th Dec 2019, sporadically reading bugmail) from comment #1) > Typically those outlook.office365.com accounts don't have IMAP enabled, so > you need to use an add-on to connect via their Exchange protocol. Well IMAP is available by default. In this case (like bug 1598861) IMAP should be completely useable, per their instructions at https://www.imperial.ac.uk/admin-services/ict/self-service/connect- communicate/email/use/thunderbird/ -- 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/1846877 Title: Thunderbird provides no way to interact with the interface after adding an account. Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: New Bug description: Hi, I’ve tried to add an account from an Office account. The default suggestion from Thunderbird is to use Owl, a paid add-on, which is probably the best solution for non-technical users. I however am a technical user and don’t mind just setting what I’m being asked to do here: https://www.imperial.ac.uk/admin-services/ict/self-service/connect-communicate/email/use/thunderbird/ After all the setting done, I just click on the button “Done”. What I expected: Thunderbird closing the setting window and adding the account. What I got: Thunderbird not closing the setting window, but greying all its buttons but “Cancel”. After waiting some time, still the same. I eventually clicked on “Cancel”. The account was not added, but the new SMTP was added. It seems that the addition the new account stopped in the middle of the process, and that Thunderbird did not catch the error or whatever happened. Regards, Martin. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:60.8.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2009 F pulseaudio BuildID: 20190705191649 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 12:00:38 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-28 (37 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.6 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705191649 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07C17G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd07/23/2019:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn07C17G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5540 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
Comment on attachment 9104623
Bug 1590984 - Use poll() instead of select() in WebRTC code r=drno
### ESR Uplift Approval Request
* **If this is not a sec:{high,crit} bug, please state case for ESR
consideration**: This fixes a crash that can easily occur when using WebRTC.
* **User impact if declined**: Firefox may crash when using WebRTC; this will
happen independently of the user since it's triggered by the file descriptor
numbers used by the WebRTC devices (camera, microphone, etc...).
* **Fix Landed on Version**: 72
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: The fix
is small and almost mechanical and the patch has been in nightly and then beta
for two months now without causing regressions.
* **String or UUID changes made by this patch**: None
--
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/1849615
Title:
WebRTC-related crashes
Status in Mozilla Firefox:
Fix Released
Status in firefox package in Ubuntu:
Fix Committed
Bug description:
In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
version of Firefox 69.0.x. All the crashes are happening in the WebRTC
code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
checking safety is causing an abort. Is it possible that Firefox is
being built with a FD_SETSIZE value that's different from what's used
in libc?
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855997] Re: firefox www.google.com crashes when a firefox instance is already running and MOZ_ENABLE_WAYLAND is set to 1
Launchpad has imported 14 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1598995. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-11-25T04:03:50+00:00 Bjonnh-ff wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0 Steps to reproduce: - Open firefox (empty or used profile, no difference) - Open an URL from xdg or from a terminal (firefox-developer-edition https://www.mozilla.org) Actual results: Firefox Crashes and ask to restart. If I run firefox in a terminal I see: (firefoxdeveloperedition:496386): Gdk-WARNING **: 21:58:25.007: (../gtk/gdk/wayland/gdkwindow-wayland.c:810):buffer_release_callback: runtime check failed: (impl->staging_cairo_surface != cairo_surface) firefox: cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed. ExceptionHandler::GenerateDump cloned child 496921 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Expected results: Firefox should open a new tab Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/0 On 2019-11-25T04:11:39+00:00 Bjonnh-ff wrote: I tried with setting GDK_BACKEND=x11. As long as GDK_BACKEND is set for the new firefox call, when adding a new tab in a terminal it works. If I set GDK_BACKEND only for the initial firefox call, the subsequent calls in another terminal with GDK_BACKEND unset do not open a new tab, and after a few seconds a window saying that firefox is not responding appears. I will make firefox run in X11 mode for now. But I would be happy run any experiment that could help solve that issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/1 On 2019-11-25T04:17:16+00:00 Release-mgmt-account-bot wrote: [Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should belong to this component, but please revert this change in case of error. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/2 On 2019-11-26T13:32:37+00:00 Stransky wrote: Which desktop do you run? And do you see it also with nightly and release? Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/3 On 2019-11-28T18:47:02+00:00 Bjonnh-ff wrote: I do not see it with release. Desktop is gnome-shell. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/4 On 2019-11-28T18:59:12+00:00 Bjonnh-ff wrote: Doesn't happen with 20191128-firefox-72.0a1 . So I guess it has been fixed and will make its way in the DE? Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/5 On 2019-11-29T22:04:04+00:00 François Glais wrote: Isn't it expected to have some issues when meddling with GDK_BACKEND? Wouldn't the use of MOZ_ENABLE_WAYLAND=1 solve the issue? Or Firefox really tries to support both approaches? Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/6 On 2019-12-02T17:40:11+00:00 Bjonnh-ff wrote: I only used GDK_BACKEND to revert to x11 (and then solving the issue). GDK_BACKEND was unset in the issue reported. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1855997/comments/7 On 2019-12-04T21:59:57+00:00 Maxime de Roucy wrote: I can confirm this bug. Archlinux (uptodate) Mozilla Firefox 71.0 Same result with `MOZ_ENABLE_WAYLAND=1` or `GDK_BACKEND=wayland`. ``` max@mde-oxalide % MOZ_ENABLE_WAYLAND=1 firefox (firefox:2094): Gdk-WARNING **: 22:52:46.806: (../gtk/gdk/wayland/gdkwindow-wayland.c:810):buffer_release_callback: runtime check failed: (impl->staging_cairo_surface != cairo_surface) firefox: cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed. ExceptionHandler::GenerateDump cloned
[Desktop-packages] [Bug 1849615]
There's quite a few crashes coming from ESR68 on Debian. The patch is not large and low-risk, maybe we could uplift it. I'll see if it applies cleanly there. -- 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/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843044]
Alternatively to patching this, what is the modern way to enable FIPS in Firefox? I found these instructions: https://support.mozilla.org/en- US/kb/Configuring%20Firefox%20for%20FIPS%20140-2 but no matter what I do I can't get FIPS enabled - nor will "Enable FIPS" not be grayed out in Security Devices. -- 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/1843044 Title: firefox crashes on a FIPS enabled machine Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since firefox with bundled nss is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
Hi Gabriele, is qa needed here? And if so, could you please provide us some steps? Thanks! -- 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/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849615]
No testing is needed, thanks Catalin. -- 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/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened
Launchpad has imported 10 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1566053. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-07-15T13:38:27+00:00 Timj-8 wrote: Created attachment 9078136 Screenshot from 2019-07-15 15-33-31.png User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Steps to reproduce: 1. Start Firefox-68.0 (fresh profile) on Ubuntu 18.04.2 LTS with X11 on Linux 4.15.0-50-generic x86_64. (Note, this behaviour has also been observed with FF-67 versions.) 2. Start an application with libchromiumcontent >= 69.0.3497.128, e.g. by starting electron-4 (v69.0.3497.128) or electron-5 (v73.0.3683.121) or gooogle-chrome (v75.0.3770.100). Example: npm i electron@4 && node_modules/electron/dist/electron 3. The second application can be closed immediately, starting it is enough already to trigger FF. Note, libchromiumcontent v66.0.3359.181 (from electron-3) does *NOT* trigger FF. Actual results: Firefox uses up *all* CPU cores (8 here) at 100% for several seconds, observable e.g. via `htop` with thread view. Even exiting the libchromiumcontent using application immediately doesn't cure FF from overloading all CPU cores for several more seconds. If you happen to have `about:performance` opened during the overload situation, it will display *only* the "Task Manager" row, until it recovers from the overload situation, after that point it also lists the other rows for additional tabs again. Expected results: A) FF CPU usage should not be triggered by libchromiumcontent using applications. B) Tab "about:performance" should actually indicate where the CPU cycles are being wasted. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856624/comments/0 On 2019-07-23T10:55:55+00:00 Aflorinescu wrote: Thanks Tim for the report! Could you please be more specific with the steps to reproduce? npm i electron@4 && node_modules/electron/dist/electron opens for me: Electron v4.2.8Chromium v69.0.3497.128Node v10.11.0v8 v6.9.427.31-electron.0 Not sure how to trigger firefox to load when starting electron. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856624/comments/1 On 2019-07-23T18:02:21+00:00 Timj-8 wrote: (In reply to Adrian Florinescu [:adrian_sv] from comment #1) > Thanks Tim for the report! Could you please be more specific with the steps > to reproduce? > > npm i electron@4 && node_modules/electron/dist/electron opens for me: > Electron v4.2.8Chromium v69.0.3497.128Node v10.11.0v8 v6.9.427.31-electron.0 > > Not sure how to trigger firefox to load when starting electron. Hi Adrian, starting electrong (or a new version of google-chrome) is enough already. If you cannot notice the overload (are you using X11?) can you give it a shot under Ubuntu 18.04? Or let me know what dist you're testing on, so I can give that a shot as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856624/comments/2 On 2019-07-24T06:40:29+00:00 Aflorinescu wrote: Apologies, I've tested with Ubuntu 16.04 and I haven't noticed a Firefox process starting or any overload; that's why I assumed I was missing a step or two. Sure, will give it a try on Ubuntu 18.04 and post back if I get a positive result. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856624/comments/3 On 2019-08-02T09:09:30+00:00 Aflorinescu wrote: Slipped my todo list, adding a NI to get back to this. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856624/comments/4 On 2019-08-04T00:18:38+00:00 Timj-8 wrote: I'm still seeing massive CPU overload with Firefox 68.0.1 and e.g. electron-6. Attaching gdb to a running /usr/lib/firefox/firefox shows that, as soon as electron is started, the firefox process gets a *massive* amount of SIGSYS signals. Apparently all due to looking for font files. And each firefox process does gets these signals which seems to cause the overload, we're talking about ca 12000 signals on my system, probably due to the great number of font files I have installed here. Here are some excerpts from the debugging session: Thread 1 "Web Content" received signal SIGSYS, Bad system call. 0x7f8d210fd775 in __GI___xstat (vers=, name=0x7f8cff489aa0 "/etc/fonts/fonts.conf", buf=0x7fffe2acfb70) at
[Desktop-packages] [Bug 1849615]
Looks like this grafts cleanly to ESR68 - did you want to nominate it for uplift? -- 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/1849615 Title: WebRTC-related crashes Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: In Mozilla we've detected a spike of crashes in the Ubuntu-packaged version of Firefox 69.0.x. All the crashes are happening in the WebRTC code and specifically libc's FD_SET, FD_CLR and FD_ISSET range- checking safety is causing an abort. Is it possible that Firefox is being built with a FD_SETSIZE value that's different from what's used in libc? To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1849615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
