[Desktop-packages] [Bug 1827428] Re: [nvidia] Mouse cursor left frozen copy of itself
My bug got marked a duplicate of this one but with the latest change that might be wrong: It affected me on a machine with AMD graphics, not nVidia. BTW I recently tried it again on the offchance it had been fixed since (by re-enabling the xrandr scaling setting), and it had not. Also not fixed on 19.10 (which tbh is barely advanced from 19.04 at this stage). On the flipside, a different machine with only Intel graphics (Dell XPS 9370) did *not* show this problem. -- 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/1827428 Title: [nvidia] Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. 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] Is a directory: '/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] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP 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/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825940] Re: [graphics] Enable ICL
while ICL support is broken right now, and the version in proposed doesn't change that, I'll still mark this verified so that the current version can move to -updates I've verified ICL support without the softpin revert, and it's fine. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done ** Changed in: mesa (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1825940 Title: [graphics] Enable ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Bug description: [Impact] Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based on 18.04.3 graphics stack with linux-oem-osp1 kernel. [Test case] The usual desktop usage, graphics tests etc. [Regression potential] Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and it can't regress any currently running system. Mesa backports are limited to ICL, so they shouldn't regress earlier generations either. -- Original description: ICL graphics is not enabled in 19.04. if you want to use 19.04 on ICL platform, you need do like this Add kernel option i915.alpha_support=1 Target Release:19.10 Target Kernel: 5.2 Target Mesa: 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1825940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831700] Re: Mesa 19.0.8 stable release
** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831700 Title: Mesa 19.0.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Disco: Fix Committed Bug description: [Impact] 19.04 released with mesa 19.0.2. We need the last point release of the 19.0.x series in disco and backported for 18.04.3 in order to have the most robust base for the image. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] this is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
** Summary changed: - [nvidia] Mouse cursor left frozen copy of itself + Mouse cursor left frozen copy of itself -- 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/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. 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] Is a directory: '/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] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP 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/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828102] Re: Regression in ModemManager
No, I no longer use ubuntu, and don't have the patience to verify on a live cd. the patch works, it is literally fixing a one word typo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Bionic: Fix Released Status in modemmanager source package in Cosmic: Won't Fix Status in modemmanager source package in Disco: Fix Committed Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] ModemManager disconnects from CDMA modem after 30 sec failing to check signal status due to incorrect error handling [Test case] connect to a cdma device without an extra AT channel (Eg. Samsung brightside phone) and modemmanager will terminate the connection [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837399] Re: file selection does not work properly in 'search-results' mode
Thank you for your bug report, the problem is known upstream as https://gitlab.gnome.org/GNOME/nautilus/issues/365 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #365 https://gitlab.gnome.org/GNOME/nautilus/issues/365 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/365 Importance: Unknown Status: Unknown -- 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/1837399 Title: file selection does not work properly in 'search-results' mode Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: When nautilus is in 'search-results' mode, the first found file is displayed as selected (the file symbol and text have an orange background color) but apparently in fact it is not. (Copying the file does not work, or a file that was selected previously is copied instead.) How to reproduce: * open two tabs at different paths * use CTRL+F to enter 'find' mode * type some letters until a file is found * use CTRL+C to copy the first found file * switch to the second tab * use CTRL+V to paste the file What I expected to happen: * the file should be copied to the second tab What happened instead: * the file was not copied or a different file is copied instead Also when using CTRL+left click to select addition files, these are also displayed as selected, but nothing is copied. When using SHIFT instead, the behaviour is a little bit different, as you have to click two times for the files to be selected, but then all files are copied correctly. Workaround: * unselect the first found file after searching by clicking into the white * select the file(s) again * copy works as expected Nautilus version: 3.26.4 Ubuntu version: 18.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1837399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837428] Re: /usr/bin/nautilus-desktop:11:gdk_x11_device_manager_xi2_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event:_gdk_x11_display_queue
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) -- 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/1837428 Title: /usr/bin/nautilus- desktop:11:gdk_x11_device_manager_xi2_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event:_gdk_x11_display_queue_events:gdk_display_get_event Status in gtk+3.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu9, the problem page at https://errors.ubuntu.com/problem/536dbb166a16f5aca72158c1d0b706ac0da76625 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/gtk+3.0/+bug/1837428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836091] Re: Nautilus does not allow thumbnail for image size above 4096 KiB
Thanks, closing the bug then! ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- 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/1836091 Title: Nautilus does not allow thumbnail for image size above 4096 KiB Status in nautilus package in Ubuntu: Fix Released Bug description: In Ubuntu 18.10, Nautilus doesn't allow thumbnail size for image above 4096KiB. In preference pane, it is not possible to increase value above 4096. This is a regression, because it was possible before. By the way, whatever the value of dconf property org/gnome/nautilus/preferences /thumbnail-limit, if it is above 4096, Nautilus will not observe it (Setting the max image size for thumbnail generation in Nautilus preference pane is correctly changing org/gnome/nautilus/preferences /thumbnail-limit) Other funny things : the default value for org/gnome/nautilus/preferences/thumbnail-limit is 10MiB, so if it is at default value, Nautilus is showing (and observing) its hard-coded max of "4096" (4MiB) ! No workaround found as there is no anwser to this question: https://askubuntu.com/questions/1140576/nautilus-doesn-allow-thumbnail-for-image-size-above-4096-kib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1836091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
A bit more detail to reproduce this that I think was missed out before: It happens when the configured desktop mode/scaling is set to a fractional value. You can have that experimental xrandr setting set, but be configured to scaling of 100% or 200% (but see below on latter) and you won't see this problem. Set it to 150%, log out, log in again, you should see it. That applies to my experience anyway on the AMD graphics system. NB: Today when I tried to confirm this, I found that it would ignore my setting scaling to 200% on login, and would instead go in as if it was 100%, which would also be what it showed in the display settings dialogue itself. I'm pretty sure that wasn't the case earlier. I am able to select and use 200% in the session, it just won't be remembered. This sounds like a separate problem though. The problem *here* is what happens when scaling is set to a fractional value like 150% (which it does seem to have no problem remembering). It also means that a kind of workaround is to set scaling to 200% or 100% before logging out, then set it back to the 150% you want after logging in again. The problem is only when you're logging in and the setting is already fractional, so the switch in resolution happens during login. -- 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/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. 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] Is a directory: '/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] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP 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
[Desktop-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
** Bug watch added: bugzilla.gnome.org/ #776147 https://bugzilla.gnome.org/show_bug.cgi?id=776147 ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=776147 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Released Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838179] Re: gnome-system-monitor snap segfaults
The issue is due to those invalid permissions which make the initial setup fail What's the output of those commands? $ ls -ld /home/vyzivus/snap/gnome-system-monitor/100/ $ ls -l /home/vyzivus/snap/gnome-system-monitor/100/ ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1838179 Title: gnome-system-monitor snap segfaults Status in gnome-system-monitor package in Ubuntu: Incomplete Bug description: I have gnome-system-monitor installed as a snap. It never starts for me - it always segfaults. $ snap info gnome-system-monitor name: gnome-system-monitor summary: System Monitor publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bugs?field.tag=snap license: unset description: | GNOME System Monitor is a GNOME process viewer and system monitor with an attractive, easy-to-use interface, It has features, such as a tree view for process dependencies, icons for processes, the ability to hide processes that you don't want to see, graphical time histories of CPU/memory/swap usage, the ability to kill/renice processes needing root access, as well as the standard features that you might expect from a process viewer. commands: - gnome-system-monitor snap-id: 9BTClmjz31r0UltmbJ5nnGe0Xm1AzfMp tracking: stable/ubuntu-18.10 refresh-date: 18 days ago, at 23:46 EEST channels: stable:3.32.1-3-g0ea89b4922 2019-07-09 (100) 3MB - candidate: 3.32.1-3-g0ea89b4922 2019-07-09 (100) 3MB - beta: ↑ edge: ↑ installed: 3.32.1-3-g0ea89b4922(100) 3MB - $ gnome-system-monitor mkdir: cannot create directory '/home/vyzivus/snap/gnome-system-monitor/100/.config': Permission denied mkdir: cannot create directory '/home/vyzivus/snap/gnome-system-monitor/100/.local': Permission denied /snap/gnome-system-monitor/100/bin/desktop-launch: line 246: /home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.dirs: No such file or directory cp: cannot create regular file '/home/vyzivus/snap/gnome-system-monitor/100/.config': Permission denied /snap/gnome-system-monitor/100/bin/desktop-launch: line 249: /home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.dirs.md5sum: No such file or directory /snap/gnome-system-monitor/100/bin/desktop-launch: line 249: /home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.locale.md5sum: No such file or directory Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Desktop Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Downloads Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Templates Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Public Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Documents Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Music Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Pictures Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Videos realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory realpath: '': No such file or directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.config’: Permission denied /snap/gnome-system-monitor/100/bin/desktop-launch: line 381: /home/vyzivus/snap/gnome-system-monitor/100/.config/fontconfig/fonts.conf: No such file or directory ln: failed to create symbolic link '/home/vyzivus/snap/gnome-system-monitor/100/.local/share': No such file or directory ln: failed to create symbolic link '/home/vyzivus/snap/gnome-system-monitor/100/.themes': Permission denied mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied ln: target '/home/vyzivus/snap/gnome-system-monitor/100/.local/share/glib-2.0/schemas' is not a directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.config’: Permission denied ln: failed to create symbolic link '/home/vyzivus/snap/gnome-system-monitor/100/.config/dconf': No such file or directory mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied mkdir: cannot create directory ‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied ln: target '/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/DMZ-Black' is no
[Desktop-packages] [Bug 1837452] Re: segfault at 0 {...} error 4 in libgio-2.0.so.0.5600.4
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Changed in: shotwell (Ubuntu)
Importance: Undecided => Low
** Changed in: shotwell (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1837452
Title:
segfault at 0 {...} error 4 in libgio-2.0.so.0.5600.4
Status in shotwell package in Ubuntu:
Invalid
Bug description:
Shotwell segfaults every time I close it.
shotwell[11186]: segfault at 0 ip 7f33b2e3b7e0 sp 7aeabaa8
error 4 in libgio-2.0.so.0.5600.4[7f33b2d9+195000]
I have no idea why.
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(0x7fc9005ed000)
Apport has automatically reported the crash.
ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: called for pid 11186,
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: executable:
/usr/bin/shotwell (command line "shotwell /tmp/P7200010.JPG")
ERROR: apport (pid 11201) Sat Jul 20 11:58:50 2019: debug: session gdbus
call: (true,)
ERROR: apport (pid 11201) Sat Jul 20 11:59:05 2019: wrote report
/var/crash/_usr_bin_shotwell.1000.crash
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: shotwell 0.28.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Jul 22 19:54:12 2019
InstallationDate: Installed on 2019-06-09 (42 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1837452/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838132] Re: file browser hangs system for several seconds on save/load/exit
Thank you for your bug report. That's not specific to nautilus then? Could you add your 'journalctl -b 0' log after getting the issue? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1838132 Title: file browser hangs system for several seconds on save/load/exit Status in nautilus package in Ubuntu: Incomplete Bug description: For the last month, saving a file or printing a file from my browser or any other application, or even trying to quit the file browser without doing anything, causes the file dialog and the entire system to hang (become unresponsive) for several seconds. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 05:53:20 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (183 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-05-29 (58 days ago) usr_lib_nautilus: dropbox 2018.11.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835936] Re: gnome-control-center crash ubuntu 18.04.2
Ok, thank you for the update! -- 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/1835936 Title: gnome-control-center crash ubuntu 18.04.2 Status in gnome-control-center package in Ubuntu: Invalid Bug description: Ubuntu 18.04.02 fresh installed on Virtualbox 6.0.8 including Guest Additions on host Mac Pro running 10.14.5 Mojave in April 2019. Ubuntu system has latest patches EXCEPT mutter-2 (which cause login GUI to fail after reboot). crash logs for gnome-control-center, gnome-shell and seahorse attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839068] [NEW] Wrong password every time after changing login password
Public bug reported: After changing password with "passwd" command it's not possible to open the keyring anymore. Each time I have the dialog that open asking me for the password. I've tried to enter the old password and the new password but nothing changes. I've changed back the login password to the old one but even in that case the seahorse password dialog opens saying that the login password doesn't matches the keyring password and asking me to enter it again. I need a procedure to change the keyring password without login into the seahorse, so that it can match the login password of Ubuntu. Ubuntu 18.04.2 LTS Seahorse 3.20.0-5 from http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1839068 Title: Wrong password every time after changing login password Status in seahorse package in Ubuntu: New Bug description: After changing password with "passwd" command it's not possible to open the keyring anymore. Each time I have the dialog that open asking me for the password. I've tried to enter the old password and the new password but nothing changes. I've changed back the login password to the old one but even in that case the seahorse password dialog opens saying that the login password doesn't matches the keyring password and asking me to enter it again. I need a procedure to change the keyring password without login into the seahorse, so that it can match the login password of Ubuntu. Ubuntu 18.04.2 LTS Seahorse 3.20.0-5 from http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1839068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838902] Re: GNOME Control Center sticks when I add other keyboard in settings
Could you give a bit more details on the issue. What do you mean by "stick"? That it takes some time to load and freeze while doing so? ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Triaged -- 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/1838902 Title: GNOME Control Center sticks when I add other keyboard in settings Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: But then the list of languages opens and I can choose needing variant. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 22:30:32 2019 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1838902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837448] Re: gnome-keyring-daemon constantly hangs on fresh ubuntu 19.04 install
Great, thanks for the update, closing! ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-keyring (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1837448 Title: gnome-keyring-daemon constantly hangs on fresh ubuntu 19.04 install Status in gnome-keyring package in Ubuntu: Fix Released Bug description: fresh install of ubuntu 19.04, and using all my ssh keys I had before the reinstall, anything with ssh just hangs when gnome-keyring-daemon is providing the keys: ``` ssh -v my-test-host [...] debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks [ hangs here forever ] ``` it appears to be setting at least some of the environment vars incorrectly, with the agent pid pointing to nothing: ``` $ export | grep SSH declare -x SSH_AGENT_PID="3300" declare -x SSH_AUTH_SOCK="/run/user/1000/keyring/ssh" $ ps auxf | grep 3300 tessa 5950 0.0 0.0 8856 760 pts/0S+ 11:50 0:00 | | \_ grep --color=auto 3300 $ ps axf | grep keyring 2642 pts/0S+ 0:00 | | \_ grep --color=auto keyring 27662 ?S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh 6177 ?Sl44:10 /usr/bin/gnome-keyring-daemon --daemonize --login $ ls -lah /run/user/1000/keyring/ total 0 drwx-- 2 tessa tessa 120 Jul 22 10:54 . drwx-- 11 tessa tessa 260 Jul 22 10:47 .. srwxrwxr-x 1 tessa tessa 0 Jul 22 10:54 control srwxrwxr-x 1 tessa tessa 0 Jul 22 10:54 pkcs11 srw--- 1 tessa tessa 0 Jul 22 10:47 .ssh srwxrwxr-x 1 tessa tessa 0 Jul 22 10:54 ssh ``` if I set the SSH_AUTH_SOCK to the path being set by ssh-agent instead of gnome-keyring-daemon, things work correctly. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 22 11:02:52 2019 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1837448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839006] Re: No sound is playing from this laptop
the issue is probably not from the UI but from pulseaudio/alsa/kernel ** Package changed: gnome-control-center (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: New Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
this will be fixed in the kernel ** Changed in: xorg-server (Ubuntu) Status: Triaged => Invalid ** Changed in: xorg-server (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in HWE Next: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839097] [NEW] [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
Public bug reported: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic drivers radeon 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/1839097 Title: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in xorg package in Ubuntu: New Bug description: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1839097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https
[Desktop-packages] [Bug 1839111] [NEW] Please merge libvdpau 1.2-1 (main) from Debian unstable (main)
Public bug reported: Please merge libvdpau 1.2-1 (main) from Debian unstable (main) ** Affects: libvdpau (Ubuntu) Importance: Wishlist Assignee: Alberto Milone (albertomilone) Status: In Progress ** Changed in: libvdpau (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1839111 Title: Please merge libvdpau 1.2-1 (main) from Debian unstable (main) Status in libvdpau package in Ubuntu: In Progress Bug description: Please merge libvdpau 1.2-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1839111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839097] Re: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
** Package changed: xorg (Ubuntu) => linux (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/1839097 Title: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in linux package in Ubuntu: New Bug description: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
Can you tell where in the log Wi-Fi is failing? I see only a lot of errors of GNOME shell, not of Wi-Fi. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: Incomplete Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED b
[Desktop-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
I also encountered that bug in 19.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Won't Fix Status in gnome-session source package in Zesty: Won't Fix Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1829113] Re: CUPS says job completed but the PDF doesnt print, wile printing via lpr works
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1829113 Title: CUPS says job completed but the PDF doesnt print, wile printing via lpr works Status in cups package in Ubuntu: Confirmed Bug description: Driver installed from manufacturer's website, test page prints OK on USB printer Brother DCP-1510. When I send the PDF document for printing, the printer displays "Receiving data" but then nothing prints. CUPS says "job completed" and I cant discern any useful errors in /var/log/cups/error_log Printing the same document via lpr worked -- the document printed fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.4 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 15 12:08:27 2019 InstallationDate: Installed on 2019-04-12 (32 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: device for Brother-DCP-1510-series: usb://Brother/DCP-1510%20series?serial=E72065A8N348435 MachineType: Hewlett-Packard HP Z420 Workstation Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother-DCP-1510-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother-DCP-1510-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=b3062c40-ce3c-4a67-9e83-4bca7967e954 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v02.55 dmi.board.asset.tag: JPWH505625 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: JPWH505625 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v02.55:bd02/07/2013:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: LJ449AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1559228] Re: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all
I am using Samsung Galaxy Book with ALC298 card and there is no sound at all. -- 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/1559228 Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a Lenovo P50 with the docking station. When the laptop is plugged into the docking station sound will not play out the external port. An lspci -n gives me: 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) I have updated the bios. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bgoodman 1698 F pulseaudio /dev/snd/pcmC0D0p: bgoodman 1698 F...m pulseaudio /dev/snd/controlC0: bgoodman 1698 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 18 12:08:52 2016 InstallationDate: Installed on 2016-03-17 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bgoodman 1698 F pulseaudio /dev/snd/pcmC0D0p: bgoodman 1698 F...m pulseaudio /dev/snd/controlC0: bgoodman 1698 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [20ENCTO1WW, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET45W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET45W(1.19):bd02/22/2016:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-03-18T12:01:21.161389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1559228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1838902] Re: GNOME Control Center sticks when I add other keyboard in settings
That it takes some time to load and freeze while doing so? Yes, it is. I meant this. вт, 6 авг. 2019 г., 11:45 Sebastien Bacher : > Could you give a bit more details on the issue. What do you mean by > "stick"? That it takes some time to load and freeze while doing so? > > ** Changed in: gnome-control-center (Ubuntu) >Status: Confirmed => Triaged > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1838902 > > Title: > GNOME Control Center sticks when I add other keyboard in settings > > Status in gnome-control-center: > Unknown > Status in gnome-control-center package in Ubuntu: > Triaged > > Bug description: > But then the list of languages opens and I can choose needing variant. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-control-center 1:3.32.2-1ubuntu4 > ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 > Uname: Linux 5.2.0-8-generic x86_64 > ApportVersion: 2.20.11-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Aug 4 22:30:32 2019 > InstallationDate: Installed on 2019-08-04 (0 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-control-center/+bug/1838902/+subscriptions > -- 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/1838902 Title: GNOME Control Center sticks when I add other keyboard in settings Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: But then the list of languages opens and I can choose needing variant. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 22:30:32 2019 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1838902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835622] Re: Cannot start desktop session with compositor enabled
@Timo: I could not test this earlier because I was on holidays. So finally here are the results: 1. (If I understand correctly the fix from bug 1836721 is already in bionic-updates) I upgraded all packages, but the bug still persists (error message "xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed.") 2. So I enabled ppa:ubuntu-x-swat/updates and upgraded all packages, but the error still persists. >From my point of view it seems this bug is not fixed by bug 1836721. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835622 Title: Cannot start desktop session with compositor enabled Status in Xfwm4: Invalid Status in mesa package in Ubuntu: New Status in xfwm4 package in Ubuntu: Invalid Bug description: I cannot login to the Xfce desktop session anymore. in ~/.xsession- errors there's the message: xfwm4: ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed. Earlier today Mesa was upgraded via bionic-updates from 18.2 to 19.0. I'm running Xubuntu 18.04 and I'm also using the Xubuntu Staging PPA with xfwm4 4.13.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
Any further progress on this? Why have a bug reporter if bugs are going to sit out here forever unresolved. This is a definite issue with the metadata in the fonts. Easily fixable. -- 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/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" Status in One Hundred Papercuts: In Progress Status in Ubuntu Font Family: In Progress Status in chromium-browser package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: In Progress Bug description: After upgrading from Vivid to Wily, pages using the "Ubuntu light" font actually renders with a weight heavier than the regular one in web pages. This happens with Chrome/Chromium and also the Ubuntu browser. After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in place of 0.83-0ubuntu1), the issue is fixed. See the attached screenshot showing the result seen browing https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ttf-ubuntu-font-family 0.83-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 17:55:19 2015 Dependencies: InstallationDate: Installed on 2014-10-14 (382 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users which impacts the usability and visual design. The new version of font package (0.831) corrects the relationship between Light and Medium weight to follow the commonly used naming standards: Ubuntu Light Light Light Italic UbuntuRegular Italic BoldBold Italic Ubuntu Medium Medium Medium Italic Ubuntu Condensed Regular Ubuntu Mono Regular Italic BoldBold Italic TEST CASE: in 15.10, go to https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu If the Light weight renders heavier than Normal weight, the bug is in place REGRESSION POTENTIAL 0.831 was tested by manually running in 15.10 and no regression was noticed, while the bug was fixed. The potential for regression is small. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436942] Re: /usr/bin/file-roller:11:g_action_map_lookup_action:fr_window_enable_action:fr_window_update_paste_command_sensitivity:fr_window_update_paste_command_sensitivity:fr
*** This bug is a duplicate of bug 1725017 *** https://bugs.launchpad.net/bugs/1725017 ** This bug has been marked a duplicate of bug 1725017 file-roller crashed with SIGSEGV in g_action_map_lookup_action() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1436942 Title: /usr/bin/file- roller:11:g_action_map_lookup_action:fr_window_enable_action:fr_window_update_paste_command_sensitivity:fr_window_update_paste_command_sensitivity:fr_window_update_sensitivity Status in File Roller: Confirmed Status in file-roller package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding file-roller. This problem was most recently seen with version 3.14.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/8a4da79ec26dfb3201e6a8a68f2bbfd1c3b92965 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1436942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838249] Re: crash on startup
Apologies for the radio silence on this issue thus far. Over the next 2 weeks we'll be rolling out new versions of LibreOffice across the board. Once that's done, we will come back to this. Thank you for your patience. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1838249 Title: crash on startup Status in libreoffice package in Ubuntu: New Bug description: libreoffice --norestore --safe-mode dbus[16783]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3ba93)[0x7f62a2538a93] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3bca3)[0x7f62a2538ca3] /lib/x86_64-linux-gnu/libc.so.6(+0x43f60)[0x7f62a2329f60] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f62a2329ed7] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f62a230b535] /lib/x86_64-linux-gnu/libdbus-1.so.3(+0xb78d)[0x7f62a19e578d] /lib/x86_64-linux-gnu/libdbus-1.so.3(_dbus_strdup+0x0)[0x7f62a1a07380] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_iter_append_basic+0x369)[0x7f62a19f8a79] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args_valist+0x154)[0x7f62a19f93d4] /lib/x86_64-linux-gnu/libdbus-1.so.3(dbus_message_append_args+0x99)[0x7f62a19f9669] /usr/lib/x86_64-linux-gnu/libavahi-client.so.3(avahi_record_browser_new+0x17c)[0x7f629d11ac9c] /usr/lib/x86_64-linux-gnu/libcups.so.2(+0x28f1e)[0x7f62a0537f1e] /usr/lib/x86_64-linux-gnu/libcups.so.2(cupsGetDests2+0x94)[0x7f62a05380b4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e97a17)[0x7f62a53f0a17] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3e6f8)[0x7f62a253b6f8] /lib/x86_64-linux-gnu/libpthread.so.0(+0x9182)[0x7f62a1a34182] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f62a2403b1f] --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-10-29 (273 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: libreoffice-core 1:6.2.5-0ubuntu0.19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Tags: disco Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-25 (95 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1838249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819082] Re: [snap] LibreOffice crashes after enabling OpenCL in the settings
Apologies for the radio silence on this issue thus far. Over the next 2 weeks we'll be rolling out new versions of LibreOffice across the board. Once that's done, we will come back to this. Thank you for your patience. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1819082 Title: [snap] LibreOffice crashes after enabling OpenCL in the settings Status in libreoffice package in Ubuntu: Confirmed Bug description: Reproduce steps --- 1. Enable OpenCL in settings 2. Click "Apply" 3. Choose "restart now" in the restart prompt Symptoms LibreOffice crash prompt appears and terminates with exit status 79. After restarting it the OpenCL option remains untoggled. Version --- ``` $ snap info libreoffice name:libreoffice snap-id: CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v tracking: candidate refresh-date: today at 02:41 CST channels: stable:6.2.0.3 2019-02-13 (104) 507MB - candidate: 6.2.1.2 2019-03-02 (106) 507MB - beta: 6.2.0.3 2019-01-31 (103) 505MB - edge: ↑ installed: 6.2.1.2(106) 507MB - ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837757] Re: adding extension caused libreoffice to fail loading on restart
Apologies for the radio silence on this issue thus far. Over the next 2 weeks we'll be rolling out new versions of LibreOffice across the board. Once that's done, we will come back to this. Thank you for your patience. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1837757 Title: adding extension caused libreoffice to fail loading on restart Status in libreoffice package in Ubuntu: New Bug description: I had writer, calc and impress open. I clicked on the Language Tool extension here: https://extensions.libreoffice.org/extensions/languagetool/4.6 I took the choice to add it to Libreoffice since it was open. The dialogue then said to restart Libroffice. After closing, it would not restart. However, I just now clicked and downloaded the extension. After it downloaded, libreoffice began to restart. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-writer 1:6.2.5-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Wed Jul 24 11:42:41 2019 InstallationDate: Installed on 2019-01-11 (194 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1837757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725017] Re: file-roller crashed with SIGSEGV in g_action_map_lookup_action()
** Bug watch added: gitlab.gnome.org/GNOME/file-roller/issues #31 https://gitlab.gnome.org/GNOME/file-roller/issues/31 ** Changed in: file-roller Importance: Medium => Unknown ** Changed in: file-roller Status: Confirmed => Unknown ** Changed in: file-roller Remote watch: GNOME Bug Tracker #746829 => gitlab.gnome.org/GNOME/file-roller/issues #31 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1725017 Title: file-roller crashed with SIGSEGV in g_action_map_lookup_action() Status in File Roller: Unknown Status in file-roller package in Ubuntu: Triaged Bug description: Description: Ubuntu 17.10 Release: 17.10 file-roller: Installed: 3.26.1-0ubuntu1 Candidate: 3.26.1-0ubuntu1 Version table: *** 3.26.1-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Don't know how this happned. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: file-roller 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 18:23:52 2017 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: file-roller /home/username/Downloads/discord-0.0.2.tar.gz SegvAnalysis: Segfault happened at: 0x7f4a0e78271c : mov0x10(%rax),%rax PC (0x7f4a0e78271c) ok source "0x10(%rax)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: g_action_map_lookup_action () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with SIGSEGV in g_action_map_lookup_action() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1725017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] Re: headerbar buttons can get hidden if left column is too narrow
** Attachment added: "Screenshot-20190806135742-897x641.png" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+attachment/5281175/+files/Screenshot-20190806135742-897x641.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: New Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] Re: headerbar buttons can get hidden if left column is too narrow
This is how I think it should be wide as minimum. Note however that I have buttons on the left, hence my suggestion of a dynamic minimum width. People who have them on the right shouldn't have unnecessary padding. ** Attachment added: "Screenshot-20190806135750-897x641.png" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+attachment/5281188/+files/Screenshot-20190806135750-897x641.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: New Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] [NEW] headerbar buttons can get hidden if left column is too narrow
Public bug reported: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot-20190806135639-909x641.png" https://bugs.launchpad.net/bugs/1839127/+attachment/5281170/+files/Screenshot-20190806135639-909x641.png ** Summary changed: - headerbar buttons can hide if too narrow column + headerbar buttons can get hidden if left column is too narrow -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: New Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839127] Re: headerbar buttons can get hidden if left column is too narrow
** Attachment added: "Screenshot-20190806135701-897x641.png" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+attachment/5281174/+files/Screenshot-20190806135701-897x641.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839127 Title: headerbar buttons can get hidden if left column is too narrow Status in gnome-disk-utility package in Ubuntu: New Bug description: Check the left column of gnome-disk-utility, you can reduce it in ways that hide the buttons contained within. I think other apps have some dynamically computed minimum width to avoid such behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 13:47:55 2019 InstallationDate: Installed on 2019-02-03 (183 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to eoan on 2019-07-21 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839136] [NEW] Temporary freeze / delay with some dialog windows
Public bug reported: Some dialog popups take a while to open, as if the system froze for a bit (even though journalctl -f doesn't show anything related) which is extremely annoying. Example: - the dialog shown if a file should be saved when trying to close a tab in Gedit - the popup confirmation dialog when using Shift + Delete in Nautilus - the dialog shown when trying to close a terminal that has a running process This does not happen every time, but I'm not sure what triggers it. I made a video showcasing the issue: https://streamable.com/xqjlf The first time I try to close a Gedit unsaved tab this issue happens, but the second time it does not happen. What I tried and did not solve this issue: - using modal or detached dialogs - disabling all Gnome Shell extensions (including those that ship with Ubuntu by default, by removing the packages) This seems related to using multiple monitors. I have two monitors, one using 2560x1080 resolution, and the other 19220x1080 (both with the default 100% scalx). When I mirrored the displays, this issue no longer happened. It only happens with extended (using the "Join Displays" option) display. To replicate, just click (focus) on other windows multiple times (on both monitors), then go to the window that causes these issues and it should happen, like I explained. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 14:10:26 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-10-17 (292 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- 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/1839136 Title: Temporary freeze / delay with some dialog windows Status in gnome-shell package in Ubuntu: New Bug description: Some dialog popups take a while to open, as if the system froze for a bit (even though journalctl -f doesn't show anything related) which is extremely annoying. Example: - the dialog shown if a file should be saved when trying to close a tab in Gedit - the popup confirmation dialog when using Shift + Delete in Nautilus - the dialog shown when trying to close a terminal that has a running process This does not happen every time, but I'm not sure what triggers it. I made a video showcasing the issue: https://streamable.com/xqjlf The first time I try to close a Gedit unsaved tab this issue happens, but the second time it does not happen. What I tried and did not solve this issue: - using modal or detached dialogs - disabling all Gnome Shell extensions (including those that ship with Ubuntu by default, by removing the packages) This seems related to using multiple monitors. I have two monitors, one using 2560x1080 resolution, and the other 19220x1080 (both with the default 100% scalx). When I mirrored the displays, this issue no longer happened. It only happens with extended (using the "Join Displays" option) display. To replicate, just click (focus) on other windows multiple times (on both monitors), then go to the window that causes these issues and it should happen, like I explained. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 14:10:26 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-10-17 (292 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1839136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 510562] Re: Mouse spinning wheel not working properly
Upstream bug was closed "RESOLVED OBSOLETE" on 2017-07-17 as working as expected with evince 3.26. No comments here for nearly 7 years and works for me with evince 3.28 and Ubuntu 18.04 so closing as fixed. ** Changed in: evince (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/510562 Title: Mouse spinning wheel not working properly Status in Evince: Expired Status in evince package in Ubuntu: Fix Released Bug description: Binary package hint: evince Using the spinning wheel of the mouse with the option "continuous" disabled I found a nasty bug in evice and that is easy to reproduce: * Put yourself in the first page of the document * Spin the wheel until the page view is forced to do an scroll * Go back using the wheel to the first page What is expected to happen is that the cursor in the page view of the right is in the first page and that in the right you are viewing the same page. What happened instead is that the page view is correct (the cursor is in the first page), but in the left you are now viewing the second page, which is obviously incorrect. When the window lost its focus evince finally shows the correct page (I discovered this trying to include a capture in the bug description) Ubuntu version: Ubuntu 9.10 (64 bits) Evince package: 2.28.1-0ubuntu1.2 ProblemType: Bug Architecture: amd64 Date: Thu Jan 21 10:11:17 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NonfreeKernelModules: nvidia Package: evince 2.28.1-0ubuntu1.2 ProcEnviron: LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: evince Uname: Linux 2.6.31-17-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/510562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838902] Re: GNOME Control Center sticks when I add other keyboard in settings
Could you describe what actions you do and what screen/UI element is slow to load exactly? -- 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/1838902 Title: GNOME Control Center sticks when I add other keyboard in settings Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: But then the list of languages opens and I can choose needing variant. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 22:30:32 2019 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1838902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 622004] Re: Rhythmbox does not remember column width
Issue is now being tracked at: https://gitlab.gnome.org/GNOME/rhythmbox/issues/409 ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #409 https://gitlab.gnome.org/GNOME/rhythmbox/issues/409 ** Changed in: rhythmbox Importance: Medium => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #460668 => GNOME Bug Tracker #627619 ** Tags added: bionic -- 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/622004 Title: Rhythmbox does not remember column width Status in One Hundred Papercuts: Triaged Status in Rhythmbox: Unknown Status in rhythmbox package in Ubuntu: Triaged Bug description: Binary package hint: rhythmbox Rhythmbox does not remember the column width that you set. Upon restart, all the columns in it goes back to some default width. This is annoying because I like to see the file location, which needs lots of space, so I make most of the other columns narrower. But every time I restart rhythmbox, I have to do this all over again. This bug has been around for a long time. I'm using Rhythmbox 0.12.8 on Ubuntu 10.04.1 (32bit). To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/622004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1038738] Re: Rhythmbox does not show the Library Location
Issue is now being tracked at: https://gitlab.gnome.org/GNOME/rhythmbox/issues/532 ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #532 https://gitlab.gnome.org/GNOME/rhythmbox/issues/532 ** Changed in: rhythmbox Importance: Wishlist => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #523162 => gitlab.gnome.org/GNOME/rhythmbox/issues #532 -- 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/1038738 Title: Rhythmbox does not show the Library Location Status in One Hundred Papercuts: Confirmed Status in Rhythmbox: Unknown Status in rhythmbox package in Ubuntu: Confirmed Bug description: Once again, I accidentally opened Rhythmbox and it started importing a lot of something—I don't know what. Since I prefer to have control over what parts of my computer Rhythmbox uses, I opened 'Rhythmbox Preferences' ▸ 'Music' with the intention of dissuading it from rampaging through whatever location it has defaulted to. Frustratingly, all Rhythmbox chooses to reveal to me about its automated behavior is: Music files are placed in: Multiple locations set When I click 'Browse' and open a location of my preference (~/sandbox), nothing changes. Rhythmbox still displays: Music files are placed in: Multiple locations set Even as I write this its progress bar is bouncing away, doing... something. I have no idea what it's doing. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia zfs zcommon znvpair zavl zunicode ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Aug 19 11:36:21 2012 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1038738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 301875] Re: rhythmbox doesn't play media files when you start em from nautilus
Upstream bug was closed "RESOLVED FIXED" on 2010-09-21 Confirmed working with rhythmbox 3.4.2 in Ubuntu 18.04 Closing as fixed. ** Changed in: rhythmbox (Ubuntu) Status: Triaged => 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/301875 Title: rhythmbox doesn't play media files when you start em from nautilus Status in Rhythmbox: Fix Released Status in rhythmbox package in Ubuntu: Fix Released Bug description: Binary package hint: rhythmbox when i choose rhytmbox as the default playbackapplication for mp3s in nautilus and open a file rhythmbox starts but doesn't play the tune, i have to click another time on the file. sometimes it starts to play BUT a completely different file. i'm using 8.10 and the packages are the newest from the repos To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/301875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 904390] Re: Error Jamendo plugin for rhythmbox loading catalogue
Upstream bug was closed "RESOLVED FIXED" on 2010-09-21 so fixed in Ubuntu some time ago. Cannot test as Jamendo support since removed. ** Changed in: rhythmbox (Ubuntu) Status: Triaged => 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/904390 Title: Error Jamendo plugin for rhythmbox loading catalogue Status in Rhythmbox: Fix Released Status in rhythmbox package in Ubuntu: Fix Released Bug description: Ubuntu 11.10 Rhythmbox 2.90.1 Open Rhythmbox, click jamendo on the left, it says it's loading catalogue... never ends. Running with -d noticed method get_url_chunks in file /usr/lib/rhythmbox/plugins/rb/Loader.py is the problem as it raises a "not implemented" exception on first line. See paste http://pastebin.com/fvsHPFYE To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/904390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: [SRU] Screen sharing panels abort using an non-existent vino gsettings key Status in unity-control-center package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in vino package in Ubuntu: Invalid Status in unity-control-center source package in Bionic: In Progress Status in unity-settings-daemon source package in Bionic: In Progress Bug description: *Impact This happens because Gnome removed that particular gsettings key. The removal did not happen with the ui removal but rather much later than that. That is why it doesn't work with the latest version of vino. As of now If users try to open the new sharing panel, unity-control- center will crash. This sort behavior is not desired on LTS release (18.04). Test Case 1) Go to unity-control-center 2) Click sharing (Remote desktop) * Regression potential None The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a 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/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1838902] Re: GNOME Control Center sticks when I add other keyboard in settings
"Add keyboard" -> "Other" (in the end of list). And after touch the button "Other" gnome-control-center will stick for some time. вт, 6 авг. 2019 г. в 15:11, Sebastien Bacher : > Could you describe what actions you do and what screen/UI element is > slow to load exactly? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1838902 > > Title: > GNOME Control Center sticks when I add other keyboard in settings > > Status in gnome-control-center: > Unknown > Status in gnome-control-center package in Ubuntu: > Triaged > > Bug description: > But then the list of languages opens and I can choose needing variant. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-control-center 1:3.32.2-1ubuntu4 > ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 > Uname: Linux 5.2.0-8-generic x86_64 > ApportVersion: 2.20.11-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Aug 4 22:30:32 2019 > InstallationDate: Installed on 2019-08-04 (0 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) > SourcePackage: gnome-control-center > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-control-center/+bug/1838902/+subscriptions > -- 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/1838902 Title: GNOME Control Center sticks when I add other keyboard in settings Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: But then the list of languages opens and I can choose needing variant. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.2-1ubuntu4 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 4 22:30:32 2019 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1838902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295925] Re: Rhythmbox displays the wrong album art
Upstream bug closed "RESOLVED FIXED" on 2015-03-13 Confirming fixed in rhythmbox 3.4.2 and Ubuntu 18.04 ** Changed in: rhythmbox (Ubuntu) Status: Confirmed => 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/1295925 Title: Rhythmbox displays the wrong album art Status in Rhythmbox: Fix Released Status in rhythmbox package in Ubuntu: Fix Released Bug description: Rhythmbox displays album art itself at the top of the window, among the controls. It also sends album art to notify-osd for display in notification bubbles, and in indicator-sound. Rhythmbox is using the wrong album art much of the time. In the instant case, the mp3 files have no embedded album art, so I would expect either the correct album art is downloaded, or none is displayed (default image or blank). Instead, album art is apparently picked randomly from my music collection. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Mar 21 23:17:25 2014 InstallationDate: Installed on 2013-01-12 (433 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: Upgraded to saucy on 2013-10-23 (149 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1295925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key
@Khurshid: My turn to be late.. Yes, the u-c-c part is merged, but it's not uploaded. Some sponsor needs to do that - maybe they can pick the changelog entry from disco: https://launchpad.net/ubuntu/+source/unity-control- center/15.04.0+19.04.20181122-0ubuntu1 I don't have access to anything Unity. But I would suggest that you skip the branch and simply prepare a debdiff on top of the uploaded unity- settings-daemon bionic source. A sponsor can then upload the debdiff. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: [SRU] Screen sharing panels abort using an non-existent vino gsettings key Status in unity-control-center package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in vino package in Ubuntu: Invalid Status in unity-control-center source package in Bionic: In Progress Status in unity-settings-daemon source package in Bionic: In Progress Bug description: *Impact This happens because Gnome removed that particular gsettings key. The removal did not happen with the ui removal but rather much later than that. That is why it doesn't work with the latest version of vino. As of now If users try to open the new sharing panel, unity-control- center will crash. This sort behavior is not desired on LTS release (18.04). Test Case 1) Go to unity-control-center 2) Click sharing (Remote desktop) * Regression potential None The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a 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/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
could you please test with ppa:canonical-hwe-team/ppa which has a new 4.15 kernel with a couple of backports that should fix this, and it also comes with mesa that dropped the revert apparently I don't have hw which can install 32bit ubuntu and reproduce this -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in mesa source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 58941] Re: omit Album information for files w/o album information
Upstream issue now tracked at: https://gitlab.gnome.org/GNOME/rhythmbox/issues/648 ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #648 https://gitlab.gnome.org/GNOME/rhythmbox/issues/648 ** Changed in: rhythmbox Importance: Wishlist => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #556828 => gitlab.gnome.org/GNOME/rhythmbox/issues #648 ** Tags added: bionic -- 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/58941 Title: omit Album information for files w/o album information Status in One Hundred Papercuts: Triaged Status in Rhythmbox: Unknown Status in rhythmbox package in Ubuntu: Triaged Status in rhythmbox package in Debian: Confirmed Bug description: Currently, when a new song starts which does not have an "Album" entry, the notification bubble and the track information bar say: " by from Unknown" I'd say it would look nicer if Rhythmbox would just omit the "from Unknown" (or whatever it says with LANG=C) if there is no Album tag (empty string or only nonprintable chars) in the file. Thanks, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/58941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724370] Re: NVME model does not show up
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect BUGNUMBER When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: udisks2 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-disk-utility (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1724370 Title: NVME model does not show up Status in gnome-disk-utility package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in udisks2 package in Ubuntu: Incomplete Bug description: The Model field for NVME drives is blank. I believe this issue comes from udisks2, and then from udev. udisks2 has a function for getting the model which returns blank, udisks_drive_get_model udev has a parameter that should be returned for a disk if it has a model, ID_MODEL The Linux kernel exposes the true model in a sys file, /sys/block/nvme0n1/device/model This data should be displayed in GNOME Disks when available, but is not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 329389] Re: "Party mode" ununderstandable and undocumented
Upstream issue now tracked at: https://gitlab.gnome.org/GNOME/rhythmbox/issues/701 ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #701 https://gitlab.gnome.org/GNOME/rhythmbox/issues/701 ** Changed in: rhythmbox Importance: Medium => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #572651 => gitlab.gnome.org/GNOME/rhythmbox/issues #701 ** Tags removed: precise trusty vivid wily ** Tags added: bionic -- 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/329389 Title: "Party mode" ununderstandable and undocumented Status in One Hundred Papercuts: Triaged Status in Rhythmbox: Unknown Status in rhythmbox package in Ubuntu: Triaged Bug description: Binary package hint: rhythmbox The manual does not explain what "party mode" is. The status bar help text is not helpful at all; when you hover the cursor over the Party Mode menu entry, it laconically says "Change the status of the party mode". (Is that even English?) I was scared that it would ruin all my playlists and send my email address to the spammers, but I tried it anyway. It seems to toggle a full-screen view. Then why is it not called "Full Screen"? Does it do something more? The top Google hit http://ubuntuforums.org/showthread.php?t=694932 seems inconclusive to me. Does Party mode involve changes in how the play queue can be manipulated and/or how the computer can be used? Minimal fix: * Describe Party Mode in the on-line help Bonus points: * Improve the Status bar help text vnix$ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 vnix$ apt-cache policy rhythmbox rhythmbox: Installed: 0.11.6svn20081008-0ubuntu4.2 Candidate: 0.11.6svn20081008-0ubuntu4.2 Version table: *** 0.11.6svn20081008-0ubuntu4.2 0 500 http://fi.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 0.11.6svn20081008-0ubuntu4 0 500 http://fi.archive.ubuntu.com intrepid/main Packages To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/329389/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839174] [NEW] Xorg crashes - segfault error 6 in libc-2.27.so
Public bug reported: Issue xorg crashes, there doesn't seem to be any repeatable cause, it'll happen just watching hulu or youtube, it'll happen when using citrix, or when playing steam games. Steps to reproduce use xorg for a while Expected behaviour not crashing Other information issue only happens when using pci-e passthrough to qemu virtual machines Has been an issue since setting up pci-e passthrough, have reinstalled Linux Mint (from XFCE version) but error persists, have changed numerous bios settings without having an impact Upgraded bios to most recent version, also reset bios to factory defaults, didn't make a difference Tried latest Linux 5.x kernels from uuku, same issue The virtual machine doesn't have any problems, it never crashes and stays running when the host os xorg crashes. System:Host: drac Kernel: 4.15.0-55-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.3 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic Machine: Type: Server System: Supermicro product: Super Server v: 0123456789 serial: Mobo: Supermicro model: X10SRL-F v: 1.01B serial: UEFI: American Megatrends v: 3.1c date: 05/02/2019 Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Micro-Star MSI driver: nvidia v: 430.34 bus ID: 03:00.0 Device-2: NVIDIA GK104 [GeForce GTX 770] vendor: eVga.com. driver: vfio-pci v: 0.2 bus ID: 04:00.0 Device-3: ASPEED Graphics Family vendor: Super Micro driver: ast v: kernel bus ID: 0b:00.0 Display: x11 server: X.Org 1.19.6 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 430.34 direct render: Yes CPU: Topology: 6-Core model: Intel Xeon E5-1650 v4 bits: 64 type: MT MCP arch: Broadwell rev: 1 L2 cache: 15.0 MiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 86397 Speed: 1203 MHz min/max: N/A Core speeds (MHz): 1: 1203 2: 1206 3: 1330 4: 1200 5: 1201 6: 1201 7: 1200 8: 1200 9: 2046 10: 1202 11: 1202 12: 1201 Not using PPA builds Linux Mint 19.2 (Upgraded from 19.1) 64bit root@drac:/vms# apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 1070GTX - NVIDIA-Linux-x86_64-430.34.run Left screen is a 60hz monitor, right screen is a 120hz monitor Also have a 770GTX bound to vfio for virtual machine passthrough Previously used the PPA from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa, but changed to Nvidia's .run to see if it made a different - it did not. [xsession-errors.old.upload.txt](https://github.com/linuxmint/cinnamon/files/3471789/xsession-errors.old.upload.txt) [xsession-errors.upload.txt](https://github.com/linuxmint/cinnamon/files/3471791/xsession-errors.upload.txt) [lspci.txt](https://github.com/linuxmint/cinnamon/files/3471859/lspci.txt) Syslog: [kernel.log.txt](https://github.com/linuxmint/cinnamon/files/3471804/kernel.log.txt) Grub: having mitigations on or off makes no difference GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1 drm.debug=14 log_buf_len=16M mitigations=on intel_iommu=on vfio-pci.ids=8086:8d26,10de:1184,10de:0e0a modprobe.blacklist=snd_hda_intel,snd_hda_core,snd_hda_codec,snd_hda_codec_hdmi,nouveau" Xorg crashdump traces: /var/crash/usr_lib_xorg_Xorg.0.crash Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f34b8f87432 in __GI__IO_default_xsputn (f=0x7f34b0427610, data=0x7f34b90b5030 , n=3) at genops.c:389 389 genops.c: No such file or directory. [Current thread is 1 (Thread 0x7f34b0c26700 (LWP 1320))] (gdb) thread 2 [Switching to thread 2 (Thread 0x7f34bbc10600 (LWP 1196))] #0 0x7f34b92fb2b7 in __libc_write (fd=14, buf=0x7fffd039b2c0, nbytes=23) at ../sysdeps/unix/sysv/linux/write.c:27 27 ../sysdeps/unix/sysv/linux/write.c: No such file or directory. Thread 1 backtrace: #0 0x7f34b8f87432 in __GI__IO_default_xsputn (f=0x7f34b0427610, data=0x7f34b90b5030 , n=3) at genops.c:389 #1 0x7f34b8f7937e in __GI__IO_padn (fp=fp@entry=0x7f34b0427610, pad=pad@entry=48, count=count@entry=3) at iopadn.c:64 #2 0x7f34b8f55f20 in _IO_vfprintf_internal (s=s@entry=0x7f34b0427610, format=format@entry=0x7f34bac5f55c "target PCI:%04x:%02x:%02x.%x", ap=ap@entry=0x7f34b0427790) at vfprintf.c:1642 #3 0x7f34b902b169 in ___vsnprintf_chk (s=0x7f34b0427890 "target PCI:\020\200y\360.0\323\b3\330U", maxlen=, flags=1, slen=, format=0x7f34bac5f55c "target PCI:%04x:%02x:%0
[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
What should I look for in the log? -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: Incomplete Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-SIGNAL-CHANGE above=0
[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
I tried disabling the power saver (#3). If I change networks, then no wifi is found. -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: Incomplete Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1 Jul 16 19:20:32 serval wpa_supplican
[Desktop-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
Hey Charles and Vincent, sorry to see this bug is STILL not fixed. Goodness me. The workaround I used is reported in this other bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1695775 I saw it in 17.04 and 17.10. Since then I gave up and moved to Ubuntu MATE, not just because of this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Won't Fix Status in gnome-session source package in Zesty: Won't Fix Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
Nevermind, I used a thinkpad t470s plus an external ssd which I could wipe out and install ubuntu mate 18.04 32bit on it. To reproduce I enabled the HWE ppa and upgraded mesa, then installed linux-generic and booted 4.15.0-55. It ended up with a mostly blank screen but keyboard had no effect other than the power button. Then I installed 'linux-image-4.15.0-56-generic linux- modules-4.15.0-56-generic linux-modules-extra-4.15.0-56-generic' and rebooted, and now I got to the display manager normally. ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in mesa source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839211] [NEW] Upgrade to 2.2.1-1(Debian)
Public bug reported: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan upgrade-software-version wayland-session ** Description changed: - I am testing gnome-music night, and request tracker version 2.2.0 or - higher. + I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. + [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: New Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716940] Re: gvfsd-trash crashed with signal 5 in g_main_context_new()
Upstream is here: https://bugzilla.gnome.org/show_bug.cgi?id=787633 Was closed "as no further information has been provided", so didn't make the migration to Gitlab. Potentially related upstream bugs: https://gitlab.gnome.org/GNOME/gvfs/issues/261 https://gitlab.gnome.org/GNOME/gvfs/issues/400 https://gitlab.gnome.org/GNOME/gtk/issues/1010 https://bugzilla.gnome.org/show_bug.cgi?id=792331 https://bugzilla.gnome.org/show_bug.cgi?id=792335 Potentially related bugs elsewhere: https://bugzilla.redhat.com/show_bug.cgi?id=1323079 The only workaround I've seen is "kill gvfsd-trash". I don't think anyone has been able to reliably reproduce it. If I had to guess, I think it might have to do with mounting and deleting files on USB flash drives. ** Bug watch added: bugzilla.gnome.org/ #787633 https://bugzilla.gnome.org/show_bug.cgi?id=787633 ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #261 https://gitlab.gnome.org/GNOME/gvfs/issues/261 ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #400 https://gitlab.gnome.org/GNOME/gvfs/issues/400 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #1010 https://gitlab.gnome.org/GNOME/gtk/issues/1010 ** Bug watch added: bugzilla.gnome.org/ #792331 https://bugzilla.gnome.org/show_bug.cgi?id=792331 ** Bug watch added: bugzilla.gnome.org/ #792335 https://bugzilla.gnome.org/show_bug.cgi?id=792335 ** Bug watch added: Red Hat Bugzilla #1323079 https://bugzilla.redhat.com/show_bug.cgi?id=1323079 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1716940 Title: gvfsd-trash crashed with signal 5 in g_main_context_new() Status in gvfs: Expired Status in gvfs package in Ubuntu: Incomplete Bug description: Hello, I do not know how this happened. Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-daemons 1.33.91-0ubuntu1 Uname: Linux 4.13.1-041301-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 13 11:53:40 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-trash InstallationDate: Installed on 2017-07-05 (69 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/0 Signal: 5 SourcePackage: gvfs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-trash crashed with signal 5 in g_main_context_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1716940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839212] [NEW] UX issues in "Ubuntu Software" and related applications
You have been subscribed to a public bug: I think it's important to have a look at the high level user experience around software updating in Ubuntu. This is all tested on the latest Ubuntu 19 (installed a few days ago). Apologies if this is the wrong place to post, and that I'm bundling a couple of things together. These issues go across "Ubuntu Software", "Software Updater" and "Software & Updates", and I didn't want to spam ya'll with multiple small disjointed issues. On the other hand I think this stuff is super-important for user experience and needs discussing in a bug context, not a support context. 1) Searching for "software" under "Show Applications", produces a screen with these options: "Ubuntu Softw..." "Software & Up..." "Software Upd..." This is a poor experience. There's no way for a new user to tell these 3 things apart, and for a real newbie it's not even obvious when opening them. For example, my initial thought with "Ubuntu Software" is perhaps it is just for installing snaps, that's the kind of unexpected confusion that can happen when there's multiple similar-sounding options on a menu. My suggestion would be to only have "Ubuntu Software". Remove the .desktop files for the other options, but make them available from within "Ubuntu Software". 2) "Software & Updates" has CD/DVD options, which is (a) antiquated and (b) unclear how it works. I understand it likely works by standardized mount paths, but most users nowadays will be installing with a USB stick which has no support. Imagine a new user who needs to install custom broadlink drivers from USB stick, but there's no way to easily configure the package manager to do it. That was my situation, I ended up finding the .deb file on the USB manually. I think you should just rework all this as an "Installation Media" option, and search all mounted paths for an Ubuntu signature. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- UX issues in "Ubuntu Software" and related applications https://bugs.launchpad.net/bugs/1839212 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839211] Re: Upgrade to 2.2.1-1
** Attachment added: "Captura de pantalla de 2019-08-06 16-20-51.png" https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+attachment/5281307/+files/Captura%20de%20pantalla%20de%202019-08-06%2016-20-51.png ** Summary changed: - Upgrade to 2.2.1-1 + Upgrade to 2.2.1-1(Debian) ** Summary changed: - Upgrade to 2.2.1-1(Debian) + Please upgrade to 2.2.1-1(Debian) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Please upgrade to 2.2.1-1(Debian) Status in tracker package in Ubuntu: New Bug description: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839212] Re: UX issues in "Ubuntu Software" and related applications
** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu) ** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1839212 Title: UX issues in "Ubuntu Software" and related applications Status in gnome-software package in Ubuntu: New Bug description: I think it's important to have a look at the high level user experience around software updating in Ubuntu. This is all tested on the latest Ubuntu 19 (installed a few days ago). Apologies if this is the wrong place to post, and that I'm bundling a couple of things together. These issues go across "Ubuntu Software", "Software Updater" and "Software & Updates", and I didn't want to spam ya'll with multiple small disjointed issues. On the other hand I think this stuff is super-important for user experience and needs discussing in a bug context, not a support context. 1) Searching for "software" under "Show Applications", produces a screen with these options: "Ubuntu Softw..." "Software & Up..." "Software Upd..." This is a poor experience. There's no way for a new user to tell these 3 things apart, and for a real newbie it's not even obvious when opening them. For example, my initial thought with "Ubuntu Software" is perhaps it is just for installing snaps, that's the kind of unexpected confusion that can happen when there's multiple similar-sounding options on a menu. My suggestion would be to only have "Ubuntu Software". Remove the .desktop files for the other options, but make them available from within "Ubuntu Software". 2) "Software & Updates" has CD/DVD options, which is (a) antiquated and (b) unclear how it works. I understand it likely works by standardized mount paths, but most users nowadays will be installing with a USB stick which has no support. Imagine a new user who needs to install custom broadlink drivers from USB stick, but there's no way to easily configure the package manager to do it. That was my situation, I ended up finding the .deb file on the USB manually. I think you should just rework all this as an "Installation Media" option, and search all mounted paths for an Ubuntu signature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1839212/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839217] [NEW] Bad user experience choosing partition labels
Public bug reported: For FAT partitions, labels have to be upper case. FAT is the default for a new partition, but the default example label is mixed case. This means just going on recommendation, it's not going to work out, and the user will get an error message. A better user experience would be to simply tell the user that their label will be made upper case, and ask them to confirm with yes/no. Or just do it without asking TBH because I think upper-casing it by default is a pretty harmless thing. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1839217 Title: Bad user experience choosing partition labels Status in gnome-disk-utility package in Ubuntu: New Bug description: For FAT partitions, labels have to be upper case. FAT is the default for a new partition, but the default example label is mixed case. This means just going on recommendation, it's not going to work out, and the user will get an error message. A better user experience would be to simply tell the user that their label will be made upper case, and ask them to confirm with yes/no. Or just do it without asking TBH because I think upper-casing it by default is a pretty harmless thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
I do not really see in the log snippets where the Wi-Fi does not actually work, or which step of the Wi-Fi connection attempt fails. Perhaps the relevant part is not included. You write: -- Jul 16 19:20:34 serval NetworkManager[617]: [1563330034.2504] device (p2p-dev-wlp62s0): supplicant management interface state: associating -> associated ``` ...snip... ``` Jul 16 19:20:45 serval NetworkManager[617]: [1563330045.2179] supplicant: wpa_supplicant die count reset -- Could you also post the part which you have cut away here? -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: Incomplete Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP
[Desktop-packages] [Bug 1839225] [NEW] texlive-pstricks is missing a depedency on texlive-luatex
Public bug reported: /usr/share/texlive/texmf-dist/tex/latex/pst-pdf/pst-pdf.sty contains a reference to luatex85.sty which is found in texlive-luatex. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: texlive-pstricks 2018.20190227-1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Tue Aug 6 18:38:52 2019 PackageArchitecture: all SourcePackage: texlive-extra UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-extra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1839225 Title: texlive-pstricks is missing a depedency on texlive-luatex Status in texlive-extra package in Ubuntu: New Bug description: /usr/share/texlive/texmf-dist/tex/latex/pst-pdf/pst-pdf.sty contains a reference to luatex85.sty which is found in texlive-luatex. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: texlive-pstricks 2018.20190227-1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Tue Aug 6 18:38:52 2019 PackageArchitecture: all SourcePackage: texlive-extra UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1839225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839174] Re: Xorg crashes - segfault error 6 in libc-2.27.so
Thanks for the bug report. I can't seem to find any similar crash reports on: https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=xorg- server&period=year Can you please follow these instructions to try and generate a formal crash report? https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment I would like it to confirm exactly what is crashing and where... ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: bionic -- 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/1839174 Title: Xorg crashes - segfault error 6 in libc-2.27.so Status in xorg-server package in Ubuntu: New Bug description: Issue xorg crashes, there doesn't seem to be any repeatable cause, it'll happen just watching hulu or youtube, it'll happen when using citrix, or when playing steam games. Steps to reproduce use xorg for a while Expected behaviour not crashing Other information issue only happens when using pci-e passthrough to qemu virtual machines Has been an issue since setting up pci-e passthrough, have reinstalled Linux Mint (from XFCE version) but error persists, have changed numerous bios settings without having an impact Upgraded bios to most recent version, also reset bios to factory defaults, didn't make a difference Tried latest Linux 5.x kernels from uuku, same issue The virtual machine doesn't have any problems, it never crashes and stays running when the host os xorg crashes. System:Host: drac Kernel: 4.15.0-55-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.3 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic Machine: Type: Server System: Supermicro product: Super Server v: 0123456789 serial: Mobo: Supermicro model: X10SRL-F v: 1.01B serial: UEFI: American Megatrends v: 3.1c date: 05/02/2019 Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Micro-Star MSI driver: nvidia v: 430.34 bus ID: 03:00.0 Device-2: NVIDIA GK104 [GeForce GTX 770] vendor: eVga.com. driver: vfio-pci v: 0.2 bus ID: 04:00.0 Device-3: ASPEED Graphics Family vendor: Super Micro driver: ast v: kernel bus ID: 0b:00.0 Display: x11 server: X.Org 1.19.6 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 430.34 direct render: Yes CPU: Topology: 6-Core model: Intel Xeon E5-1650 v4 bits: 64 type: MT MCP arch: Broadwell rev: 1 L2 cache: 15.0 MiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 86397 Speed: 1203 MHz min/max: N/A Core speeds (MHz): 1: 1203 2: 1206 3: 1330 4: 1200 5: 1201 6: 1201 7: 1200 8: 1200 9: 2046 10: 1202 11: 1202 12: 1201 Not using PPA builds Linux Mint 19.2 (Upgraded from 19.1) 64bit root@drac:/vms# apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 1070GTX - NVIDIA-Linux-x86_64-430.34.run Left screen is a 60hz monitor, right screen is a 120hz monitor Also have a 770GTX bound to vfio for virtual machine passthrough Previously used the PPA from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa, but changed to Nvidia's .run to see if it made a different - it did not. [xsession-errors.old.upload.txt](https://github.com/linuxmint/cinnamon/files/3471789/xsession-errors.old.upload.txt) [xsession-errors.upload.txt](https://github.com/linuxmint/cinnamon/files/3471791/xsession-errors.upload.txt) [lspci.txt](https://github.com/linuxmint/cinnamon/files/3471859/lspci.txt) Syslog: [kernel.log.txt](https://github.com/linuxmint/cinnamon/files/3471804/kernel.log.txt) Grub: having mitigations on or off makes no difference GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1 drm.debug=14 log_buf_len=16M mitigations=on intel_iommu=on vfio-pci.ids=8086:8d26,10de:1184,10de:0e0a modprobe.blacklist=snd_hda_intel,snd_hda_core,snd_hda_codec,snd_hda_codec_hdmi,nouveau" Xorg crashdump traces: /var/crash/usr_lib_xorg_Xorg.0.crash Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f34b8f87432 in __GI__IO_default_xsputn (f=0x7f34b0427610, data=0x7f34b90b5030 , n=3) at genops.c:389 389 genops.c: No such file or directory. [Current thread is 1 (Thread 0x7f34b0c26700 (LWP 1320))] (gdb) thread 2 [
[Desktop-packages] [Bug 1839136] Re: Temporary freeze / delay with some dialog windows
Please start by uninstalling the extra extensions you have: 'gpa...@gnome-shell-extensions.gnome.org' 'user-th...@gnome-shell-extensions.gcampax.github.com' 'no-title-...@franglais125.gmail.com' 'emoji-selec...@maestroschan.fr' 'indica...@johannes.super-productivity.com' 'window-corner-prev...@fabiomereu.it' 'topIcons@adel.gadl...@gmail.com' 'topic...@phocean.net' 'windowIsReady_Remover@lo...@linuxuprising.com' 'mediapla...@patapon.info' 'messagingm...@screenfreeze.net' 'perfect-osd' 'grilo_search_provi...@awamper.gmail.com' 'obmin@konkor' 'dock-settings@lagrangian' 'places-and-files-on-desk...@maestroschan.fr' 'animation-tweaks@Selenium-H' 'minimize-to-t...@elhan.io' 'transparent-win...@pbxqdown.github.com' 'gnom...@panacier.gmail.com' 'dash-to-pa...@jderose9.github.com' We find a large number of bugs are caused by extensions so need to rule those out as a cause before anything else. ** Tags added: nvidia -- 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/1839136 Title: Temporary freeze / delay with some dialog windows Status in gnome-shell package in Ubuntu: New Bug description: Some dialog popups take a while to open, as if the system froze for a bit (even though journalctl -f doesn't show anything related) which is extremely annoying. Example: - the dialog shown if a file should be saved when trying to close a tab in Gedit - the popup confirmation dialog when using Shift + Delete in Nautilus - the dialog shown when trying to close a terminal that has a running process This does not happen every time, but I'm not sure what triggers it. I made a video showcasing the issue: https://streamable.com/xqjlf The first time I try to close a Gedit unsaved tab this issue happens, but the second time it does not happen. What I tried and did not solve this issue: - using modal or detached dialogs - disabling all Gnome Shell extensions (including those that ship with Ubuntu by default, by removing the packages) This seems related to using multiple monitors. I have two monitors, one using 2560x1080 resolution, and the other 19220x1080 (both with the default 100% scalx). When I mirrored the displays, this issue no longer happened. It only happens with extended (using the "Join Displays" option) display. To replicate, just click (focus) on other windows multiple times (on both monitors), then go to the window that causes these issues and it should happen, like I explained. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 14:10:26 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-10-17 (292 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1839136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838867] Re: Bionic HWE kernel 5.0.0.23 breaks nvidia driver 340.107
Same here. Machine is a quad-GPU AMD Threadripper 1950X build. Mine boots and nvidia-smi works, but any attempt to fire up a GPU workload kills the machine on something in nvidia module. See attached dmesg. The machine is headless. ** Attachment added: "dmesg.201908062033" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1838867/+attachment/5281332/+files/dmesg.201908062033 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1838867 Title: Bionic HWE kernel 5.0.0.23 breaks nvidia driver 340.107 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: When updating my system, I got the new 5.0.0.23 kernel (coming from 4.18.0-25). DKMS fails for the nvidia 340 driver. I need to use this for my generation card (ION). Make log included. X starts, but low-res. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-340 340.107-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Aug 4 11:35:26 2019 SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to bionic on 2018-05-08 (452 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1838867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838919] Re: Slow and lost keyboard and mouse events
I had a bit of a brainwave this morning - or perhaps just awoke from my
stupidity!
I also have a laptop which runs ubuntu studio 19.04 amd64. At the
moment, my desktop which is suffering has the 5.0.0-23-generic kernel.
The laptop has the 5.0.0-21-lowlatency kernel, BUT does not have all
these problems.
The laptop also has gtk2 and gtk3 packages installed, although I haven't
yet done a package-by-package diff.
As far as I can remember, they both have mostly the same applications,
although studio has a lot more. The laptop currently has upgrades
waiting to be installed for the kernel, chromium, chrome and mutter (and
quite a few more packages).
Should I upgrade those packages on the laptop one at a time, to see
whether the same problem appears?
--
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/1838919
Title:
Slow and lost keyboard and mouse events
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
This was a fresh amd64 installation with 18.10 desktop, upgraded to
19.04 as soon as available. It has been getting worse over the last
few weeks and is now so bad I can hardly type an email (or this bug
report!) without having to fix many typos.
journalctl shows many different gnome errors, so it is difficult to
figure out which is the underlying cause and which are simply
collateral damage.
There are two sequences that appear first after a reboot, and the
first of these has been reported many times on ubuntu releases going
back for years:-
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be
loaded.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module
"canberra-gtk-module"
and
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG]
Registering StatusNotifierItem
:1.89/org/ayatana/NotificationItem/software_update_available
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable
to update overlay icon
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable
to update overlay icon
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning:
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error
from previous GL command
Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]:
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)]
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-
Is this a recent regression? I know for sure the system wasn't this
unresponsive 3 weeks ago, but I cannot be sure when it started to go
wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
fiddled around with distance and battery state until I was sure the
problem was somewhere else and started to check the system log.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software 3.30.6-2ubuntu4.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
App
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Thanks & sorry for belated response. I've never manually installed a new kernel (and am not sure how to proceed about checking integrity, etc.). Is there any resource you'd advice to get info on the topic? Thanks in advance. For now I can confirm that since I added this to the kernel options, I have had 0 occurrences of the bug over the last 3 weeks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. 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.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/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Download all the debs to a new directory, then $ sudo dpkg -i *deb $ sudo reboot ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. 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.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/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
