[Desktop-packages] [Bug 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
*** This bug is a duplicate of bug 1956915 *** https://bugs.launchpad.net/bugs/1956915 Verified internally with Ubuntu 20.04.4 + libegl-mesa0 version "21.2.6-0ubuntu0.1~20.04.2" and confirmed the crash issue is resolved. -- 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/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Impish: New Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1946621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967558] Re: major copy problem !
[Expired for thunar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunar (Ubuntu) Status: Incomplete => Expired -- 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/1967558 Title: major copy problem ! Status in nautilus package in Ubuntu: Expired Status in pcmanfm package in Ubuntu: Expired Status in thunar package in Ubuntu: Expired Bug description: Hello, it is not possible to copy a folder with subfolders, see error messages in the appendix The copy problem does not exist, using Knoppix 9.1 ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967558] Re: major copy problem !
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1967558 Title: major copy problem ! Status in nautilus package in Ubuntu: Expired Status in pcmanfm package in Ubuntu: Expired Status in thunar package in Ubuntu: Expired Bug description: Hello, it is not possible to copy a folder with subfolders, see error messages in the appendix The copy problem does not exist, using Knoppix 9.1 ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967558] Re: major copy problem !
[Expired for pcmanfm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pcmanfm (Ubuntu) Status: Incomplete => Expired -- 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/1967558 Title: major copy problem ! Status in nautilus package in Ubuntu: Expired Status in pcmanfm package in Ubuntu: Expired Status in thunar package in Ubuntu: Expired Bug description: Hello, it is not possible to copy a folder with subfolders, see error messages in the appendix The copy problem does not exist, using Knoppix 9.1 ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969637] Re: IBus lookup table appears bottom left of application (x11)
This bug was fixed in the package gnome-settings-daemon - 42.2-1ubuntu1
---
gnome-settings-daemon (42.2-1ubuntu1) kinetic; urgency=medium
* Merge with Debian. Remaining changes:
+ debian/control.in:
- Build-depend on accountsservice
- Drop build-dependency on libnss-dev and add to libgck-1-dev
- Recommend pipewire-pulse instead of pulseaudio
+ debian/patches/ubuntu:
- keyboard-sync-input-sources-to-accountsservice.patch
- keyboard-Use-ibus-sources-from-locale.patch
- lid-close-suspend-support.patch
- media-keys-correct-logout-action.patch
- media-keys-restore-terminal-keyboard-shortcut-schema.patch
- print-notifications-suppress-printer-may-not-be-connected.patch
- teach-gsd-about-the-gnome-calculator-snap-.desktop-name.patch
- Revert-media-keys-fix-gnome-settings-desktop-file.patch
+ debian/patches/p11-kit:
- Use p11-kit (via gck) as smartcards backend
+ debian/gnome-settings-daemon.install:
- Install apport hook
gnome-settings-daemon (42.2-1) unstable; urgency=medium
* Team upload
* New upstream release (LP: #1969637)
* Bump Standards-Version to 4.6.1
gnome-settings-daemon (42.1-3) unstable; urgency=medium
* Drop Revert-sharing-Don-t-manage-gnome-remote-desktop.patch
- gnome-remote-desktop 42 provides its own systemd user session
to start itself
gnome-settings-daemon (42.1-2) unstable; urgency=medium
* Team upload
[ Jeremy Bicha ]
* Seitch back to libgweather4
* debian/control.in: Build-Depend on libgweather4
* debian/control.in: Break older gnome-control-center (Closes: #1008493)
-- Gunnar Hjalmarsson Wed, 01 Jun 2022 15:29:11
+0200
** Changed in: gnome-settings-daemon (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1969637
Title:
IBus lookup table appears bottom left of application (x11)
Status in GNOME Settings Daemon:
Fix Released
Status in ibus:
Fix Released
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in im-config package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Jammy:
Fix Released
Status in im-config package in Debian:
Fix Released
Status in openSUSE:
Unknown
Bug description:
[Impact]
Changes in gnome-settings-daemon v. 42 resulted in IM issues in GNOME
on Xorg. On Ubuntu the effect is that the candidate window is
misplaced, and appears at the bottom of the application window instead
of close to the cursor. It's an annoying enough issue to justify an
SRU.
[Test Plan]
On an updated Ubuntu 22.04:
1. Install ibus-libpinyin
2. Run these commands:
sudo locale-gen zh_CN.UTF-8
sudo update-locale LC_CTYPE=zh_CN.UTF-8
3. Reboot and log in to an Ubuntu on Xorg session
4. Add "Intelligent Pinyin" to the input sources
5. Open gedit, switch to "Intelligent Pinyin", and input something.
=> Find that the candidate window is misplaced.
6. Install gnome-settings-daemon{,-common} from jammy-proposed and
reboot
7. Repeat step 5.
=> Find that the candidate window is shown close to the cursor as
expected.
[Where problems could occur]
The change is an upstream MR and a one-liner. It shouldn't reasonably
affect anything but ibus configuration, and I have successfully tested
it back and forth in both x11 and wayland sessions.
[Other Info]
This change has not yet reached kinetic, but will do so later when
g-s-d is upgraded. The issue has temporarily been addressed in Debian
(and soon in kinetic via sync) through an im-config workaround, which
will be dropped later when g-s-d is updated. But for an SRU I think
it's better to make the more proper g-s-d change directly.
[Original description]
I know it is not im-config issue. I don't know what is root cause.
how to reproduce:
1. Install Ubuntu 22.04 LTS or apply newest update
2. boot
3. select a user
4. select Ubuntu on Xorg
5. input password
6. login
7. run gedit
8. push Hankaku/Zenkaku key
9. input any keys
10. lookup table appears bottom left of application
proposed fix:
edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on
/etc/default/im-config
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: im-config 0.50-2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 21 00:13:10 2022
InstallationDate: Installed on 2022-04-20 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ja_JP.UTF-8
SHELL=/bin/bash
[Desktop-packages] [Bug 1976567] [NEW] Desktop scaling was set incorrectly until I booted up the PC AFTER turning on the monitor
Public bug reported: Whenever I boot up my PC, I turn on the monitor as well. When this happens, the Intel Mesa graphics loads, and my screen ends up being small with large pixelated icons. The resolution was capped at 1024x768. Only after I reboot my PC multiple times without changing the display settings did the resolution increase to 1680x1050, the correct resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:07:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0589] InstallationDate: Installed on 2022-05-22 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy resolution ubuntu wayland-session -- 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/1976567 Title: Desktop scaling was set incorrectly until I booted up the PC AFTER turning on the monitor Status in xorg package in Ubuntu: New Bug description: Whenever I boot up my PC, I turn on the monitor as well. When this happens, the Intel Mesa graphics loads, and my screen ends up being small with large pixelated icons. The resolution was capped at 1024x768. Only after I reboot my PC multiple times without changing the display settings did the resolution increase to 1680x1050, the correct resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:07:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0589] InstallationDate: Installed on 2022-05-22 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1
[Desktop-packages] [Bug 1976563] [NEW] All text and images in Gnome Shell are corrupted
Public bug reported: See attached screenshot. The corrupted text and images are only appearing in the Ubuntu desktop environment (like the login screen, dock, and the bar at top of the screen). Applications like Nautilus, the Terminal app, and Chrome are not affected. Maybe an Nvidia issue? I'm going to restart my PC which will probably fix the issue. I'll edit this if the issue persists after the restart. Edit: To anyone investigating this issue, I recommend looking at some of the other issues I've reported recently. It seems like they could all be connected somehow, with Nvidia as the common thread. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file. .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 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 18:58:22 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.73.05, 5.15.0-33-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (39 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 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:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu ** Attachment added: "Screenshot from 2022-06-01 18-57-55.png" https://bugs.launchpad.net/bugs/1976563/+attachment/5594368/+files/Screenshot%20from%202022-06-01%2018-57-55.png ** Description changed: See attached screenshot. The corrupted text and images are only appearing in the Ubuntu desktop environment (like the login screen, dock, and the bar at top of the screen). Applications like Nautilus, the Terminal app, and Chrome are not affected. Maybe an Nvidia issue? I'm going to restart my PC which will probably fix the issue. I'll edit this if the issue persists after the restart. + + Edit: To anyone investigating this issue, I recommend looking at some of + the other issues I've reported recently. It seems like they could all be +
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
** Changed in: network-manager Status: Unknown => 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in NetworkManager: New Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976484] Re: never sound ubuntu 20.04 22.04 alsamixer 1.2.6 card sof-hda-dsp
** Information type changed from Private Security to Public -- 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/1976484 Title: never sound ubuntu 20.04 22.04 alsamixer 1.2.6 card sof-hda-dsp Status in alsa-driver package in Ubuntu: New Bug description: no sound ubuntu 20.04 and 22.04 alsamixer 1.2.6 card sof-hda-dsp ships Intel Broxton HDMI, with and no pulseaudio ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 11:15:42 2022 InstallationDate: Installed on 2022-05-26 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: APD-BI-14.1-Y116AR150-098-E dmi.board.asset.tag: Default string dmi.board.name: N14C4WH64 dmi.board.vendor: THOMSON dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 5.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrAPD-BI-14.1-Y116AR150-098-E:bd08/11/2021:br5.12:efr5.1:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnN14C4WH64:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64: dmi.product.family: Notebook dmi.product.name: N14C4WH64 dmi.product.sku: N14C4WH64 dmi.product.version: Default string dmi.sys.vendor: THOMSON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1976484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970615] Re: WebGL does not work in snap firefox
It works now in snap Firefox 102.0b2 (64-bit) on Ubuntu 22.04 LTS. -- 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/1970615 Title: WebGL does not work in snap firefox Status in firefox package in Ubuntu: Incomplete Bug description: Since upgrading to Ubuntu 22.04 LTS I am no longer able to use WebGL on firefox. If I go to https://get.webgl.org/ it says "Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card." This is the case on my laptop with Intel HD4600 Graphics and on my desktop with AMD Vega 56 Graphics. Both are on Ubuntu 22.04 LTS with snap firefox. troels@troels-thinkpad:~$ glxinfo | grep OpenGL OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 22.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: I therefore have to use Chrome instead for developement using three.js To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976558] [NEW] upgrade from ubuntu 20.04 to 22.04 fails due to yaru-theme-gnome-shell missing files
Public bug reported: I had to delete installed files of Yaru Theme for Ubuntu 20.04 LTS before continuing the upgrade to Ubuntu 22.04 LTS. dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-enter.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/meson.build' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-layout.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift-latched-uppercase.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-hide.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift-uppercase.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: directory '/usr/share/themes/Yaru-dark/gnome-shell' contains files not owned by package yaru-theme-gnome-shell:all, cannot switch to symlink dpkg: s'ha produït un error en processar l'arxiu /tmp/apt-dpkg-install-CLn2dX/14-yaru-theme-gnome-shell_22.04.4_all.deb (--unpack): el subprocés «guió «yaru-theme-gnome-shell» nou del paquet pre-installation» retornà el codi d'eixida d'error 1 After removing those files and trying a second time, there were more missing files: /usr/share/themes/Yaru/gnome-shell/key-enter.svg /usr/share/themes/Yaru/gnome-shell/meson.build /usr/share/themes/Yaru/gnome-shell/key-layout.svg /usr/share/themes/Yaru/gnome-shell/key-shift.svg /usr/share/themes/Yaru/gnome-shell/gnome-shell-high-contrast.css /usr/share/themes/Yaru/gnome-shell/key-shift-latched-uppercase.svg /usr/share/themes/Yaru/gnome-shell/key-hide.svg /usr/share/themes/Yaru/gnome-shell/key-shift-uppercase.svg /usr/share/themes/Yaru/gnome-shell/gnome-shell.css After removing those too, I could proceed and finish the upgrade. With aptitude resolving broken dependencies was possible. Afterwards reexecuted the upgrader already unpacked to /tmp. That removed old packages not needed anymore which aptitude failed to manage. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yaru-theme-gnome-shell 22.04.4 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:47:29 2022 Dependencies: InstallationDate: Installed on 2014-06-05 (2917 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to jammy on 2022-06-01 (0 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1976558 Title: upgrade from ubuntu 20.04 to 22.04 fails due to yaru-theme-gnome-shell missing files Status in yaru-theme package in Ubuntu: New Bug description: I had to delete installed files of Yaru Theme for Ubuntu 20.04 LTS before continuing the upgrade to Ubuntu 22.04 LTS. dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-enter.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/meson.build' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-layout.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift-latched-uppercase.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-hide.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift-uppercase.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: directory '/usr/share/themes/Yaru-dark/gnome-shell' contains files not owned by package yaru-theme-gnome-shell:all, cannot switch to symlink dpkg: s'ha produït un error en processar l'arxiu /tmp/apt-dpkg-install-CLn2dX/14-yaru-theme-gnome-shell_22.04.4_all.deb (--unpack): el subprocés «guió
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
Same on 22.04 Gnome Xorg, Nouveau driver on a GeForce GTX 1650 Ti Mobile -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME 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-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976554] [NEW] Screen auto rotates randomly after suspend
Public bug reported: Description:Ubuntu 22.04 LTS Release:22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1976554 Title: Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos
** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311593/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "This is what I see (taken from a camera) after Ubuntu finishes booting and loads the login manager." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150317/+files/i5Fee.jpg ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150318/+files/Dependencies.txt ** Attachment removed: "Output of "lspci -k"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5154814/+files/output.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150319/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "xrandr" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5173498/+files/xrandr.txt ** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5173499/+files/dmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311591/+files/Dependencies.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308778/+files/Dependencies.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310808/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308779/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308780/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308786/+files/CurrentDmesg.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311592/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308787/+files/DpkgLog.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308788/+files/Lspci.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308789/+files/Lsusb.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308790/+files/ProcCpuinfo.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308791/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308792/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308793/+files/UdevDb.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308794/+files/xdpyinfo.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308795/+files/Xrandr.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308796/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308797/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308798/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310806/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310807/+files/ProcCpuinfoMinimal.txt ** Information type changed from Public to Private -- 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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu
[Desktop-packages] [Bug 1969974] Re: Gnome screen recorder doesn't work on dist-upgraded jammy systems
*** This bug is a duplicate of bug 1963264 *** https://bugs.launchpad.net/bugs/1963264 Simply deleting the cached gstreamer dir fixed it for me. rm -rf ~/.cache/gstreamer-1.0 -- 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/1969974 Title: Gnome screen recorder doesn't work on dist-upgraded jammy systems Status in gnome-shell package in Ubuntu: Confirmed Bug description: I've just installed ubuntu 22.04; Screencasting (video recording) doesn't work... every time I open the screen tools (those which you can open with prtscr), and press the red button for screen recording, a red thing appear top right of my screen and it will be disappeared immediately! And then nothing happen :( Update: log: Apr 27 12:37:52 blacklighter systemd[2022]: Started Tracker metadata extractor. Apr 27 12:39:18 blacklighter dbus-daemon[63804]: [session uid=1000 pid=63804] Activating service name='org.gnome.Shell.Screencast' requested by ':1.30' (uid=1000 pid=63952 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 12:39:18 blacklighter dbus-daemon[63804]: [session uid=1000 pid=63804] Successfully activated service 'org.gnome.Shell.Screencast' Apr 27 12:39:18 blacklighter gjs[66306]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" Apr 27 12:39:18 blacklighter gnome-shell[63952]: Error starting screencast Apr 27 12:39:20 blacklighter gnome-shell[63952]: D-Bus client with active sessions vanished Complete file: https://launchpadlibrarian.net/598628526/log.txt Also I tried installing pipwire: sudo apt update sudo apt install pipewire-media-session libpipewire-0.3-common Seems like I've already had the newest version libpipewire-0.3-common is already the newest version (0.3.48-1ubuntu1). pipewire-media-session is already the newest version (0.4.1-2ubuntu1). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 22:03:57 2022 DistUpgraded: 2022-04-22 18:01:56,000 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:828c] InstallationDate: Installed on 2021-08-07 (257 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5ae Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G4 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=cfaddaca-a453-457a-bdb2-1acc1600816e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago) dmi.bios.date: 04/11/2017 dmi.bios.release: 1.3 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.03 dmi.board.name: 828C dmi.board.vendor: HP dmi.board.version: KBC Version 45.34 dmi.chassis.asset.tag: 5CG7242D5P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 69.52 dmi.modalias: dmi:bvnHP:bvrP78Ver.01.03:bd04/11/2017:br1.3:efr69.52:svnHP:pnHPEliteBook840G4:pvr:rvnHP:rn828C:rvrKBCVersion45.34:cvnHP:ct10:cvr:skuX3V00AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G4 dmi.product.sku: X3V00AV dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+22.04.20211217-0ubuntu2 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969974/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1870597] Re: libinput says "your system is too slow"
** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350642/+files/BootLog.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350644/+files/Lspci.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345771/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345772/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ShellJournal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345773/+files/ShellJournal.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350643/+files/CurrentDmesg.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350646/+files/Lsusb-t.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350645/+files/Lsusb.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350647/+files/Lsusb-v.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350648/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350649/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350650/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350651/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350652/+files/UdevDb.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350653/+files/Xrandr.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350654/+files/xdpyinfo.txt ** Description changed: - During the freeze, the output of the install had a message from "gdm-x- - session" saying "your system is too slow". - - To reproduce: - 1. Launch the Ubuntu installer - 2. Begin the installation process - 3. When the installation process begins, move the cursor around - 4. Notice how the PC freezes and drops mouse events - - Description: Ubuntu Focal Fossa (development branch) - Release: 20.04 - - gnome-shell: - Installed: 3.36.0-2ubuntu2 - Candidate: 3.36.0-2ubuntu2 - Version table: - *** 3.36.0-2ubuntu2 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status - - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: gnome-shell 3.36.0-2ubuntu2 - ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 - Uname: Linux 5.4.0-21-generic x86_64 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - ApportVersion: 2.20.11-0ubuntu21 - Architecture: amd64 - CasperVersion: 1.442 - Date: Fri Apr 3 14:24:21 2020 - DisplayManager: gdm3 - GsettingsChanges: - - LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash - RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 - SourcePackage: gnome-shell - UpgradeStatus: No upgrade log present (probably fresh install) - --- - ProblemType: Bug - ApportVersion: 2.20.11-0ubuntu22 - Architecture: amd64 - CasperVersion: 1.442 - CompositorRunning: None - DistUpgraded: Fresh install - DistroCodename: focal - DistroRelease: Ubuntu 20.04 - DistroVariant: ubuntu - ExtraDebuggingInterest: Yes - GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Dell UHD Graphics 620 [1028:0810] - LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) - MachineType: Dell Inc. Inspiron 5570 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - Package: xorg-server (not installed) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash - ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- - ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 - Tags: focal ubuntu - Uname: Linux 5.4.0-21-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: - - _MarkForUpload: True - dmi.bios.date: 05/15/2019 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 1.2.3 - dmi.board.name: 09YTN7 -
[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive
Matthieu, more recently a more likely problem has been characterized by Alberto Mardegan and found the line in question in https://bugs.launchpad.net/snapd/+bug/1973321 In particular, restarting snapd doesn't help at all for me, so having the directory mounted before snapd starts doesn't help, and the same problem occurs with other file systems. However _starting_ outside the home directory does help. This is the situation for me with Kerberos authenticated NFS, and others with sshfs. I don't know whether it is relevant for people using NFS without authentication. It is easy to test for yourself - restart snapd and see if that helps. So I think there is progress in understanding the problem, even if not working out how to fix it. FYI: I initially tried a work around where I used the debian repository for firefox instead of the snap version, but despite giving it a higher priority (confirmed via "sudo apt policy firefox") I found the debian package twice over a week uninstalled and replaced by the snap version that then would not start. I can manually revert it but it is inconvenient. Any suggestions on how to make that work reliably would be appreciated. -- 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/1884299 Title: Chromium snap won't run with nfs home drive Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926218] Re: Disable or Remove FLoC features and the provider service
'find "$HOME"/snap/chromium -iname *floc*' gives me nothing either, but
I only installed it a couple of weeks ago.
Some things I observe:
1. In my set-up, Floc can _not_ be enabled in
.
2. Look into the parts concerning Floc in the source code, one finds several
stub functions, e.g. in
chrome/browser/privacy_sandbox/privacy_sandbox_service.cc:393
void PrivacySandboxService::SetFlocPrefEnabled(bool enabled) const {
// TODO(crbug.com/1299720): Remove this and all the UI code which uses it.
return;
}
3. In that page ,
> FLoC-the-feature has been removed from the codebase, but there are still a
> few UX surfaces that need to surface FLoC information (basically informing
> users that it's disabled).
>
> To support this, while also transitioning to Privacy Sandbox Settings 3, many
> functions have been left with stubs with little or no functionality.
>
> Once Privacy Sandbox Settings 3 has been launched, these surfaces are no
> longer required, and the remaining functions can be cleaned up.
And then the title of commit
https://chromium.googlesource.com/chromium/src/+/3c4b23ea94bf0efbc12d93e832b5888c50412b6b
is
> Privacy Sandbox Settings: Move FLoC to Topics API
This suggests Google is moving away from Floc.
4. Indeed, from
,
> The origin trial of FLoC in 2021 received a wide range of feedback from
> adtech and web ecosystem contributors. In particular, there were concerns
> that FLoC cohorts could be used as a fingerprinting surface to identify
> users, or could reveal a user's association with a sensitive category. There
> were also calls to make FLoC more transparent and understandable to users.
>
> The Topics API has been designed with this feedback in mind, to explore other
> ways to support interest-based advertising, with improved transparency,
> stronger privacy assurances and a different approach for sensitive categories.
All in all, apparently Floc is being phased out we have a moving target. So, if
that is a correct assessment, although this bug report will technically solve
itself with time (insofar as it is targeted at Floc), we will still keep an eye
for future tracking mechanisms inside Chromium, under whatever name they may
come to be.
** Changed in: chromium-browser (Ubuntu)
Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1926218
Title:
Disable or Remove FLoC features and the provider service
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
Disable or remove entire FLoc,
- FLoC component
- Any other FLoC functionalities shipped in Chromium
- FLoC client-side determinations of cohorts
- Any reporting of FLoC cohort determinations to Google (or otherwise)
servers (i.e., the reporting used for k-anonymity cohort protections)
- FLoC JS methods (i.e. document.interestCohort)
Brave, Vivaldi, Bromite have addressed FLoC issue and edge browser has
disabled it
Resources: https://github.com/brave/brave-core/pull/8468
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/696632
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1926218/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976330] Re: No dropdown menu on bookmarks folder in trunk build under wayland
still on trunc 103.0a1 -- 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/1976330 Title: No dropdown menu on bookmarks folder in trunk build under wayland Status in firefox package in Ubuntu: New Bug description: firefox-trunk: Installed: 103.0~a1~hg20220530r619138-0ubuntu0.22.10.1~umd1 Ubuntu 22.10 Kinetic Wayland session Window Protocol wayland Desktop Environment gnome problem with Bookmarks: click om Bookmarks - the list of bookmarks is displayed right click on a bookmark folder - dropdown menu with 'Open all Bookmarks/Edit Folder/Delete Folder...' open folder and right click on a second level folder - nothing happens, the dropdown menu does not appear. corrado@corrado-a4-kk-0513:~$ inxi -SCGx System: Host: corrado-a4-kk-0513 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.1 Distro: Ubuntu 22.10 (Kinetic Kudu) CPU: Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 798 high: 799 min/max: 800/3400 cores: 1: 798 2: 798 3: 799 4: 799 bogomips: 27138 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1 compositor: gnome-shell driver: gpu: i915 resolution: 1680x1050~60Hz OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2) v: 4.6 Mesa 22.0.1 direct render: Yes corrado@corrado-a4-kk-0513:~$ problem does not occur on same system with FF snap firefox 100.0.2-1 1377 Window Protocol xwayland Desktop Environment gnome same problem on Ubuntu 22.04 with firefox-trunk Installed: 102.0~a1~hg20220527r619043-0ubuntu0.22.04.1~umd1 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: firefox-trunk 103.0~a1~hg20220530r619138-0ubuntu0.22.10.1~umd1 [origin: LP-PPA-ubuntu-mozilla-daily] ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado1790 F pipewire-media- /dev/snd/controlC1: corrado1790 F pipewire-media- /dev/snd/seq:corrado1789 F pipewire BuildID: 20220530185055 CasperMD5CheckResult: pass Channel: nightly CurrentDesktop: ubuntu:GNOME Date: Tue May 31 08:37:09 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox-trunk/omni.ja:greprefs.js:306 DefaultProfilePrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox-trunk/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-05-14 (16 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512) IpRoute: default via 192.168.43.1 dev wlx48ee0c2322b8 proto dhcp src 192.168.43.140 metric 600 169.254.0.0/16 dev wlx48ee0c2322b8 scope link metric 1000 192.168.43.0/24 dev wlx48ee0c2322b8 proto kernel scope link src 192.168.43.140 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox-trunk/omni.ja:greprefs.js:306 Profile0PrefSources: /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=103.0a1/20220530185055 (In use) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M.
[Desktop-packages] [Bug 1973229] Re: Update freerdp2 to 2.7.0
Robie, for now, we are just cherrypicking the more urgent fix. I've uploaded to the jammy Unapproved queue. Feel free to reject the freerdp2 2.7.0 upload for now. ** Changed in: freerdp2 (Ubuntu Jammy) Assignee: Jeremy Bicha (jbicha) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 Status in freerdp2 package in Ubuntu: Fix Released Status in freerdp2 source package in Jammy: Incomplete Bug description: Impact -- Ubuntu 22.04 LTS includes basically a git snapshot of freerdp2 as of April 11. freerdp 2.7.0 was released April 25 with a few more bug fixes. https://github.com/FreeRDP/FreeRDP/commits/stable-2.0?after=f8a4c6a9fed51cacd7b75ca95e2fcb018f4ac5b8+46=stable-2.0 From the NEWS file, the changes are * Backported OpenSSL3 gateway support (#7822) * Backported #7733: Support 10bit X11 color (BGRX32 only) * Backported #7808: Disable websockets with /gt:rpc * Backported #7815: RAIL expect LOGON_MSG_SESSION_CONTINUE Also, this includes patches that the upstream gnome-remote-desktop maintainers believe fix LP: #1970994 I am not mentioning that bug number in the debian/changelog because I don't have a clear test case to reproduce that bug, which is needed for SRU verification to go smoothly. Test Case #1 Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Then repeat the test after updating the second computer to use the updated freerdp2 since Remmina itself uses freerdp2. Basically we want to make sure things keep working after the update but also continue to work for connections between systems that aren't using the same version of freerdp2. What Could Go Wrong --- RDP Sharing using freerdp2 is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. freerdp2 is also used by the Remmina and GNOME Connections apps as the "client" app for RDP Sharing. (The GNOME feature is the "server" side.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970994] Re: /usr/libexec/gnome-remote-desktop-daemon:11:setChannelError:rdpgfx_server_thread_func:thread_launcher:start_thread:clone3
** Description changed: + Impact + -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.0-4ubuntu1, the problem page at https://errors.ubuntu.com/problem/77f41623474304919ac793c6665505547b583b60 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/. + Test Case 1 + --- + Unfortunately, we weren't able to identify a reliable test case. - It's believed this issue will be fixed with - https://github.com/FreeRDP/FreeRDP/pull/7836 + We will know if this bug is fixed if errors.ubuntu.com stops reporting + that error with a fully upgraded system. However, that means this update + will need to be pushed to -updates + + Test Case 2 + --- + Install all updates. Log out and log back in. + Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. + Turn it off then on because there may be a gnome-control-center bug with initial enabling. + + From a second computer, connect to the first computer using Remmina. + + The Remote Desktop page on the first computer provides the username and + password to use. I wasn't able to get the "Remote Desktop Address" to + work (maybe avahi doesn't work well?) so just use the first computer's + IP address. + + So something like: + RDP jeremy@192.168.1.1 + + Ensure that the connection works. + + Then repeat the test after updating the second computer to use the + updated freerdp2 since Remmina itself uses freerdp2. Basically we want + to make sure things keep working after the update but also continue to + work for connections between systems that aren't using the same version + of freerdp2. + + What Could Go Wrong + --- + RDP Sharing using freerdp2 is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. + + RDP Sharing can be used for providing remote support so it's important + that this feature works well because it may be difficult for the remote + admin to fix issues in person. + + freerdp2 is also used by the Remmina and GNOME Connections apps as the + "client" app for RDP Sharing. (The GNOME feature is the "server" side.) + + This fix is cherrypicked from the stable freerdp2 branch. ** Changed in: gnome-remote-desktop (Ubuntu) Status: Triaged => Invalid ** Changed in: freerdp2 (Ubuntu) Status: Triaged => Fix Released ** Changed in: freerdp2 (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: freerdp2 (Ubuntu) Importance: Undecided => Medium ** Changed in: freerdp2 (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1970994 Title: /usr/libexec/gnome-remote-desktop- daemon:11:setChannelError:rdpgfx_server_thread_func:thread_launcher:start_thread:clone3 Status in freerdp2 package in Ubuntu: Fix Released Status in gnome-remote-desktop package in Ubuntu: Invalid Status in freerdp2 source package in Jammy: In Progress Bug description: Impact -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.0-4ubuntu1, the problem page at https://errors.ubuntu.com/problem/77f41623474304919ac793c6665505547b583b60 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/. Test Case 1 --- Unfortunately, we weren't able to identify a reliable test case. We will know if this bug is fixed if errors.ubuntu.com stops reporting that error with a fully upgraded system. However, that means this update will need to be pushed to -updates Test Case 2 --- Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Then repeat the test after updating the second computer to use the updated freerdp2 since Remmina itself uses freerdp2. Basically we want to make sure
[Desktop-packages] [Bug 1976547] [NEW] Update gnome-remote-desktop to 42.2
Public bug reported: Impact -- This is a new stable release in the GNOME 42 series https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.2/NEWS Test Case #1 Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. >From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Test Case #2 Do test case #1 but this time also enable the Legacy VNC option on the Remote Desktop Sharing page. Connect using VNC instead and ensure that the connection works. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-remote-desktop (Ubuntu) Importance: Wishlist Status: Fix Committed ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1976547 Title: Update gnome-remote-desktop to 42.2 Status in gnome-remote-desktop package in Ubuntu: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.2/NEWS Test Case #1 Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Test Case #2 Do test case #1 but this time also enable the Legacy VNC option on the Remote Desktop Sharing page. Connect using VNC instead and ensure that the connection works. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1976547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976498] Re: DING causes gvfsd 'Too many files open' error and fills syslog
Changed from ding to nautilus after reading about nautilus gvfsd-trash bug ** Package changed: ding (Ubuntu) => nautilus (Ubuntu) ** Summary changed: - DING causes gvfsd 'Too many files open' error and fills syslog + nautilus causes gvfsd-trash 'Too many files open' error and fills syslog ** Description changed: - My syslog is filled (to >30GB) regularly with these messages. I seem to - have this thing called DING going on, which maybe causing it? + My syslog is filled (to >30GB) regularly with these messages. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: (org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer connection failed: Unable to create socket: Too many open files. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create socket: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1 Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]:
[Desktop-packages] [Bug 1976498] [NEW] DING causes gvfsd 'Too many files open' error and fills syslog
You have been subscribed to a public bug: My syslog is filled (to >30GB) regularly with these messages. I seem to have this thing called DING going on, which maybe causing it? Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: (org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer connection failed: Unable to create socket: Too many open files. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create socket: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1 Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.636: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.636: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.637: fail: Error
[Desktop-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 Same problem and solution today in ubuntu 20.04. Thanks for the solution! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in console-setup package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969901] Re: network-manager fails to renew ipv6 address
>> The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks >> are not known > >Looking at the upstream commit description, isn't it just that a DHCPv6 lease >expires and the >server NAKs a request for the same IP again? Or is that not >sufficient to trigger the problem. > Yes, when having a look at the previously collected logs, that seems to be the case (journalctl -u NetworkManager.service). Some of our computers get this problem more often that other. Some persons claim that they have never seen the problem. That is the part that is unclear. >In any case, I appreciate there might be difficulty in testing the fix, but >what's the actual >criteria you propose to use to decide when the bug is to be >marked verification-done-bionic? In the best of worlds I would like to simulated environment where dhcp- packages could be controlled, but that is not feasible. I have been running this patch on two computers since 2022-04-13 and haven't seen the problem since. One laptop (restarted every day) and one desktop that is always on. The desktop has been running for 29 days continuously according to syslog, without me having to manually remove dhcp lease files and restart network manager. Ideas for getting confidence of this change: We could ask more users who have experienced this error to install this change and confirm if they experience lost ipv6 addresses after installing patched version. Another idea is to shutdown computer in single user mode (without network), edit the dhcp6 lease file in a way so that dhcp-server will respond with NACK when booting up in multi-user mode. What to change in the lease file I do not know. -- 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/1969901 Title: network-manager fails to renew ipv6 address Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Incomplete Bug description: [Impact] * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is used. * Network manager might kill dhclient(6) and fail to start it again causing the IPv6 address to be lost on a network that uses mixed IPv4/IPV6. The network status will still be seen as online in gnome since ipv4 is still active. The user then have to manually remove the dhcpv6 lease files and restart ipv6 connection/restart network manager to regain IPv6 connectivity. * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version is based on 1.10.6): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f * Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=783391 [Test Plan] * The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks are not known but includes using both IPv4 and IPv6, both using dhcp. [Where problems could occur] * The change is in the dchp lease expiration handling so verify that there is no regression in dhcp renewals on different type of configuration include IPv6 [Other Info] * We have tested this patch on a couple of clients where we have seen this this problem. If this patch is feasible to include in Ubuntu 18.04 we could request more users to test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976530] [NEW] gnome-software cannot run updates shown as available
Public bug reported: gnome software tells me it has a bunch of updates available, but on clicking "update all" or "update" on single entries, it first asks me for my password, but then just shows a message saying "Unable to update APPLICATION - snap has no updates available". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-software 41.5-2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 17:56:49 2022 InstallationDate: Installed on 2020-04-12 (779 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak 41.5-2 gnome-software-plugin-snap41.5-2 SourcePackage: gnome-software UpgradeStatus: Upgraded to jammy on 2022-04-28 (33 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-06-01 17-56-07.png" https://bugs.launchpad.net/bugs/1976530/+attachment/5594332/+files/Screenshot%20from%202022-06-01%2017-56-07.png -- 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/1976530 Title: gnome-software cannot run updates shown as available Status in gnome-software package in Ubuntu: New Bug description: gnome software tells me it has a bunch of updates available, but on clicking "update all" or "update" on single entries, it first asks me for my password, but then just shows a message saying "Unable to update APPLICATION - snap has no updates available". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-software 41.5-2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 17:56:49 2022 InstallationDate: Installed on 2020-04-12 (779 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak 41.5-2 gnome-software-plugin-snap41.5-2 SourcePackage: gnome-software UpgradeStatus: Upgraded to jammy on 2022-04-28 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1976530/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
Okay, I found this doc: https://www.x.org/wiki/Development/Documentation/ServerDebugging/ for the server debugging, is it enough? Do you know any other tutorials/resources so I can try do it by myself? And I would appreciate if a Ubuntu MATE contributor could help. -- 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/1976161 Title: Session restarts when opening Pluma or GitHub link in browser Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: From a fresh install with Ubuntu Mate 22.04, do: 1. Login into your user with password. 2. Open Firefox. 3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address. 4. GUI will reset and go back to login screen like started a new session. This also happens when I tried with opening a '.log' with Pluma. I've tried a lot of things at other installation to tackle this problem, but I couldn't solve the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Snap: snapd 2.55.5 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00 Auto-refresh snaps "core20", "firefox", "snapd" Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976500] Re: Update gtk4 to 4.6.5
** Description changed: Impact -- There is a new point release in the stable GTK 4.6 series. (The version in Ubuntu 22.04 LTS is currently 4.6.3). https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.5/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk is not listed in the proposed set of packages at https://wiki.ubuntu.com/StableReleaseUpdates/GNOME but I believe it should be. gtk4 has extensive build tests and autopkgtests. + + Other Info + -- + This adds a build dependency on gi-docgen so that we can reuse Debian's version of the gtk4 tarball which no longer includes the bundled copy of gi-docgen. ** Changed in: gtk4 (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gtk4 (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1976500 Title: Update gtk4 to 4.6.5 Status in gtk4 package in Ubuntu: Fix Committed Status in gtk4 source package in Jammy: In Progress Bug description: Impact -- There is a new point release in the stable GTK 4.6 series. (The version in Ubuntu 22.04 LTS is currently 4.6.3). https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.5/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk is not listed in the proposed set of packages at https://wiki.ubuntu.com/StableReleaseUpdates/GNOME but I believe it should be. gtk4 has extensive build tests and autopkgtests. Other Info -- This adds a build dependency on gi-docgen so that we can reuse Debian's version of the gtk4 tarball which no longer includes the bundled copy of gi-docgen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1976500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971112] Re: File picker gets bigger more and more each time!
** Changed in: gtk4 (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: gtk4 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu Jammy) Status: New => In Progress ** Changed in: gtk4 (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1971112 Title: File picker gets bigger more and more each time! Status in gtk4 package in Ubuntu: Fix Committed Status in gtk4 source package in Jammy: In Progress Bug description: Hello. I've just switched to Ubuntu and ever since day 1 I had this issue that whenever I tried to choose a file the file picker window was way too big and it was getting bigger and bigger each time. I have posted a video on Reddit recording this unusual/unexpected behavior. Here is the reddit post link (with video): https://www.reddit.com/r/Ubuntu/comments/ug97qx/annoying_bug_file_picker_gets_bigger_more_and/ I've also attached the video to this post, in case you don't want to click the link above. Here is my neofetch output: OS: Ubuntu 22.04 LTS x86_64 Kernel: 5.15.0-27-generic Uptime: 13 hours, 13 mins Shell: bash 5.1.16 Resolution: 1440x900, 1920x1080 DE: GNOME 42.0 WM: Mutter WM Theme: Adwaita Theme: Yaru-viridian-dark [GTK2/3] Icons: Yaru-viridian [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-8700K (12) @ 4.700GHz GPU: NVIDIA GeForce GTX 1060 3GB Memory: 5869MiB / 15936MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1971112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970662] Re: Update gnome-remote-desktop to 42.1.1
I successfully completed both test cases with gnome-remote-desktop 42.1.1-0ubuntu1 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970662 Title: Update gnome-remote-desktop to 42.1.1 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: NOTE This adds a dependency on mutter 42.1 so mutter 42.1 needs to reach jammy-updates (and I assume fully phased) before we let this update in to jammy-updates. The dependency was added to not regress support for Nvidia users. Impact -- This is a new stable release in the GNOME 42 series https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.1.1/NEWS Test Case #1 Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Test Case #2 Do test case #1 but this time also enable the Legacy VNC option on the Remote Desktop Sharing page. Connect using VNC instead and ensure that the connection works. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964601] Re: I have no processor!
> gnome-control-center-printer-renderer produces no output on the raspi. the code basically does context = gdk_window_create_gl_context (gtk_widget_get_window (win), NULL); if (!context) return NULL; gdk_gl_context_make_current (context); renderer = g_strdup ((char *) glGetString (GL_RENDERER)); so either the gl context is failing or glGetString isn't returning a value -- 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/1964601 Title: I have no processor! Status in gnome-control-center package in Ubuntu: Confirmed Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive
In https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 it is suggested that the problem is triggered by snapd starting too early (before autofs mounts any home directory) is there a way to force autofs to mount an home directory before launching snapd ? -- 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/1884299 Title: Chromium snap won't run with nfs home drive Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive
With Ubuntu 22 shipping firefox as a snap, it fails to start here : "cannot open path of the current working directory: Permission denied" -- 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/1884299 Title: Chromium snap won't run with nfs home drive Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
#76 also works on my work's WPA2 Enterprise. PEAP Authentication, No CA cert required; Auto PEAP; MSCHAPv2 inner authentication with user & pass entered. 22.04 Jammy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: New Bug description: wpa built with in openssl3 fails to connect to TLS 1.1 or lower server those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964601] Re: I have no processor!
gnome-control-center-printer-renderer produces no output on the raspi. The debug output from gnome-control-center is: (gnome-control-center:3171): GLib-GIO-DEBUG: 14:47:50.015: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (gnome-control-center:3171): dconf-DEBUG: 14:47:50.015: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.016: watch_fast: "/org/gnome/desktop/peripherals/mouse/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.016: watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.016: watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.016: watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.017: watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.017: watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.017: watch_fast: "/org/gnome/desktop/a11y/interface/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.019: watch_established: "/org/gnome/desktop/interface/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.019: watch_established: "/org/gnome/desktop/peripherals/mouse/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.019: watch_established: "/org/gnome/desktop/sound/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/desktop/a11y/interface/" (establishing: 1) (gnome-control-center:3171): GLib-DEBUG: 14:47:50.141: unsetenv() is not thread-safe and should not be used after threads are created (gnome-control-center:3171): GLib-GIO-DEBUG: 14:47:50.162: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (gnome-control-center:3171): cc-object-storage-DEBUG: 14:47:51.608: Initializing object storage (gnome-control-center:3171): GLib-DEBUG: 14:47:51.611: unsetenv() is not thread-safe and should not be used after threads are created (gnome-control-center:3171): Gtk-DEBUG: 14:47:51.612: Connecting to session manager (gnome-control-center:3171): dconf-DEBUG: 14:47:51.714: watch_fast: "/org/gnome/control-center/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:52.664: watch_established: "/org/gnome/control-center/" (establishing: 1) (gnome-control-center:3171): network-cc-panel-DEBUG: 14:47:52.694: Monitoring NetworkManager for Wi-Fi devices (gnome-control-center:3171): cc-object-storage-DEBUG: 14:47:52.723: Adding object NMClient (CcObjectStorage::nm-client → 0xffaee090) to the storage (gnome-control-center:3171): network-cc-panel-DEBUG: 14:47:52.723: Wi-Fi panel visible: yes (gnome-control-center:3171): wacom-cc-panel-DEBUG: 14:47:52.751: Wacom panel visible: no (gnome-control-center:3171): cc-object-storage-DEBUG: 14:47:52.758: Adding object MMManager (CcObjectStorage::mm-manager → 0xffb298c0) to the storage (gnome-control-center:3171): cc-wwan-panel-DEBUG: 14:47:52.758: Monitoring ModemManager for WWAN devices (gnome-control-center:3171): cc-wwan-panel-DEBUG: 14:47:52.758: WWAN panel visible: no (gnome-control-center:3171): dconf-DEBUG: 14:47:52.778: change_fast (gnome-control-center:3171): info-overview-cc-panel-DEBUG: 14:47:57.744: Getting renderer from helper for GPU 'Unknown Graphics Controller' (gnome-control-center:3171): info-overview-cc-panel-DEBUG: 14:47:57.796: About to launch '/usr/libexec/gnome-control-center-print-renderer' (gnome-control-center:3171): info-overview-cc-panel-DEBUG: 14:47:57.796: With environment: (gnome-control-center:3171): info-overview-cc-panel-DEBUG: 14:47:57.797: DRI_PRIME = platform-fec0_v3d (gnome-control-center:3171): cc-window-DEBUG: 14:47:58.842: Time to open panel 'About': 6.063688s ** (gnome-control-center:3171): DEBUG: 14:47:59.261: No extra argument (gnome-control-center:3171): diagnostics-cc-panel-DEBUG: 14:47:59.284: ABRT vanished (gnome-control-center:3171): dconf-DEBUG: 14:48:02.202: unwatch_fast: "/org/gnome/control-center/" (active: 1, establishing: 0) (gnome-control-center:3171):
[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
Thanks! ** Changed in: nautilus (Ubuntu) Status: Incomplete => Triaged ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2277 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
This issue has now been reported to upstream: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2277 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2277 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2277 -- 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/1970921 Title: Drag and drop does not work Status in nautilus package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969901] Re: network-manager fails to renew ipv6 address
> The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks are not known Looking at the upstream commit description, isn't it just that a DHCPv6 lease expires and the server NAKs a request for the same IP again? Or is that not sufficient to trigger the problem. In any case, I appreciate there might be difficulty in testing the fix, but what's the actual criteria you propose to use to decide when the bug is to be marked verification-done-bionic? ** Also affects: network-manager (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1969901 Title: network-manager fails to renew ipv6 address Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Incomplete Bug description: [Impact] * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is used. * Network manager might kill dhclient(6) and fail to start it again causing the IPv6 address to be lost on a network that uses mixed IPv4/IPV6. The network status will still be seen as online in gnome since ipv4 is still active. The user then have to manually remove the dhcpv6 lease files and restart ipv6 connection/restart network manager to regain IPv6 connectivity. * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version is based on 1.10.6): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f * Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=783391 [Test Plan] * The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks are not known but includes using both IPv4 and IPv6, both using dhcp. [Where problems could occur] * The change is in the dchp lease expiration handling so verify that there is no regression in dhcp renewals on different type of configuration include IPv6 [Other Info] * We have tested this patch on a couple of clients where we have seen this this problem. If this patch is feasible to include in Ubuntu 18.04 we could request more users to test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926218] Re: Disable or Remove FLoC features and the provider service
That's right. But I wonder whether this is enough to guarantee that FLoC is fully disabled? In my profile directory, there's a folder named "Floc". Files under that directory were last modified 2021-10-27 though, so it might be that this was created by an older version of chromium and isn't used any longer. I'm not seeing any reference to FLoC in the Preferences file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1926218 Title: Disable or Remove FLoC features and the provider service Status in chromium-browser package in Ubuntu: Triaged Bug description: Disable or remove entire FLoc, - FLoC component - Any other FLoC functionalities shipped in Chromium - FLoC client-side determinations of cohorts - Any reporting of FLoC cohort determinations to Google (or otherwise) servers (i.e., the reporting used for k-anonymity cohort protections) - FLoC JS methods (i.e. document.interestCohort) Brave, Vivaldi, Bromite have addressed FLoC issue and edge browser has disabled it Resources: https://github.com/brave/brave-core/pull/8468 https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/696632 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1926218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
Thank you for all the background information, Dave! I've drafted a PR at upstream netplan, to allow setting the regulatory domain via wpa_supplicant.conf as well as setting it "globally" via 'iw reg set XX', using a systemd service unit. https://github.com/canonical/netplan/pull/281 -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971532] Re: Fileselector Unable To Paste Into Filename
This was fixed in https://launchpad.net/ubuntu/+source/gtk4/4.6.3+ds1-0ubuntu1 ** Changed in: gtk4 (Ubuntu Jammy) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1971532 Title: Fileselector Unable To Paste Into Filename Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Jammy: Fix Released Bug description: related to a few other bug reports: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970168 Save File prompt disallows paste to filename. Attached is a screenshot of what pops up. Tested in various directories. Info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04 LTS Release: 22.04 Codename: jammy uname -a Linux j5awry-sys76 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux snap version snap2.55.3+22.04ubuntu1 snapd 2.55.3+22.04ubuntu1 series 16 ubuntu 22.04 kernel 5.15.0-27-generic snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable refresh-date: 21 days ago, at 14:48 CDT ... installed: 99.0.1-1 (1232) 163MB - (tracking latest/stable) Reproduction: Download a file to get file prompt Cut the name attempt to paste the name back in Reproducible when targeting ~/Downloads, ~/Documents, and /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1971532/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976500] [NEW] Update gtk4 to 4.6.5
Public bug reported: Impact -- There is a new point release in the stable GTK 4.6 series. (The version in Ubuntu 22.04 LTS is currently 4.6.3). https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.5/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk is not listed in the proposed set of packages at https://wiki.ubuntu.com/StableReleaseUpdates/GNOME but I believe it should be. gtk4 has extensive build tests and autopkgtests. ** Affects: gtk4 (Ubuntu) Importance: High Status: Triaged ** Affects: gtk4 (Ubuntu Jammy) Importance: High Status: Triaged ** Tags: jammy upgrade-software-version ** Also affects: gtk4 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gtk4 (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1976500 Title: Update gtk4 to 4.6.5 Status in gtk4 package in Ubuntu: Triaged Status in gtk4 source package in Jammy: Triaged Bug description: Impact -- There is a new point release in the stable GTK 4.6 series. (The version in Ubuntu 22.04 LTS is currently 4.6.3). https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.5/NEWS Test Case 1 --- Make sure that opening and saving files from the Firefox and Chromium snaps still work Test Case 2 --- snap install portal-test snap run portal-test Verify that the app seems to still work ok What Could Go Wrong --- Ubuntu includes xdg-desktop-portal-gnome by default which is used for many snap actions like providing a file chooser. This is critical functionality for our snaps. The Ubuntu flavors use a different portal backend, most commonly xdg- desktop-portal-gtk which uses GTK3 so it's not affected by this SRU. The other gtk4 apps installed by default in Ubuntu are gnome-chess and gnome-shell-extension-prefs. gtk is not listed in the proposed set of packages at https://wiki.ubuntu.com/StableReleaseUpdates/GNOME but I believe it should be. gtk4 has extensive build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1976500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969893] Re: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9]
** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Status: New => Triaged ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => High -- 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/1969893 Title: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Triaged Bug description: gnome-shell crashes with SIGSEGV just after logging: gnome-shell[3117]: JS ERROR: TypeError: window is null _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16 Examples: https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206 https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206 https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0 Tracking in: https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470 ^^^ this is the second most common gnome-shell crash on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976381] Re: Update mutter to 42.2
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Status: New => Triaged ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1976381 Title: Update mutter to 42.2 Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Triaged Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.2/NEWS Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
Sure -- I'll try not to drown them in verbiage :) -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
@Dave, do you want to maybe add your input directly to the upstream report? -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973733] Proposed package upload rejected
An upload of cups to focal-proposed has been rejected from the upload queue for the following reason: "As requested in https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/comments/4;. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 Status in cups package in Ubuntu: Fix Released Status in cups source package in Focal: Invalid Bug description: no change rebuild to get riscv64 build out [Impact] * riscv64 build of cups security update failed, and then succeeded in groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 * do a no change rebuild of cups as an SRU to get updated cups package out on focal [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * As usual, no change rebuilds of packages may introduce miss builds. [Other Info] * currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973733] Re: no change rebuild to get security update out on riscv64
There was another security upload on 27th of may which is built on all arches, thus this rebuild is no longer needed. please reject cups from focal unapproved. ** Changed in: cups (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: cups (Ubuntu Focal) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 Status in cups package in Ubuntu: Fix Released Status in cups source package in Focal: Invalid Bug description: no change rebuild to get riscv64 build out [Impact] * riscv64 build of cups security update failed, and then succeeded in groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 * do a no change rebuild of cups as an SRU to get updated cups package out on focal [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * As usual, no change rebuilds of packages may introduce miss builds. [Other Info] * currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970978] Re: On Save As dialog, any navigation operation (e.g. change to sub-folder) takes focus away from file name entry and instead switches to search
*** This bug is a duplicate of bug 1878076 *** https://bugs.launchpad.net/bugs/1878076 ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** This bug has been marked a duplicate of bug 1878076 GTK save-dialogs input-focus moves from filename to file search if a folder is selected -- 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/1970978 Title: On Save As dialog, any navigation operation (e.g. change to sub- folder) takes focus away from file name entry and instead switches to search Status in gtk+3.0 package in Ubuntu: New Bug description: Within "Save As" dialogs from any desktop application, all navigation operations, specifically the most common one of changing folders, switches focus away from the file name input, resulting in the search input box accepting keyboard input instead of the filename input box. This is extremely frustrating for a several reasons: 1. After navigating to the desired folder, typing the name for the file is instead captured by the search input box instead of the expected filename input box 2. The search input box does not even appear until key presses are received, making it even more surprising that the filename is not being altered and is instead the beginning of a search 3. Using the mouse to re-focus on the filename input box deselects the originally selected default file name text, causing the user to have to re-select everything 4. Re-selecting everything (see previous item) causes the default file name extension (which is excluded in the initial selection) to also be selected, requiring the user to think about what it was and to re- enter that extension as well 5. "Tab" key navigation takes an inordinate number of tab key presses to return to the filename input box Sorry to complain about this, but I almost ALWAYS choose to change folders, and then when I type in the name, I have to re-do all the steps described above because the search input has invariably captured my key presses instead of the changing the filename. It is very annoying. I would like to suggest that the search input box either not be automatically switched to in the "Save As" mode of the dialog, or to have a separate and explicit search input box that does not automatically receive input after folder navigation operations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 11:06:32 2022 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2021-09-13 (227 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 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/gtk+3.0/+bug/1970978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
> It could be maybe added to NetworkManager, if somebody sends a > patch. But it's not actually clear to me that this is really > NetworkManager's task. Maybe it is, but what are the arguments for > that? I could be glib, and say "because the kernel says so [1]". However, I suspect that's not a great reason :) [1]: https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA#using_network_manager_to_change_regulatory_domains A more complete argument would be: it appears that, where possible, wifi region selection is handled automatically by interpreting information from the AP's beacon. However, that appears to be sparsely implemented (at best) and in the (extremely common) event that an AP *doesn't* advertise its region, it's up to the user to manage this themselves (where/when needed; as noted above, in 2.4GHz setups this usually doesn't matter that much). All the underlying pieces are in place for the user to do so. Nothing is lacking in wpa-supplicant regarding this (iwd does lack a direct option for the wifi region but it appears "use ieee80211_regdom or iw to override the automatic selection" is the answer there), so it's "simply" a matter of exposing this configuration via their preferred UI. Command line users already have the tools to do this (iw), although they notably lack a persistence mechanism for now. But GUI users have ... nothing. No means of querying, adjusting, or persisting this setting. Why NetworkManager? This setting could arguably go under "Language and Region". It is quite literally a region setting after all. And I'm still of the opinion that, at least initially, it should be set from the region selection during first-time setup. But consider the debugging scenario: I've travelled from the UK to Germany and, in the place I'm working, I'm having trouble with wifi connectivity or performance. What settings do I look at first? The wifi settings, almost certainly. If I were to see that my wifi region was "unset" or "UK" I'd likely adjust that to "DE" and see if that fixes things. To me at least, it does seem to make sense for this to go under the wifi settings (which are presumably the purview of NetworkManager?). -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967844] Re: firefox snap does not work with home directories outside of /home
*** This bug is a duplicate of bug 1776800 *** https://bugs.launchpad.net/bugs/1776800 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1967844 Title: firefox snap does not work with home directories outside of /home Status in firefox package in Ubuntu: Confirmed Bug description: Firefox version information below. I don't think replacing the deb version with the snap was a good idea. If your home directory is outside of /home (quite common for central home directories on a file server mounted via NFS or some other way for example) you cannot use Firefox in Ubuntu 22.04 anymore. $ firefox Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. This is a long standing issue and should have been addressed before replacing the deb with the snap version imho. --- $ snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/products/firefox license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable refresh-date: today at 10:17 CEST channels: latest/stable:98.0.2-12022-03-24 (1154) 162MB - latest/candidate: 99.0-2 2022-03-31 (1188) 163MB - latest/beta: 100.0b1-1 2022-04-05 (1200) 163MB - latest/edge: 100.0a1 2022-04-05 (1201) 179MB - esr/stable: 91.7.1esr-2 2022-03-14 (1116) 161MB - esr/candidate:91.8.0esr-1 2022-03-30 (1184) 161MB - esr/beta: ↑ esr/edge: ↑ installed: 98.0.2-1 (1154) 162MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
Gael Lafond, I confirm it worked for me too. Thank you so much for a simple solution to a perennial problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/960 Importance: Unknown Status: Unknown -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain
>> it's apparently never worked for me at home or at various friends >> houses, and only once worked when I travelled to Germany for a >> sprint. > is that having a visible impact for users? like was your computer > not able to connect to some access point? Personally, I've never encountered issues with WiFi on a Pi. However, firstly it's worth noting the vast majority of pis around my house are connected via ethernet and, secondly that my broadband connection typically hovers around 60-80Mbps, so the 54Mbps max bandwidth of 802.11g is "fast enough" that anything more wouldn't be noticed anyway. Notably, this also means I *don't* use bonded 5GHz channels in my home setup. The reason I mention this is that, over the last few years there's been a slow (but steady) drum-beat of complaints about WiFi on the Pi when using Ubuntu [1][2][3][4] (some of those are comments from the same bug, but it seems to be one that people land on when googling this for Ubuntu). [1]: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1851129/comments/1 [2]: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1862760/comments/11 [3]: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1862760/comments/29 [4]: https://bugs.launchpad.net/netplan/+bug/1908951 > if that's the consequence of the issue it is a bit surprising that > we got no user report of the type of 'my laptop isn't able to > connect to my AP anymore since the upgrade to the new LTS' no? or is > the issue somehow specific to raspi devices? The complaint usually isn't "I can't connect to my AP anymore". It's usually "my WiFi connection is slow" (which is obviously a much harder problem to debug and address) but this does appear to be a problem specific to the Pi. Mostly though, this comes up on IRC, and it's a safe bet that the person involved has a 5GHz setup, sometimes with bonded channels. Obviously bonded channel setups require more (typically adjacent) channels and this makes them particularly susceptible to poor performance when the region code hasn't been set (and the channels, or channel mitigations are limited). With pure 5GHz APs (no 2.4GHz channels at all) we've also had reports of no connectivity. One other (anecdotal) observation is that despite RaspiOS having a considerably larger installed base of Ubuntu on the Pi, WiFi issues rarely crop up there. Notably, RaspiOS prompts for a wifi regulatory region in its first time setup. There are several other differences, but under the covers we're using the same firmware, and wpa-supplicant is ultimately in charge of the WiFi connection on both OS'. Given 5GHz setups are only likely to become more common in future (802.11ac, which the Pi 3+ and 4 are compatible with, is notably 5GHz only [5]) my suspicion is this will only become more important in the coming years. [5]: https://en.wikipedia.org/wiki/IEEE_802.11ac-2013 -- 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/1951586 Title: Need option to specify wifi regulatory domain Status in cloud-init: Invalid Status in netplan: New Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Status in netplan.io source package in Jammy: Triaged Status in network-manager source package in Jammy: Incomplete Status in netplan.io source package in Kinetic: Triaged Status in network-manager source package in Kinetic: Incomplete Bug description: It would be nice if netplan offered an option to specify the wifi regulatory domain (country code). For devices such as the Raspberry Pi you are currently advertising that users can simply setup Ubuntu Server headless by putting the wifi configuration details in cloudinit/netplan's "network-config" on the FAT partition of the SD card: https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet But an option to set the wifi country code there does not seem to exist, so may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969602] Re: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
Sorry, didn't see the reply with the upstream link. It seems different to me, I haven't had any issues (that I've noticed) with invisible windows. I've attached a screen recording. In this, I have terminal in the foreground and alt-tab to settings. Because the mouse is outside the settings window (i.e., still over terminal), terminal gets pulled almost immediately to the front again. ** Attachment added: "video of the issue" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969602/+attachment/5594297/+files/Screencast%20from%2001-06-22%2012%3A19%3A59.webm -- 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/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1975578] Re: NetworkManager does not push search domains to systemd-resolved
** Changed in: network-manager (Ubuntu) Status: Incomplete => 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/1975578 Title: NetworkManager does not push search domains to systemd-resolved Status in network-manager package in Ubuntu: New Bug description: Search domains defined in a NetworkManager connection are not pushed to systemd-resolved. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian UBUNTU_CODENAME=jammy NetworkManager -V 1.36.4 resolvectl --version systemd 249 (249.11-0ubuntu3.1) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Details: DNS search domains can be set per NetworkManager connection. In my case it looks like this: nmcli con show MyConnection | grep ipv4.dns-search ipv4.dns-search: mydomain.at,org.mydomain.at,linux.mydomain.at Afaik NetworkManager should push them to systemd-resolved automatically. But this does not happen. The entries do not make it to /etc/resolv.conf. (If I do it manually with resolvectl, it works.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1975578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
Confirm #76 Works for me with enterprise Wifi. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: New Bug description: wpa built with in openssl3 fails to connect to TLS 1.1 or lower server those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
This issue also effects electronics hobbyist as I couldn't upload any code to my ESP32 controller because the port keeps disappearing. It is that after I found the dmesg message about the brltty, I have realized something was wrong. I was checking my hardware because of it. I breaks my ESP32 uploader as well as my FTDI adapter that I use for uploading codes to other circuits. The same issue occurs on connecting other tty devices such as an xbee coordinator we use in our servers at our company. I don't know how this could be fixed, but ubuntu 22.04 broke everything by including this package by default. It wasn't happening in 20.04. Thanks for your help. [ 7196.861667] usb 3-2: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 7196.864844] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 7214.115056] usb 3-2: cp210x converter now attached to ttyUSB0 [ 7223.376707] usb 3-2: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 7223.379955] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [10318.411400] usb 3-2: cp210x converter now attached to ttyUSB0 [10319.151002] usb 3-2: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [10319.156189] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [10361.791685] usb 3-2: cp210x converter now attached to ttyUSB0 [10372.120057] usb 3-2: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [10372.123222] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [10433.747532] usb 3-2: cp210x converter now attached to ttyUSB0 [10451.436173] usb 3-2: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [10451.445241] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Confirmed Status in brltty source package in Oneiric: Fix Released Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973733] Re: no change rebuild to get security update out on riscv64
Ah - is it that the same version is now built and published in Groovy and we can't safely copy the binary backwards? => correct. I didn't check if we can or cannot safely copy the binary backwards, but imho we should not. This is not going via focal-security, because the security issue has already been fixed on all other arches, and riscv64 currently has best effort security support. I don't want to trigger cups security upgrade for $everyone, just because of the fix missing on riscv64 only. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973733 Title: no change rebuild to get security update out on riscv64 Status in cups package in Ubuntu: Fix Released Status in cups source package in Focal: In Progress Bug description: no change rebuild to get riscv64 build out [Impact] * riscv64 build of cups security update failed, and then succeeded in groovy. See https://launchpad.net/ubuntu/+source/cups/2.3.1-9ubuntu1.1 * it means that focal-updates & focal-security are lacking a security update of cups on riscv64 * do a no change rebuild of cups as an SRU to get updated cups package out on focal [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * As usual, no change rebuilds of packages may introduce miss builds. [Other Info] * currently snap review tooling reports that cups has CVEs on riscv64 when one builds base:core20 snaps for riscv64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972034] Re: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box
Thank you for your bug report. In which software do you see the issue and which language and input method do you use? Trying in gedit or firefox, doing ctrl-S and then typing correctly edit the filename on my Ubuntu installations ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1972034 Title: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box Status in nautilus package in Ubuntu: Incomplete Bug description: This has bugged me for many years now, and figure as long as the kinks are being worked out on this bug: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971516 I should bring it up: When you download a file from a browser, the save dialog pops up, and the filename in the name box at the top is highlighted (just the name, not the extension), which is the universal symbol for "I'm highlighted, start typing and you'll overwrite me!" However, typing does nothing unless you click the box, at which point the cursor is in the middle of the name, and you have re-highlight if you want to rename the file. This is still confusing to me after many years. Expected behaviour: Either: Filename is highlighted and you can start typing to replace the name (but not the extension) Or: Filname is NOT highlighted by default, indicating you are not ready to edit. Since Ubuntu 20.04... possibly longer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1972034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971712] Re: Add support for Intel DG2
works fine on Dell hybrid with ADL iGPU and DG2 dGPU -- 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/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970783] Re: Multiple vulnerabilities in Bionic
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26700 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26709 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26717 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26716 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26719 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-30293 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-30294 ** Changed in: webkit2gtk (Ubuntu) Status: Confirmed => In Progress ** Changed in: webkit2gtk (Ubuntu) Assignee: (unassigned) => Luís Cunha dos Reis Infante da Câmara (luis220413) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1970783 Title: Multiple vulnerabilities in Bionic Status in webkit2gtk package in Ubuntu: In Progress Bug description: The version in Bionic has multiple vulnerabilities. Please backport version 2.36.0 or at least the security fixes in that version. Upstream and Debian have released advisories on April 8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1970783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971712] Re: Add support for Intel DG2
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1971712 Title: Add support for Intel DG2 Status in linux-oem-5.17 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: use a dkms provided by Intel and integrated in the OEM kernel source, the module will be shipped in a separate modules package [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964601] Re: I have no processor!
On the disk issue, there are some related discussion on https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/633 but basically gnome-control-center currently ignore removable devices because it shouldn't account for a connected usb stick or sdcard as system capacity one suggested heuristic tweak that could fix the raspi case is 'Use the size of the disk with a partition mounted at / only if there are no non- removable devices.' ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #633 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/633 -- 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/1964601 Title: I have no processor! Status in gnome-control-center package in Ubuntu: Confirmed Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964601] Re: I have no processor!
What's the output of /usr/libexec/gnome-control-center-print-renderer on the raspi? and $ G_MESSAGES_DEBUG=all gnome-control-center info-overview -- 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/1964601 Title: I have no processor! Status in gnome-control-center package in Ubuntu: Confirmed Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976433] Re: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Your title & package details match bionic/18.04 (ie. "chromium-browser | 101.0.4951.64-0ubuntu0.18.04.1 | bionic-security/universe | source, amd64, arm64, armhf, i386") but your release is shown as focal/20.04. Are you sure you wouldn't benefit from support? Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 I've marked this bug report 'incomplete'; if you believe I'm in error, please leave a comment saying why (or details as to your problem) and the status can be returned to 'new' Thank you! ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1976433 Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el código de salida de error 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: upgrading from comand line from 18.04 yo 20.08 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-180.189-generic 4.15.18 Uname: Linux 4.15.0-180-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-LVDS-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGr1wyAAAVAQOAGg54CpmFlVVWkigiUFQBAQEBAQEBAQEBAQEBAQEBEhtWWlAAGTAwIDYAAJAQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTE2WFcwMyBWMiAKAOY= modes: 1366x768 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Tue May 31 16:20:05 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-01-07 (144 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) InstalledPlugins: Load-Avg-1min: 1.01 Load-Processes-Running-Percent: 0.6% MachineType: Acer Aspire V5-121 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-180-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to focal on 2022-05-31 (0 days ago) dmi.bios.date: 04/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ZA10_BZ dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd04/16/2013:svnAcer:pnAspireV5-121:pvrV2.12:rvnAcer:rnZA10_BZ:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Aspire V5-121 dmi.product.version: V2.12 dmi.sys.vendor: Acer modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to:
[Desktop-packages] [Bug 1964601] Re: I have no processor!
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- 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/1964601 Title: I have no processor! Status in gnome-control-center package in Ubuntu: Confirmed Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969602] Re: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969602] Re: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
Could you report it upstream on https://gitlab.gnome.org/GNOME/nautilus/-/issues ? -- 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/1970921 Title: Drag and drop does not work Status in nautilus package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
> Do you use gpaste? I don't have gpaste package(s) installed. -- 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/1970921 Title: Drag and drop does not work Status in nautilus package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection
Thanks for the details. I'm unsure about your question, you might have a
better chance asking directly upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager ?
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
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/1975549
Title:
NetworkManager uses tethered Android phone as ethernet connection
instead of wired ethernet connection
Status in network-manager package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
trouble the last week or two ssh'sing into the machine, and printing
from the machine when I am sitting at the keyboard. I also could not
connect to my external firewall when sitting at the keyboard.
I keep a Google Pixel 4a tethered to the USB hub for charging. The
Android phone is running Android 12, and the phone is set to "USB
Tethering". The phone is fully patched, too.
I found if I reboot the machine with the phone tethered, then the
machine uses the Android phone as the ethernet connection. It
literally calls the connection "ethernet", as if it was using the
network adapter. This is new behavior over the last week or two.
This is unexpected behavior for three reasons. First, it is new
behavior. Second, the wired gigabit ethernet connection is not used by
default. And thrid, the Android phone's connection is called
"ethernet" instead of something more meaningful like "USB" or
"Android" or "wired hotspot".
The third item ("ethernet" name when using Android phone) was
misleading enough to waste a lot of time troubleshooting the issue. I
thought I had an odd firewall issue or a mDNS issue.
The reason I was having so many troubles, like printing and ssh, is
the Android phone uses Wifi and it is on a different VLAN and subnet
to keep traffic segregated from my trusted internal network.
-
It looks like I am running network-manager via systemd:
# service systemd-networkd status
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendor prese>
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: >
Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
Docs: man:NetworkManager(8)
Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
Memory: 12.0M
CGroup: /system.slice/NetworkManager.service
└─928 /usr/sbin/NetworkManager --no-daemon
...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (107 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via 172.16.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
Package: network-manager 1.22.10-1ubuntu2.3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-con:
NAME UUID TYPE TIMESTAMP
TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY
DBUS-PATH ACTIVE DEVICE STATE
ACTIVE-PATH SLAVE FILENAME
Ethernet 5d31ea14-c1cd-318f-a982-09ce6723dadb ethernet 1653403311 Tue 24
May 2022 10:41:51 AM EDT yes -100 no
/org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated
/org/freedesktop/NetworkManager/ActiveConnection/4 --
/etc/NetworkManager/system-connections/Ethernet.nmconnection
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
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-02-05 (108 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819.1)
IpRoute:
default via
[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1976204 Title: system freeze and gnome-shell reports multiple stack trace Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] System will be freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-17 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Package: gnome-shell 42.1-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
If I remove gnome-shell-extension-desktop-icons-ng, I can't reproduce this issue. Also I can't reproduce this issue under x-session. -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] System will be freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-17 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Package: gnome-shell 42.1-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
