[Desktop-packages] [Bug 1901391] Re: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement)
Looks like the mutter part is still in proposed (3.38.3-2ubuntu1). ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Fix Committed ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1901391 Title: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I'm using gnome-shell with wayland (don't know if that matters), and, when I press CTRL-ALT-SHIFT-R, nothing happens. I checked my keyboard shortcuts, and this shortcut is supposed to trigger screencasting. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Oct 25 10:39:48 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-07 (260 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1901391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Hi, thanks, can't I just do a sudo apt purge linux-generic-hwe-20.04 ? For now, i'll keep the choice to boot on kernel 5.8 or 5.4. About the subject you opened on https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 it seems to have some news. That's very technical, can you put here informations when you have a piece of solution ? Many thanks -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Sorry to hear that. To remove the 5.8 kernel packages, first run this
command to find their names:
dpkg -l | grep 5.8.0 | grep linux | awk '{print $2;}'
Then you can remove them with:
sudo dpkg -P PACKAGENAMES
--
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/1871959
Title:
Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Status in Mesa:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f
---
nothing particular done to trigger this, just opening the lid
apparently crashed the x server (ubuntu 20.04); then after reboot
apport prompted me to report a crash
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.7-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CompositorRunning: None
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Apr 10 00:50:52 2020
DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
DistroCodename: focal
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
InstallationDate: Installed on 2019-11-27 (134 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device 003: ID 8087:0029 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5500
ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet
splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
__GI_abort () at abort.c:79
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
Title: Xorg crashed with SIGABRT in __GI_raise()
UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
UserGroups:
dmi.bios.date: 08/21/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 0M14W7
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5500
dmi.product.sku: 08B9
dmi.sys.vendor: Dell Inc.
separator:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/mesa/+bug/1871959/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Hello, This is why you have no report from kernel 5.8+ : "The supported kernel version range is from 4.15 to 5.5, minimum supported Xorg version is 1.16 and minimum supported Mutter (Wayland) is 3.32." https://support.displaylink.com/knowledgebase/articles/684649 Some people seems to have kernel 5.9 working, but I tried without success, still have the above message. Here's an entry on DisplayLink forum with the same problem : https://displaylink.org/forum/showthread.php?t=67561 I can't create an account on this forum, don't know why... The mail with code never arrive. If anyone has my problem, he can reply on displaylink forum to get help with kernel 5.8+ Here's a tuto for kernel 5.9, don't work for me, but seemed to help sometimes : https://displaylink.org/forum/showpost.php?p=90853=2 -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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:
[Desktop-packages] [Bug 1913601] Re: add-apt-repository does not correctly enable sources
This bug was fixed in the package software-properties - 0.99.7 --- software-properties (0.99.7) hirsute; urgency=medium * Fix add-apt-repository operation (LP: #1913601) * Add build-time test for add-apt-repository * Remove autopkgtests for add-apt-repository -- Dan Streetman Thu, 11 Feb 2021 06:51:01 -0500 ** Changed in: software-properties (Ubuntu Hirsute) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1913601 Title: add-apt-repository does not correctly enable sources Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Groovy: In Progress Status in software-properties source package in Hirsute: Fix Released Bug description: [impact] 'add-apt-repository -s' should enable deb-src for all existing repos, but doesn't [test case] root@sp-g:~# add-apt-repository -sL deb http://archive.ubuntu.com/ubuntu groovy restricted universe multiverse main deb http://archive.ubuntu.com/ubuntu groovy-updates restricted universe multiverse main deb http://archive.ubuntu.com/ubuntu groovy-backports restricted universe multiverse main deb http://security.ubuntu.com/ubuntu groovy-security restricted universe multiverse main root@sp-g:~# add-apt-repository -s Enabling deb-src for all repositories. Press [ENTER] to continue or Ctrl-c to cancel. Enabled: None Enabled: None Enabled: deb-src http://archive.ubuntu.com/ubuntu groovy-backports multiverse universe restricted main Enabled: deb-src http://archive.canonical.com/ubuntu groovy partner Enabled: None Hit:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Get:2 http://security.ubuntu.com/ubuntu groovy-security/universe Sources [6608 B] Hit:3 http://archive.ubuntu.com/ubuntu groovy InRelease Hit:4 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Get:6 http://archive.ubuntu.com/ubuntu groovy/multiverse Sources [279 kB] Get:7 http://archive.ubuntu.com/ubuntu groovy/universe Sources [16.3 MB] Get:8 http://archive.canonical.com/ubuntu groovy InRelease [11.4 kB] Get:9 http://archive.ubuntu.com/ubuntu groovy-updates/multiverse Sources [3124 B] Get:10 http://archive.ubuntu.com/ubuntu groovy-updates/universe Sources [19.0 kB] Get:11 http://archive.ubuntu.com/ubuntu groovy-backports/universe Sources [2004 B] Get:12 http://archive.canonical.com/ubuntu groovy/partner Sources [720 B] Fetched 16.6 MB in 6s (2884 kB/s) Reading package lists... Done root@sp-g:~# add-apt-repository -sL deb http://archive.ubuntu.com/ubuntu groovy multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy multiverse universe deb http://archive.ubuntu.com/ubuntu groovy-updates multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy-updates multiverse universe deb http://archive.ubuntu.com/ubuntu groovy-backports multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy-backports multiverse restricted main universe deb-src http://archive.canonical.com/ubuntu groovy partner deb http://security.ubuntu.com/ubuntu groovy-security multiverse restricted main universe deb-src http://security.ubuntu.com/ubuntu groovy-security multiverse universe [regression potential] any regression would likely cause add-apt-repository to incorrectly update the apt sources.list and/or sources.list.d file(s), most likely when modifying the deb-src lines [scope] this is needed in g and later the --enable-source parameter in focal and earlier could only be used with a specific repo to be modified, so this is not applicable to f or earlier To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1913601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874438] Re: [USB-Audio - USB Device 0x46d:0x802, recording] Sound is distorted
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/874438 Title: [USB-Audio - USB Device 0x46d:0x802, recording] Sound is distorted Status in alsa-driver package in Ubuntu: Expired Bug description: In natty the sound on this device was flawless. On a fresh install of Oneiric I sound more like Alvin and the Chipmunks. I've tried plugging in a headset on the off chance that it was a device driver at fault no joy. So it can only be a codec (but you'd have more reports) or an issue with the onboard soundcard driver. I'll have and tinker and report any improvements here. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: davmor21574 F pulseaudio /dev/snd/controlC0: davmor21574 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xdfef8000 irq 22' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18493662,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'U0x46d0x802'/'USB Device 0x46d:0x802 at usb-:00:02.1-3.1, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0802' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6144 Mono: Capture 5711 [93%] [28.30dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xdffbc000 irq 43' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Oct 14 17:53:17 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:U0x46d0x802 successful Symptom_Card: Manhattan HDMI Audio [Mobility Radeon HD 5000 Series] - HD-Audio Generic Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:U0x46d0x802 successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - USB Device 0x46d:0x802, recording] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: N61P-S 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.00:bd09/18/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnN61P-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915481] Re: gnome crashes after running `apt upgrade`
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: 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/1915481 Title: gnome crashes after running `apt upgrade` Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915481] Re: gnome crashes after running `apt upgrade`
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915481 Title: gnome crashes after running `apt upgrade` Status in gnome-shell package in Ubuntu: New Bug description: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915449] Re: XWayland hangs at 100% of CPU causing gnome-shell to hang
I've been looking at the code but isn't really much different on that
scenario so far...
--
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/1915449
Title:
XWayland hangs at 100% of CPU causing gnome-shell to hang
Status in X.Org X server:
Unknown
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
This is happening in Hirsute (running in vmware player) quite easily,
just move around a firefox (or any other x11 window) around, hitting
the shell edges and you'll get all freezing with Xwayland process at
100%.
Hangs seems to have this trace:
0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at
../../../../../hw/xwayland/xwayland.c:869
869 ../../../../../hw/xwayland/xwayland.c: No such file or directory.
(gdb) bt
#0 0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0)
at ../../../../../hw/xwayland/xwayland.c:869
#1 block_handler (data=0x55b9ac423dd0, timeout=) at
../../../../../hw/xwayland/xwayland.c:1037
#2 0x55b9ac0ecf3e in BlockHandler
(pTimeout=pTimeout@entry=0x7ffdc8574204) at ../../../../dix/dixutils.c:388
#3 0x55b9ac119a52 in WaitForSomething (are_ready=0) at
../../../../os/WaitFor.c:201
#4 0x55b9ac0e8297 in Dispatch () at ../../../../dix/dispatch.c:421
#5 0x55b9ac0ec5a4 in dix_main (argc=16, argv=0x7ffdc85743e8,
envp=) at ../../../../dix/main.c:276
#6 0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 ,
argc=16, argv=0x7ffdc85743e8, init=,
fini=, rtld_fini=,
stack_end=0x7ffdc85743d8) at ../csu/libc-start.c:332
#7 0x55b9abfb5abe in _start ()
(gdb) info local
xwl_window = 0x55b9acbf18f0
next_xwl_window = 0x7ffdc8574150
commit_window_list = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
xwl_window =
next_xwl_window =
commit_window_list = {next = , prev = }
(gdb) print commit_window_list
$1 = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
(gdb) print commit_window_list->next
$2 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next
$3 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next
$4 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next
$5 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next->next->next
$6 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next->next->next
$7 = (struct xorg_list *) 0x7ffdc8574170
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1915449/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915481] [NEW] gnome crashes after running `apt upgrade`
You have been subscribed to a public bug: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core- launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- gnome crashes after running `apt upgrade` https://bugs.launchpad.net/bugs/1915481 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915449] Re: XWayland hangs at 100% of CPU causing gnome-shell to hang
It might be worth trying the newer version of Xwayland being prepared
here:
https://launchpad.net/ubuntu/+source/xwayland
--
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/1915449
Title:
XWayland hangs at 100% of CPU causing gnome-shell to hang
Status in X.Org X server:
Unknown
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
This is happening in Hirsute (running in vmware player) quite easily,
just move around a firefox (or any other x11 window) around, hitting
the shell edges and you'll get all freezing with Xwayland process at
100%.
Hangs seems to have this trace:
0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at
../../../../../hw/xwayland/xwayland.c:869
869 ../../../../../hw/xwayland/xwayland.c: No such file or directory.
(gdb) bt
#0 0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0)
at ../../../../../hw/xwayland/xwayland.c:869
#1 block_handler (data=0x55b9ac423dd0, timeout=) at
../../../../../hw/xwayland/xwayland.c:1037
#2 0x55b9ac0ecf3e in BlockHandler
(pTimeout=pTimeout@entry=0x7ffdc8574204) at ../../../../dix/dixutils.c:388
#3 0x55b9ac119a52 in WaitForSomething (are_ready=0) at
../../../../os/WaitFor.c:201
#4 0x55b9ac0e8297 in Dispatch () at ../../../../dix/dispatch.c:421
#5 0x55b9ac0ec5a4 in dix_main (argc=16, argv=0x7ffdc85743e8,
envp=) at ../../../../dix/main.c:276
#6 0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 ,
argc=16, argv=0x7ffdc85743e8, init=,
fini=, rtld_fini=,
stack_end=0x7ffdc85743d8) at ../csu/libc-start.c:332
#7 0x55b9abfb5abe in _start ()
(gdb) info local
xwl_window = 0x55b9acbf18f0
next_xwl_window = 0x7ffdc8574150
commit_window_list = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
xwl_window =
next_xwl_window =
commit_window_list = {next = , prev = }
(gdb) print commit_window_list
$1 = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
(gdb) print commit_window_list->next
$2 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next
$3 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next
$4 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next
$5 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next->next->next
$6 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next->next->next
$7 = (struct xorg_list *) 0x7ffdc8574170
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1915449/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915455] Re: Problème affichage
Thanks for the bug report. The attached kernel log appears to show the problem: [ 3550.311498] i915 :00:02.0: GPU HANG: ecode 4:1:0xeee5fad6, in Xorg [1573], hang on rcs0 [ 3555.497536] i915 :00:02.0: intel_gt_reset_global timed out, cancelling all in-flight rendering. [ 3555.501693] i915 :00:02.0: Resetting chip for hang on rcs0 [ 4192.516761] perf: interrupt took too long (12630 > 12601), lowering kernel.perf_event_max_sample_rate to 15750 [ 8281.689442] i915 :00:02.0: Resetting chip for hang on rcs0 [13280.554731] TCP: enp2s0: Driver has suspect GRO implementation, TCP performance may be compromised. [16940.329087] i915 :00:02.0: Resetting chip for hang on rcs0 so I will assign this to the kernel. Although 5.4.96-050496-generic might not be officially supported by Ubuntu :( ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915455 Title: Problème affichage Status in linux package in Ubuntu: Confirmed Bug description: Le pc se fige pendant quelques secondes ensuite l'écran devient noir et tout redevient normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.96-050496-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 22:14:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller [1043:81ea] InstallationDate: Installed on 2021-02-06 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.96-050496-generic root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0510 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-VM 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.:bvr0510:bd05/22/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/linux/+bug/1915455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915014] Re: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot
Yes, it sounds like it's related to frames where the whole screen is changing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1915014 Title: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot Status in mutter package in Ubuntu: Incomplete Bug description: Weird issue which has come to my system via updates - possibly the Linux kernel 5.8? Steps to repro: - Take a screenshot (prt scr) - Continue using the computer After I have taken a screenshot, my display gets quick black flashes when using other applications. Manipulating the screenshot with Pinta, opening web browser, etc.. Screen goes black for a second and then resumes normal operation. This does not happen before taking the screenshot, so it obviously triggers something. The system works and is usable, but the black flashes are pretty odd and distracting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:39:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1025:1367] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:1366] InstallationDate: Installed on 2020-05-16 (268 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Nitro AN515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=675bb42c-4c3c-461b-bce1-53e34e786eaa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 1.8 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd12/24/2019:br1.8:efr1.5:svnAcer:pnNitroAN515-43:pvrV1.08:rvnPK:rnOctavia_PKS:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1915014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915382] Re: external Monitor shows »No Signal« after dpms sleep
** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1915382 Title: external Monitor shows »No Signal« after dpms sleep Status in xorg-server package in Ubuntu: New Bug description: My external Monitor connected via HDMI is behaving strange and my educated guess is it is related to dpms. Plugging in the monitor it will show »No Signal« although recognized by `xrandr`. I would have to boot my machine with the monitor plugged in to make it work. When going to standby (screen blanks after lock, then screen goes to standby) the monitor is switched on (LED is going white) and shortly after it will show the no-signal-message. `xrandr` claims the monitor to be existent. Unplugging and replugging does not help. Same happens when logging out to greeter. Strange in so far as when booting up, the greeter is okay with the monitor. When issuing `xset -dpms` the behaviour changes and the monitor will enter sleep and come back as expected when locking the session. Console (tty1-6) is available though at all times. (I generated the bug report with dpms set off accidentally) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Feb 11 09:51:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2021-02-10 (0 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: Dell Inc. Precision 7550 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 090NVT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd07/15/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn090NVT:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Please try the suggestion in comment #60. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
If you have any information about this bug then please put it in the upstream issue for the developers to see: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2872 ** Tags added: bionic 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/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-3.38.4 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915175] Re: wifi network stops working and shows a green wifi icon
** Description changed: I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at first the wifi worked fine, but suddenly the wifi stopped connecting, and after a few seconds it said "unable to activate network". I checked the "additional drivers tab" and it showed my wifi adapter, but it said "this device is using an alternate driver". right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it stops working, usually after suspend. UPDATE #1: Apparently it's working now, I suppose it's from an update. Anyways I guess it's fixed. + + UPDATE #2: it's broken again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 12:09:28 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2021-02-08T22:50:26.196692 nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Betancur 5G cda009c8-c845-4366-8436-8e9c44da2cbf /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled -- 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/1915175 Title: wifi network stops working and shows a green wifi icon Status in network-manager package in Ubuntu: New Bug description: I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at first the wifi worked fine, but suddenly the wifi stopped connecting, and after a few seconds it said "unable to activate network". I checked the "additional drivers tab" and it showed my wifi adapter, but it said "this device is using an alternate driver". right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it stops working, usually after suspend. UPDATE #1: Apparently it's working now, I suppose it's from an update. Anyways I guess it's fixed. UPDATE #2: it's broken again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 12:09:28 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2021-02-08T22:50:26.196692 nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Betancur 5G cda009c8-c845-4366-8436-8e9c44da2cbf /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING
[Desktop-packages] [Bug 1913781] Re: gnome-session-properties allow to explore all file system
** Attachment removed: "image.png" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1913781/+attachment/5460723/+files/image.png -- 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/1913781 Title: gnome-session-properties allow to explore all file system Status in gnome-session package in Ubuntu: Invalid Bug description: With Startup applications, you can explore the entire file system without privilege, including other users' files. You can run any command on the administrator files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1913781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913781] Re: gnome-session-properties allow to explore all file system
Thanks for following up, Magdalena. This is not a bug, but rather expected behavior: https://wiki.ubuntu.com/SecurityTeam/Policies#Home_Directory_Access Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Invalid -- 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/1913781 Title: gnome-session-properties allow to explore all file system Status in gnome-session package in Ubuntu: Invalid Bug description: With Startup applications, you can explore the entire file system without privilege, including other users' files. You can run any command on the administrator files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1913781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915468] [NEW] calendar should have a button in its top bar
Public bug reported: Having a "synchronize' entry in a dropdown list is VERY userUNfriendly. I cannot imagine the mindset that deems it okay. The button should always be visible, so put it on the top bar of the application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 10:09:20 2021 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2021-01-14 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1915468 Title: calendar should have a button in its top bar Status in gnome-calendar package in Ubuntu: New Bug description: Having a "synchronize' entry in a dropdown list is VERY userUNfriendly. I cannot imagine the mindset that deems it okay. The button should always be visible, so put it on the top bar of the application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 10:09:20 2021 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2021-01-14 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1915468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891767] Re: Nautilus does not show video thumbnails
nautilus starts thumbnailer, but this times out: 49547 ?Sl 0:01 \_ /usr/bin/nautilus --gapplication-service 49596 ?S 0:00 \_ bwrap --ro-bind /usr /usr --ro-bind /etc/ld.so.cache /etc/ld.so.cache --ro-bind /bin /bin --ro-bind /lib64 /lib64 49597 ?S 0:00 \_ bwrap --ro-bind /usr /usr --ro-bind /etc/ld.so.cache /etc/ld.so.cache --ro-bind /bin /bin --ro-bind /lib64 /l 49598 ?SNLl 0:00 \_ /usr/bin/totem-video-thumbnailer -s 256 file:///tmp/2007-10-04T194656Spiel.mkv /tmp/gnome-desktop-thumbna -- 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/1891767 Title: Nautilus does not show video thumbnails Status in nautilus package in Ubuntu: Expired Bug description: Using Ubuntu 20.10 (Groovy) Daily Live, GNOME session (gnome-session) on Wayland. Nautilus is no longer showing thumbnails (generated by Totem) for some video files, although the Totem thumbnail generator (totem-video-thumbnailer) is working. Nautilus is showing thumbnails for video files with (Ogg) Theora codec content (even if wrapped in a non-Ogg file format, such as mkv), but not for others, although I have installed all the required/usual libraries (libav*, gstreamer1*). Deleting the thumbnail fail cache (~/.cache/thumbnails/fail/) does not help. Installing ffmpegthumbnailer does not help either. This seems to be a regression, or maybe some libraries for video files in non-free codec formats have not been updated properly. Package versions are as follows:- Nautilus: 1:3.37.90-1ubuntu1 Totem: 3.34.1-2ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Aug 15 23:47:22 2020 InstallationDate: Installed on 2020-08-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200814) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
** Changed in: systemd (Ubuntu) Assignee: Ubuntu containers team (ubuntu-lxc) => Christian Brauner (cbrauner) -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915449] Re: XWayland hangs at 100% of CPU causing gnome-shell to hang
Upstream issue:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1132
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1132
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1132
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1132
Importance: Unknown
Status: Unknown
--
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/1915449
Title:
XWayland hangs at 100% of CPU causing gnome-shell to hang
Status in X.Org X server:
Unknown
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
This is happening in Hirsute (running in vmware player) quite easily,
just move around a firefox (or any other x11 window) around, hitting
the shell edges and you'll get all freezing with Xwayland process at
100%.
Hangs seems to have this trace:
0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at
../../../../../hw/xwayland/xwayland.c:869
869 ../../../../../hw/xwayland/xwayland.c: No such file or directory.
(gdb) bt
#0 0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0)
at ../../../../../hw/xwayland/xwayland.c:869
#1 block_handler (data=0x55b9ac423dd0, timeout=) at
../../../../../hw/xwayland/xwayland.c:1037
#2 0x55b9ac0ecf3e in BlockHandler
(pTimeout=pTimeout@entry=0x7ffdc8574204) at ../../../../dix/dixutils.c:388
#3 0x55b9ac119a52 in WaitForSomething (are_ready=0) at
../../../../os/WaitFor.c:201
#4 0x55b9ac0e8297 in Dispatch () at ../../../../dix/dispatch.c:421
#5 0x55b9ac0ec5a4 in dix_main (argc=16, argv=0x7ffdc85743e8,
envp=) at ../../../../dix/main.c:276
#6 0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 ,
argc=16, argv=0x7ffdc85743e8, init=,
fini=, rtld_fini=,
stack_end=0x7ffdc85743d8) at ../csu/libc-start.c:332
#7 0x55b9abfb5abe in _start ()
(gdb) info local
xwl_window = 0x55b9acbf18f0
next_xwl_window = 0x7ffdc8574150
commit_window_list = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
xwl_window =
next_xwl_window =
commit_window_list = {next = , prev = }
(gdb) print commit_window_list
$1 = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
(gdb) print commit_window_list->next
$2 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next
$3 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next
$4 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next
$5 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next->next->next
$6 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next->next->next
$7 = (struct xorg_list *) 0x7ffdc8574170
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1915449/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915455] [NEW] Problème affichage
Public bug reported: Le pc se fige pendant quelques secondes ensuite l'écran devient noir et tout redevient normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.96-050496-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 22:14:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller [1043:81ea] InstallationDate: Installed on 2021-02-06 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.96-050496-generic root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0510 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-VM 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.:bvr0510:bd05/22/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1915455 Title: Problème affichage Status in xorg package in Ubuntu: New Bug description: Le pc se fige pendant quelques secondes ensuite l'écran devient noir et tout redevient normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.96-050496-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 22:14:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller [1043:81ea] InstallationDate: Installed on 2021-02-06 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.96-050496-generic root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0510 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-VM 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.:bvr0510:bd05/22/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
[Desktop-packages] [Bug 1915449] Re: XWayland hangs at 100% of CPU causing gnome-shell to hang
** Description changed:
- This is happening in Hirsute quite easily, just move around a firefox
- (or any other x11 window) around, hitting the shell edges and you'll get
- all freezing with Xwayland process at 100%.
+ This is happening in Hirsute (running in vmware player) quite easily,
+ just move around a firefox (or any other x11 window) around, hitting the
+ shell edges and you'll get all freezing with Xwayland process at 100%.
Hangs seems to have this trace:
0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at
../../../../../hw/xwayland/xwayland.c:869
869 ../../../../../hw/xwayland/xwayland.c: No such file or directory.
(gdb) bt
#0 0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0)
at ../../../../../hw/xwayland/xwayland.c:869
#1 block_handler (data=0x55b9ac423dd0, timeout=) at
../../../../../hw/xwayland/xwayland.c:1037
#2 0x55b9ac0ecf3e in BlockHandler
(pTimeout=pTimeout@entry=0x7ffdc8574204) at ../../../../dix/dixutils.c:388
#3 0x55b9ac119a52 in WaitForSomething (are_ready=0) at
../../../../os/WaitFor.c:201
#4 0x55b9ac0e8297 in Dispatch () at ../../../../dix/dispatch.c:421
#5 0x55b9ac0ec5a4 in dix_main (argc=16, argv=0x7ffdc85743e8,
envp=) at ../../../../dix/main.c:276
- #6 0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 ,
argc=16, argv=0x7ffdc85743e8, init=,
- fini=, rtld_fini=,
stack_end=0x7ffdc85743d8) at ../csu/libc-start.c:332
+ #6 0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 ,
argc=16, argv=0x7ffdc85743e8, init=,
+ fini=, rtld_fini=,
stack_end=0x7ffdc85743d8) at ../csu/libc-start.c:332
#7 0x55b9abfb5abe in _start ()
(gdb) info local
xwl_window = 0x55b9acbf18f0
next_xwl_window = 0x7ffdc8574150
commit_window_list = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
xwl_window =
next_xwl_window =
commit_window_list = {next = , prev = }
-
(gdb) print commit_window_list
$1 = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
(gdb) print commit_window_list->next
$2 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next
$3 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next
$4 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next
$5 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next->next->next
$6 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next->next->next
$7 = (struct xorg_list *) 0x7ffdc8574170
** Tags added: rls-hh-incoming
--
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/1915449
Title:
XWayland hangs at 100% of CPU causing gnome-shell to hang
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
This is happening in Hirsute (running in vmware player) quite easily,
just move around a firefox (or any other x11 window) around, hitting
the shell edges and you'll get all freezing with Xwayland process at
100%.
Hangs seems to have this trace:
0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at
../../../../../hw/xwayland/xwayland.c:869
869 ../../../../../hw/xwayland/xwayland.c: No such file or directory.
(gdb) bt
#0 0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0)
at ../../../../../hw/xwayland/xwayland.c:869
#1 block_handler (data=0x55b9ac423dd0, timeout=) at
../../../../../hw/xwayland/xwayland.c:1037
#2 0x55b9ac0ecf3e in BlockHandler
(pTimeout=pTimeout@entry=0x7ffdc8574204) at ../../../../dix/dixutils.c:388
#3 0x55b9ac119a52 in WaitForSomething (are_ready=0) at
../../../../os/WaitFor.c:201
#4 0x55b9ac0e8297 in Dispatch () at ../../../../dix/dispatch.c:421
#5 0x55b9ac0ec5a4 in dix_main (argc=16, argv=0x7ffdc85743e8,
envp=) at ../../../../dix/main.c:276
#6 0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 ,
argc=16, argv=0x7ffdc85743e8, init=,
fini=, rtld_fini=,
stack_end=0x7ffdc85743d8) at ../csu/libc-start.c:332
#7 0x55b9abfb5abe in _start ()
(gdb) info local
xwl_window = 0x55b9acbf18f0
next_xwl_window = 0x7ffdc8574150
commit_window_list = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
xwl_window =
next_xwl_window =
commit_window_list = {next = , prev = }
(gdb) print commit_window_list
$1 = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
(gdb) print commit_window_list->next
$2 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next
$3 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next
$4 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next
$5 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print
[Desktop-packages] [Bug 1915449] [NEW] XWayland hangs at 100% of CPU causing gnome-shell to hang
Public bug reported:
This is happening in Hirsute quite easily, just move around a firefox
(or any other x11 window) around, hitting the shell edges and you'll get
all freezing with Xwayland process at 100%.
Hangs seems to have this trace:
0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at
../../../../../hw/xwayland/xwayland.c:869
869 ../../../../../hw/xwayland/xwayland.c: No such file or directory.
(gdb) bt
#0 0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at
../../../../../hw/xwayland/xwayland.c:869
#1 block_handler (data=0x55b9ac423dd0, timeout=) at
../../../../../hw/xwayland/xwayland.c:1037
#2 0x55b9ac0ecf3e in BlockHandler (pTimeout=pTimeout@entry=0x7ffdc8574204)
at ../../../../dix/dixutils.c:388
#3 0x55b9ac119a52 in WaitForSomething (are_ready=0) at
../../../../os/WaitFor.c:201
#4 0x55b9ac0e8297 in Dispatch () at ../../../../dix/dispatch.c:421
#5 0x55b9ac0ec5a4 in dix_main (argc=16, argv=0x7ffdc85743e8,
envp=) at ../../../../dix/main.c:276
#6 0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 ,
argc=16, argv=0x7ffdc85743e8, init=,
fini=, rtld_fini=, stack_end=0x7ffdc85743d8)
at ../csu/libc-start.c:332
#7 0x55b9abfb5abe in _start ()
(gdb) info local
xwl_window = 0x55b9acbf18f0
next_xwl_window = 0x7ffdc8574150
commit_window_list = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
xwl_window =
next_xwl_window =
commit_window_list = {next = , prev = }
(gdb) print commit_window_list
$1 = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
(gdb) print commit_window_list->next
$2 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next
$3 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next
$4 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next
$5 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next->next->next
$6 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next->next->next
$7 = (struct xorg_list *) 0x7ffdc8574170
** Affects: xorg-server (Ubuntu)
Importance: High
Status: Triaged
--
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/1915449
Title:
XWayland hangs at 100% of CPU causing gnome-shell to hang
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
This is happening in Hirsute quite easily, just move around a firefox
(or any other x11 window) around, hitting the shell edges and you'll
get all freezing with Xwayland process at 100%.
Hangs seems to have this trace:
0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at
../../../../../hw/xwayland/xwayland.c:869
869 ../../../../../hw/xwayland/xwayland.c: No such file or directory.
(gdb) bt
#0 0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0)
at ../../../../../hw/xwayland/xwayland.c:869
#1 block_handler (data=0x55b9ac423dd0, timeout=) at
../../../../../hw/xwayland/xwayland.c:1037
#2 0x55b9ac0ecf3e in BlockHandler
(pTimeout=pTimeout@entry=0x7ffdc8574204) at ../../../../dix/dixutils.c:388
#3 0x55b9ac119a52 in WaitForSomething (are_ready=0) at
../../../../os/WaitFor.c:201
#4 0x55b9ac0e8297 in Dispatch () at ../../../../dix/dispatch.c:421
#5 0x55b9ac0ec5a4 in dix_main (argc=16, argv=0x7ffdc85743e8,
envp=) at ../../../../dix/main.c:276
#6 0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 ,
argc=16, argv=0x7ffdc85743e8, init=,
fini=, rtld_fini=,
stack_end=0x7ffdc85743d8) at ../csu/libc-start.c:332
#7 0x55b9abfb5abe in _start ()
(gdb) info local
xwl_window = 0x55b9acbf18f0
next_xwl_window = 0x7ffdc8574150
commit_window_list = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
xwl_window =
next_xwl_window =
commit_window_list = {next = , prev = }
(gdb) print commit_window_list
$1 = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
(gdb) print commit_window_list->next
$2 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next
$3 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next
$4 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next
$5 = (struct xorg_list *) 0x7ffdc8574170
(gdb) print commit_window_list->next->next->next->next->next
$6 = (struct xorg_list *) 0x55b9acbf1910
(gdb) print commit_window_list->next->next->next->next->next->next
$7 = (struct xorg_list *) 0x7ffdc8574170
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915449/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More
[Desktop-packages] [Bug 1915382] Re: external Monitor shows »No Signal« after dpms sleep
To make thing even weirder, one time the external monitor went to sleep while the system was waiting for cryptfs passphrase input and the situation occured already in login screen: Could move the mouse into the black screen with login window following there, and back. I tried to restart lightdm. Still the same. I logged in, restarted lightdm: tada. Monitor back awake showing my desktop. I already tried a different cable but no success. All my other machines are working well with that monitor hosting the same setup (ubuntu/i3). -- 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/1915382 Title: external Monitor shows »No Signal« after dpms sleep Status in xorg-server package in Ubuntu: Incomplete Bug description: My external Monitor connected via HDMI is behaving strange and my educated guess is it is related to dpms. Plugging in the monitor it will show »No Signal« although recognized by `xrandr`. I would have to boot my machine with the monitor plugged in to make it work. When going to standby (screen blanks after lock, then screen goes to standby) the monitor is switched on (LED is going white) and shortly after it will show the no-signal-message. `xrandr` claims the monitor to be existent. Unplugging and replugging does not help. Same happens when logging out to greeter. Strange in so far as when booting up, the greeter is okay with the monitor. When issuing `xset -dpms` the behaviour changes and the monitor will enter sleep and come back as expected when locking the session. Console (tty1-6) is available though at all times. (I generated the bug report with dpms set off accidentally) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Feb 11 09:51:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2021-02-10 (0 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: Dell Inc. Precision 7550 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 090NVT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd07/15/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn090NVT:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890924] Re: Location services work with location services off, 20.04
Thank you very much for adding the SRU to the desktop team's agenda! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1890924 Title: Location services work with location services off, 20.04 Status in geoclue-2.0 package in Ubuntu: Fix Released Bug description: Not sure if this is the right package, but in the privacy -> location settings, in 18.04 I had to have my application be approved by user to access location with Geoclue. Now it seems this is working without the location services "enabled"?? My application is repeater-START: https://sourceforge.net/projects /repeater-start/ Steps to see issue: 1) install Repeater-START and click the locate me button circle to the left. It goes to your rough location on map. 2) Go to settings, privacy, location, note that location is turned off!? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 8 19:38:12 2020 InstallationDate: Installed on 2017-07-29 (1106 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-06-22 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1890924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
nah I am giving up. this debugger is not working as expected. also this code is riddled with exceptions. uninstalling and going back to better times -- 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/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
We should probably ignore failure to start NetworkManager-wait- online.service in the autopkgtests for now. ** Changed in: systemd (Ubuntu) Importance: High => Wishlist -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872522] Re: Ubuntu software will not install .deb files on focal fossa
*** This bug is a duplicate of bug 1867610 *** https://bugs.launchpad.net/bugs/1867610 The same happens in Debian 10, so that's not Ubuntu-specific. Reproduction steps: 1. Download a .deb file, for example Jami from https://dl.jami.net/ring-manual/debian_10/jami-all_amd64.deb. 2. If you try to open it from your browser, it'll invoke the Archive Manager application, which isn't useful (it should really open the gnome-software application 3. If you choose to open it in the Gnome Software application, you get the message: "Failed to install: not supported". My Debian 10 VM is running amd64, and so is the .deb file linked above. I hope that helps! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1872522 Title: Ubuntu software will not install .deb files on focal fossa Status in gnome-software package in Ubuntu: Incomplete Bug description: On focal fossa Ubuntu software will not install .deb files (such as Google Chrome installer) however gdebi has no problem with the same files. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 19:36:10 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
how do I set a breakpoint early in the call stack?
Uncaught
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure
code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.port]", result: 2147500037,
filename: "chrome://pippki/content/exceptionDialog.js", lineNumber: 156,
columnNumber: 0, data: null, stack:
"getURI@chrome://pippki/content/exceptionDialog.js:156:7\naddException@chrome://pippki/content/exceptionDialog.js:386:13\n_fireButtonEvent@chrome://global/content/elements/dialog.js:487:19\n_doButtonCommand@chrome://global/content/elements/dialog.js:466:29\n_handleButtonCommand@chrome://global/content/elements/dialog.js:460:19\nInformUserOfCertError@chrome://messenger/content/mailWindow.js:685:10\nOnStopRunningUrl@chrome://messenger/content/mailWindowOverlay.js:2940:30\n",
location: XPCWrappedNative_NoHelper }
exceptionDialog.js:156
getURI chrome://pippki/content/exceptionDialog.js:156
addException chrome://pippki/content/exceptionDialog.js:386
_fireButtonEvent chrome://global/content/elements/dialog.js:487
_doButtonCommand chrome://global/content/elements/dialog.js:466
_handleButtonCommand chrome://global/content/elements/dialog.js:460
_handleButtonCommand self-hosted:844
InformUserOfCertError chrome://messenger/content/mailWindow.js:685
OnStopRunningUrl chrome://messenger/content/mailWindowOverlay.
--
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/1904789
Title:
[snap] Cannot confirm security exception for invalid certificate
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Note: This bug is specific to the Snap version of Thunderbird, I can't
reproduce it with the Ubuntu-packaged version for example (which I
have installed on Ubuntu, used for multiple years and stopped using
recently to get the more recent versions of TB available with Snap).
When a certificate problem arrises with a server from which
Thunderbird tries to retrieve emails, the "Add Security Exception"
window gives you the option to "Confirm Security Exception" (meaning
that Thunderbird will overlook the invalid certificate).
The problem is that nothing happens when I click the "Confirm Security
Exception" button. I've tried the usual workarounds, including
removing the email account and adding it again, to no avail.
The peculiar thing here is that I have had certificate problems
before, when using a non-snap version of Thunderbird, and clicking the
"Confirm Security Exception" button has always worked. Not with the
Snap version it seems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
chrome://pippki/content/exceptionDialog.js
line 156
if (uri.port == -1) { //offending line. url.port == undefined
mutator.setPort(443);
}
how do I change the source code to just not do this if statement?
--
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/1904789
Title:
[snap] Cannot confirm security exception for invalid certificate
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Note: This bug is specific to the Snap version of Thunderbird, I can't
reproduce it with the Ubuntu-packaged version for example (which I
have installed on Ubuntu, used for multiple years and stopped using
recently to get the more recent versions of TB available with Snap).
When a certificate problem arrises with a server from which
Thunderbird tries to retrieve emails, the "Add Security Exception"
window gives you the option to "Confirm Security Exception" (meaning
that Thunderbird will overlook the invalid certificate).
The problem is that nothing happens when I click the "Confirm Security
Exception" button. I've tried the usual workarounds, including
removing the email account and adding it again, to no avail.
The peculiar thing here is that I have had certificate problems
before, when using a non-snap version of Thunderbird, and clicking the
"Confirm Security Exception" button has always worked. Not with the
Snap version it seems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
never mind, am now in the debugger with the offending piece of code. if I can figure this out in 20 minutes then great. otherwise I will give up -- 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/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
like a boomerang I found myself ending up again with 78.7.1 (64bit) Thunderbird. The issue still remains :( Is there a workaround yet? Can I set a breakpoint perhaps in the offending code and then tweak the local variables in such a way to get it working? I know how to debug with the dev tools. I just do not know yet where to look. If you guys help me get going I'll post the workaround steps here and then report it on bugzilla -- 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/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
** Changed in: network-manager (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Ubuntu containers team (ubuntu-lxc) -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915410] Re: gnome-remote-desktop crashes in grd_session_vnc_take_buffer -> rfbProcessEvents -> rfbMakeRichCursorFromXCursor
** Changed in: libvncserver (Ubuntu) Importance: Critical => High ** Changed in: libvncserver (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvncserver in Ubuntu. https://bugs.launchpad.net/bugs/1915410 Title: gnome-remote-desktop crashes in grd_session_vnc_take_buffer -> rfbProcessEvents -> rfbMakeRichCursorFromXCursor Status in libvncserver package in Ubuntu: Fix Committed Bug description: When connecting via gnome remote desktop in ubuntu hirsute with Wayland: #0 0x7f39d7c08497 in rfbMakeRichCursorFromXCursor (rfbScreen=, cursor=cursor@entry=0x7f39d7c32020 ) at ./libvncserver/cursor.c:497 #1 0x7f39d7c089b7 in rfbSendCursorShape (cl=cl@entry=0x55e0530c5ae0) at ./libvncserver/cursor.c:54 #2 0x7f39d7bfa33d in rfbSendFramebufferUpdate (cl=cl@entry=0x55e0530c5ae0, givenUpdateRegion=) at ./libvncserver/rfbserver.c:3190 #3 0x7f39d7bf48a5 in rfbUpdateClient (cl=cl@entry=0x55e0530c5ae0) at ./libvncserver/main.c:1252 #4 0x7f39d7bf4920 in rfbProcessEvents (screen=, usec=, usec@entry=0) at ./libvncserver/main.c:1216 #5 0x55e052add793 in grd_session_vnc_take_buffer (session_vnc=, data=) at ../src/grd-session-vnc.c:169 #6 0x55e052ae2bde in do_render (loop=, async=, seq=, data=, size=, user_data=) at ../src/grd-vnc-pipewire-stream.c:248 #7 0x7f39d193e806 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #8 0x7f39d193e712 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #9 0x7f39d193f063 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #10 0x55e052ade72a in pipewire_loop_source_dispatch (source=, callback=, user_data=) at ../src/grd-vnc-pipewire-stream.c:97 #11 0x7f39d7f8e6eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f39d7f8e998 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f39d7f8ea63 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f39d7e3a46d in g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x55e052aca90b in main (argc=, argv=) at ../src/grd-daemon.c:351 This is the same of https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/issues/45 and seems to be fixed by https://github.com/LibVNC/libvncserver/pull/444 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvncserver/+bug/1915410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
This is a systemd/udev bug. We're aware of the CONTAINER_INTERFACE and it being wrong doesn't mean we need to change LXD to make it similarly wrong. LXD containers need to have udevd running to function properly, so you'll need to undo that change. If there is a bug in how udevd now behaves, that's what needs to be fixed and we can assist you with that. ** Changed in: lxd (Ubuntu) Status: New => Won't Fix -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915425] Re: mozilla thunderbird update
*** This bug is a duplicate of bug 1895643 *** https://bugs.launchpad.net/bugs/1895643 ** This bug has been marked a duplicate of bug 1895643 Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1915425 Title: mozilla thunderbird update Status in thunderbird package in Ubuntu: New Bug description: mozilla thunderbird update ubuntu 20.04 LTS mozilla thunderbird update last 2020 summer mozilla thunderbird always keep update and upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1915425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915425] Re: mozilla thunderbird update
** Project changed: launchpad => thunderbird (Ubuntu) -- 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/1915425 Title: mozilla thunderbird update Status in thunderbird package in Ubuntu: New Bug description: mozilla thunderbird update ubuntu 20.04 LTS mozilla thunderbird update last 2020 summer mozilla thunderbird always keep update and upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1915425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915425] [NEW] mozilla thunderbird update
You have been subscribed to a public bug: mozilla thunderbird update ubuntu 20.04 LTS mozilla thunderbird update last 2020 summer mozilla thunderbird always keep update and upgrades ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- mozilla thunderbird update https://bugs.launchpad.net/bugs/1915425 You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915410] Re: gnome-remote-desktop crashes in grd_session_vnc_take_buffer -> rfbProcessEvents -> rfbMakeRichCursorFromXCursor
Fixed by https://salsa.debian.org/debian-remote- team/libvncserver/-/merge_requests/6/ ** Changed in: libvncserver (Ubuntu) Status: Triaged => In Progress ** Changed in: libvncserver (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvncserver in Ubuntu. https://bugs.launchpad.net/bugs/1915410 Title: gnome-remote-desktop crashes in grd_session_vnc_take_buffer -> rfbProcessEvents -> rfbMakeRichCursorFromXCursor Status in libvncserver package in Ubuntu: In Progress Bug description: When connecting via gnome remote desktop in ubuntu hirsute with Wayland: #0 0x7f39d7c08497 in rfbMakeRichCursorFromXCursor (rfbScreen=, cursor=cursor@entry=0x7f39d7c32020 ) at ./libvncserver/cursor.c:497 #1 0x7f39d7c089b7 in rfbSendCursorShape (cl=cl@entry=0x55e0530c5ae0) at ./libvncserver/cursor.c:54 #2 0x7f39d7bfa33d in rfbSendFramebufferUpdate (cl=cl@entry=0x55e0530c5ae0, givenUpdateRegion=) at ./libvncserver/rfbserver.c:3190 #3 0x7f39d7bf48a5 in rfbUpdateClient (cl=cl@entry=0x55e0530c5ae0) at ./libvncserver/main.c:1252 #4 0x7f39d7bf4920 in rfbProcessEvents (screen=, usec=, usec@entry=0) at ./libvncserver/main.c:1216 #5 0x55e052add793 in grd_session_vnc_take_buffer (session_vnc=, data=) at ../src/grd-session-vnc.c:169 #6 0x55e052ae2bde in do_render (loop=, async=, seq=, data=, size=, user_data=) at ../src/grd-vnc-pipewire-stream.c:248 #7 0x7f39d193e806 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #8 0x7f39d193e712 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #9 0x7f39d193f063 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #10 0x55e052ade72a in pipewire_loop_source_dispatch (source=, callback=, user_data=) at ../src/grd-vnc-pipewire-stream.c:97 #11 0x7f39d7f8e6eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f39d7f8e998 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f39d7f8ea63 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f39d7e3a46d in g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x55e052aca90b in main (argc=, argv=) at ../src/grd-daemon.c:351 This is the same of https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/issues/45 and seems to be fixed by https://github.com/LibVNC/libvncserver/pull/444 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvncserver/+bug/1915410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Problem remains, my environment: - Kernel: 5.8.0-43-generic - OS: Ubuntu 20.04.2 LTS - Machine: Dell Latitude 7410 - Headset: Mi TW Earphones 2 Basic -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915421] [NEW] package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.1 failed to install/upgrade: hi ha un bucle d'activadors, s'ha abandonat
Public bug reported: Gràcies ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 11 14:18:32 2021 ErrorMessage: hi ha un bucle d'activadors, s'ha abandonat InstallationDate: Installed on 2020-10-26 (107 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.1 failed to install/upgrade: hi ha un bucle d'activadors, s'ha abandonat UpgradeStatus: Upgraded to groovy on 2021-02-11 (0 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1915421 Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.1 failed to install/upgrade: hi ha un bucle d'activadors, s'ha abandonat Status in gdk-pixbuf package in Ubuntu: New Bug description: Gràcies ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 11 14:18:32 2021 ErrorMessage: hi ha un bucle d'activadors, s'ha abandonat InstallationDate: Installed on 2020-10-26 (107 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-5ubuntu0.1 failed to install/upgrade: hi ha un bucle d'activadors, s'ha abandonat UpgradeStatus: Upgraded to groovy on 2021-02-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1915421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915410] [NEW] gnome-remote-desktop crashes in grd_session_vnc_take_buffer -> rfbProcessEvents -> rfbMakeRichCursorFromXCursor
Public bug reported: When connecting via gnome remote desktop in ubuntu hirsute with Wayland: #0 0x7f39d7c08497 in rfbMakeRichCursorFromXCursor (rfbScreen=, cursor=cursor@entry=0x7f39d7c32020 ) at ./libvncserver/cursor.c:497 #1 0x7f39d7c089b7 in rfbSendCursorShape (cl=cl@entry=0x55e0530c5ae0) at ./libvncserver/cursor.c:54 #2 0x7f39d7bfa33d in rfbSendFramebufferUpdate (cl=cl@entry=0x55e0530c5ae0, givenUpdateRegion=) at ./libvncserver/rfbserver.c:3190 #3 0x7f39d7bf48a5 in rfbUpdateClient (cl=cl@entry=0x55e0530c5ae0) at ./libvncserver/main.c:1252 #4 0x7f39d7bf4920 in rfbProcessEvents (screen=, usec=, usec@entry=0) at ./libvncserver/main.c:1216 #5 0x55e052add793 in grd_session_vnc_take_buffer (session_vnc=, data=) at ../src/grd-session-vnc.c:169 #6 0x55e052ae2bde in do_render (loop=, async=, seq=, data=, size=, user_data=) at ../src/grd-vnc-pipewire-stream.c:248 #7 0x7f39d193e806 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #8 0x7f39d193e712 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #9 0x7f39d193f063 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #10 0x55e052ade72a in pipewire_loop_source_dispatch (source=, callback=, user_data=) at ../src/grd-vnc-pipewire-stream.c:97 #11 0x7f39d7f8e6eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f39d7f8e998 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f39d7f8ea63 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f39d7e3a46d in g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x55e052aca90b in main (argc=, argv=) at ../src/grd-daemon.c:351 This is the same of https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/issues/45 and seems to be fixed by https://github.com/LibVNC/libvncserver/pull/444 ** Affects: libvncserver (Ubuntu) Importance: Critical Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvncserver in Ubuntu. https://bugs.launchpad.net/bugs/1915410 Title: gnome-remote-desktop crashes in grd_session_vnc_take_buffer -> rfbProcessEvents -> rfbMakeRichCursorFromXCursor Status in libvncserver package in Ubuntu: Triaged Bug description: When connecting via gnome remote desktop in ubuntu hirsute with Wayland: #0 0x7f39d7c08497 in rfbMakeRichCursorFromXCursor (rfbScreen=, cursor=cursor@entry=0x7f39d7c32020 ) at ./libvncserver/cursor.c:497 #1 0x7f39d7c089b7 in rfbSendCursorShape (cl=cl@entry=0x55e0530c5ae0) at ./libvncserver/cursor.c:54 #2 0x7f39d7bfa33d in rfbSendFramebufferUpdate (cl=cl@entry=0x55e0530c5ae0, givenUpdateRegion=) at ./libvncserver/rfbserver.c:3190 #3 0x7f39d7bf48a5 in rfbUpdateClient (cl=cl@entry=0x55e0530c5ae0) at ./libvncserver/main.c:1252 #4 0x7f39d7bf4920 in rfbProcessEvents (screen=, usec=, usec@entry=0) at ./libvncserver/main.c:1216 #5 0x55e052add793 in grd_session_vnc_take_buffer (session_vnc=, data=) at ../src/grd-session-vnc.c:169 #6 0x55e052ae2bde in do_render (loop=, async=, seq=, data=, size=, user_data=) at ../src/grd-vnc-pipewire-stream.c:248 #7 0x7f39d193e806 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #8 0x7f39d193e712 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #9 0x7f39d193f063 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #10 0x55e052ade72a in pipewire_loop_source_dispatch (source=, callback=, user_data=) at ../src/grd-vnc-pipewire-stream.c:97 #11 0x7f39d7f8e6eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f39d7f8e998 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f39d7f8ea63 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f39d7e3a46d in g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x55e052aca90b in main (argc=, argv=) at ../src/grd-daemon.c:351 This is the same of https://gitlab.gnome.org/GNOME/gnome-remote- desktop/-/issues/45 and seems to be fixed by https://github.com/LibVNC/libvncserver/pull/444 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvncserver/+bug/1915410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@stgraber or work with systemd upstream to extend the container API. -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@stgraber nothing should break honoring https://systemd.io/CONTAINER_INTERFACE/ and we are in constant uphill battle with systemd and other upstreams checking /sys's ro status. Detecting the init system is easy, please do it in LXD. It may make sense to allow the user to override that and force /sys readonly in LXC config, but then it is up to the user to fix failing services, the user cares about, too. ** Changed in: lxd (Ubuntu) Status: Invalid => New -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Making /sys read-only will break very very many things that we have no intention of breaking. LXD is also completely init system agnostic and we have no idea what the init system in a particular container may be. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
This issue still happens on Ubuntu 20.04. I use a laptop with Bluetooth keyboard. I couldn't use media keys like volume up and down due to the large delay. Even if I use the media keys in a single keyboard, the delay happens. Post #8 solution works for me. Make sure to restart after applying the fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@seb128 I tried remounting /sys in systemd but it created other issues. I've fixed udevd to not start in lxc in systemd, but this is all systemd can do. Please detect running udev in network-manager without assuming that rw /sys implies running udev. @ LXD devs, please check if the init to start is systemd and if so please mount /sys ro to conform to systemd's https://systemd.io/CONTAINER_INTERFACE/ or sort convince systemd upstream to include LXC in the container interface with rw /sys. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551171]
Are you going to fix this one day? The bug exists now over a decade, the internet is full of help requests and no one seems to care … https://www.google.de/search?hl=de=hp=firefox%20kde%20okular%20pdf%20system%20handler=f=g10===h Just use xdg-mime to make it cross desktop compatible. Gnome is just one fucking desktop on Linux, but its still the only one that is supported by Firefox. -- 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/1551171 Title: /usr/share/applications/mimeinfo.cache is used for default applications in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=727422 With Firefox, default applications are selected by Firefox using /usr/share/applications/mimeinfo.cache, however, this list is a system generated list in random order and therefor does not reflect the user's preferences of which application should be used to open a file. When I click on a pdf (for example), I want to have the option to open it in my default application, in my case in okular, and not in something else. However, acroread is invariably presented is presented as default choice because it happens to be the first entry in /usr/share/applications/mimeinfo.cache for application/pdf. This happens in spite of the fact that the desktop provides correct defaults.list and mimeapps.list files The comments in the firefox bug seem to suggest that firefox developers are convinced that firefox calls the correct gtk libraries to determine the correct application. If this is the case, then it is necessarily the ubuntu (or possibly kubuntu) infrastructure to be failing. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: firefox 44.0.2+build1-0ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BuildID: 20160209234513 CurrentDesktop: KDE Date: Mon Feb 29 11:37:25 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (808 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: firefox UpgradeStatus: Upgraded to wily on 2015-10-23 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1551171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1915382] Re: external Monitor shows»No Signal«after dpms sleep
Thanks for your prompt answer! I narrowed things down a bit. As I am using i3 wayland is not an option. I tried a live ubuntu 20.04 and could still reproduce the behaviour described. I went on to enable wayland in live session but failed eventually: XDG_SESSION_TYPE still yielded `x11` but in the process I restarted gdm3 -- and things were fixed. Okay, I went back to the os installed (regolith linux which is i3 based on ubuntu) and after restarting lightdm via systemctl, things are working as expected. That's weird. Regarding your first question: It is HDMI indeed although xrandr claiming otherwise. There is an HDMI port beneath a DP at the rear and the rest of it is USB. Can I somehow convice the live system to run on wayland? The procedure described here: https://askubuntu.com/a/1258280/595512 did not work for me. -- 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/1915382 Title: external Monitor shows »No Signal« after dpms sleep Status in xorg-server package in Ubuntu: Incomplete Bug description: My external Monitor connected via HDMI is behaving strange and my educated guess is it is related to dpms. Plugging in the monitor it will show »No Signal« although recognized by `xrandr`. I would have to boot my machine with the monitor plugged in to make it work. When going to standby (screen blanks after lock, then screen goes to standby) the monitor is switched on (LED is going white) and shortly after it will show the no-signal-message. `xrandr` claims the monitor to be existent. Unplugging and replugging does not help. Same happens when logging out to greeter. Strange in so far as when booting up, the greeter is okay with the monitor. When issuing `xset -dpms` the behaviour changes and the monitor will enter sleep and come back as expected when locking the session. Console (tty1-6) is available though at all times. (I generated the bug report with dpms set off accidentally) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Feb 11 09:51:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2021-02-10 (0 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: Dell Inc. Precision 7550 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 090NVT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd07/15/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn090NVT:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902436] Re: Mouse slow in fractional scaling
I too can confirm this. I have much simpler configuration, a single 17-inch laptop with full HD resolution. OS version is Ubuntu 20.04. Under X11, if I select any fractional scaling above 100%, the mouse cursor moves slower via the touchpad. Under Wayland there are no problems on any scaling. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1902436 Title: Mouse slow in fractional scaling Status in mutter package in Ubuntu: Triaged Bug description: I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external monitor with 3840 x 1600 resolution. When I use only one of them it works totally fine. I use the external monitor without scaling and my notebook display with fractional scaling of 150%. But when i want to use both at the same time, my mouse starts to be slow. So in this scenario i have the external monitor at 100% and the notebook screen at 150%. Everything works fine expect the mouse which is slow,on both screens. What I found is, when i set both my screens to 200% while fractional scaling is enabled. The issue is gone. Same with 100%. But as soon as I start using fractions, the mouse is slow again. I don't believe it is an power issue because my hardware is mostly in idle. Also, i tried different mouses over Bluetooth and USB but no change. I am currently using 20.10 but had the same issue with 20.04. But when i use Wayland, the problem is gone. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 14:01:59 2020 DistUpgraded: 2020-10-30 12:11:16,382 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.8.0-26-generic, x86_64: installed nvidia, 450.80.02, 5.8.0-26-generic, x86_64: installed soundwire, 1.2.2: added DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:098f] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU106M [GeForce RTX 2060 Max-Q] [1028:098f] InstallationDate: Installed on 2020-09-19 (42 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 17 9700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=6d098ea0-9d87-46ec-beb0-cc19a3b20841 ro quiet splash resume=UUID=723b6007-ad35-4e89-be9e-341d54fe18f8 nouveau.modset=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) dmi.bios.date: 08/18/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0P1CHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd08/18/2020:br1.3:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P1CHN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1
[Desktop-packages] [Bug 1901240] Re: Ubuntu GNOME Path Traversal
This bug was fixed in the package gnome-autoar - 0.2.3-2ubuntu0.1 --- gnome-autoar (0.2.3-2ubuntu0.1) focal-security; urgency=medium * SECURITY UPDATE: directory traversal issue (LP: #1901240) - debian/patches/CVE-2020-36241.patch: do not extract files outside the destination dir in gnome-autoar/autoar-extractor.c. - CVE-2020-36241 -- Marc Deslauriers Wed, 10 Feb 2021 13:59:00 -0500 ** Changed in: gnome-autoar (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/1901240 Title: Ubuntu GNOME Path Traversal Status in gnome-autoar package in Ubuntu: Fix Released Bug description: Summary: A malicious package may be able to overwrite arbitrary files Proof of concept: 1- Download "example.tar" 2- Click on the right button on a mouse (on "example.tar") 3- Click "Extract Here" 4- Check the "/tmp" path for "test" file Version: Ubuntu 20.04.1 GNOME Files 3.36.3-stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1901240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901240] Re: Ubuntu GNOME Path Traversal
This bug was fixed in the package gnome-autoar - 0.2.4-2ubuntu0.1 --- gnome-autoar (0.2.4-2ubuntu0.1) groovy-security; urgency=medium * SECURITY UPDATE: directory traversal issue (LP: #1901240) - debian/patches/CVE-2020-36241.patch: do not extract files outside the destination dir in gnome-autoar/autoar-extractor.c. - CVE-2020-36241 -- Marc Deslauriers Wed, 10 Feb 2021 13:55:36 -0500 ** Changed in: gnome-autoar (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-autoar (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/1901240 Title: Ubuntu GNOME Path Traversal Status in gnome-autoar package in Ubuntu: Fix Released Bug description: Summary: A malicious package may be able to overwrite arbitrary files Proof of concept: 1- Download "example.tar" 2- Click on the right button on a mouse (on "example.tar") 3- Click "Extract Here" 4- Check the "/tmp" path for "test" file Version: Ubuntu 20.04.1 GNOME Files 3.36.3-stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1901240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901240] Re: Ubuntu GNOME Path Traversal
This bug was fixed in the package gnome-autoar - 0.2.3-1ubuntu0.1 --- gnome-autoar (0.2.3-1ubuntu0.1) bionic-security; urgency=medium * SECURITY UPDATE: directory traversal issue (LP: #1901240) - debian/patches/CVE-2020-36241.patch: do not extract files outside the destination dir in gnome-autoar/autoar-extractor.c. - CVE-2020-36241 -- Marc Deslauriers Wed, 10 Feb 2021 13:59:35 -0500 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-autoar in Ubuntu. https://bugs.launchpad.net/bugs/1901240 Title: Ubuntu GNOME Path Traversal Status in gnome-autoar package in Ubuntu: Fix Released Bug description: Summary: A malicious package may be able to overwrite arbitrary files Proof of concept: 1- Download "example.tar" 2- Click on the right button on a mouse (on "example.tar") 3- Click "Extract Here" 4- Check the "/tmp" path for "test" file Version: Ubuntu 20.04.1 GNOME Files 3.36.3-stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/+bug/1901240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915003] Re: Always update the initramfs when changing power profile
I think that change has a different scope, and needs further discussion. The fix in this bug report works with the way we currently do things. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-prime source package in Focal: In Progress Status in nvidia-settings source package in Focal: In Progress Status in nvidia-prime source package in Groovy: In Progress Status in nvidia-settings source package in Groovy: In Progress Bug description: The different power profiles require loading the nvidia drivers with different options (or blacklisting them, in case of intel mode). We need to call update-initramfs whenever we switch to a different profile, or things may fall out sync, resulting in a failure. The update-initramfs command takes a few seconds, therefore we also need to provide feedback, so that users know that they have to wait for the operation to complete. For this reason, prime-select will provide a spinner on the command line, and nvidia-settings will show a progress dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878568] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita.
*** This bug is a duplicate of bug 1886059 *** https://bugs.launchpad.net/bugs/1886059 ** This bug is no longer a duplicate of bug 1877075 gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed ** This bug has been marked a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] -- 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/1878568 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita. 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.1-5ubuntu2, the problem page at https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7 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/1878568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877075] Re: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed
*** This bug is a duplicate of bug 1886059 *** https://bugs.launchpad.net/bugs/1886059 ** This bug has been marked a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1877075 Title: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [Impact] This is the #1 crasher of gnome-shell in Ubuntu 20.04, though it's duplicated across multiple problem reports according to locale: https://errors.ubuntu.com/problem/4de3d315d9df1c9699bda54beafa8d52053c https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7 https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0 [Test Case] None known. The plan is to just continue monitoring crash reports. Still, we are confident this is the fix because: * The offending source code in libx11 tells us it is :) and * The crash only started in Ubuntu with gnome-shell 3.34, which is the exact release in which XInitThreads was removed from mutter. [Regression Potential] Low. We add a single function call that tells libX11 to enable thread safety. This is the same as what we had in bionic, cosmic and disco, so it's well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1877075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877092] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Zusicherung \302\273!xcb_xlib_threads_sequence_lost\302\253 nicht erf\303\274llt.
*** This bug is a duplicate of bug 1886059 *** https://bugs.launchpad.net/bugs/1886059 ** This bug is no longer a duplicate of bug 1877075 gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed ** This bug has been marked a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] -- 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/1877092 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Zusicherung \302\273!xcb_xlib_threads_sequence_lost\302\253 nicht erf\303\274llt. 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.1-5ubuntu2, the problem page at https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b 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/1877092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878569] Re: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: \320\237\321\200\320\276\320\262\320\265\321\200\320\276\321\207\320\275\320\276\320\265
*** This bug is a duplicate of bug 1886059 *** https://bugs.launchpad.net/bugs/1886059 ** This bug is no longer a duplicate of bug 1877075 gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed ** This bug has been marked a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] -- 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/1878569 Title: /usr/bin/gnome-shell:gnome-shell: ../../src/xcb_io.c:260: poll_for_event: \320\237\321\200\320\276\320\262\320\265\321\200\320\276\321\207\320\275\320\276\320\265 \321\203\321\202\320\262\320\265\321\200\320\266\320\264\320\265\320\275\320\270\320\265 \302\253!xcb_xlib_threads_sequence_lost\302\273 \320\275\320\265 \320\262\321\213\320\277\320\276\320\273\320\275\320\265\320\275\320\276. 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.1-5ubuntu2, the problem page at https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0 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/1878569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915014] Re: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot
The original bug report was slightly inaccurate. "Black flashes" may occur also without taking a screenshot, usually when closing an application. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1915014 Title: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot Status in mutter package in Ubuntu: Incomplete Bug description: Weird issue which has come to my system via updates - possibly the Linux kernel 5.8? Steps to repro: - Take a screenshot (prt scr) - Continue using the computer After I have taken a screenshot, my display gets quick black flashes when using other applications. Manipulating the screenshot with Pinta, opening web browser, etc.. Screen goes black for a second and then resumes normal operation. This does not happen before taking the screenshot, so it obviously triggers something. The system works and is usable, but the black flashes are pretty odd and distracting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:39:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1025:1367] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:1366] InstallationDate: Installed on 2020-05-16 (268 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Nitro AN515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=675bb42c-4c3c-461b-bce1-53e34e786eaa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 1.8 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd12/24/2019:br1.8:efr1.5:svnAcer:pnNitroAN515-43:pvrV1.08:rvnPK:rnOctavia_PKS:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1915014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
Happens very frequently for me also on a vanilla 18.04 (Thinkpad), but only on a small subset of applications. What's strange is that the bug appeared a few days ago after years without problem. I do not use any external peripheral (nothing connected to the laptop except the power supply). An easy solution to solve this without rebooting the whole system is to disable then enable the TouchScreen (disabling alone is not sufficient). Following Paul Müller's steps: - find your TouchScreen input ID with ``xinput`` (in my case ``Melfas LGDisplay Incell Touch id=9`` - ``xinput --disable 9`` - ``xinput --enable 9`` If you want to automate this in a script/alias, you can easily retrieve the ID once you know the name of the TouchScreen: - ``xinput list --id-only 'Melfas LGDisplay Incell Touch'`` -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Ubnutu you need to consider on giving a Solid solution for Bluetooth headsets since that is a common use case for most. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
So this bug is here from around 2016 , still haven't yet solved -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915358] Re: sound hdmi 5.1 subwoofer always disabled
** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/936 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/1915358 Title: sound hdmi 5.1 subwoofer always disabled Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Invalid Bug description: In System Sound Settings, I chose HDMI 5.1 audio, but there is no sound from my subwoofer in any audio application. The System Sound Settings for HDMI 5.1 always shows a disabled subwoofer slider. When I open the test window and hit the subwoofer icon button, no sound is produced. But if I open Pulse Audio Volume Control -> Output Devices -> (unlock icon), all show mid-volume on the slider except for subwoffer. But the subwoofer slider is enabled. So I slide it to mid-volume, and go back to System Sound Settings -> test window and hit the subwoofer icon button, I hear my subwoofer is working fine. I also then hear the subwoofer in all audio applications. If I were to touch the System Sound Slider for the subwoofer, it immediately stops working again. I can fix it again in Pulse Audio Volumne Control again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:47:38 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-01-25 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1915358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915382] Re: external Monitor shows »No Signal« after dpms sleep
Thanks for the bug report. A couple of questions: 1. Xrandr.txt says nothing is connected to HDMI, but a monitor is connected to DisplayPort. Are you using an adapter? 2. Does the same bug occur is you choose 'Ubuntu on Wayland' from the login screen? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915382 Title: external Monitor shows »No Signal« after dpms sleep Status in xorg-server package in Ubuntu: Incomplete Bug description: My external Monitor connected via HDMI is behaving strange and my educated guess is it is related to dpms. Plugging in the monitor it will show »No Signal« although recognized by `xrandr`. I would have to boot my machine with the monitor plugged in to make it work. When going to standby (screen blanks after lock, then screen goes to standby) the monitor is switched on (LED is going white) and shortly after it will show the no-signal-message. `xrandr` claims the monitor to be existent. Unplugging and replugging does not help. Same happens when logging out to greeter. Strange in so far as when booting up, the greeter is okay with the monitor. When issuing `xset -dpms` the behaviour changes and the monitor will enter sleep and come back as expected when locking the session. Console (tty1-6) is available though at all times. (I generated the bug report with dpms set off accidentally) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Feb 11 09:51:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2021-02-10 (0 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: Dell Inc. Precision 7550 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 090NVT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd07/15/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn090NVT:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
I got this too, comes out of nowhere, typing stalls for a second or two, sometimes the keystrokes are remembered, and typed a bit later, other times they're just dropped and i sit and look at the screen, then try typing and the letter shows up, very annoying for a developer. Danish keyboard layout (only) Single keyboard (Logitech K520) Ubuntu 20.04 (had it on 18.04 too) MSI GeForce GT 1030 Nvidia 460 (just updated from 450 1½ day ago, haven't seen the bug since this so far) Display manager gdm3 Xinput shows me a funny thing, a webcam as keyboard. This webcam is quite new, so i'll try and disable it next time i experience the bug. xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech M310 id=9[slave pointer (2)] ⎜ ↳ Logitech K520 id=10 [slave pointer (2)] ⎜ ↳ ATEN DVI DL KVMP id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ ATEN DVI DL KVMP id=11 [slave keyboard (3)] ↳ Trust Webcam: Trust Webcamid=13 [slave keyboard (3)] ↳ Eee PC WMI hotkeysid=14 [slave keyboard (3)] ↳ Logitech K520 id=15 [slave keyboard (3)] `xev -event keyboard` did not show anything odd. Feel free to ask for any other info (add commands please) Kind regards Kim -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915358] Re: sound hdmi 5.1 subwoofer always disabled
Since the pulseaudio control work let's assuming it's a bug in the settings -- 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/1915358 Title: sound hdmi 5.1 subwoofer always disabled Status in gnome-control-center package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Invalid Bug description: In System Sound Settings, I chose HDMI 5.1 audio, but there is no sound from my subwoofer in any audio application. The System Sound Settings for HDMI 5.1 always shows a disabled subwoofer slider. When I open the test window and hit the subwoofer icon button, no sound is produced. But if I open Pulse Audio Volume Control -> Output Devices -> (unlock icon), all show mid-volume on the slider except for subwoffer. But the subwoofer slider is enabled. So I slide it to mid-volume, and go back to System Sound Settings -> test window and hit the subwoofer icon button, I hear my subwoofer is working fine. I also then hear the subwoofer in all audio applications. If I were to touch the System Sound Slider for the subwoofer, it immediately stops working again. I can fix it again in Pulse Audio Volumne Control again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:47:38 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-01-25 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915358] Re: sound hdmi 5.1 subwoofer always disabled
Thank you for your bug report, that's known upstream https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/936 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #936 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/936 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1915358 Title: sound hdmi 5.1 subwoofer always disabled Status in gnome-control-center package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Invalid Bug description: In System Sound Settings, I chose HDMI 5.1 audio, but there is no sound from my subwoofer in any audio application. The System Sound Settings for HDMI 5.1 always shows a disabled subwoofer slider. When I open the test window and hit the subwoofer icon button, no sound is produced. But if I open Pulse Audio Volume Control -> Output Devices -> (unlock icon), all show mid-volume on the slider except for subwoffer. But the subwoofer slider is enabled. So I slide it to mid-volume, and go back to System Sound Settings -> test window and hit the subwoofer icon button, I hear my subwoofer is working fine. I also then hear the subwoofer in all audio applications. If I were to touch the System Sound Slider for the subwoofer, it immediately stops working again. I can fix it again in Pulse Audio Volumne Control again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:47:38 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-01-25 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915092] Re: lib-gtk-3 / lib-gtk-3-dev NOT compatible
Closing the bug then, thanks. There was a matching dev binary but you hit a special case where the stable update failed verification and was removed and you were left on a version that doesn't exists anymore, that's one of the risk of opt-in for proposed updates. ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1915092 Title: lib-gtk-3 / lib-gtk-3-dev NOT compatible Status in gtk+3.0 package in Ubuntu: Invalid Bug description: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1915092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915377] Re: Nautilus crashes on rename
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1915377 Title: Nautilus crashes on rename Status in nautilus package in Ubuntu: Invalid Bug description: Bug Description: I wanted to rename a directory. Nautilus crashes with error 'Files not responding'. Name contains A-Z, a-z, 0-9, Underscore, Hyphen. Versions: Ubuntu Description: Ubuntu 20.10 Release: 20.10 Nautilus (Files) 1:3.38.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 08:22:41 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 1006)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-02-02 (8 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows
I thought I was losing my mind! I have also been experiencing this issue, and today finally managed to narrow it down to a specific cause. My issue starts when I am making use of the CTRL+SHIFT+PRTSCR shortcut to take a screenshot of an area you select. I use this function frequently, and it sometimes results in my mouse functionality being isolated to the window that currently has focus. If I move my mouse cursor over another window I can see that the window registers the mouse position (for example hover animations are triggered) and scrolling works, but left and right click do not register in that window until I use ALT+TAB to change focus to that window. If I hover my mouse pointer over the top bar, the pointer icon changes to a + which is the same icon that it changes to when you take the screenshot, so it seems almost like the screenshot overlay mechanism doesn't get reset/cleared correctly. I hope this helps! -- 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/362359 Title: Focus gets stuck to a window - impossible to select other windows Status in xorg-server package in Ubuntu: Fix Released Bug description: Alright, terribly annoying bug that gets me to reboot several times a day, but very hard to understand how to trigger it. What happens: after some time of usage, you get "stuck" in a window. Idem est, you can not select another window. You can still click, select and drag in the window that has the focus, but clicking on other windows, or on the panel, just doesn't work. Notes: - With window I don't mean "application window". For example it can only be the page view in firefox, and you won't be able to click the buttons or the URL field. It can also be the main text window in xchat, and you wont be able to click in the user list or to change the chatroom. - The click seems to be grabbed by the window having the focus, even if you click outside of it. For example, using xchat, if the main text window has focus, clicking and dragging in the user list will actually select text in the main text window. - Using xev, it seems that clics do not get passed to the correct window at all (nothing received) - I have no idea what triggers this as sometimes it will trigger alone - pc works, I leave it for an hour, I come back, the problem is triggered - Curious effect now: dragging and dropping to another window gives focus to the window, and seems to be the only way to do so. For example if in firefox the main page view window has the focus and I cant click the buttons, drag and dropping text to the buttons gives the focus to the buttons, and I can't clic the page view window anymore. Drag and dropping a button to the page view window gives it its focus back Additional info: * Compiz disabled * Intel graphic card * Ubuntu jaunty - latest patches * Using a laptop, with an USB mouse HAL, xserver, I have no idea where to file this bug into. I hope it will be fixed before the release, it is really terribly annoying :s Please tell me if there is any other detail I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/362359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915382] [NEW] external Monitor shows »No Signal« after dpms sleep
Public bug reported: My external Monitor connected via HDMI is behaving strange and my educated guess is it is related to dpms. Plugging in the monitor it will show »No Signal« although recognized by `xrandr`. I would have to boot my machine with the monitor plugged in to make it work. When going to standby (screen blanks after lock, then screen goes to standby) the monitor is switched on (LED is going white) and shortly after it will show the no-signal-message. `xrandr` claims the monitor to be existent. Unplugging and replugging does not help. Same happens when logging out to greeter. Strange in so far as when booting up, the greeter is okay with the monitor. When issuing `xset -dpms` the behaviour changes and the monitor will enter sleep and come back as expected when locking the session. Console (tty1-6) is available though at all times. (I generated the bug report with dpms set off accidentally) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Feb 11 09:51:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2021-02-10 (0 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: Dell Inc. Precision 7550 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 090NVT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd07/15/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn090NVT:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1915382 Title: external Monitor shows »No Signal« after dpms sleep Status in xorg package in Ubuntu: New Bug description: My external Monitor connected via HDMI is behaving strange and my educated guess is it is related to dpms. Plugging in the monitor it will show »No Signal« although recognized by `xrandr`. I would have to boot my machine with the monitor plugged in to make it work. When going to standby (screen blanks after lock, then screen goes to standby) the monitor is switched on (LED is going white) and shortly after it will show the no-signal-message. `xrandr` claims the monitor to be existent. Unplugging and replugging does not help. Same happens when logging out to greeter. Strange in so far as when booting up, the greeter is okay with the monitor. When issuing `xset -dpms` the behaviour changes and the monitor will enter sleep and come back as expected when locking the session. Console (tty1-6) is available though at all times. (I generated the bug report with dpms set off accidentally) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Feb 11 09:51:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2021-02-10 (0
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Hello, Well I tried... and have some troubles :). After reboot, displaylink didn't work anymore. I tried to uninstall but when I try to reinstall, here what I get : ERROR (dkms apport): binary package for evdi: 1.7.0 not found Error! Bad return status for module build on kernel: 5.8.0-43-generic (x86_64) Consult /var/lib/dkms/evdi/1.7.0/build/make.log for more information. ERROR: Failed to install evdi/5.3.1.34 to the kernel tree. I know this is ubuntu, not displaylink, but if you have any idea that would be great. Notice : If i run install twice, I got only 1 error : "Error! DKMS tree already contains: evdi-1.7.0" and installation continue. But don't work... Uninstall / reinstall will do same thing (1st fatal error that stop installer, then this one) -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/mesa/+bug/1871959/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1913388] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-02-11 03:27 EDT--- IBM Bugzilla status->closed, Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Fix Released Status in clucene-core package in Ubuntu: Fix Released Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
