[Desktop-packages] [Bug 1972914] Re: frequent 15-sec guest freeze with ubuntu 22.04 host and guest
Increasing video memory appears to have fixed my problem. My virtual screen size is 1920x1080 and in virt-manager's Video panel / XML tab, vgamem was set to the default value of 16384. After increasing it to 65536, I'm no longer seeing the freeze (though with only a few minutes of testing, so far). I don't know enough about this software to know if this means there is no flaw in QXL. If it does, then this bug report can be closed, although the freeze is a confusing failure mode. It would be nice if the overall user experience could be improved somehow. Perhaps the gnome Settings program's Displays panel could detect when a resolution is requested which exceeds available video memory and prevent it, preferably with a useful message to the user. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1972914 Title: frequent 15-sec guest freeze with ubuntu 22.04 host and guest Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: I'm running a new installation of Ubuntu 22.04 Desktop on a Thinkpad T450s (core i5-5200, 2 cores / 4 vCPUs, 12 GB memory). Using the virt- manager GUI, I performed what I believe is a simple, plain-vanilla installation of an Ubuntu 22.04 guest running under qemu/kvm with 2 vCPUs and 4 GB memory. I'm seeing very frequent, 15-second freezes of the guest. When it happens, the guest is completely unresponsive. After about 15 seconds, it works normally again, until the next freeze. The duration of the freeze appears to be the same every time. The guest isn't doing much - just open the calculator app and click number buttons. The freeze doesn't happen if I don't interact with the guest (just leave the system monitor running in the guest, so I can see that it's not frozen). I observe the freeze when I have 2 of the 4 vCPUs dedicated to the guest. I do NOT observe it when I have only one vCPU dedicated to the guest. Both the host and guest are using only a small fraction of the memory available to them. When the problem happens, the host indicates that CPU usage is very low across all vCPUs. The host appears to be operating normally when the guest is frozen. I see the following pair of lines in the guest syslog every time the freeze occurs (and only when the freeze occurs): May 10 13:48:40 qemu-jammy kernel: [ 144.259799] qxl :00:01.0: object_init failed for (8298496, 0x0001) May 10 13:48:40 qemu-jammy kernel: [ 144.259819] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO I don't see anything in the host syslog that correlates with the freeze. If I choose "Virtio" in the Video drop-down in the virt-manager GUI, with "3D acceleration" UNchecked, the guest works fine, and the freeze never happens. Unfortunately, that loses fractional scaling, which is important to me. If I check "3D acceleration," the guest won't boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1972914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972749] Re: Logging into a second Wayland session/user doesn't work [Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"]
The same failure is seen with a single user in: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5462 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5462 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5462 -- 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/1972749 Title: Logging into a second Wayland session/user doesn't work [Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix"] Status in mutter package in Ubuntu: New Bug description: On my system with Nvidia 510 drivers I found that if I'm logged in and lock the session another user can't login. I reset the 2nd user's account to verify that if I login and lock my session they can't login. I found this in permission error in the logs. May 09 21:58:20 x1 gnome-shell[17718]: Failed to start X Wayland: Wrong ownership for directory "/tmp/.X11-unix" I've confirmed that /tmp/.X11-unix is owned by the 1st user, so something seems to be causing the system to use the same tmp directory for both users. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-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..01.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.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed nvidia/510.60.02, 5.17.6, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] [1458:401a] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vg-root ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: PRIME H270-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/11/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH270-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1972749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801205] Re: Can't mount veracrypt volumes
Thanks Sebastien. That clarified the panorama. After the creation of the file (and a reboot) gnome-disks do see if there is a partition on any HD that has some resemblance to a veracrypt encryption and if the pass was saved under "seahorse" it opens it up automatically. Manually I get the same result (encrypted container files). Now the question is why this feature was added like a main upgrade if that involve on the creation of a obscure file? Anyways. Closing the thread. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1801205 Title: Can't mount veracrypt volumes Status in gnome-disk-utility package in Ubuntu: New Bug description: Using mount from nautilus (open with) or right from Gnome Disk, the file in question is "mounted" as a loop device. Therefore, no opening of that container nor questions about how to open the file. This is Ubuntu 18.10 from 18.04. Already tried 18.10 on a VM (Live session) and Gnome on Xorg & Wayland. Also tryed Tail in order to see the Veracrypt property working. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-disk-utility 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 1 18:35:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-08 (146 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to cosmic on 2018-10-30 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1801205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964560] Re: file transfers have trouble finishing
[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/1964560 Title: file transfers have trouble finishing Status in linux package in Ubuntu: Expired Status in nautilus package in Ubuntu: Expired Bug description: Ubuntu 21.10 with wayland windowing system sits on completed file transfers on and off usb and takes its time realising its finished and closing the little transfer progress logo. running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an HD 4600 onboard graphics card. It's either the linux system or old flash drives causing it. Don't think its the circuit boards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964560] Re: file transfers have trouble finishing
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (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/1964560 Title: file transfers have trouble finishing Status in linux package in Ubuntu: Expired Status in nautilus package in Ubuntu: Expired Bug description: Ubuntu 21.10 with wayland windowing system sits on completed file transfers on and off usb and takes its time realising its finished and closing the little transfer progress logo. running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an HD 4600 onboard graphics card. It's either the linux system or old flash drives causing it. Don't think its the circuit boards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
** Changed in: kbd-chooser Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: Fix Released Status in console-setup package in Ubuntu: New Status in kbd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login
** Description changed: - If I disable sharing/remote desktop in GNOME Control Center, then log - out and back in, it is automatically enabled again. I report this as a - security vulnerability because remote desktop is enabled without the - user's knowledge. + Details: + Turning off RDP Remote Desktop Sharing with gnome-control-center would only turn off RDP sharing for the current session. Upon logging back in, RDP Sharing would be enabled again without any additional user interaction or notification. + + Other Info: + As mentioned in the comments at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1825 + this issue could have been avoided if Ubuntu's gnome-remote-desktop didn't keep the systemd user service always running. I do intend to fix that issue also but it is a more complicated fix. I think it will require a maintainer script to remove the automatic conffiles added by dh. I will do the gnome-remote-desktop bugfix as a normal non-security SRU. + + Original Bug Report: + If I disable sharing/remote desktop in GNOME Control Center, then log out and back in, it is automatically enabled again. I report this as a security vulnerability because remote desktop is enabled without the user's knowledge. Software versions: - Ubuntu 22.04 - gnome-remote-desktop 42.0-4ubuntu1 - gnome-control-center 1:41.4-1ubuntu13 Steps to reproduce: 1. Start with Remote Desktop enabled. "systemctl --user status gnome-remote-desktop.service" reports "active (running)". 2. Disable Remote Desktop in Control Center. systemctl reports "inactive (dead)". 3. Log out and back in. 4. Open Control Center. Remote Desktop is enabled again. systemctl reports "active (running)". Expected behavior: Remote Desktop should stay disabled upon the new login. Actual behavior: Remote Desktop was automatically enabled again. Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1775#note_1443319 -- 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/1971415 Title: Remote desktop is automatically enabled after login Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Jammy: Confirmed Bug description: Details: Turning off RDP Remote Desktop Sharing with gnome-control-center would only turn off RDP sharing for the current session. Upon logging back in, RDP Sharing would be enabled again without any additional user interaction or notification. Other Info: As mentioned in the comments at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1825 this issue could have been avoided if Ubuntu's gnome-remote-desktop didn't keep the systemd user service always running. I do intend to fix that issue also but it is a more complicated fix. I think it will require a maintainer script to remove the automatic conffiles added by dh. I will do the gnome-remote-desktop bugfix as a normal non-security SRU. Original Bug Report: If I disable sharing/remote desktop in GNOME Control Center, then log out and back in, it is automatically enabled again. I report this as a security vulnerability because remote desktop is enabled without the user's knowledge. Software versions: - Ubuntu 22.04 - gnome-remote-desktop 42.0-4ubuntu1 - gnome-control-center 1:41.4-1ubuntu13 Steps to reproduce: 1. Start with Remote Desktop enabled. "systemctl --user status gnome-remote-desktop.service" reports "active (running)". 2. Disable Remote Desktop in Control Center. systemctl reports "inactive (dead)". 3. Log out and back in. 4. Open Control Center. Remote Desktop is enabled again. systemctl reports "active (running)". Expected behavior: Remote Desktop should stay disabled upon the new login. Actual behavior: Remote Desktop was automatically enabled again. Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1775#note_1443319 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login
** Patch added: "gnome-control-center-lp1971415.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+attachment/5588335/+files/gnome-control-center-lp1971415.debdiff -- 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/1971415 Title: Remote desktop is automatically enabled after login Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Jammy: Confirmed Bug description: Details: Turning off RDP Remote Desktop Sharing with gnome-control-center would only turn off RDP sharing for the current session. Upon logging back in, RDP Sharing would be enabled again without any additional user interaction or notification. Other Info: As mentioned in the comments at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1825 this issue could have been avoided if Ubuntu's gnome-remote-desktop didn't keep the systemd user service always running. I do intend to fix that issue also but it is a more complicated fix. I think it will require a maintainer script to remove the automatic conffiles added by dh. I will do the gnome-remote-desktop bugfix as a normal non-security SRU. Original Bug Report: If I disable sharing/remote desktop in GNOME Control Center, then log out and back in, it is automatically enabled again. I report this as a security vulnerability because remote desktop is enabled without the user's knowledge. Software versions: - Ubuntu 22.04 - gnome-remote-desktop 42.0-4ubuntu1 - gnome-control-center 1:41.4-1ubuntu13 Steps to reproduce: 1. Start with Remote Desktop enabled. "systemctl --user status gnome-remote-desktop.service" reports "active (running)". 2. Disable Remote Desktop in Control Center. systemctl reports "inactive (dead)". 3. Log out and back in. 4. Open Control Center. Remote Desktop is enabled again. systemctl reports "active (running)". Expected behavior: Remote Desktop should stay disabled upon the new login. Actual behavior: Remote Desktop was automatically enabled again. Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1775#note_1443319 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Hi, would you please share:
1. lspci -nvk
2. /var/log/gpu-manager.log
3. journalctl -b -k
4. dpkg -l | grep nvidia
5. lsmod | grep nvidia
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
[1]
[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login
** Also affects: gnome-control-center (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-control-center (Ubuntu Jammy) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu Jammy) Status: New => 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/1971415 Title: Remote desktop is automatically enabled after login Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Jammy: Confirmed Bug description: If I disable sharing/remote desktop in GNOME Control Center, then log out and back in, it is automatically enabled again. I report this as a security vulnerability because remote desktop is enabled without the user's knowledge. Software versions: - Ubuntu 22.04 - gnome-remote-desktop 42.0-4ubuntu1 - gnome-control-center 1:41.4-1ubuntu13 Steps to reproduce: 1. Start with Remote Desktop enabled. "systemctl --user status gnome-remote-desktop.service" reports "active (running)". 2. Disable Remote Desktop in Control Center. systemctl reports "inactive (dead)". 3. Log out and back in. 4. Open Control Center. Remote Desktop is enabled again. systemctl reports "active (running)". Expected behavior: Remote Desktop should stay disabled upon the new login. Actual behavior: Remote Desktop was automatically enabled again. Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1775#note_1443319 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972831] Re: pulseaudio-module-bluetooth is not installed after upgrade to jammy
Yes it sounds like the cause was the PPA: https://launchpad.net/~berglh/+archive/ubuntu/pulseaudio-a2dp pulseaudio-module-bluetooth is in fact installed by default in jammy and in focal. ** Summary changed: - Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3 + pulseaudio-module-bluetooth is not installed after upgrade to jammy ** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1972831 Title: pulseaudio-module-bluetooth is not installed after upgrade to jammy Status in pulseaudio package in Ubuntu: Invalid Bug description: I think that the issue might be partly because I have pulseaudio-bt- modules package with alternative codecs I removed tht package but still same issue lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53 lut 07 22:14:40 graf systemd[1]: Started Bluetooth service. lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 initialized lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/LDAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/SBC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/SBC lut 08 08:37:50 graf bluetoothd[1366]: Terminating ...skipping... maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:51:49 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:52:59 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:54:08 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:55:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:56:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:57:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:58:45 graf bluetoothd[1293]:
[Desktop-packages] [Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
Thanks for the bug report. Firstly please try disabling any extensions you might have installed. Please also run: cd ~/.local/share/gnome-shell rm -rf extensions and log in again. If the bug still happens then please check for crashes of the gnome- shell process by following these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment I expect a crash of gnome-shell is the most likely explanation and will result in it restarting. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972812 Title: The operating system does not ask for a password after unlocking the screen. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I found a security vulnerability in Ubuntu 22.04 LTS operating system (Laptops only) It is reproduced like this (in steps): 1. I lock the screen Win + L 2. Close the laptop lid 3. Then I open the lid of the laptop 4. I get a vulnerability, the operating system does not ask for a password, but immediately shows the desktop without the need to unlock it. that is, closing and opening the laptop lid leads to unlocking the screen without asking for a password. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 12:20:28 2022 InstallationDate: Installed on 2022-04-21 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971221] Re: [nvidia] firefox is flashing
** Changed in: firefox (Ubuntu) Status: Confirmed => New -- 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/1971221 Title: [nvidia] firefox is flashing Status in firefox package in Ubuntu: New Bug description: when firefox window behind other APP windows, it is flashing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-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..01.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.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 11:53:34 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP104 [GeForce GTX 1080] [103c:82fb] InstallationDate: Installed on 2022-05-01 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=ff0f1b3b-e57d-46bf-817b-a2bf7bd47098 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2022 dmi.bios.release: 14.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z690-A GAMING WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd04/01/2022:br14.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-AGAMINGWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
Given the specific circumstances required to hit this bug I think it's now just medium, not high. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: High => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: New => Triaged ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: Currently testing a fresh install of the beta for 22.04. All packages are up to date. When having the dock auto-hide option enabled, a glitch occurs when opening the windows selector (when multiple instances of the same program are opened). The selector does open, but the dock will hide itself immediately instead of waiting for a selection. Selecting a window will then cause a glitch where the selector will align with the hidden dock in a non natural way before disappearing. A proposed fix would be to prevent the dock from auto-hiding when the miniatures selector opens and wait for a second input. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971010] Re: [vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in VirtualBox when paravirtualization is enabled
> Looks like with the latest update the problem is solved. What packages got updated? Certainly not gnome-shell, mutter or mesa. ** No longer affects: mutter (Ubuntu) ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: mesa (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1971010 Title: [vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in VirtualBox when paravirtualization is enabled Status in linux package in Ubuntu: Incomplete Bug description: Screen and mouse doesn't work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 30 09:35:20 2022 DistUpgraded: 2022-04-29 07:32:33,356 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2021-11-09 (171 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=fdb10ec1-b027-47b9-bcc7-9dc7ae1897d8 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (1 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972889] Re: Screen reader reads the data while computer is locked
** Tags added: jammy -- 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/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: New Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972921] Re: Simple-scan does not adhere to the globally set scheme
Attached is the settings window, which is clearly dark and calls for dark theme. ** Attachment added: "Settings-Dark.png" https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1972921/+attachment/5588333/+files/Settings-Dark.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1972921 Title: Simple-scan does not adhere to the globally set scheme Status in simple-scan package in Ubuntu: New Bug description: In Xubuntu 22.04, upgraded from 21.10: I have my appearance set to dark for many reasons. Most apps adhere to these settings, but simple-scan always comes up with a light colored background instead of dark. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1972921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972921] [NEW] Simple-scan does not adhere to the globally set scheme
Public bug reported: In Xubuntu 22.04, upgraded from 21.10: I have my appearance set to dark for many reasons. Most apps adhere to these settings, but simple-scan always comes up with a light colored background instead of dark. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Attachment added: "SimpleScan-Light.png" https://bugs.launchpad.net/bugs/1972921/+attachment/5588332/+files/SimpleScan-Light.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1972921 Title: Simple-scan does not adhere to the globally set scheme Status in simple-scan package in Ubuntu: New Bug description: In Xubuntu 22.04, upgraded from 21.10: I have my appearance set to dark for many reasons. Most apps adhere to these settings, but simple-scan always comes up with a light colored background instead of dark. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1972921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972914] [NEW] frequent 15-sec guest freeze with ubuntu 22.04 host and guest
Public bug reported: I'm running a new installation of Ubuntu 22.04 Desktop on a Thinkpad T450s (core i5-5200, 2 cores / 4 vCPUs, 12 GB memory). Using the virt- manager GUI, I performed what I believe is a simple, plain-vanilla installation of an Ubuntu 22.04 guest running under qemu/kvm with 2 vCPUs and 4 GB memory. I'm seeing very frequent, 15-second freezes of the guest. When it happens, the guest is completely unresponsive. After about 15 seconds, it works normally again, until the next freeze. The duration of the freeze appears to be the same every time. The guest isn't doing much - just open the calculator app and click number buttons. The freeze doesn't happen if I don't interact with the guest (just leave the system monitor running in the guest, so I can see that it's not frozen). I observe the freeze when I have 2 of the 4 vCPUs dedicated to the guest. I do NOT observe it when I have only one vCPU dedicated to the guest. Both the host and guest are using only a small fraction of the memory available to them. When the problem happens, the host indicates that CPU usage is very low across all vCPUs. The host appears to be operating normally when the guest is frozen. I see the following pair of lines in the guest syslog every time the freeze occurs (and only when the freeze occurs): May 10 13:48:40 qemu-jammy kernel: [ 144.259799] qxl :00:01.0: object_init failed for (8298496, 0x0001) May 10 13:48:40 qemu-jammy kernel: [ 144.259819] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO I don't see anything in the host syslog that correlates with the freeze. If I choose "Virtio" in the Video drop-down in the virt-manager GUI, with "3D acceleration" UNchecked, the guest works fine, and the freeze never happens. Unfortunately, that loses fractional scaling, which is important to me. If I check "3D acceleration," the guest won't boot. ** Affects: xserver-xorg-video-qxl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1972914 Title: frequent 15-sec guest freeze with ubuntu 22.04 host and guest Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: I'm running a new installation of Ubuntu 22.04 Desktop on a Thinkpad T450s (core i5-5200, 2 cores / 4 vCPUs, 12 GB memory). Using the virt- manager GUI, I performed what I believe is a simple, plain-vanilla installation of an Ubuntu 22.04 guest running under qemu/kvm with 2 vCPUs and 4 GB memory. I'm seeing very frequent, 15-second freezes of the guest. When it happens, the guest is completely unresponsive. After about 15 seconds, it works normally again, until the next freeze. The duration of the freeze appears to be the same every time. The guest isn't doing much - just open the calculator app and click number buttons. The freeze doesn't happen if I don't interact with the guest (just leave the system monitor running in the guest, so I can see that it's not frozen). I observe the freeze when I have 2 of the 4 vCPUs dedicated to the guest. I do NOT observe it when I have only one vCPU dedicated to the guest. Both the host and guest are using only a small fraction of the memory available to them. When the problem happens, the host indicates that CPU usage is very low across all vCPUs. The host appears to be operating normally when the guest is frozen. I see the following pair of lines in the guest syslog every time the freeze occurs (and only when the freeze occurs): May 10 13:48:40 qemu-jammy kernel: [ 144.259799] qxl :00:01.0: object_init failed for (8298496, 0x0001) May 10 13:48:40 qemu-jammy kernel: [ 144.259819] [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO I don't see anything in the host syslog that correlates with the freeze. If I choose "Virtio" in the Video drop-down in the virt-manager GUI, with "3D acceleration" UNchecked, the guest works fine, and the freeze never happens. Unfortunately, that loses fractional scaling, which is important to me. If I check "3D acceleration," the guest won't boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1972914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970244] Re: [SRU] Enable support for Zed Cloud Archive
This bug was fixed in the package software-properties - 0.99.22.1 --- software-properties (0.99.22.1) jammy; urgency=medium * cloudarchive: Enable support for the Zed Ubuntu Cloud Archive on 22.04 (LP: #1970244). -- Corey Bryant Fri, 29 Apr 2022 13:57:51 -0400 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1970244 Title: [SRU] Enable support for Zed Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: Please add support for: cloud-archive:zed cloud-archive:zed-proposed This will also need to be SRU'd back to jammy. [Impact] End users have to manually enable the zed cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:zed sudo add-apt-repository cloud-archive:zed-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972889] Re: Screen reader reads the data while computer is locked
Good job Loaf :3 ** Information type changed from Private Security to Public Security -- 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/1972889 Title: Screen reader reads the data while computer is locked Status in gnome-shell package in Ubuntu: New Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu is installed on a laptop. Within five minutes of inactivity, the screen lock activates and locks the system. Computer is secured. 10 minutes later, my cat (her name is Loaf) comes up to the laptop and sits down on the keyboard. This activates a screen reader. (Shortcut is Alt + Super + S) What I've expected: Screen reader would start reading the contents of a lock screen What happened: Screen reader app started reading contents of a Brave Browser window that was opened on my desktop. It read all tabs and proceeded reading the opened web page. I've reported this bug at secur...@ubuntu.org and got the following answer: > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too > - I suspect this is a vulnerability in gnome-shell as it is > responsible for handling the lock screen in standard Ubuntu. As per further directions, I'm posting this bug here and in gnome repo. P.S. I expect Loaf being credited for this find. She really likes treats. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970658] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted zenity into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zenity/3.42.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1970658 Title: Update zenity to 3.42.1 Status in zenity package in Ubuntu: Fix Released Status in zenity source package in Jammy: Fix Committed Bug description: Impact -- New stable release in the 3.42 series. https://gitlab.gnome.org/GNOME/zenity/-/blob/3.42.1/NEWS Test Case - zenity --info --text="1234566789 223456789 323456789 423456789 523456789 623456789 723456789 823456789 923456789" Should wrap the dialog onto 2 lines, instead of one line for each set of numbers. What Could Go Wrong --- This is part of core GNOME so it falls under the microrelease exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1970658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970658] Re: Update zenity to 3.42.1
Okay, it'd be real nice if we could wrap up the GNOME MRE discourse post and have a solid list of packages to which we can all refer. ** Changed in: zenity (Ubuntu Jammy) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1970658 Title: Update zenity to 3.42.1 Status in zenity package in Ubuntu: Fix Released Status in zenity source package in Jammy: Fix Committed Bug description: Impact -- New stable release in the 3.42 series. https://gitlab.gnome.org/GNOME/zenity/-/blob/3.42.1/NEWS Test Case - zenity --info --text="1234566789 223456789 323456789 423456789 523456789 623456789 723456789 823456789 923456789" Should wrap the dialog onto 2 lines, instead of one line for each set of numbers. What Could Go Wrong --- This is part of core GNOME so it falls under the microrelease exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1970658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959345] Re: vulkaninfo reports error
All the same, perhaps vulkaninfo should issue a warning about vestigial config if it can find a perfectly usable icd somewhere else! Presumably it looks for the one supplied by Ubuntu. -- 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/1959345 Title: vulkaninfo reports error Status in mesa package in Ubuntu: Invalid Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
@georgiag we could move the abstraction include to "include if exists" to take care of the depends. Generally speaking evince shouldn't depend on apparmor, but of course make use of it if it is available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in apparmor source package in Jammy: New Status in evince source package in Jammy: New Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
@Sebastien, yes, I asked people from the security team to sponsor it but we are still reviewing the snap_browsers abstraction. We are denying access to /run/user/[0-9]*/gdm/Xauthority in the policy but if that was the case, then the browser should not have been able to open, but it does open so we are investigating if there's an issue. Regarding the evince debdiff, even though it looks like the dependency is on Build-Depends on the debdiff, it is actually under Depends. If we don't set this dependency, then the snap_browsers abstraction might not be available. So if the new evince is installed with an old apparmor, then the evince apparmor policy will fail to load and evince will run unconfined. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in apparmor source package in Jammy: New Status in evince source package in Jammy: New Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04
https://www.kernel.org/doc/Documentation/Intel-IOMMU.txt If you encounter issues with graphics devices, you can try adding option intel_iommu=igfx_off to turn off the integrated graphics engine. If this fixes anything, please ensure you file a bug reporting the problem. So the underlying issue is not fixed. On my system audio (and any video playing) stops when changing audio to integrated hdmi output, i7-4790s haswell cpu with ubuntu 22.04. -- 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/1970050 Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: After upgrading today from 20.04 LTS to 22.04 HDMI Audio does not work at all. Audio from speakers from a headphone jack works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 21:13:23 2022 InstallationDate: Installed on 2020-04-24 (729 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH97M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97M-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972897] [NEW] redirect seen as error
Public bug reported: NOTE: this bug report is for the package iputils-ping, but the website did not let me enter that: $ dpkg-query -S /bin/ping iputils-ping: /bin/ping $ dpkg-query -l iputils-ping Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== ii iputils-ping 3:20211215-1 amd64Tools to test the reachability of network hosts $ This is on 22.04 (Jammy Jellyfish), but the bug is also present in 20.04 (Focal Fossa) The deadline option is documented to exit on receiving an ICMP error: -w deadline Specify a timeout, in seconds, before ping exits regardless of how many packets have been sent or received. In this case ping does not stop after count packet are sent, it waits either for deadline expire or until count probes are answered or for some error notification from network. However, it exits too when a redirect is received, which is not an error. This make it useless for liveness probes when a redirect occurs. $ ping -w 2 strange.soleus.nu PING strange.soleus.nu (94.142.246.148) 56(84) bytes of data. >From hv02.rtij.nl (10.0.2.4) icmp_seq=1 Redirect Host(New nexthop: lte.rtij.nl >(10.0.0.137)) --- strange.soleus.nu ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms $ Note that the -c option suffers from the same problem. This does not happen in 18.04 (Bionic Beaver), which shows the expected behaviour: martijn@popeye:~$ ping -w 2 strange.soleus.nu PING strange.soleus.nu (94.142.246.148) 56(84) bytes of data. >From hv02.rtij.nl (10.0.2.4): icmp_seq=1 Redirect Host(New nexthop: >lte.rtij.nl (10.0.0.137)) 64 bytes from strange.soleus.nu (94.142.246.148): icmp_seq=1 ttl=53 time=47.9 ms --- strange.soleus.nu ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 47.908/47.908/47.908/0.000 ms martijn@popeye:~$ grep VERSION /etc/os-release VERSION="18.04.6 LTS (Bionic Beaver)" VERSION_ID="18.04" VERSION_CODENAME=bionic martijn@popeye:~$ dpkg-query -S /bin/ping iputils-ping: /bin/ping martijn@popeye:~$ ** Affects: iputils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1972897 Title: redirect seen as error Status in iputils package in Ubuntu: New Bug description: NOTE: this bug report is for the package iputils-ping, but the website did not let me enter that: $ dpkg-query -S /bin/ping iputils-ping: /bin/ping $ dpkg-query -l iputils-ping Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== ii iputils-ping 3:20211215-1 amd64Tools to test the reachability of network hosts $ This is on 22.04 (Jammy Jellyfish), but the bug is also present in 20.04 (Focal Fossa) The deadline option is documented to exit on receiving an ICMP error: -w deadline Specify a timeout, in seconds, before ping exits regardless of how many packets have been sent or received. In this case ping does not stop after count packet are sent, it waits either for deadline expire or until count probes are answered or for some error notification from network. However, it exits too when a redirect is received, which is not an error. This make it useless for liveness probes when a redirect occurs. $ ping -w 2 strange.soleus.nu PING strange.soleus.nu (94.142.246.148) 56(84) bytes of data. From hv02.rtij.nl (10.0.2.4) icmp_seq=1 Redirect Host(New nexthop: lte.rtij.nl (10.0.0.137)) --- strange.soleus.nu ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms $ Note that the -c option suffers from the same problem. This does not happen in 18.04 (Bionic Beaver), which shows the expected behaviour: martijn@popeye:~$ ping -w 2 strange.soleus.nu PING strange.soleus.nu (94.142.246.148) 56(84) bytes of data. From hv02.rtij.nl (10.0.2.4): icmp_seq=1 Redirect Host(New nexthop: lte.rtij.nl (10.0.0.137)) 64 bytes from strange.soleus.nu (94.142.246.148): icmp_seq=1 ttl=53 time=47.9 ms --- strange.soleus.nu ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 47.908/47.908/47.908/0.000 ms martijn@popeye:~$ grep VERSION /etc/os-release VERSION="18.04.6 LTS (Bionic Beaver)"
[Desktop-packages] [Bug 1639372] Re: CVE-2016-9082: DOS attack in converting SVG to PNG
Fixed in xenial 1.14.6-1ubuntu0.1~esm1: https://ubuntu.com/security/notices/USN-5407-1 ** Changed in: cairo (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1639372 Title: CVE-2016-9082: DOS attack in converting SVG to PNG Status in cairo: Unknown Status in cairo package in Ubuntu: Fix Released Status in cairo source package in Precise: Won't Fix Status in cairo source package in Trusty: Confirmed Status in cairo source package in Xenial: Fix Released Status in cairo source package in Yakkety: Confirmed Status in cairo package in Debian: Fix Released Bug description: I'm attaching debdiffs for trusty, xenial and yakkety. Zesty is already fixed by syncing cairo 1.14.6-1.1 from Debian. Maybe someone else can work on the precise update. Proof of Concept at http://seclists.org/oss-sec/2016/q4/44 I didn't get gdb to work, but when I tried to convert the file, I got a crash report named /var/crash/_usr_bin_rsvg-convert.1000.crash . After the update, no crash happened. I reproduced the crash and verified that the new package doesn't crash on yakkety. In xenial I wasn't able to reproduce the crash. I did not test on trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1639372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969220] Re: Pinch to zoom not working on Wayland on Jammy
Thanks ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1766042 Importance: Unknown Status: Unknown ** Changed in: firefox (Ubuntu) Importance: Undecided => Low ** Changed in: firefox (Ubuntu) Status: Confirmed => Triaged -- 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/1969220 Title: Pinch to zoom not working on Wayland on Jammy Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Triaged Bug description: Firefox running within snap confinement is unable to use the pinch to zoom gesture on 22.04. This is a regression as it does work on 21.10. I had been following https://bugs.launchpad.net/bugs/1964541 as it was suspected that these two issues were linked, however I am using the updated mutter released as a fix for the drag and drop bug but this didn't result in a fix for pinch to zoom. Pinch to zoom does work when using Firefox from the official tarball with the variable MOZ_ENABLE_WAYLAND=1 set. Originally reported on the snapcraft forum:https://forum.snapcraft.io/t/firefox-pinch-to-zoom-not-working- on-22-04/29391 Screen recording attached showing pinch to zoom not working on snap firefox and comparing with the gesture working on mozilla tarball firefox with libinput debug-gui showing the pinch gesture Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 $ 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/beta refresh-date: 2 days ago, at 18:06 BST channels: latest/stable:99.0.1-12022-04-13 (1232) 163MB - latest/candidate: 99.0.1-12022-04-12 (1232) 163MB - latest/beta: 100.0b6-1 2022-04-15 (1244) 163MB - latest/edge: 101.0a1 2022-04-15 (1243) 180MB - esr/stable: 91.8.0esr-1 2022-04-05 (1184) 161MB - esr/candidate:91.8.0esr-1 2022-03-30 (1184) 161MB - esr/beta: ↑ esr/edge: ↑ installed: 100.0b5-1 (1236) 163MB - mutter: Installed: (none) Candidate: 42.0-3ubuntu2 Version table: 42.0-3ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1969220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961854] Re: Thunderbid saves accepted calendar events in different identity
** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1961854 Title: Thunderbid saves accepted calendar events in different identity Status in thunderbird package in Ubuntu: Incomplete Bug description: When user have configured e.g: 1. One self hosted e-mail 2. One GMail account 3. One Microsoft Office360 account with calendar When he will accept calendar event in 1 or 2 and the only available calendar (from Thunderbird perspective) is 3, clicking the bluebar over e-mail to add calendar entry will save it in wrong identity(the 3). As identities are also boundaries for control -this should be considered privacy threat. E.g one can have private and business e-mail accounts in one Thunderbird where business ones could be inspected manually of automatically . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1961854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972856] Re: Cannot add printer
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1972856 Title: Cannot add printer Status in gnome-control-center package in Ubuntu: New Bug description: When I try to add a HP OfficeJet the system cannot find drivers, it shows an error. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 15:25:16 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (49 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967539] Re: All file downloads fail
you could do $ journalctl -f then trigger the issue and copy the log displayed in that section -- 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/1967539 Title: All file downloads fail Status in firefox package in Ubuntu: New Bug description: Moving to the snap version results in all file download failing. Message is just "failed". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 5.16.0-18.2-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 1 15:56:13 2022 InstallationDate: Installed on 2017-12-06 (1577 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2021-12-08 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969593] Re: rules to prevent non-root users from rebooting not taken into account
I'm setting the status of this bug as "incomplete". Please let us know if that solved the problem for you or not. Thanks! ** Changed in: policykit-1 (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1969593 Title: rules to prevent non-root users from rebooting not taken into account Status in policykit-1 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: On fresh Ubuntu Jammy installation, I add a "/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the following contents : [Disable power-off] Identity=unix-user:* Action=org.freedesktop.login1.power-off ResultActive=no ResultInactive=no ResultAny=no [Disable power-off when others are logged in] Identity=unix-user:* Action=org.freedesktop.login1.power-off-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot] Identity=unix-user:* Action=org.freedesktop.login1.reboot ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot_when_others_are_logged_in] Identity=unix-user:* Action=org.freedesktop.login1.reboot-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no It must prevent non-root users from shutdowning and rebooting the system. But it only prevent shutdowning. Rebooting is still possible for a non-root user. We can see it using pkcheck command (as a non-root user) : $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo $? Not authorized. 1 $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $? 0 As this problem can lead to unexpected reboot on multi-users systems (a disponibilty concern), I checked the "This bug is a security vulnerability" box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 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 10:53:27 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969593] Re: rules to prevent non-root users from rebooting not taken into account
Systemd has a bunch of "imply" rules on other actionstry adding the following: [Disable more reboot actions] Identity=unix-user:* Action=org.freedesktop.login1.reboot-ignore-inhibit;org.freedesktop.login1.set-reboot-* ResultActive=no ResultInactive=no ResultAny=no -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1969593 Title: rules to prevent non-root users from rebooting not taken into account Status in policykit-1 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: On fresh Ubuntu Jammy installation, I add a "/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the following contents : [Disable power-off] Identity=unix-user:* Action=org.freedesktop.login1.power-off ResultActive=no ResultInactive=no ResultAny=no [Disable power-off when others are logged in] Identity=unix-user:* Action=org.freedesktop.login1.power-off-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot] Identity=unix-user:* Action=org.freedesktop.login1.reboot ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot_when_others_are_logged_in] Identity=unix-user:* Action=org.freedesktop.login1.reboot-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no It must prevent non-root users from shutdowning and rebooting the system. But it only prevent shutdowning. Rebooting is still possible for a non-root user. We can see it using pkcheck command (as a non-root user) : $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo $? Not authorized. 1 $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $? 0 As this problem can lead to unexpected reboot on multi-users systems (a disponibilty concern), I checked the "This bug is a security vulnerability" box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 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 10:53:27 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login
I'm reassigning to gnome-control-center. Still doing further investigating. ** Package changed: gnome-remote-desktop (Ubuntu) => gnome-control- center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged -- 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/1971415 Title: Remote desktop is automatically enabled after login Status in gnome-control-center package in Ubuntu: Triaged Bug description: If I disable sharing/remote desktop in GNOME Control Center, then log out and back in, it is automatically enabled again. I report this as a security vulnerability because remote desktop is enabled without the user's knowledge. Software versions: - Ubuntu 22.04 - gnome-remote-desktop 42.0-4ubuntu1 - gnome-control-center 1:41.4-1ubuntu13 Steps to reproduce: 1. Start with Remote Desktop enabled. "systemctl --user status gnome-remote-desktop.service" reports "active (running)". 2. Disable Remote Desktop in Control Center. systemctl reports "inactive (dead)". 3. Log out and back in. 4. Open Control Center. Remote Desktop is enabled again. systemctl reports "active (running)". Expected behavior: Remote Desktop should stay disabled upon the new login. Actual behavior: Remote Desktop was automatically enabled again. Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1775#note_1443319 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961854] Re: Thunderbid saves accepted calendar events in different identity
Hi Bartłomiej, was this issue reported to mozilla? Do you have a bug report there? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1961854 Title: Thunderbid saves accepted calendar events in different identity Status in thunderbird package in Ubuntu: New Bug description: When user have configured e.g: 1. One self hosted e-mail 2. One GMail account 3. One Microsoft Office360 account with calendar When he will accept calendar event in 1 or 2 and the only available calendar (from Thunderbird perspective) is 3, clicking the bluebar over e-mail to add calendar entry will save it in wrong identity(the 3). As identities are also boundaries for control -this should be considered privacy threat. E.g one can have private and business e-mail accounts in one Thunderbird where business ones could be inspected manually of automatically . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1961854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967626] Re: 22.04 beta Network Manager still sets wrong IPv6 routing
Given that this issue is public in the freedesktop gitlab instance, I'm making this issue public here as well. ** Information type changed from Private Security to Public Security -- 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/1967626 Title: 22.04 beta Network Manager still sets wrong IPv6 routing Status in network-manager package in Ubuntu: New Bug description: Hi, that's a bug I've already reported earlier both to ubuntu and network- manager upstream, and nobody seems to care about. I'm using an AVM FritzBox, a router family very common in Germany and Europe for DSL and DOCSIS, but saw reports of people confirming the problem with other routers. The router sends ICMPv6 router advertisements, which contain for both the configured site-local address and the provider-assigned world- routable address range both a * prefix information * router advertisement on itself All other OS and machines I have, including * Debian * Ubuntu Server * Ubuntu Core * Raspberry Pi OS * Other Linuxes * MacOS *... correctly set a link route on the network device for both the official and the site local address. Only Ubuntu Desktop machines with that damned Network Manager set a route to the router instead of a link route. The consequence is, that IPv6 still works, but significantly to slow, since packages are not switched on the network switch, but routed on the router, which dramatically decreases speed. I've reported this upstream to Network Manager, see the discussion on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/840 but they do not even seem to understand the issue (Network Manager written by people not really understanding routing...) Their point of view is that the router will fix things by sending redirects. However, ICMPv6 redirects are considered a security problem and usually recommended to be turned off. The answer from NetworkManager developers is to fix the router, not the Network Manager to stop sending router advertisings, but can't explain why all other OS and other Linux distributions, including Ubuntu server and Ubuntu core do it correctly, and just NM doing it wrong. So Ubuntu/NetworkManagers unability to fix or even notice this essential problem forces people to either accept terribly slow IPv6 traffic in local networks, or to leave the machine open for ICMPv6 redirects, which, in general, is a security flaw and vulnerable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1967626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971415] Re: Remote desktop is automatically enabled after login
Jeremy, is there any progress on this? -- 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/1971415 Title: Remote desktop is automatically enabled after login Status in gnome-remote-desktop package in Ubuntu: New Bug description: If I disable sharing/remote desktop in GNOME Control Center, then log out and back in, it is automatically enabled again. I report this as a security vulnerability because remote desktop is enabled without the user's knowledge. Software versions: - Ubuntu 22.04 - gnome-remote-desktop 42.0-4ubuntu1 - gnome-control-center 1:41.4-1ubuntu13 Steps to reproduce: 1. Start with Remote Desktop enabled. "systemctl --user status gnome-remote-desktop.service" reports "active (running)". 2. Disable Remote Desktop in Control Center. systemctl reports "inactive (dead)". 3. Log out and back in. 4. Open Control Center. Remote Desktop is enabled again. systemctl reports "active (running)". Expected behavior: Remote Desktop should stay disabled upon the new login. Actual behavior: Remote Desktop was automatically enabled again. Previous discussion: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1775#note_1443319 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Information type changed from Private Security to Public Security -- 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/1972812 Title: The operating system does not ask for a password after unlocking the screen. Status in gnome-shell package in Ubuntu: New Bug description: I found a security vulnerability in Ubuntu 22.04 LTS operating system (Laptops only) It is reproduced like this (in steps): 1. I lock the screen Win + L 2. Close the laptop lid 3. Then I open the lid of the laptop 4. I get a vulnerability, the operating system does not ask for a password, but immediately shows the desktop without the need to unlock it. that is, closing and opening the laptop lid leads to unlocking the screen without asking for a password. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 12:20:28 2022 InstallationDate: Installed on 2022-04-21 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972870] Re: Video is scalled, resizing windows re-scale it well
** Description changed: Hi, On Ubuntu 22.04 LTS on a fresh install: - - I click on a video + - I double click on a video in nautilus, launch totem by default - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space - - Another thing not only it is not well scalled, but it is black (nocolors), as you can see on the 1st screenshot + - Another thing not only it is not well scalled, but it is black (nocolors), as you can see on the 1st screenshot I'm attaching 2 screenshots: - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' ** Summary changed: - Video is scalled, resizing windows re-scale it well + Video is wrongly scalled, resizing windows re-scale it well ** Summary changed: - Video is wrongly scalled, resizing windows re-scale it well + Video is wrongly scalled, resizing window re-scales it well -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972870 Title: Video is wrongly scalled, resizing window re-scales it well Status in gstreamer1.0 package in Ubuntu: New Bug description: Hi, On Ubuntu 22.04 LTS on a fresh install: - I double click on a video in nautilus, launch totem by default - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space - Another thing not only it is not well scalled, but it is black (nocolors), as you can see on the 1st screenshot I'm attaching 2 screenshots: - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972870] Re: Video is scalled, resizing windows re-scale it well
** Description changed: Hi, On Ubuntu 22.04 LTS on a fresh install: - I click on a video - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space + - Another thing not only it is not well scalled, but it is black (nocolors), as you can see on the 1st screenshot I'm attaching 2 screenshots: - - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) + - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) + - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972870 Title: Video is scalled, resizing windows re-scale it well Status in gstreamer1.0 package in Ubuntu: New Bug description: Hi, On Ubuntu 22.04 LTS on a fresh install: - I click on a video - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space - Another thing not only it is not well scalled, but it is black (nocolors), as you can see on the 1st screenshot I'm attaching 2 screenshots: - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959345] Re: vulkaninfo reports error
see, remnants of amdgpu-pro ;) -- 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/1959345 Title: vulkaninfo reports error Status in mesa package in Ubuntu: Invalid Bug description: Tracker says mesa-vulkan-drivers is not in Ubuntu!? mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 [installed] Ubuntu 18.04.6 LTS AMD Ryzen 7 2700x eight-core processor x 16 AMD Radeon rx 5700 xt apt-cache show says that vulkan-mesa-drivers provides vulkan-icd. find / -name vulkan-icd finds nothing vulkaninfo reports: ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in /usr/share/vulkan/icd.d/ Either the error is a false positive or I should have amd_icd64.json - and then maybe all the other problems with the GPU would go away! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gary 12435 F pulseaudio /dev/snd/controlC2: gary 12435 F pulseaudio /dev/snd/controlC0: gary 12435 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c InstallationDate: Installed on 2020-02-14 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.173.20 RfKill: Tags: bionic Uname: Linux 5.4.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F63d dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972870] Re: Video is scalled, resizing windows re-scale it well
** Attachment added: "resize_totem_2022-05-10_17-47-51.png" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+attachment/5588254/+files/resize_totem_2022-05-10_17-47-51.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972870 Title: Video is scalled, resizing windows re-scale it well Status in gstreamer1.0 package in Ubuntu: New Bug description: Hi, On Ubuntu 22.04 LTS on a fresh install: - I click on a video - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space I'm attaching 2 screenshots: - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972870] Re: Video is scalled, resizing windows re-scale it well
** Attachment removed: "launch_video_2022-05-10_17-47-21.png" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+attachment/5588241/+files/launch_video_2022-05-10_17-47-21.png ** Attachment removed: "resize_totem_2022-05-10_17-47-51.png" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+attachment/5588246/+files/resize_totem_2022-05-10_17-47-51.png ** Attachment added: "re-uploaded to hide personnal information" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+attachment/5588253/+files/launch_video_2022-05-10_17-47-21.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972870 Title: Video is scalled, resizing windows re-scale it well Status in gstreamer1.0 package in Ubuntu: New Bug description: Hi, On Ubuntu 22.04 LTS on a fresh install: - I click on a video - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space I'm attaching 2 screenshots: - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972870] Re: Video is scalled, resizing windows re-scale it well
** Attachment added: "resize_totem_2022-05-10_17-47-51.png" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+attachment/5588246/+files/resize_totem_2022-05-10_17-47-51.png ** Description changed: Hi, On Ubuntu 22.04 LTS on a fresh install: - - I click on a video - - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space + - I click on a video + - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. + - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space - I'm attaching 2 screenshots, 1 before manually resize, 1 after resizing - a few pixel larger the window + I'm attaching 2 screenshots: + - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) + - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) + + Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972870 Title: Video is scalled, resizing windows re-scale it well Status in gstreamer1.0 package in Ubuntu: New Bug description: Hi, On Ubuntu 22.04 LTS on a fresh install: - I click on a video - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space I'm attaching 2 screenshots: - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969934] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted evolution-data-server into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evolution-data- server/3.44.1-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1969934 Title: Update evolution-data-server to 3.44.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the 3.44 series (corresponding with GNOME 42). https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.1/NEWS It is required to update evolution to 3.44.1 (LP: #1969935) Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972870] [NEW] Video is scalled, resizing windows re-scale it well
Public bug reported: Hi, On Ubuntu 22.04 LTS on a fresh install: - I click on a video - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space I'm attaching 2 screenshots: - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "launch_video_2022-05-10_17-47-21.png" https://bugs.launchpad.net/bugs/1972870/+attachment/5588241/+files/launch_video_2022-05-10_17-47-21.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972870 Title: Video is scalled, resizing windows re-scale it well Status in gstreamer1.0 package in Ubuntu: New Bug description: Hi, On Ubuntu 22.04 LTS on a fresh install: - I click on a video - It plays (sound + video), but the video is scale horizontally smaller, so it will display a vertical rectangle, when expected a horizontal 4:3 or 16:9 rectangle) so the windows has a lot of black space. - If I resize the windows of totem, the video is well rescalled to the new size and have the expected shape, no unexpected black space I'm attaching 2 screenshots: - 1 before manually resize (launch_video_2022-05-10_17-47-21.png) - 1 after resizing a few pixel larger the window (resize_totem_2022-05-10_17-47-51.png) Expected result: no need to resize windows to have the decent scale ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 16:42:14 2022 InstallationDate: Installed on 2022-04-29 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967539] Re: All file downloads fail
Hi Sebastion, Please could you tell me what you are looking for? Is there a way I can prune it down first? It runs to some 17,000 lines! -- 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/1967539 Title: All file downloads fail Status in firefox package in Ubuntu: New Bug description: Moving to the snap version results in all file download failing. Message is just "failed". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 5.16.0-18.2-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 1 15:56:13 2022 InstallationDate: Installed on 2017-12-06 (1577 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2021-12-08 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967539] Re: All file downloads fail
-- 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/1967539 Title: All file downloads fail Status in firefox package in Ubuntu: New Bug description: Moving to the snap version results in all file download failing. Message is just "failed". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 5.16.0-18.2-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 1 15:56:13 2022 InstallationDate: Installed on 2017-12-06 (1577 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2021-12-08 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
Turned off COMPOSITE, and am getting the same reaction. See attached Xorg.0.log On Tue, May 10, 2022 at 3:20 AM Sebastien Bacher <1972...@bugs.launchpad.net> wrote: > The Xorg log was sent via email and contains > > (WW) NVIDIA: The Composite and Xinerama extensions are both enabled, which > (WW) NVIDIA: is an unsupported configuration. The driver will continue > (WW) NVIDIA: to load, but may behave strangely. > (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the > (WW) NVIDIA: X server. > > gnome-control-center should handle the situation better but that's a bit > of a special graphical display configuration, did you try to do without > xinerama? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1972037 > > Title: > Stack Overflow - gnome-control-center > > Status in gnome-control-center package in Ubuntu: > New > > Bug description: > > Program: gnome-control-center > Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) > OS: ubuntu 20.04.4 LTS > GNOME Version: 3.36.8 (ubuntu default download) > Windowing System: X11 > Graphics: GeForce 8400GS/PCIe/SSE2 > Driver: Using NVIDIA binary driver version 340.108 > Source: download version from ubuntu > > Steps to reproduce: > > Reset GNOME settings with: > dconf reset -f /org/gnome/control-center/ > Open GNOME Settings with: > /usr/bin/gnome-control-center > Click on "Displays" and receive: > Xlib: extension "RANDR" missing on display ":0". > Xlib: extension "RANDR" missing on display ":0". > Segmentation fault (core dumped) > > Repeated using gdb with package symbols. > Output of "bt -full" in attachment (with a few comments). > > (Submitted to gnome.org, but they said it is out of date and not > supported by them.) > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-control-center 1:3.36.5-0ubuntu4 > ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 > Uname: Linux 5.4.0-100-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 2.20.11-0ubuntu27.23 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: GNOME-Flashback:GNOME > Date: Fri May 6 20:38:55 2022 > InstallationDate: Installed on 2011-07-11 (3952 days ago) > InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 > (20110426) > SourcePackage: gnome-control-center > UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions > > ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/bugs/1972037/+attachment/5588238/+files/Xorg.0.log -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911133] Re: [Regression] RS482M [Mobility Radeon Xpress 200]
Can't boot USB LiveCD of Kubuntu 20.04.4. I've moved HDD from another PC with an almost fresh installation of 20.04. ksplashqml crashes. I'm trying to install Ubuntu 18.04.6. It won't load without pci=nomsi noapic nolapic kernel args. Next I'll try Kubuntu 16.04... Also Dell Inspiron 1501 resurrecion. -- 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/1911133 Title: [Regression] RS482M [Mobility Radeon Xpress 200] Status in mesa package in Ubuntu: Confirmed Bug description: RS482M [Mobility Radeon Xpress 200] crash gnome desktop at startup with Oh no! Something has gone wrong after latest updates It works fine before them System: Hp Nx6325 Video: Advanced Micro Deviceº Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] (prog-if 00 [VGA controller]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
@Gunnar, thanks for helping with resolving the issue at least for my case, I hope, this information will help with further investigation. -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
Hi,
seems that the change from 1:0.9.0~0.20.04.5 to 1:0.9.0~0.20.04.6
did introduce for me a 10s extra delay at each startup,
despite the fact that it's a desktop with only one (pretty old) Nvidia discrete
graphic card.
systemd-analyze blame
10.403s gpu-manager.service
9.927s plymouth-quit-wait.service
2.641s dev-sda3.device
While investigating, I found in
/var/log/gpu-manager.log
can't access /run/u-d-c-nvidia-drm-was-loaded file
...
can't access /run/u-d-c-nvidia-drm-was-loaded file
Takes 1ms to wait for nvidia udev rules completed.
Single card detected
which lead me here ...
Has anyone an idea to workaround this ?
Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching
[Desktop-packages] [Bug 1972856] Re: Cannot add printer
$ driverless ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/ $ driverless 'ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/' > 1.ppd ERROR: Unable to create PPD file: Could not poll sufficient capability info from the printer (ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/, ipps://HPF80DAC5CDC21.local:631/ipp/print) via IPP! $ driverless 'ipps://HPF80DAC5CDC21.local:631/ipp/print' > 2.ppd ERROR: Unable to create PPD file: Could not poll sufficient capability info from the printer (ipps://HPF80DAC5CDC21.local:631/ipp/print, ipps://HPF80DAC5CDC21.local:631/ipp/print) via IPP! Files created but empty. -- 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/1972856 Title: Cannot add printer Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I try to add a HP OfficeJet the system cannot find drivers, it shows an error. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 15:25:16 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (49 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966524] Re: Multiple apps crashing with SIGSEGV in WebKit::WaylandCompositor::Buffer::createImage() from WebKit::WaylandCompositor::Surface::commit()
The new version has been synced to kinetic, I'm checking with security if they are planning an update since often webkitgtk updates go through security ** Changed in: webkit2gtk (Ubuntu) Status: Confirmed => Fix Released ** Changed in: webkit2gtk (Ubuntu) Importance: Medium => High -- 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/1966524 Title: Multiple apps crashing with SIGSEGV in WebKit::WaylandCompositor::Buffer::createImage() from WebKit::WaylandCompositor::Surface::commit() Status in webkit2gtk package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/1480830c20c6b9ecf11782320e3ece075cf4589a https://errors.ubuntu.com/problem/d77723e6d12027009d8765f11aac355d7297f337 https://errors.ubuntu.com/problem/7a57cde3ad49926d9176d3e34d2a434798e05784 --- From gnome-terminal, menu -> help, it opens for a moment and then crashes ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: yelp 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 23:52:56 2022 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2022-03-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) ProcCmdline: yelp help:gnome-terminal SegvAnalysis: Segfault happened at: 0x7f54b529030b:mov0x8,%rax PC (0x7f54b529030b) ok source "0x8" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: yelp StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 Title: yelp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1966524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971010] Re: [vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in VirtualBox when paravirtualization is enabled
Looks like with the latest update the problem is solved. -- 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/1971010 Title: [vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in VirtualBox when paravirtualization is enabled Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Screen and mouse doesn't work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 30 09:35:20 2022 DistUpgraded: 2022-04-29 07:32:33,356 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2021-11-09 (171 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=fdb10ec1-b027-47b9-bcc7-9dc7ae1897d8 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-29 (1 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969220] Re: Pinch to zoom not working on Wayland on Jammy
Bug created under Mozilla bug tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1766042 ** Bug watch added: Mozilla Bugzilla #1766042 https://bugzilla.mozilla.org/show_bug.cgi?id=1766042 -- 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/1969220 Title: Pinch to zoom not working on Wayland on Jammy Status in firefox package in Ubuntu: Confirmed Bug description: Firefox running within snap confinement is unable to use the pinch to zoom gesture on 22.04. This is a regression as it does work on 21.10. I had been following https://bugs.launchpad.net/bugs/1964541 as it was suspected that these two issues were linked, however I am using the updated mutter released as a fix for the drag and drop bug but this didn't result in a fix for pinch to zoom. Pinch to zoom does work when using Firefox from the official tarball with the variable MOZ_ENABLE_WAYLAND=1 set. Originally reported on the snapcraft forum:https://forum.snapcraft.io/t/firefox-pinch-to-zoom-not-working- on-22-04/29391 Screen recording attached showing pinch to zoom not working on snap firefox and comparing with the gesture working on mozilla tarball firefox with libinput debug-gui showing the pinch gesture Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 $ 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/beta refresh-date: 2 days ago, at 18:06 BST channels: latest/stable:99.0.1-12022-04-13 (1232) 163MB - latest/candidate: 99.0.1-12022-04-12 (1232) 163MB - latest/beta: 100.0b6-1 2022-04-15 (1244) 163MB - latest/edge: 101.0a1 2022-04-15 (1243) 180MB - esr/stable: 91.8.0esr-1 2022-04-05 (1184) 161MB - esr/candidate:91.8.0esr-1 2022-03-30 (1184) 161MB - esr/beta: ↑ esr/edge: ↑ installed: 100.0b5-1 (1236) 163MB - mutter: Installed: (none) Candidate: 42.0-3ubuntu2 Version table: 42.0-3ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971195] Re: gnome-remote-desktop leads to a session crash inside qemu with virtio-vga
** Tags removed: rls-jj-incoming -- 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/1971195 Title: gnome-remote-desktop leads to a session crash inside qemu with virtio- vga Status in gnome-remote-desktop package in Ubuntu: Fix Committed Status in gnome-remote-desktop source package in Jammy: Triaged Bug description: Steps to reproduce: 1. On a jammy host, create a jammy guest: $ qemu-img create -f qcow2 vm.qcow2 50G $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga -display gtk,grab-on-hover=on -hda vm.qcow2 -cdrom [jammy ISO] 2. Install Ubuntu in that VM (minimal install), no problems are expected yet. 3. After the installation is concluded and the VM reboots, try to login using the Wayland session (it should be the default, no need to select anything). It will fail and bring you back to the login screen (apparently due to a gnome-shell crash; I don't think the details are relevant to the problem here). What is expected: that both the Wayland and X11 sessions work out-of- the-box. Workaround: remove gnome-remote-desktop, and the Wayland session will work just fine in the conditions described above. This is why I'm reporting this issue in gnome-remote-desktop instead of Wayland or gnome-shell or qemu. I might be wrong though... Extra information: 1. gnome-shell starts as expected if the X11 session is selected instead. 2. Alternatively, using the OpenGL enabled virtio-vga driver also makes it work in both the X11 and Wayland sessions: $ qemu-system-x86_64 -accel kvm -cpu host -smp cpus=4 -m 3072 -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda vm.qcow2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1971195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Also affects: evince (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Jammy) Importance: Undecided Status: New ** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in apparmor source package in Jammy: New Status in evince source package in Jammy: New Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
** Tags removed: rls-jj-incoming -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Importance: Undecided Status: New ** Tags removed: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock source package in Jammy: New Bug description: Currently testing a fresh install of the beta for 22.04. All packages are up to date. When having the dock auto-hide option enabled, a glitch occurs when opening the windows selector (when multiple instances of the same program are opened). The selector does open, but the dock will hide itself immediately instead of waiting for a selection. Selecting a window will then cause a glitch where the selector will align with the hidden dock in a non natural way before disappearing. A proposed fix would be to prevent the dock from auto-hiding when the miniatures selector opens and wait for a second input. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1967121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971076] Re: 2.36 doesn't work with orca anymore
** Also affects: webkit2gtk (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: webkit2gtk (Ubuntu Jammy) Importance: Undecided => High ** Tags removed: rls-jj-incoming -- 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/1971076 Title: 2.36 doesn't work with orca anymore Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk source package in Jammy: New Bug description: Since Ubuntu 22.04 I can not read the content of the yelp pages, le content of a mail from evolution or a web page from epiphany. This worked correctly for Ubuntu 21.10 or Ubuntu 20.04 LTS. This problem occurs if I migrate from a previous version, or if I reinstall from scrash. Is there a new setting that I don't aware of? This also could be related to webkitgtk I suppose. A work arround is to select all the texte and to copy it to a place that I can read (gedit). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: orca 42.0-1ubuntu1 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: MATE Date: Sun May 1 10:03:38 2022 InstallationDate: Installed on 2022-04-03 (27 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: orca UpgradeStatus: Upgraded to jammy on 2022-04-12 (18 days ago) mtime.conffile..etc.xdg.autostart.orca-autostart.desktop: 2022-04-17T10:13:33.207956 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1971076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972856] Re: Cannot add printer
Could you run the command driverless and post the output here? Does it contain the printer's URI ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/ or ipps://HPF80DAC5CDC21.local:631/ipp/print ? could you also run driverless 'ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/' > 1.ppd driverless 'ipps://HPF80DAC5CDC21.local:631/ipp/print' > 2.ppd and attach the files 1.ppd and 2.ppd? Please do not compress them and do not package them together, attach them one by one. Thanks. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1972856 Title: Cannot add printer Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I try to add a HP OfficeJet the system cannot find drivers, it shows an error. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 15:25:16 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (49 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
@Sergii: Then, even if I'm not certain, it's reasonable to assume that your observation — a need to press Ctrl+Shift twice to switch from English — is related to this wayland bug. Thanks for reporting about that aspect of the issue! -- 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/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970081] Re: The background image of the login window cannot be changed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: arctica-greeter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1970081 Title: The background image of the login window cannot be changed Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom wallpaper was replaced with the default one. I can make a change via the menu, but it stays with the default background image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970081] Re: The background image of the login window cannot be changed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1970081 Title: The background image of the login window cannot be changed Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom wallpaper was replaced with the default one. I can make a change via the menu, but it stays with the default background image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970081] Re: The background image of the login window cannot be changed
I have the same problem, both after upgrading and after a new installation. Ubuntu Mate 22.04 -- 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/1970081 Title: The background image of the login window cannot be changed Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 20.04 Mate to 22.04 Mate, my custom wallpaper was replaced with the default one. I can make a change via the menu, but it stays with the default background image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959417] Re: browsers and other apps packaged as snaps can't read files under ~/.local/share/
@Olivier, if we can do that from the interface I think that's probably the easiest way to address the issue now -- 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/1959417 Title: browsers and other apps packaged as snaps can't read files under ~/.local/share/ Status in snapd: New Status in chromium package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in jupyter-notebook package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 22.04 LTS 2. Install jupyter-notebook package 3. Open terminal to launch jupyter-notebook command $ jupyter-notebook [I 18:53:12.601 NotebookApp] Serving notebooks from local directory: /home/j [I 18:53:12.601 NotebookApp] Jupyter Notebook 6.4.5 is running at: [I 18:53:12.601 NotebookApp] http://localhost:/?token=6df6a314b44a50e058ff27f735d91cbd46bfaf0e403bd2e9 [I 18:53:12.601 NotebookApp] or http://127.0.0.1:/?token=6df6a314b44a50e058ff27f735d91cbd46bfaf0e403bd2e9 [I 18:53:12.601 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation). [C 18:53:12.635 NotebookApp] To access the notebook, open this file in a browser: file:///home/j/.local/share/jupyter/runtime/nbserver-45601-open.html Or copy and paste one of these URLs: http://localhost:/?token=6df6a314b44a50e058ff27f735d91cbd46bfaf0e403bd2e9 or http://127.0.0.1:/?token=6df6a314b44a50e058ff27f735d91cbd46bfaf0e403bd2e9 Expected results: * default web-browser opened and it shows jupyter-notebook interface after redirection from local html-file to http://localhost: Actual results: * default web-browser opened with error message > Access to the file was denied > The file at /home/j/.local/share/jupyter/runtime/nbserver-45601-open.html is not readable. > It may have been removed, moved, or file permissions may be preventing access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: jupyter-notebook 6.4.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Jan 28 18:49:44 2022 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220128) PackageArchitecture: all SourcePackage: jupyter-notebook UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-01-28T14:45:41.897765 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1959417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972856] Re: Cannot add printer
>From the cups error_log: E [10/May/2022:15:33:08 +0200] [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/, ipps://HPF80DAC5CDC21.local:631/ipp/print) via IPP! E [10/May/2022:15:33:08 +0200] copy_model: empty PPD file E [10/May/2022:15:33:08 +0200] [Client 109] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/HP_OfficeJet_Pro_8020_series) from localhost. -- 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/1972856 Title: Cannot add printer Status in gnome-control-center package in Ubuntu: New Bug description: When I try to add a HP OfficeJet the system cannot find drivers, it shows an error. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 15:25:16 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (49 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972856] [NEW] Cannot add printer
Public bug reported: When I try to add a HP OfficeJet the system cannot find drivers, it shows an error. Description:Ubuntu 22.04 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 15:25:16 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (49 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1972856 Title: Cannot add printer Status in gnome-control-center package in Ubuntu: New Bug description: When I try to add a HP OfficeJet the system cannot find drivers, it shows an error. Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 10 15:25:16 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (49 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971221] Re: [nvidia] firefox is flashing
thanks for your replying. that is surely not a security issue. switching the window back and forth by clicking firefox window can solve this problem . I think that is firefox problem. some other software also has a little bugs. such as : intellgence pinyin, file Explore, document viewer (default pdf reader in OS). they are not deadly, just need to be cafurelly, use them with regular way. one serious bug is still in ubuntu 22.04 —— "programming is not responding" 。 clicking "Force Quit " or "wait" buttons cannot solve the problem. kill process through "system monitor" is also not okay. the last thing I can do is rebootint the OS. ** Changed in: firefox (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1971221 Title: [nvidia] firefox is flashing Status in firefox package in Ubuntu: Confirmed Bug description: when firefox window behind other APP windows, it is flashing. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-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..01.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.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 11:53:34 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP104 [GeForce GTX 1080] [103c:82fb] InstallationDate: Installed on 2022-05-01 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=ff0f1b3b-e57d-46bf-817b-a2bf7bd47098 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2022 dmi.bios.release: 14.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1404 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z690-A GAMING WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1404:bd04/01/2022:br14.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-AGAMINGWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972820] Re: LibreOffice crash when entering data in MySQL database
Launchpad has imported 14 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=143317. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-07-12T14:47:42+00:00 Allan Kelly wrote: Created attachment 173510 Test table use to recreate bug When using Base (via direct connector) to scroll through a mysql table, or clicking last row, or add new row, Base crashes and starts recovery dialog. Ubuntu: 5.8.0-59-generic #66~20.04.1-Ubuntu Libreoffice: Version: 6.4.7.2 Build ID: 1:6.4.7-0ubuntu0.20.04.1 Connector: libreoffice-mysql-connector/focal-updates,now 1:6.4.7-0ubuntu0.20.04.1 amd64 [installed] mysql: Ver 8.0.25-0ubuntu0.20.04.1 for Linux on x86_64 ((Ubuntu)) Using a small test table, scrolling seems is OK up around 150 rows scrolling further crashes. My work around at the moment is to use jdbc conector Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/comments/0 On 2021-07-12T18:36:38+00:00 julien2412 wrote: Could you give a try to LO 7.1.4 from LO ppa (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa)? Indeed 6.X branch is EOL and there won't be any new LO version on 7.0 branch after the released 7.0.6 version. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/comments/1 On 2021-07-13T10:21:44+00:00 Allan Kelly wrote: I have upgraded using the PPA LO is now Version: 7.1.4.2 / LibreOffice Community Build ID: 10(Build:2) CPU threads: 12; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.1.4~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded libreoffice-mysql-connector/focal,now 1:7.1.4~rc2-0ubuntu0.20.04.1~lo1 amd64 [installed] Problem still occurs. Second page forward browsing the test table results in Base crashing and recovery dialog starts. It has also introduced authentication issues for my jdbc connection so I will will have to revert to previous version as this is not a testing system. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/comments/2 On 2021-07-13T16:13:48+00:00 Iplaw67-h wrote: The test SQL dump has a collation "utf8mb4_0900_ai_ci" which unfortunately fails to get imported into my version 5 server. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/comments/3 On 2021-07-13T16:26:38+00:00 Iplaw67-h wrote: Copied and pasted the SQL manually and removed the collation statement via the mysql CLI. No crash for me when scrolling through result set in Table browse mode with Version: 7.1.4.2 / LibreOffice Community Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded I scrolled from the first record to the last record with no crash. This sounds like a bug that is specific to the Ubuntu version, whether it is GTK3 or some other handling error causing a crash. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/comments/4 On 2021-07-14T14:57:34+00:00 Nv4y-robert wrote: Couldn't confirm the buggy behavior. Tested with the attached table, also with a table with 8000 rows and 12 columns and a table with 3 rows and 15 columns. Scrolled though the table to the end and back to the start. Couldn't reproduce a crash with direct connection - here to MariaDB - and LO 7.2.0.1 VCL:kf5 on OpenSUSE 15.2 64bit rpm Linux. Think it is a special bug of Ubuntu version of LO and direct connection. Please try the packages from LO directly. You could install these packages parallel as a user-defined installation. If you need help for this: Send me a private mail. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/comments/5 On 2021-07-14T17:34:08+00:00 Allan Kelly wrote: The problem is occurring on a system I have just migrated from Ubuntu 18.04 with mysql 5 which connected fine, to Ubuntu 20.04 with mysql 8. Mysql 8 seems less supported in 20.04. odbc and jdbc drivers are no longer in Ubuntu repositories and needed to be obtained from mysql community. Have any of these attempts to reproduce issue been against a mysql 8 server? Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/comments/6
[Desktop-packages] [Bug 1972831] [NEW] Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3
Public bug reported: I think that the issue might be partly because I have pulseaudio-bt- modules package with alternative codecs I removed tht package but still same issue lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53 lut 07 22:14:40 graf systemd[1]: Started Bluetooth service. lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 initialized lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/LDAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/SBC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/VENDOR/APTX lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/AAC lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/SBC lut 08 08:37:50 graf bluetoothd[1366]: Terminating ...skipping... maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:51:49 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:52:59 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:54:08 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:55:18 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:56:27 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:57:36 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:58:45 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 13:59:55 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:01:05 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:02:14 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:03:23 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:04:33 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:05:42 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:06:52 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:08:01 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:08:31 graf bluetoothd[1293]: Controller resume with wake event 0x0 maj 10 14:10:26 graf bluetoothd[1293]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:1B:66:E9:99:8F: Protocol not available maj
[Desktop-packages] [Bug 1972820] Re: LibreOffice crash when entering data in MySQL database
** Bug watch added: Document Foundation Bugzilla #143317 https://bugs.documentfoundation.org/show_bug.cgi?id=143317 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=143317 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1972820 Title: LibreOffice crash when entering data in MySQL database Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Bug description: When I try to enter a new record in a MySQL table in LO Base, the new record is accepted but Base close suddenly when I close the table. MySQL database is connected by the direct connector (embedded). Same kind of problem with LO 6.4 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu2 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: Tue May 10 12:29:06 2022 InstallationDate: Installed on 2020-04-10 (759 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: libreoffice UpgradeStatus: Upgraded to jammy on 2022-04-09 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1972820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972820] [NEW] LibreOffice crash when entering data in MySQL database
Public bug reported: When I try to enter a new record in a MySQL table in LO Base, the new record is accepted but Base close suddenly when I close the table. MySQL database is connected by the direct connector (embedded). Same kind of problem with LO 6.4 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu2 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: Tue May 10 12:29:06 2022 InstallationDate: Installed on 2020-04-10 (759 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: libreoffice UpgradeStatus: Upgraded to jammy on 2022-04-09 (30 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1972820 Title: LibreOffice crash when entering data in MySQL database Status in libreoffice package in Ubuntu: New Bug description: When I try to enter a new record in a MySQL table in LO Base, the new record is accepted but Base close suddenly when I close the table. MySQL database is connected by the direct connector (embedded). Same kind of problem with LO 6.4 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu2 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: Tue May 10 12:29:06 2022 InstallationDate: Installed on 2020-04-10 (759 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: libreoffice UpgradeStatus: Upgraded to jammy on 2022-04-09 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
@Georgia, thanks for the work! Is anyone from the security team going to sponsor the apparmor updates for you? Also in the evince debdiff, you added apparmor to the Build-Depends but is that needed? If the intend is to ensure a recent enough apparmor is available on the sytem then the Depends should be enough? Also evince didn't depends on apparmor before, it's probably fine to change that but I still want to raise the question. What would be the outcome of installing the new evince with an old apparmor? would the missing rules just be ignored or would they create issues? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727628] Re: Please fix PLUGIN_FALLBACK_LOCATION variable in installer/pluginhandler.py with respect of new website
The Fallback location link is : https://developers.hp.com/sites/default/files/ Fix is present in HPLIP 3.22.4 ** Changed in: hplip Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1727628 Title: Please fix PLUGIN_FALLBACK_LOCATION variable in installer/pluginhandler.py with respect of new website Status in HPLIP: Fix Released Status in hplip package in Ubuntu: In Progress Bug description: Hi, moving to new website https://developers.hp.com/ makes hp plugin non- downloadable - this breaks installing any printer where hp plugin is needed - please fix it immediately. I cannot find hp plugin on your new website, so I cannot even create a temporary patch, which could fix it. Patch would be changing fallback url in installer/pluginhandler.py to the newest url, where we can find hp plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1727628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947434] Re: Windows always open across monitors in a multi-monitor setup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1947434 Title: Windows always open across monitors in a multi-monitor setup Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor (Dell U2719DC). Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 21.04 too. If I log in using Wayland (the default), the initial window position of any app is always in the middle (half on the internal display and half on the external monitor). No setting that I have found appears to be able to change this behavior. If I switch to Xorg, this problem does not exist. With Xorg, the app window always opens on the primary monitor (the external one, in my case). This is the preferred behavior. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-06-18 (487 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-14 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947434] Re: Windows always open across monitors in a multi-monitor setup
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-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1947434 Title: Windows always open across monitors in a multi-monitor setup Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor (Dell U2719DC). Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 21.04 too. If I log in using Wayland (the default), the initial window position of any app is always in the middle (half on the internal display and half on the external monitor). No setting that I have found appears to be able to change this behavior. If I switch to Xorg, this problem does not exist. With Xorg, the app window always opens on the primary monitor (the external one, in my case). This is the preferred behavior. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-06-18 (487 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-14 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
@ManOnTheMoon (manonthemoon): I have tested both, both have the same problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: New Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947434] Re: Windows always open across monitors in a multi-monitor setup
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1947434 Title: Windows always open across monitors in a multi-monitor setup Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I have a laptop (Dell XPS 13 9300) connected to an external USB-C monitor (Dell U2719DC). Ubuntu 21.10 Impish is installed, although this problem existed under Ubuntu 21.04 too. If I log in using Wayland (the default), the initial window position of any app is always in the middle (half on the internal display and half on the external monitor). No setting that I have found appears to be able to change this behavior. If I switch to Xorg, this problem does not exist. With Xorg, the app window always opens on the primary monitor (the external one, in my case). This is the preferred behavior. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-06-18 (487 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 40.5-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-14 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor)
Bug 1947434 sounds similar and suggests the problem only happens with Ubuntu Dock. ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972151 Title: App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor) Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 357315] Re: "There was an error while getting the sharing information"
Thanks Cheng Wang. Sometimes happiness is just in front of us and we cannot see it. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/357315 Title: "There was an error while getting the sharing information" Status in nautilus-share package in Ubuntu: New Bug description: Sometimes I get this message. "There was an error while getting the sharing information" bla bla bla something about samba. I cannot reproduce it because it sometimes occurs. Especially when I right click on a folder and see its properties. My version is Ubuntu 8.10 with all updates. I am new to Linux. Samba is not installed, not running. I am concerned somehow may be it can be a intrusion attempt or something like that? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/357315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor)
** Summary changed: - File dialog not displayed within screen range + App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Triaged ** Tags added: multimonitor -- 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/1972151 Title: App window starts overlapping two (vertical) monitors (under the panel of the bottom monitor) Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
** Attachment added: "video_2022-05-10_10-35-26.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588164/+files/video_2022-05-10_10-35-26.mp4 -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
** Attachment added: "video_2022-05-10_10-35-26.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588165/+files/video_2022-05-10_10-35-26.mp4 -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
** Attachment added: "video_2022-05-10_10-35-26.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588166/+files/video_2022-05-10_10-35-26.mp4 -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
Yes it's not related to unlocking at all and I believe it happens only if there is external monitor connected. And sometimes it opens in full screen mode. ** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+attachment/5588163/+files/xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04
Add logging ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5588142/+files/log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine as Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Incomplete Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
I just realized there's no dot next to the Files icon. So the window is either untracked or it might be tracked on a different monitor/dock. Please run: xrandr > xrandr.txt and attach the resulting text file here. -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
Thanks. That shows the most recent gnome-shell crash was 8 days ago so that's probably not the issue. Let's forget about crashes... Are you sure the problem isn't caused by locking the screen or the screensaver? ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2258 https://gitlab.gnome.org/GNOME/mutter/-/issues/2258 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2258 Importance: Unknown Status: Unknown -- 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/1972151 Title: File dialog not displayed within screen range Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972790] [NEW] Can't connect to hotspot created on ubuntu
Public bug reported: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] 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 Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Attachment added: "log" https://bugs.launchpad.net/bugs/1972790/+attachment/5588135/+files/log -- 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/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: New Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] 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 Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.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/1972790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
@Dave, thanks for trying. Do you get some warnings from totem? If so you might be able to get a backtrace as described on https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1408065 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" Status in Totem: Unknown Status in totem package in Ubuntu: Confirmed Bug description: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
https://errors.ubuntu.com/user/2b93ad219b48c9b97a7a077caec6d69c0c1775edbb7ed9adc197eb0f82ef67bad56000432096446e2a08ce86802994b7d7974a33972dece2b7b97ff663da8f05 -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971089] Re: Network Manager bug constant reconnecting and CPU usage
It's not installed by Ubuntu by default so you installed it. If you are not using it then simply $ sudo apt remove miredo and restart your system and see if that resolve the issue -- 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/1971089 Title: Network Manager bug constant reconnecting and CPU usage Status in network-manager package in Ubuntu: New Bug description: Anyconnectin result cpu heavy usage. constant reconnections wifi/ethernet..no matter ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun May 1 17:00:00 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-03 (1793 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.148 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to jammy on 2022-04-25 (6 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972708] Re: Wired connection is off after resuming from sleep
Thank you for your bug report. We currently don't have an active
maintainer for that component so you might want to directly report the
issue upstream as well on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues
--
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/1972708
Title:
Wired connection is off after resuming from sleep
Status in network-manager package in Ubuntu:
New
Bug description:
When coming out of sleep mode, the wired connection is always off,
fresh installation of 22.04. It goes up easily by toggling it on from
the UI ("Turn On")
Relevant /var/log/syslog messages:
May 9 17:11:49 olivier-desktop kernel: [12935.927375] Bluetooth: hci0: Timed
out waiting for suspend events
May 9 17:11:49 olivier-desktop kernel: [12935.927381] Bluetooth: hci0:
Suspend timeout bit: 6
May 9 17:11:49 olivier-desktop kernel: [12935.927395] Bluetooth: hci0:
Suspend notifier action (3) failed: -110
May 9 17:11:49 olivier-desktop kernel: [12935.927420] Freezing user space
processes ... (elapsed 0.003 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.931100] OOM killer disabled.
May 9 17:11:49 olivier-desktop kernel: [12935.931101] Freezing remaining
freezable tasks ... (elapsed 0.001 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.932442] printk: Suspending
console(s) (use no_console_suspend to debug)
May 9 17:11:49 olivier-desktop kernel: [12935.933372] nuvoton-cir 00:01:
disabled
May 9 17:11:49 olivier-desktop kernel: [12935.933511] e1000e: EEE TX LPI
TIMER: 0011
[...]
May 9 17:11:49 olivier-desktop ModemManager[753]: [sleep-monitor]
system is resuming
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4217] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4218] device (enp0s25): state change: activated -> unmanaged (reas
on 'sleeping', sys-iface-state: 'managed')
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4445] dhcp4 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 192.168.1.39 on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv4 with address 192.168.1.39.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv4 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:5c93:eaf1:5741:587a on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:5
c93:eaf1:5741:587a.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Joining mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset search domain list.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
set default route setting: no
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset DNS server list.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4638] manager: NetworkManager state is now CONNECTED_GLOBAL
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv6 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop kernel: [12936.658740] e1000e :00:19.0
enp0s25: NIC Link is Down
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:ce9a:6874:2c00:f41c on enp0s25.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5495] manager: NetworkManager state is now DISCONNECTED
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5520] device (enp0s25): state change: unmanaged -> unavailable (re
ason 'managed', sys-iface-state: 'external')
[...]
May 9 17:11:51
[Desktop-packages] [Bug 1972151] Re: File dialog not displayed within screen range
No problem. Please just share the link to the page here. I should be able to access it. -- 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/1972151 Title: File dialog not displayed within screen range Status in gnome-shell package in Ubuntu: Incomplete Bug description: When opening a file dialog, it's dimensions are not displayed within the screen range. It happens randomly but frequently. Not sure if it's related to multiple displays. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 09:10:14 2022 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2022-02-03 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to jammy on 2022-04-21 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972711] Re: Videos (totem) corrupt video playback mkv/h264
Thank you for your bug report. Could you perhaps report it also directly upstream on https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1972711 Title: Videos (totem) corrupt video playback mkv/h264 Status in gstreamer1.0 package in Ubuntu: New Bug description: playback of mkv/h264 is corrupt. Works fine in VLC Description: Ubuntu 22.04 LTS Release: 22.04 totem: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Wayland, HD Graphics 4000 Kernel: 5.17.0-1003-oem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.1-1 ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0 Uname: Linux 5.17.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 9 08:52:21 2022 InstallationDate: Installed on 2021-02-06 (456 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1972711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center
The Xorg log was sent via email and contains (WW) NVIDIA: The Composite and Xinerama extensions are both enabled, which (WW) NVIDIA: is an unsupported configuration. The driver will continue (WW) NVIDIA: to load, but may behave strangely. (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the (WW) NVIDIA: X server. gnome-control-center should handle the situation better but that's a bit of a special graphical display configuration, did you try to do without xinerama? -- 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/1972037 Title: Stack Overflow - gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: Program: gnome-control-center Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download) OS: ubuntu 20.04.4 LTS GNOME Version: 3.36.8 (ubuntu default download) Windowing System: X11 Graphics: GeForce 8400GS/PCIe/SSE2 Driver: Using NVIDIA binary driver version 340.108 Source: download version from ubuntu Steps to reproduce: Reset GNOME settings with: dconf reset -f /org/gnome/control-center/ Open GNOME Settings with: /usr/bin/gnome-control-center Click on "Displays" and receive: Xlib: extension "RANDR" missing on display ":0". Xlib: extension "RANDR" missing on display ":0". Segmentation fault (core dumped) Repeated using gdb with package symbols. Output of "bt -full" in attachment (with a few comments). (Submitted to gnome.org, but they said it is out of date and not supported by them.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Fri May 6 20:38:55 2022 InstallationDate: Installed on 2011-07-11 (3952 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
