[Desktop-packages] [Bug 1870479] [NEW] .desktop files were open by gedit
Public bug reported: On 20.04,the .desktop file could not show correct icons and open by correct applications. It only show a 'setting' icon, and when you double click it, it will use gedit to open it. nautilus 1:3.36.1-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1870479 Title: .desktop files were open by gedit Status in nautilus package in Ubuntu: New Bug description: On 20.04,the .desktop file could not show correct icons and open by correct applications. It only show a 'setting' icon, and when you double click it, it will use gedit to open it. nautilus 1:3.36.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1870479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870278] Re: Shell is unresponsive at the lock screen for ~10s after unlocking
I have tried, and will try again, to understand how extensions and JavaScript in general are able to use so many megabytes so quickly... -- 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/1870278 Title: Shell is unresponsive at the lock screen for ~10s after unlocking Status in gnome-shell package in Ubuntu: Incomplete Bug description: When unlocking the session GNOME Shell now appears to be entirely unresponsive (still showing the lock screen) for ~10s after entering a correct password. This occurs on both an X11 and a Wayland session; on the Wayland session the mouse cursor is frozen, while on X11 it is responsive (and still changes the cursor image appropriately when moving over windows) This only started recently (maybe a couple of days ago?); it's now 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 16:49:34 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861043] Re: GUI frozen when memory was exhausted (by non-GUI processes)
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1861043 Title: GUI frozen when memory was exhausted (by non-GUI processes) Status in gnome-shell package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861043] Re: GUI frozen when memory was exhausted (by non-GUI processes)
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1861043 Title: GUI frozen when memory was exhausted (by non-GUI processes) Status in gnome-shell package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870278] Re: Shell is unresponsive at the lock screen for ~10s after unlocking
No, it doesn't start that high on login. The desktop is currently at 370MB RSS in a fairly fresh X11 session (now that Shell actually starts again after I removed all the extensions 臘) -- 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/1870278 Title: Shell is unresponsive at the lock screen for ~10s after unlocking Status in gnome-shell package in Ubuntu: Incomplete Bug description: When unlocking the session GNOME Shell now appears to be entirely unresponsive (still showing the lock screen) for ~10s after entering a correct password. This occurs on both an X11 and a Wayland session; on the Wayland session the mouse cursor is frozen, while on X11 it is responsive (and still changes the cursor image appropriately when moving over windows) This only started recently (maybe a couple of days ago?); it's now 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 16:49:34 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870468] Re: /usr/bin/gnome-shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_xrandr_apply_monitors_config:meta_monitor_manager_apply_mo
*** This bug is a duplicate of bug 1870454 *** https://bugs.launchpad.net/bugs/1870454 ** This bug has been marked a duplicate of bug 1870454 gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign() -- 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/1870468 Title: /usr/bin/gnome- shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_xrandr_apply_monitors_config:meta_monitor_manager_apply_monitors_config:restore_previous_config Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870454] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign()
** Summary changed: - gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs() + gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign() ** Information type changed from Private to Public -- 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/1870454 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 --- I don't really know what caused this, I didn't notice anything out of the ordinary, so I'm not sure exactly when it occurred. I usually plug and unplug an external monitor, this seems related. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 2 19:31:02 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-14 (475 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fdf6e50156b : mov 0x8(%rax,%rdi,1),%rax PC (0x7fdf6e50156b) ok source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 meta_monitor_config_manager_assign () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs() UpgradeStatus: Upgraded to focal on 2020-03-25 (8 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870467] Re: /usr/bin/gnome-shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_xrandr_apply_monitors_config:meta_monitor_manager_apply_mo
*** This bug is a duplicate of bug 1870454 *** https://bugs.launchpad.net/bugs/1870454 ** This bug has been marked a duplicate of bug 1870454 gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign() -- 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/1870467 Title: /usr/bin/gnome- shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_xrandr_apply_monitors_config:meta_monitor_manager_apply_monitors_config:orientation_changed Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870454] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870454 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 --- I don't really know what caused this, I didn't notice anything out of the ordinary, so I'm not sure exactly when it occurred. I usually plug and unplug an external monitor, this seems related. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 2 19:31:02 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-14 (475 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fdf6e50156b : mov 0x8(%rax,%rdi,1),%rax PC (0x7fdf6e50156b) ok source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 meta_monitor_config_manager_assign () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs() UpgradeStatus: Upgraded to focal on 2020-03-25 (8 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870467] [NEW] /usr/bin/gnome-shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_xrandr_apply_monitors_config:meta_monitor_manager_apply_
*** This bug is a duplicate of bug 1870454 *** https://bugs.launchpad.net/bugs/1870454 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- 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/1870467 Title: /usr/bin/gnome- shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_xrandr_apply_monitors_config:meta_monitor_manager_apply_monitors_config:orientation_changed Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870454] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign()
Tracking in https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba but see also https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 ** Description changed: + https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba + https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 + + --- + I don't really know what caused this, I didn't notice anything out of the ordinary, so I'm not sure exactly when it occurred. I usually plug and unplug an external monitor, this seems related. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 2 19:31:02 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-14 (475 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: - Segfault happened at: 0x7fdf6e50156b : mov 0x8(%rax,%rdi,1),%rax - PC (0x7fdf6e50156b) ok - source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7fdf6e50156b : mov 0x8(%rax,%rdi,1),%rax + PC (0x7fdf6e50156b) ok + source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 - meta_monitor_config_manager_assign () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 - () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 - () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 - () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 + meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 + meta_monitor_config_manager_assign () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs() UpgradeStatus: Upgraded to focal on 2020-03-25 (8 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers separator: -- 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/1870454 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 --- I don't really know what caused this, I didn't notice anything out of the ordinary, so I'm not sure exactly when it occurred. I usually plug and unplug an external monitor, this seems related. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 2 19:31:02 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-14 (475 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fdf6e50156b : mov 0x8(%rax,%rdi,1),%rax PC (0x7fdf6e50156b) ok source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 meta_monitor_config_manager_assign () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs() UpgradeStatus: Upgraded to focal on 2020-03-25 (8 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870454/+subscriptions
[Desktop-packages] [Bug 1870468] [NEW] /usr/bin/gnome-shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_xrandr_apply_monitors_config:meta_monitor_manager_apply_
*** This bug is a duplicate of bug 1870454 *** https://bugs.launchpad.net/bugs/1870454 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: disco eoan focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870468 Title: /usr/bin/gnome- shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_xrandr_apply_monitors_config:meta_monitor_manager_apply_monitors_config:restore_previous_config Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870435] Re: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command
Please attach a photo or video of the problem so we can get a better idea. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron
[Desktop-packages] [Bug 1870464] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() from _g_closure_invoke_va() from g_
*** This bug is a duplicate of bug 1870354 *** https://bugs.launchpad.net/bugs/1870354 ** Summary changed: - /usr/bin/gnome-shell:11:st_theme_node_get_text_align:_st_set_text_from_style:st_label_style_changed:_g_closure_invoke_va:g_signal_emit_valist + gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() from _g_closure_invoke_va() from g_signal_emit_valist() ** This bug has been marked a duplicate of bug 1870354 gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() -- 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/1870464 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() from _g_closure_invoke_va() from g_signal_emit_valist() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868353] Re: Bose SLIII appears in blueman-manager in response to adapter search, but pair fails
** Summary changed: - regression: bose sl iii works in bionic lubuntu, and in focal ubuntu, but fails in focal lubuntu + Bose SLIII appears in blueman-manager in response to adapter search, but pair fails ** Package changed: pulseaudio (Ubuntu) => blueman (Ubuntu) ** Changed in: blueman (Ubuntu) Importance: Low => Undecided ** Changed in: blueman (Ubuntu) Status: Triaged => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1868353 Title: Bose SLIII appears in blueman-manager in response to adapter search, but pair fails Status in PulseAudio: New Status in blueman package in Ubuntu: New Bug description: blueman-manager successfully pairs and connects to the Bose SL III in both bionic and in focal. in bionic, the Bose SL III then immediately shows up in pavucontrol. in focal, it remains absent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Fri Mar 20 19:53:54 2020 InstallationDate: Installed on 2020-03-15 (5 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1868353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870354] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed()
It looks like the offending caller might be: https://github.com/mlutfy/hidetopbar/blob/master/intellihide.js#L93 so please try removing that hidetopbar extension. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1870354 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() Status in gnome-shell package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf --- Seems to be happening when docking/undocking or when locking the screen. Ignore the LD_LIBRARY_PATH bit, it's just dqlite/raft dev libraries for LXD, doesn't affect desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 09:37:12 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LocalLibraries: /home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6 ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f4da0ee6de9 : repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x7f4da0ee6de9) ok source "%es:(%rdi)" (0x7f4da0f17934) ok destination "%ds:(%rsi)" (0xe9f78948fa1e0ff3) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_get_text_align () at /usr/lib/gnome-shell/libst-1.0.so _st_set_text_from_style () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() UpgradeStatus: Upgraded to focal on 2018-12-17 (472 days ago) UserGroups: adm dialout kvm libvirt lp lpadmin lxd plugdev sbuild scanner sudo video separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870354] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align()
Looks like a pretty rare problem. 2 occurrences in focal and 4 in xenial... https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf ** Description changed: + https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf + + --- + Seems to be happening when docking/undocking or when locking the screen. Ignore the LD_LIBRARY_PATH bit, it's just dqlite/raft dev libraries for LXD, doesn't affect desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 09:37:12 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LocalLibraries: /home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6 ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: - Segfault happened at: 0x7f4da0ee6de9 : repz cmpsb %es:(%rdi),%ds:(%rsi) - PC (0x7f4da0ee6de9) ok - source "%es:(%rdi)" (0x7f4da0f17934) ok - destination "%ds:(%rsi)" (0xe9f78948fa1e0ff3) not located in a known VMA region (needed writable region)! + Segfault happened at: 0x7f4da0ee6de9 : repz cmpsb %es:(%rdi),%ds:(%rsi) + PC (0x7f4da0ee6de9) ok + source "%es:(%rdi)" (0x7f4da0f17934) ok + destination "%ds:(%rsi)" (0xe9f78948fa1e0ff3) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - st_theme_node_get_text_align () at /usr/lib/gnome-shell/libst-1.0.so - _st_set_text_from_style () at /usr/lib/gnome-shell/libst-1.0.so - () at /usr/lib/gnome-shell/libst-1.0.so - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + st_theme_node_get_text_align () at /usr/lib/gnome-shell/libst-1.0.so + _st_set_text_from_style () at /usr/lib/gnome-shell/libst-1.0.so + () at /usr/lib/gnome-shell/libst-1.0.so + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() UpgradeStatus: Upgraded to focal on 2018-12-17 (472 days ago) UserGroups: adm dialout kvm libvirt lp lpadmin lxd plugdev sbuild scanner sudo video separator: ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low ** Summary changed: - gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() + gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() ** Information type changed from Private to Public -- 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/1870354 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() Status in gnome-shell package in Ubuntu: New Bug description: https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf --- Seems to be happening when docking/undocking or when locking the screen. Ignore the LD_LIBRARY_PATH bit, it's just dqlite/raft dev libraries for LXD, doesn't affect desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 09:37:12 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LocalLibraries: /home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6 ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f4da0ee6de9 : repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x7f4da0ee6de9) ok source "%es:(%rdi)" (0x7f4da0f17934) ok destination "%ds:(%rsi)" (0xe9f78948fa1e0ff3) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_get_text_align () at /usr/lib/gnome-shell/libst-1.0.so _st_set_text_from_style () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() UpgradeStatus: Upgraded to focal on 2018-12-17 (472 days ago) UserGroups: adm dialout
[Desktop-packages] [Bug 1870464] [NEW] /usr/bin/gnome-shell:11:st_theme_node_get_text_align:_st_set_text_from_style:st_label_style_changed:_g_closure_invoke_va:g_signal_emit_valist
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal quantal trusty xenial yakkety -- 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/1870464 Title: /usr/bin/gnome- shell:11:st_theme_node_get_text_align:_st_set_text_from_style:st_label_style_changed:_g_closure_invoke_va:g_signal_emit_valist Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.0-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868353] Re: regression: bose sl iii works in bionic lubuntu, and in focal ubuntu, but fails in focal lubuntu
better description of failure: Bose SLIII appears in blueman-manager in response to adapter search, but pair fails. as noted above, this works properly in focal ubuntu, and fails in focal lubuntu. this can be reproduced by merely booting the focal ubuntu and lubuntu live ISOs and installing blueman-manager into the live systems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1868353 Title: regression: bose sl iii works in bionic lubuntu, and in focal ubuntu, but fails in focal lubuntu Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Bug description: blueman-manager successfully pairs and connects to the Bose SL III in both bionic and in focal. in bionic, the Bose SL III then immediately shows up in pavucontrol. in focal, it remains absent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Fri Mar 20 19:53:54 2020 InstallationDate: Installed on 2020-03-15 (5 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1868353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870414] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
*** This bug is a duplicate of bug 1865300 *** https://bugs.launchpad.net/bugs/1865300 ** This bug is no longer a duplicate of private bug 1870380 ** This bug has been marked a duplicate of bug 1865300 gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() -- 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/1870414 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() Status in gnome-shell package in Ubuntu: New Bug description: I don't know! ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 16:13:38 2020 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-03-24 (9 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fb1a2be7494 : movsbl (%rdi),%eax PC (0x7fb1a2be7494) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to focal on 2020-03-24 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870338] Re: freezes on boot
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. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1870338 Title: freezes on boot Status in Ubuntu: Incomplete Bug description: My graphics driver in Intel® UHD Graphics 620 (Kabylake GT2).Randomly when I start my system it freezes on boot screen. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 18:29:35 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:083f] InstallationDate: Installed on 2020-03-26 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3576 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=84a1d448-771c-483b-b554-a93ba329ff67 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0Y4H0F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd07/04/2019:svnDellInc.:pnInspiron3576:pvr:rvnDellInc.:rn0Y4H0F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3576 dmi.product.sku: 083F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1870338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870338] Re: freezes on boot
Thanks for the bug report. The only thing I can see wrong in the above attachments right now is some kind of hardware fault on the motherboard: [ 100.336754] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 100.336760] pcieport :00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 100.336764] pcieport :00:1c.5: AER: device [8086:9d15] error status/mask=0001/2000 [ 100.336767] pcieport :00:1c.5: AER:[ 0] RxErr [ 238.598172] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 238.598182] pcieport :00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 238.598190] pcieport :00:1c.5: AER: device [8086:9d15] error status/mask=0001/2000 [ 238.598194] pcieport :00:1c.5: AER:[ 0] RxErr That might just be a poorly seated PCIe card. And it might not even be related to the main issue you experience, so... -- 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/1870338 Title: freezes on boot Status in Ubuntu: Incomplete Bug description: My graphics driver in Intel® UHD Graphics 620 (Kabylake GT2).Randomly when I start my system it freezes on boot screen. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 18:29:35 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:083f] InstallationDate: Installed on 2020-03-26 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3576 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=84a1d448-771c-483b-b554-a93ba329ff67 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0Y4H0F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd07/04/2019:svnDellInc.:pnInspiron3576:pvr:rvnDellInc.:rn0Y4H0F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3576 dmi.product.sku: 083F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1870338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869470] Re: Can't minimize Thunderbird Lightning reminder window
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 1869470 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. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** No longer affects: thunderbird (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Bug watch removed: Mozilla Bugzilla #1271097 https://bugzilla.mozilla.org/show_bug.cgi?id=1271097 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1869470 Title: Can't minimize Thunderbird Lightning reminder window Status in mutter package in Ubuntu: Incomplete Bug description: Ever since Ubuntu moved back to Gnome from Unity, it's impossible to minimize the Thunderbird Lightning reminder window. It's really annoying, the window is always on top of Thunderbird and has to be constantly moved around to use the program. Closing the window makes no sense as a) it tends to start syncing the events with reminders, which can show conflict prompts requiring even more work from the user and b) the window comes back very quickly. So, minimize makes the most sense. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868353] Re: regression: bose sl iii works in bionic lubuntu, and in focal ubuntu, but fails in focal lubuntu
** Summary changed: - regression: Bose SL III works in bionic but not in focal + regression: bose sl iii works in bionic lubuntu, and in focal ubuntu, but fails in focal lubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1868353 Title: regression: bose sl iii works in bionic lubuntu, and in focal ubuntu, but fails in focal lubuntu Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Bug description: blueman-manager successfully pairs and connects to the Bose SL III in both bionic and in focal. in bionic, the Bose SL III then immediately shows up in pavucontrol. in focal, it remains absent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Fri Mar 20 19:53:54 2020 InstallationDate: Installed on 2020-03-15 (5 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1868353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867806] Re: why when i create an icon on the desktop that if goes behind the launcher
This should only happen if your dock is set to automatically hide. Is that set? ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1867806 Title: why when i create an icon on the desktop that if goes behind the launcher Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: when I create an icon on the desktop it goes behind the launcher --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-26 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1867806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868353] Re: regression: Bose SL III works in bionic but not in focal
i installed from this lubuntu iso: 1779384320 2020-03-14 Sat 11:49:43 lubuntu/focal-desktop-amd64.iso i just booted up that iso again, installed blueman and pavucontrol-qt into the live system, and it fails as above. my installed system is fully updated and also still fails as above. so then i downloaded the ubuntu iso: 2810314752 2020-04-01 Wed 11:10:05 ubuntu/focal-desktop-amd64.iso it's a little more recent, which could be the difference, but my bet is the difference is it has more/different packages. it works. so this issue should be re-titled 'regression: bose sl iii works in bionic lubuntu, and in focal ubuntu, but fails in focal lubuntu' and i'm guessing it's a dependency issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1868353 Title: regression: Bose SL III works in bionic but not in focal Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Bug description: blueman-manager successfully pairs and connects to the Bose SL III in both bionic and in focal. in bionic, the Bose SL III then immediately shows up in pavucontrol. in focal, it remains absent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Fri Mar 20 19:53:54 2020 InstallationDate: Installed on 2020-03-15 (5 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1868353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870461] [NEW] zsysd uses more than half of CPU and disk IO
Public bug reported: I was installed Ubuntu 20.04 with zfs yesterday, it was OK until a few updates, after that the zsysd was started draining CPU and IO. How can I fix it to back to normal? Is it possible to rollback recent system state? If Yes, just how? NOTE: I was stopped and disabled zsysd service and removed zsysd.socket file, after that it worked normally for now. I just don't know is this good approach? or not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zsys 0.4.2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 3 05:37:29 2020 InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 focal zfs zsys zsysd ** Attachment added: "htop view" https://bugs.launchpad.net/bugs/1870461/+attachment/5345362/+files/htop.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1870461 Title: zsysd uses more than half of CPU and disk IO Status in zsys package in Ubuntu: New Bug description: I was installed Ubuntu 20.04 with zfs yesterday, it was OK until a few updates, after that the zsysd was started draining CPU and IO. How can I fix it to back to normal? Is it possible to rollback recent system state? If Yes, just how? NOTE: I was stopped and disabled zsysd service and removed zsysd.socket file, after that it worked normally for now. I just don't know is this good approach? or not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zsys 0.4.2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 3 05:37:29 2020 InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym
Sorry for the confusion, I was travelling at the time of comment #20. Mention of "wl_drm_interface" in bug 1866356 convinces me that it's just a duplicate of this one. And this one is still open for bionic. ** Tags added: rls-bb-incoming -- 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/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in Libva: Fix Released Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in intel-vaapi-driver source package in Bionic: Confirmed Status in libva source package in Bionic: Confirmed Status in mesa source package in Bionic: Invalid Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791981] Re: X Server session crash for "No space left on device"
And apparently I solved the mystery. As a desperate attempt I changed the refresh rate of the from 59.xx Hz to 60 Hz, and Xorg stopped crashing coming out of suspend. I suggest giving it a try. Note: I do not know why the screen was initially set to 59.xx Hz. -- 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/1791981 Title: X Server session crash for "No space left on device" Status in Nvidia: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu Release: Ubuntu 18.04.1 LTS Package version: xserver-xorg: 1:7.7+19ubuntu7.1 When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data! The expected behavior would be obviously to restore the suspended session. I had a look through log files and found that Xorg.0.log ends with the following error lines: [ 6004.019] (II) NVIDIA(0): Setting mode "NULL" [ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device [ 6004.026] (EE) Fatal server error: [ 6004.026] (EE) EnterVT failed for gpu screen 0 [ 6004.027] (EE) [ 6004.027] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6004.027] (EE) [ 6004.065] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865079] Re: balance slider mutes sound on midle and left or rigth make loud for both ears
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1865079 Title: balance slider mutes sound on midle and left or rigth make loud for both ears Status in alsa-driver package in Ubuntu: Confirmed Bug description: when using headset audio is inaudible going to settings and putting balance to left or right works kinda like an audio slider with mute at the center and left/right as max for both ears (meaning regular balance functionality does not work) resets to center(mute) whenever plug or unplug regular system volume still works as expected ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vin2991 F pulseaudio /dev/snd/pcmC0D0c: vin2991 F...m pulseaudio /dev/snd/pcmC0D0p: vin2991 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 16:39:32 2020 InstallationDate: Installed on 2019-04-19 (314 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulseAudioLog: fev 27 15:16:09 vin-Aspire-VX5-591G dbus-daemon[1258]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.42' (uid=1001 pid=1542 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [Aspire VX5-591G, Realtek ALC255, Black Headphone Out, Front] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1865079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869597] Re: FF74.0 in UBudgie 19.10 : LIBDBUSMENU-GTK-CRITICAL dbusmenu_menuitem_property_set_shortcut: assertion 'gtk_accelerator_valid(key, modifier)' failed
*** This bug is a duplicate of bug 1870450 *** https://bugs.launchpad.net/bugs/1870450 ** This bug has been marked a duplicate of bug 1870450 Firefox takes a moment before being reactive after launch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1869597 Title: FF74.0 in UBudgie 19.10 : LIBDBUSMENU-GTK-CRITICAL dbusmenu_menuitem_property_set_shortcut: assertion 'gtk_accelerator_valid(key, modifier)' failed Status in firefox package in Ubuntu: New Bug description: Hi, on a freshly installed Ubuntu Budgie 19.10, I've noticed Firefox is kind of slow at start : ⋅ I can launch Firefox but it’s unresponsive for a moment ( no blinking cursor anywhere ) ⋅ then cursor eventually appears in address bar but blinking slowly and not usable, ⋅ still, clicking anywhere has no effect, or effect delayed much later, ⋅ a moment later, cursor blinks at its usual pace and Firefox becomes responsive as expected. The whole process takes 30 seconds to 1 minute and Firefox runs rather ok later on with some slow moments though ( sometimes tabs are slow to react, or any interactions with buttons in FF menu ). Same behavior in safe-mode ( without any FF addons ) Same without any Budgie applets regarding app-menu ( such as pixel- saver or global-menu applets ). see also : ⋅ https://discourse.ubuntubudgie.org/t/firefox-in-19-10-is-kind-of-slow-to-start/3265 ⋅ https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/813775 django@ASGARD:~$ firefox --safe-mode (firefox:19093): LIBDBUSMENU-GTK-CRITICAL **: 22:08:02.177: dbusmenu_menuitem_property_set_shortcut: assertion 'gtk_accelerator_valid(key, modifier)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870450] [NEW] Firefox takes a moment before being reactive after launch
Public bug reported: Hi, sorry for duplicata, I did not know how to add info on the other same bug, see https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869597 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 74.0+build3-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: django 6230 F pulseaudio /dev/snd/controlC1: django 6230 F pulseaudio /dev/snd/pcmC1D0p: django 6230 F...m pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: Budgie:GNOME Date: Fri Apr 3 02:04:06 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:732 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-03-22 (11 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.254 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.99 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:732 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=74.0/20200309095159 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1870450 Title: Firefox takes a moment before being reactive after launch Status in firefox package in Ubuntu: New Bug description: Hi, sorry for duplicata, I did not know how to add info on the other same bug, see https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869597 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 74.0+build3-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: django 6230 F pulseaudio /dev/snd/controlC1: django 6230 F pulseaudio /dev/snd/pcmC1D0p: django 6230 F...m pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: Budgie:GNOME Date: Fri Apr 3 02:04:06 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:732 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-03-22 (11 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.254 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.99 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt
[Desktop-packages] [Bug 1870435] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345264/+files/XorgLogOld.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell
[Desktop-packages] [Bug 1870435] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345265/+files/Xrandr.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc.
[Desktop-packages] [Bug 1870435] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345266/+files/xdpyinfo.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc.
[Desktop-packages] [Bug 1870435] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345262/+files/UdevDb.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc.
[Desktop-packages] [Bug 1870435] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345263/+files/XorgLog.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc.
[Desktop-packages] [Bug 1870435] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345253/+files/CurrentDmesg.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor:
[Desktop-packages] [Bug 1870435] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345258/+files/ProcCpuinfo.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell
[Desktop-packages] [Bug 1870435] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345259/+files/ProcCpuinfoMinimal.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810
[Desktop-packages] [Bug 1870435] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345261/+files/ProcModules.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell
[Desktop-packages] [Bug 1870435] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345260/+files/ProcInterrupts.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810
[Desktop-packages] [Bug 1870435] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345256/+files/Lspci.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc.
[Desktop-packages] [Bug 1870435] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345257/+files/Lsusb.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc.
[Desktop-packages] [Bug 1870435] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345255/+files/DpkgLog.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc.
[Desktop-packages] [Bug 1870435] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1870435/+attachment/5345254/+files/Dependencies.txt -- 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor:
[Desktop-packages] [Bug 1870435] Re: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command
apport information ** Tags added: apport-collected ** Description changed: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + CompositorRunning: None + DistUpgraded: Fresh install + DistroCodename: bionic + DistroRelease: Ubuntu 18.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) +Subsystem: Dell UHD Graphics 620 [1028:0810] + InstallationDate: Installed on 2020-04-01 (1 days ago) + InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) + MachineType: Dell Inc. Inspiron 5570 + Package: xorg 1:7.7+19ubuntu7.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 + Tags: bionic ubuntu + Uname: Linux 5.3.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 05/15/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.2.3 + dmi.board.name: 09YTN7 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5570 + dmi.product.sku: 0810 + dmi.sys.vendor: Dell Inc. + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 + version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 + version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 + version.xserver-xorg-core: xserver-xorg-core N/A + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A +
[Desktop-packages] [Bug 1870443] [NEW] white fonts on white background on highlighted line in gedit with dark-theme
Public bug reported: Gedit with Ubuntu Dark-Theme and Tango shows white fonts on white background when the line is highlighted (current line). Attached image exemplifies it. The expected behaviour is to have a darker background with white fonts, or darker fonts with white background. To fix it i had to change Gedit's Color Scheme or disabling "Highlight current line". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 19:27:57 2020 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Captura de tela de 2020-04-02 19-22-59.png" https://bugs.launchpad.net/bugs/1870443/+attachment/5345248/+files/Captura%20de%20tela%20de%202020-04-02%2019-22-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1870443 Title: white fonts on white background on highlighted line in gedit with dark-theme Status in gedit package in Ubuntu: New Bug description: Gedit with Ubuntu Dark-Theme and Tango shows white fonts on white background when the line is highlighted (current line). Attached image exemplifies it. The expected behaviour is to have a darker background with white fonts, or darker fonts with white background. To fix it i had to change Gedit's Color Scheme or disabling "Highlight current line". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 19:27:57 2020 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1870443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.
I first noticed this issue when I attempted to refresh my feed on Twitter after a Tweet I was writing failed to send. -- 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/1870442 Title: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on. Status in network-manager package in Ubuntu: New Bug description: When I was trying to connect to the network after rebooting the computer, and I disabled verification before the reboot, the laptop connected, but then, even though no other computers had this problem, the speed of the wi-fi shut down, and then the connection with the router dropped. All this until I turned Airplane Mode on and Wi-Fi on my PC for a brief second before disabling airplane mode and reenabling Wi-Fi. Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 2 18:25:30 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 wifi 1585866147 Thu 02 Apr 2020 06:22:27 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 0c4f5994-e9fb-3218-9aa5-d46003ebcd5a ethernet 1585865851 Thu 02 Apr 2020 06:17:31 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1870442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870442] [NEW] Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.
Public bug reported: When I was trying to connect to the network after rebooting the computer, and I disabled verification before the reboot, the laptop connected, but then, even though no other computers had this problem, the speed of the wi-fi shut down, and then the connection with the router dropped. All this until I turned Airplane Mode on and Wi-Fi on my PC for a brief second before disabling airplane mode and reenabling Wi- Fi. Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 2 18:25:30 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 wifi 1585866147 Thu 02 Apr 2020 06:22:27 PM EDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 0c4f5994-e9fb-3218-9aa5-d46003ebcd5a ethernet 1585865851 Thu 02 Apr 2020 06:17:31 PM EDT yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 6fbfa44b-461e-4067-b37a-26f63bc54f88 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1870442 Title: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on. Status in network-manager package in Ubuntu: New Bug description: When I was trying to connect to the network after rebooting the computer, and I disabled verification before the reboot, the laptop connected, but then, even though no other computers had this problem, the speed of the wi-fi shut down, and then the connection with the router dropped. All this until I turned Airplane Mode on and Wi-Fi on my PC for a brief second before disabling airplane mode and reenabling Wi-Fi. Ubuntu 18.04.4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Thu Apr 2 18:25:30 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true
[Desktop-packages] [Bug 1867806] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1867806/+attachment/5345233/+files/GsettingsChanges.txt -- 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/1867806 Title: why when i create an icon on the desktop that if goes behind the launcher Status in gnome-shell package in Ubuntu: Incomplete Bug description: when I create an icon on the desktop it goes behind the launcher --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-26 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867806] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1867806/+attachment/5345235/+files/ShellJournal.txt -- 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/1867806 Title: why when i create an icon on the desktop that if goes behind the launcher Status in gnome-shell package in Ubuntu: Incomplete Bug description: when I create an icon on the desktop it goes behind the launcher --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-26 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867806] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1867806/+attachment/5345234/+files/ProcCpuinfoMinimal.txt -- 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/1867806 Title: why when i create an icon on the desktop that if goes behind the launcher Status in gnome-shell package in Ubuntu: Incomplete Bug description: when I create an icon on the desktop it goes behind the launcher --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-26 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867806] Re: why when i create an icon on the desktop that if goes behind the launcher
apport information ** Tags added: apport-collected ** Description changed: when I create an icon on the desktop it goes behind the launcher + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu21 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-03-26 (7 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) + Package: gnome-shell 3.36.0-2ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 + Tags: focal + Uname: Linux 5.4.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1867806/+attachment/5345232/+files/Dependencies.txt -- 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/1867806 Title: why when i create an icon on the desktop that if goes behind the launcher Status in gnome-shell package in Ubuntu: Incomplete Bug description: when I create an icon on the desktop it goes behind the launcher --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-26 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Both applications are fine with standard Yaru and Adwaita. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Is the problem reproducible with adwaita-dark? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Yes, just tested both applications with Adwaita-dark. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870053] Re: gnome-keyring ftbfs in focal
** Changed in: gnome-keyring (Ubuntu) Importance: High => Low -- 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/1870053 Title: gnome-keyring ftbfs in focal Status in gnome-keyring package in Ubuntu: Triaged Bug description: https://launchpadlibrarian.net/471798344/buildlog_ubuntu-focal-amd64 .gnome-keyring_3.36.0-1ubuntu1_BUILDING.txt.gz seen in the second focal test rebuild: [...] PASS: test-xdg-trust 24 /xdg-store/trust/netscape_map_ipsec_user PASS: test-xdg-trust 25 /xdg-store/trust/netscape_map_time_stamping PASS: test-timer 4 /gkm/timer/multiple PASS: test-timer 5 /gkm/timer/outstanding E: Caught signal ‘Terminated’: terminating immediately make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make[6]: *** Deleting file 'test-gkd-ssh-agent-service.log' make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. make[5]: *** [Makefile:6572: check-TESTS] Terminated make[2]: *** [Makefile:7271: check] Error 2 make[4]: *** [Makefile:7269: check-am] Terminated make[6]: *** [Makefile:6765: test-gkd-ssh-agent-service.log] Terminated Build killed with signal TERM after 150 minutes of inactivity Build finished at 20200330-2014 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1870053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
I've attached a screen shot from a program called Ghidra. It is a Java application and so it may be that it is a different issue. But it is using the GTK theme and the colours look the same as gedit. ** Attachment added: "Screenshot from 2020-04-02 22-42-48.png" https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1857191/+attachment/5345217/+files/Screenshot%20from%202020-04-02%2022-42-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
** Changed in: gtksourceview4 (Ubuntu) Importance: Undecided => Low ** Changed in: gtksourceview4 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870435] [NEW] Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command
Public bug reported: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in xorg package in Ubuntu: New Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic
[Desktop-packages] [Bug 1870424] [NEW] Can not add server cert
Public bug reported:
When I try to add Server Cert to chromium-browser I get the following message
Could Not read the contents of void
Error opening directory '/var/lib/snap/void': Permission denied
This worked on 18.04 but not 19.10.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGr+tCACEcAQS1IhN4Au+Vo1Q1tSYPUFQBAQEBAQEBAQEBAQEBAQEBUtAAoPBwPoAwIDUAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2WkFOMDQuMiAKAZoCAw8A4wWAAOYGBQFgYCgAqg==
modes: 3840x2160
Date: Thu Apr 2 15:55:40 2020
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
pool/home zfs1.3T 148G 1.2T 12% /home
tmpfs tmpfs 32G 45M 32G 1% /dev/shm
pool/home zfs1.3T 148G 1.2T 12% /home
InstallationDate: Installed on 2020-03-30 (3 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QNCTO1WW
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic
root=UUID=6973399c-724d-4607-985d-9426190dc41b ro VGA=1920x1080
Snap.Changes:
ID Status Spawn Ready Summary
7Done2020-04-01T21:41:35-04:00 2020-04-01T21:41:52-04:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.162
(f2c5dd6138153bb0658091205bd1a1717f16081a-refs/branch-heads/3987@{#1034})
Snap.ChromiumVersion: Chromium 80.0.3987.162 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2NET35W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QNCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QNCTO1WW:pvrThinkPadP53:rvnLENOVO:rn20QNCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P53
dmi.product.name: 20QNCTO1WW
dmi.product.sku: LENOVO_MT_20QN_BU_Think_FM_ThinkPad P53
dmi.product.version: ThinkPad P53
dmi.sys.vendor: LENOVO
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan snap
--
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/1870424
Title:
Can not add server cert
Status in chromium-browser package in Ubuntu:
New
Bug description:
When I try to add Server Cert to chromium-browser I get the following message
Could Not read the contents of void
Error opening directory '/var/lib/snap/void': Permission denied
This worked on 18.04 but not 19.10.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGr+tCACEcAQS1IhN4Au+Vo1Q1tSYPUFQBAQEBAQEBAQEBAQEBAQEBUtAAoPBwPoAwIDUAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2WkFOMDQuMiAKAZoCAw8A4wWAAOYGBQFgYCgAqg==
modes: 3840x2160
Date: Thu Apr 2 15:55:40 2020
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
pool/home zfs1.3T 148G 1.2T 12% /home
tmpfs tmpfs 32G 45M 32G 1% /dev/shm
pool/home zfs1.3T 148G 1.2T 12% /home
InstallationDate: Installed on 2020-03-30 (3 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QNCTO1WW
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic
root=UUID=6973399c-724d-4607-985d-9426190dc41b ro VGA=1920x1080
Snap.Changes:
ID Status Spawn
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Which other applications? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
The same issue happens with other applications too. It's not just gedit. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586678] Re: Should have better support for GNOME Online Accounts
** Changed in: thunderbird Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1586678 Title: Should have better support for GNOME Online Accounts Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Triaged Bug description: I think that it would be really good if Thunderbird had proper support for GNOME Online Accounts. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1586678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586678]
I also would enjoy being able to have such an integration, it would offer a more consistent user experience for Linux / Gnome users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1586678 Title: Should have better support for GNOME Online Accounts Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Triaged Bug description: I think that it would be really good if Thunderbird had proper support for GNOME Online Accounts. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1586678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869470] Re: Can't minimize Thunderbird Lightning reminder window
Do you really think it’s an issue with TB and not the window manager? Before I reported the bug here I looked at this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1271097 and it looks like the reminder window can or cannot be minimised depending on where it’s running (it can in Unity, apparently Windows, it can’t in Gnome and MATE). So... it’s WM dependent? ** Bug watch added: Mozilla Bugzilla #1271097 https://bugzilla.mozilla.org/show_bug.cgi?id=1271097 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1869470 Title: Can't minimize Thunderbird Lightning reminder window Status in thunderbird package in Ubuntu: Confirmed Bug description: Ever since Ubuntu moved back to Gnome from Unity, it's impossible to minimize the Thunderbird Lightning reminder window. It's really annoying, the window is always on top of Thunderbird and has to be constantly moved around to use the program. Closing the window makes no sense as a) it tends to start syncing the events with reminders, which can show conflict prompts requiring even more work from the user and b) the window comes back very quickly. So, minimize makes the most sense. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1869470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870414] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
*** This bug is a duplicate of bug 1870380 *** https://bugs.launchpad.net/bugs/1870380 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1870380, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1870414/+attachment/5345113/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1870414/+attachment/5345115/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1870414/+attachment/5345120/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1870414/+attachment/5345121/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1870414/+attachment/5345122/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1870414/+attachment/5345124/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1870414/+attachment/5345125/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1870380 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870414 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() Status in gnome-shell package in Ubuntu: New Bug description: I don't know! ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 16:13:38 2020 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-03-24 (9 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fb1a2be7494 : movsbl (%rdi),%eax PC (0x7fb1a2be7494) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to focal on 2020-03-24 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845801 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch
Update to #5 The WiFi always fails to connect in a TTY with the error: rtlwifi: AP off, try to reconnect now. The WiFi card is the Realtek rtl8723de. I can only download/ping from a TTY via Ethernet connection. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1870111 Title: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch Status in thunderbird package in Ubuntu: Incomplete Bug description: When Launching thunderbird (pinned on Favourites) from the dock/dash it shows 2 orange dots on default theme that is one for email setup and the other for the main window. After setting up an email and closing the email config window, the two dots are still shown on the dash/dock before the icon. Thunderbird causes the graphical session except for the mouse cursor to freeze until I switch to a TTY and reboot. Also when closing thunderbird, one dot is shown and when launching the application the graphical session except for mouse cursor freezes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BuildID: 20200110143530 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 13:26:59 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-03-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.1/20200110143530 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1870111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch
The WiFi that I use refuses to connect via the TTY and works with the graphical session. In the graphical session the WiFi connects sometimes instantly, sometimes with a delay or connects when the Airplane mode is turned on then off again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1870111 Title: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch Status in thunderbird package in Ubuntu: Incomplete Bug description: When Launching thunderbird (pinned on Favourites) from the dock/dash it shows 2 orange dots on default theme that is one for email setup and the other for the main window. After setting up an email and closing the email config window, the two dots are still shown on the dash/dock before the icon. Thunderbird causes the graphical session except for the mouse cursor to freeze until I switch to a TTY and reboot. Also when closing thunderbird, one dot is shown and when launching the application the graphical session except for mouse cursor freezes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BuildID: 20200110143530 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 13:26:59 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-03-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.1/20200110143530 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1870111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I have the same issue on a fresh install of the Focal Beta. Using a GTX1060 with any proprietary drivers (I tested 440, 435, 390) breaks autologin. Removing "splash" from /etc/default/grub and doing "sudo update-grub" fixes it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1868543] Re: New upstream version 68.6.0 available, fixes security vulnerabilities
@Olivier: thank you for the explanation. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6814 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1868543 Title: New upstream version 68.6.0 available, fixes security vulnerabilities Status in thunderbird package in Ubuntu: Fix Released Bug description: There is a new upstream version 68.6.0 available which fixes several medium and high risk security vulnerabilities. Please release a new Ubuntu package ASAP - see the Debian project, which has already done so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1868543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870393] [NEW] Poor contrast in some applications
Public bug reported: In some applications the contrast between the background and text colour is very poor when using the Yaru theme in "Dark Mode". For example, If the theme is set to Dark via the settings application under "Appearance" and gedit (GNOME Text Editor" is launched. The background of the line the cursor is on is light very similar to the text colour. I've attached a screenshot. In the "Standard" mode the theme subtly highlights the current line. But this is not the case for the "Dark" mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:46:15 2020 InstallationDate: Installed on 2020-03-20 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-04-02 17-47-43.png" https://bugs.launchpad.net/bugs/1870393/+attachment/5345056/+files/Screenshot%20from%202020-04-02%2017-47-43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1870393 Title: Poor contrast in some applications Status in yaru-theme package in Ubuntu: New Bug description: In some applications the contrast between the background and text colour is very poor when using the Yaru theme in "Dark Mode". For example, If the theme is set to Dark via the settings application under "Appearance" and gedit (GNOME Text Editor" is launched. The background of the line the cursor is on is light very similar to the text colour. I've attached a screenshot. In the "Standard" mode the theme subtly highlights the current line. But this is not the case for the "Dark" mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:46:15 2020 InstallationDate: Installed on 2020-03-20 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1870393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869470] Re: Can't minimize Thunderbird Lightning reminder window
I can confirm that when using the unity session, the reminder window can be minimized, whereas in the stock (GNOME) Ubuntu session, it cannot, and it remains on top of the main thunderbird window. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1869470 Title: Can't minimize Thunderbird Lightning reminder window Status in thunderbird package in Ubuntu: Confirmed Bug description: Ever since Ubuntu moved back to Gnome from Unity, it's impossible to minimize the Thunderbird Lightning reminder window. It's really annoying, the window is always on top of Thunderbird and has to be constantly moved around to use the program. Closing the window makes no sense as a) it tends to start syncing the events with reminders, which can show conflict prompts requiring even more work from the user and b) the window comes back very quickly. So, minimize makes the most sense. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1869470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869470] Re: Can't minimize Thunderbird Lightning reminder window
Thanks for the report Dominik. Would you mind filing an upstream bug at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CCalendar, and sharing the link to it here? ** Changed in: thunderbird (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1869470 Title: Can't minimize Thunderbird Lightning reminder window Status in thunderbird package in Ubuntu: Confirmed Bug description: Ever since Ubuntu moved back to Gnome from Unity, it's impossible to minimize the Thunderbird Lightning reminder window. It's really annoying, the window is always on top of Thunderbird and has to be constantly moved around to use the program. Closing the window makes no sense as a) it tends to start syncing the events with reminders, which can show conflict prompts requiring even more work from the user and b) the window comes back very quickly. So, minimize makes the most sense. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1869470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c
** Description changed: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as - connecting/disconnecting to the device works perfectly if I use - bluetooth-manager instead of gnome-control-center. + connecting/disconnecting to the device works perfectly if I use blueman- + manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use blueman-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c
It has been reported upstream as well https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/925 It seems the bluetooth panel is generating activity (through sharing/discovery enablement probably) which create access conflicts... https://www.reddit.com/r/gnome/comments/flpy74/does_anyone_else_see_this_bug_with_bluetooth_ive/?sort=new suggests the issue is not new though ** Summary changed: - Can't connect to paired bluetooth devices via g-c-c; works with blueman + Can't connect to paired bluetooth devices via g-c-c ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #925 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/925 ** Changed in: gnome-control-center (Ubuntu) Importance: Low => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/925 Importance: Unknown Status: Unknown -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854676] Re: [snap] Web Midi API doesn't work
I'll need some time. I already have the debian repo version of Chromium installed and I'm concerned that if I also install the snap version of Chromium it might corrupt that setup. I have another computer that I can set up to test this, I'll post back when I do. I'll try to do it tonight. -- 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/1854676 Title: [snap] Web Midi API doesn't work Status in chromium-browser package in Ubuntu: Confirmed Bug description: With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ Although it is supposed to be supported in Chromium, none of these samples work in Ubuntu 19.10's snap-package installation of Chromium: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c; works with blueman
Thanks for the detail. I think if you had let blueman out of the description and focussed on the actual issue the bug would have been easier to understand but I think I understand what you describe now -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870372] Re: nautilus crashed with SIGSEGV in update_dbus_opened_locations()
*** This bug is a duplicate of bug 1869124 *** https://bugs.launchpad.net/bugs/1869124 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1869124, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1870372/+attachment/5344977/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1870372/+attachment/5344979/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1870372/+attachment/5344983/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1870372/+attachment/5344984/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1870372/+attachment/5344985/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1870372/+attachment/5344986/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1870372/+attachment/5344987/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1869124 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1870372 Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations() Status in nautilus package in Ubuntu: New Bug description: Ubuntu 20.04 offered to report this crash. No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 16:38:43 2020 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2020-03-27 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) ProcCmdline: /usr/bin/nautilus --version SegvAnalysis: Segfault happened at: 0x7f1b15a62144:mov0x20(%rdi),%rax PC (0x7f1b15a62144) ok source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 update_dbus_opened_locations () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGSEGV in update_dbus_opened_locations() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1870372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing
Removing ~/snap/chromium/common/.cache/fontconfig was enough for me. It was not necessary to remove the whole .cache directory. I start Chromium with a script which always removes that directory first. But I still observe the broken dialog boxes from time to time. -- 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/1864365 Title: [snap] Dialog font missing Status in chromium-browser package in Ubuntu: Confirmed Bug description: $ lsb_release -rb Description: Ubuntu 19.10 Release: 19.10 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 01:56 CET channels: stable:80.0.3987.116 2020-02-19 (1036) 160MB - candidate: 80.0.3987.116 2020-02-19 (1036) 160MB - beta: 81.0.4044.17 2020-02-17 (1028) 161MB - edge: 81.0.4044.17 2020-02-14 (1028) 161MB - installed: 80.0.3987.116(1036) 160MB - Basic Ubuntu 19.10 installation using "factory default" font settings. Expected : When opening any file dialog (to open or upload a file, for example) from Chromium snap application, the file dialog renders normally. What happened instead: When opening any file dialog (to open or upload a file, for example) from Chromium snap application, all characters in the dialog box are empty squares (see attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869733] Re: Firefox mouse ignored on the whole page but on top bar
Thank you for the report. Could you please elaborate on what you mean by "mouse ignored"? Do you mean that mouse clicks are not registered/handled? Is this on the webcontent only, or also in the address bar and menu buttons? Does this happen all the time, or is being triggered by some action? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1869733 Title: Firefox mouse ignored on the whole page but on top bar Status in firefox package in Ubuntu: Incomplete Bug description: Firefox mouse ignored on the page, NOT ignored if i click the resize icon on the top bar ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: corrado4547 F pulseaudio /dev/snd/controlC0: corrado4547 F pulseaudio /dev/snd/pcmC0D0p: corrado4547 F...m pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 16:31:15 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-03-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) IpRoute: default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.155 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=74.0/20200309095159 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
@ilya Hi, I've heard of people managing to make it work on other models. Are you using the UX580gd as well ? Are you using a dual boot with Windows ? @Taha Apologies, I forgot to subscribe to the bug. Yes I did and met no success :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and screen - all in one) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Oct 1 00:53:26 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.0.0-29-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1021] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:180e] InstallationDate: Installed on 2019-09-27 (3 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GDX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868543] Re: New upstream version 68.6.0 available, fixes security vulnerabilities
There is no other tracker than this bug report. For 18.04 and 19.10, the update is ready and is only pending validation and publication by the security team, I expect this will happen shortly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1868543 Title: New upstream version 68.6.0 available, fixes security vulnerabilities Status in thunderbird package in Ubuntu: Fix Released Bug description: There is a new upstream version 68.6.0 available which fixes several medium and high risk security vulnerabilities. Please release a new Ubuntu package ASAP - see the Debian project, which has already done so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1868543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c; works with blueman
Thanks Sebastien. I already know uninstalling blueman doesn't help as I did install it exactly because I couldn't connect to the bluetooth device with gnome-control-center. I was pretty surprised to see it worked. bluetoothctl behaves exactly like blueman-manager: does not work if gnome-control-center is open on the Bluetooth section, does work otherwise. This is the failure message: Attempting to connect to 00:22:D9:00:1A:6F Failed to connect: org.bluez.Error.Failed I'll reboot before collecting the full `journalctl -b 0` log you requested, so you'll get a cleaner log. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c; works with blueman Status in gnome-control-center package in Ubuntu: New Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854676] Re: [snap] Web Midi API doesn't work
I've tested the demo list, and at least a couple of them work here (tested on 19.10 and 20.04): http://www.cappel-nord.de/webaudio/conways-melodies/ http://webaudiodemos.appspot.com/pitchdetect/index.html In the second one, microphone input doesn't seem to be detected though, but as far as MIDI playback is concerned, it's working. This is with version 80.0.3987.162 of the chromium snap. Would you mind testing again and letting me know whether things have improved since you originally reported the bug? -- 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/1854676 Title: [snap] Web Midi API doesn't work Status in chromium-browser package in Ubuntu: Confirmed Bug description: With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ Although it is supposed to be supported in Chromium, none of these samples work in Ubuntu 19.10's snap-package installation of Chromium: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1870356/+attachment/5344958/+files/ProcCpuinfoMinimal.txt -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c; works with blueman Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c; works with blueman
apport information ** Tags added: apport-collected focal third-party-packages uec-images wayland-session ** Description changed: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. - I don't know if this is a regression as I was not using bluetooth before - installing Focal. FWIW (very little), the device connects/disconnects - perfectly to Android phones. + I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu22 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-02-26 (400 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: gnome-control-center 1:3.36.1-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 + Tags: focal uec-images wayland-session third-party-packages + Uname: Linux 5.4.0-20-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) + UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1870356/+attachment/5344957/+files/Dependencies.txt -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c; works with blueman Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1870356/+attachment/5344959/+files/ProcEnviron.txt -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c; works with blueman Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-02-26 (400 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-control-center 1:3.36.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Tags: focal uec-images wayland-session third-party-packages Uname: Linux 5.4.0-20-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev sambashare sbuild sudo utah _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854676] Re: [snap] Web Midi API doesn't work
** Summary changed: - Web Midi API Doesn't Work in Snap-Version of Chromium + [snap] Web Midi API doesn't work -- 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/1854676 Title: [snap] Web Midi API doesn't work Status in chromium-browser package in Ubuntu: Confirmed Bug description: With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ Although it is supposed to be supported in Chromium, none of these samples work in Ubuntu 19.10's snap-package installation of Chromium: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing
The problem is most likely elsewhere nevertheless, because I don't even have a ~/.fonts directory: $ cd $HOME/.fonts bash: cd: /home/steven/.fonts: No such file or directory Happy to provide any information that can help you, please let me know. -- 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/1864365 Title: [snap] Dialog font missing Status in chromium-browser package in Ubuntu: Confirmed Bug description: $ lsb_release -rb Description: Ubuntu 19.10 Release: 19.10 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 01:56 CET channels: stable:80.0.3987.116 2020-02-19 (1036) 160MB - candidate: 80.0.3987.116 2020-02-19 (1036) 160MB - beta: 81.0.4044.17 2020-02-17 (1028) 161MB - edge: 81.0.4044.17 2020-02-14 (1028) 161MB - installed: 80.0.3987.116(1036) 160MB - Basic Ubuntu 19.10 installation using "factory default" font settings. Expected : When opening any file dialog (to open or upload a file, for example) from Chromium snap application, the file dialog renders normally. What happened instead: When opening any file dialog (to open or upload a file, for example) from Chromium snap application, all characters in the dialog box are empty squares (see attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing
I straced the chromium snap and I'm not seeing anything obviously problematic when opening font files in ~/.fonts/. No related apparmor denials either. ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium -- 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/1864365 Title: [snap] Dialog font missing Status in chromium-browser package in Ubuntu: Confirmed Bug description: $ lsb_release -rb Description: Ubuntu 19.10 Release: 19.10 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 01:56 CET channels: stable:80.0.3987.116 2020-02-19 (1036) 160MB - candidate: 80.0.3987.116 2020-02-19 (1036) 160MB - beta: 81.0.4044.17 2020-02-17 (1028) 161MB - edge: 81.0.4044.17 2020-02-14 (1028) 161MB - installed: 80.0.3987.116(1036) 160MB - Basic Ubuntu 19.10 installation using "factory default" font settings. Expected : When opening any file dialog (to open or upload a file, for example) from Chromium snap application, the file dialog renders normally. What happened instead: When opening any file dialog (to open or upload a file, for example) from Chromium snap application, all characters in the dialog box are empty squares (see attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c; works with blueman
Thank you for your bug report, could you try to uninstall blueman and see if it works better with the default installation software? Can you connect the device from bluetoothctl when you get the issue from gnome-control-center? Could you add your 'journalctl -b 0' log to the bug after getting the issue? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c; works with blueman Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing
And removing the custom font in ~/.fonts appears to resolve the problem. -- 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/1864365 Title: [snap] Dialog font missing Status in chromium-browser package in Ubuntu: Confirmed Bug description: $ lsb_release -rb Description: Ubuntu 19.10 Release: 19.10 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 01:56 CET channels: stable:80.0.3987.116 2020-02-19 (1036) 160MB - candidate: 80.0.3987.116 2020-02-19 (1036) 160MB - beta: 81.0.4044.17 2020-02-17 (1028) 161MB - edge: 81.0.4044.17 2020-02-14 (1028) 161MB - installed: 80.0.3987.116(1036) 160MB - Basic Ubuntu 19.10 installation using "factory default" font settings. Expected : When opening any file dialog (to open or upload a file, for example) from Chromium snap application, the file dialog renders normally. What happened instead: When opening any file dialog (to open or upload a file, for example) from Chromium snap application, all characters in the dialog box are empty squares (see attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing
Thanks for the investigation Chris, I can confirm the problem by following instructions in comment #11. -- 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/1864365 Title: [snap] Dialog font missing Status in chromium-browser package in Ubuntu: Confirmed Bug description: $ lsb_release -rb Description: Ubuntu 19.10 Release: 19.10 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 3 days ago, at 01:56 CET channels: stable:80.0.3987.116 2020-02-19 (1036) 160MB - candidate: 80.0.3987.116 2020-02-19 (1036) 160MB - beta: 81.0.4044.17 2020-02-17 (1028) 161MB - edge: 81.0.4044.17 2020-02-14 (1028) 161MB - installed: 80.0.3987.116(1036) 160MB - Basic Ubuntu 19.10 installation using "factory default" font settings. Expected : When opening any file dialog (to open or upload a file, for example) from Chromium snap application, the file dialog renders normally. What happened instead: When opening any file dialog (to open or upload a file, for example) from Chromium snap application, all characters in the dialog box are empty squares (see attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c; works with blueman
More data points: - When I try to connect from gnome-control-center, this error is logged: bluetoothd[1635]: connect error: Device or resource busy (16) - Connecting *fails* from blueman-manager if gnome-control-center is open at the Bluetooth section at the same time. The same error is logged. When another section is selected in gnome-control-center, then blueman-manager will work. It's like if gnome-control-center is keeping the device busy (always scanning?), preventing connections. -- 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/1870356 Title: Can't connect to paired bluetooth devices via g-c-c; works with blueman Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have a paired bluetooth device listed as "Disconnected" in the Bluetooth section of gnome-control-center. In order to connect to it I click on the device name and switch the "Connection" slider to the "on" position. The slider moves but immediately bounces back to the "off" position, and nothing happens: the connection is not established. It never works even if I try several times. This happens on an up-to-date Focal system and it's always reproducible across reboots and power cycles of the device. I don't think it's a problem of the device itself or of the underlying bluetooth stack, as connecting/disconnecting to the device works perfectly if I use bluetooth-manager instead of gnome-control-center. I don't know if this is a regression as I was not using bluetooth before installing Focal. FWIW (very little), the device connects/disconnects perfectly to Android phones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864001] Re: Dialog windows of Chromium with unprintable characters
*** This bug is a duplicate of bug 1864365 *** https://bugs.launchpad.net/bugs/1864365 ** This bug has been marked a duplicate of bug 1864365 [snap] Dialog font missing -- 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/1864001 Title: Dialog windows of Chromium with unprintable characters Status in chromium-browser package in Ubuntu: New Bug description: In Chromium with the following version numbers (output of “snap list”): chromium 80.0.3987.100 1026 stable canonical✓ - (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable characters, i.e., I see only small boxes instead of letters. I don’t observe this in comparable dialogs of other programs, e.g. Inkscape. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons anymore
Tested to create a new user there the icons seem to be able to drag fine with the dock only to the left side at the right side they drag only at the upper half part of the dock down they do not drag at all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867613 Title: Ubuntu dock does not allow drag and move icons anymore Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 daily development branch @ 16/3/2020 After a clean install daily at 14/3/2020 the ubuntu dock does not allow drag and move icons anymore you can still mouseclick and hold the icon, but it does not make space between other icons to release starting an application still showing the icon, and add to favorites still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 12:31:30 2020 InstallationDate: Installed on 2020-03-14 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870161] Re: Tabs in Firefox 74.0 crash on some websites: [GFX1-]: DrawTargetCairo::Snapshot with bad surface
Thanks for the additional information. I'm marking the bug confirmed, per the upstream crash reports. Hopefully this will be investigated upstream. The only thing that stands out in your updates' log is the kernel one. ** Changed in: firefox (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1870161 Title: Tabs in Firefox 74.0 crash on some websites: [GFX1-]: DrawTargetCairo::Snapshot with bad surface Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu: 19.10 Firefox: 74.0+build3-0ubuntu0.19.10.1 Since 2020.03.31 tabs in Firefox started to crash regularly on some websites (mainly Vbulletin and phpBB forums). This happens also in --safe-mode. stderr output (just this one line): [GFX1-]: DrawTargetCairo::Snapshot with bad surface 0x7efdd6d99b00, context 0x7efdd5cba000, status 0 When trying to reload tabs they keep crashing, but after like 10-20 retries they display properly and continue to work fine. Example of a website that regularly crashes Firefox: https://aryion.com/forum/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
