[Desktop-packages] [Bug 2019481] Re: Xorg freeze
Thanks for the bug report. Please reproduce the problem again so we can collect the full system log, then reboot to a terminal and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Although your Xorg log already mentions: [20.820] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please [20.820] (EE) NVIDIA(GPU-0): check your system's kernel log for additional error [20.820] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8: Common Problems in the [20.820] (EE) NVIDIA(GPU-0): README for additional information. [20.820] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics device! we still need to see what happened before that. ** Summary changed: - Xorg freeze + System boots to a black screen when nvidia-390 is installed ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2019481 Title: System boots to a black screen when nvidia-390 is installed Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Upon installing the 3rd party nVidia version 390 drivers for the Dell E6520 laptop, after reboot hangs with a black screen and a blinking cursor in the upper left hand corner. Booting to a terminal prompt and using "sudo apt remove *nvidia*" and rebooting solves the issue. This did NOT happen in 22.04 LTS on this laptop with no other hardware or BIOS changes. This install of 23.04 was a clean install, the 22.04 install was wiped. vendor : NVIDIA Corporation model: GF119M [NVS 4200M] driver : nvidia-driver-390 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin If I install that driver the system will not boot, removing it solves the issue. I've wiped and reinstalled 23.04 4x, both with full options and minimal, the problem always returns. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 13 10:46:41 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF119M [NVS 4200M] [1028:1494] InstallationDate: Installed on 2023-05-13 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dell Inc. Latitude E6520 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=f7260292-99f4-4e45-a79a-97643cc0cb92 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0692FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd03/06/2018:br4.6:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:sku: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/nvidia-graphics-drivers-390/+bug/2019481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packa
[Desktop-packages] [Bug 2019499] Re: interrupt sound if the disk is writing data (btrfs+compress-zstd)
It sounds like btrfs+compress-zstd is just blocking too much if there is no problem with ext4. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2019499 Title: interrupt sound if the disk is writing data (btrfs+compress-zstd) Status in linux package in Ubuntu: Incomplete Status in pipewire package in Ubuntu: New Bug description: ubuntu 23.04 interrupt sound (interval 5-30s) if the disk is writing data (btrfs+compress-zstd) before upgrading from ubuntu 22.04+pulse interrupt sound one time (1-10s) only when ending write interrupt sound net download (15M/bit max) or copy and write to btrfs+compress-zstd. download app: (firefox, uget, seamonkey, yt-dlp, synaptic) playing app: (vlc, rhythmbox, smplayer) interrupted sound even if the file is played from another disc. sound OK if write to ext4 or ramdisc. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire-bin 0.3.65-3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun May 14 13:52:08 2023 ExecutablePath: /usr/bin/pipewire ProcEnviron: LANG=sk_SK.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pipewire UpgradeStatus: Upgraded to lunar on 2022-06-18 (329 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019745] Re: problem closing a window on the desktop
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 Sounds like you're getting blocked by bug 2012388 ** Package changed: xorg (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 2012388 X11 window at top-right of the screen is invisible and steals mouse clicks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2019745 Title: problem closing a window on the desktop Status in Ubuntu: New Bug description: If I fully open my Firefox or any program and then I want to close it nothing happens.You have to drag the window from the title bar downwards and move it away from the top of the screen. Any app that's fully open has the same problem. Only happens since I upgraded. I am using dual screen and this happens on the screen on the first line. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 15 19:05:39 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/390.157, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1458:d000] InstallationDate: Installed on 2020-05-19 (1091 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. B550 AORUS ELITE V2 ProcEnviron: LANG=en_ZA.UTF-8 LANGUAGE=en_ZA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=7ccfa3c6-7f5e-43fc-8097-6169b339d161 ro ...security=apparmor apparmor=1... SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F14 dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd01/04/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu3 version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/+bug/2019745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019958] Re: 23.04 : all windows and shell animations are suddenly gone away
It looks like you don't have a fully working graphics driver. Please run: journalctl -b0 > journal.txt lspci -k > lspci.txt dpkg -l > packages.txt and attach the resulting text files here. ** 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/2019958 Title: 23.04 : all windows and shell animations are suddenly gone away Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, once of a sudden, all shell and windows animations are gone away. maximizing / minimizing windows / app's or activities views, all animations. Login logout session → no change. Disabling / removing gnome-shell extensions change nothing either. Same on next reboot. It was ok during live-session ( trying without installing ). It was ok a long moment after installation. I can't « see » which event stopped animations. org.gnome.desktop.interface enable-animations true django@ASGARD:~$ gnome-shell --force-animations libmutter-Message: 14:51:45.811: Running GNOME Shell (using mutter 44.0) as a X11 window and compositing manager org.gnome.Shell already exists on bus and --replace not specified django@ASGARD:~$ ↑ is the X11 window expected here ? ↑ ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 17 14:35:13 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018458] Re: Screen tearing when playing video
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected primary 1920x1080+0+0 (0x47) normal (normal left inverted right x axis y axis) 344mm x 193mm Identifier: 0x42 Timestamp: 161828447 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 2 3 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: _MUTTER_PRESENTATION_OUTPUT: 0 EDID: 00000dae1e15 2a1d0104a52213780228659759548e27 1e50540001010101010101010101 010101010101363680a070382040442d 350058c1101800fe004e3135 364843412d4541430a2000fe0043 4d4e0a20202020202020202000fe 004e3135364843412d4541430a2000f7 vrr_capable: 0 range: (0, 1) Colorspace: Default supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC max bpc: 12 range: (6, 12) Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 panel orientation: Normal supported: Normal, Upside Down, Left Side Up, Right Side Up scaling mode: Full aspect supported: Full, Center, Full aspect link-status: Good supported: Good, Bad CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 CONNECTOR_ID: 236 supported: 236 non-desktop: 0 range: (0, 1) 1920x1080 (0x47) 138.780MHz -HSync -VSync *current +preferred h: width 1920 start 1988 end 2033 total 2080 skew0 clock 66.72KHz v: height 1080 start 1083 end 1088 total 1112 clock 60.00Hz 1920x1080 (0x48) 138.655MHz +HSync -VSync h: width 1920 start 1968 end 2000 total 2080 skew0 clock 66.66KHz v: height 1080 start 1083 end 1088 total clock 60.00Hz 1680x1050 (0x49) 119.234MHz +HSync -VSync h: width 1680 start 1728 end 1760 total 1840 skew0 clock 64.80KHz v: height 1050 start 1053 end 1059 total 1080 clock 60.00Hz 1400x1050 (0x4a) 122.051MHz +HSync +VSync h: width 1400 start 1488 end 1640 total 1880 skew0 clock 64.92KHz v: height 1050 start 1052 end 1064 total 1082 clock 60.00Hz 1600x900 (0x4b) 97.787MHz +HSync -VSync h: width 1600 start 1648 end 1680 total 1760 skew0 clock 55.56KHz v: height 900 start 903 end 908 total 926 clock 60.00Hz 1280x1024 (0x4c) 107.966MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 63.96KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.00Hz 1400x900 (0x4d) 86.675MHz +HSync -VSync h: width 1400 start 1448 end 1480 total 1560 skew0 clock 55.56KHz v: height 900 start 903 end 913 total 926 clock 60.00Hz 1280x960 (0x4e) 108.001MHz +HSync +VSync h: width 1280 start 1376 end 1488 total 1800 skew0 clock 60.00KHz v: height 960 start 961 end 964 total 1000 clock 60.00Hz 1440x810 (0x4f) 151.941MHz +HSync -VSync DoubleScan h: width 1440 start 1464 end 1480 total 1520 skew0 clock 99.96KHz v: height 810 start 811 end 814 total 833 clock 60.00Hz 1368x768 (0x50) 72.428MHz +HSync -VSync h: width 1368 start 1416 end 1448 total 1528 skew0 clock 47.40KHz v: height 768 start 771 end 781 total 790 clock 60.00Hz 1280x800 (0x51) 71.108MHz +HSync -VSync h: width 1280 start 1328 end 1360 total 1440 skew0 clock 49.38KHz v: height 800 start 803 end 809 total 823 clock 60.00Hz 1280x720 (0x52) 64.023MHz +HSync -VSync h: width 1280 start 1328 end 1360 total 1440 skew0 clock 44.46KHz v: height 720 start 723 end 728 total 741 clock 60.00Hz 1024x768 (0x53) 64.996MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 960x720 (0x54) 117.002MHz -HSync +VSync DoubleScan h: width 960 start 1024 end 1128 total 1300 skew0 clock 90.00KHz v: height 720 start 720 end 722 total 750 clock 60.00Hz 928x696 (0x55) 109.059MHz -HSync +VSync DoubleScan h: width 928 start 976 end 1088 total 1264 skew0 clock 86.28KHz v: height 696 start 696 end 698 total 719 clock 60.00Hz 896x672 (0x56) 102.
[Desktop-packages] [Bug 2019976] Re: gdm3(8) manual page is actually gdm-screenshot
Confirmed in 22.04, but seemingly fixed in 23.04. I'm not sure when it got fixed. ** Changed in: gdm3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2019976 Title: gdm3(8) manual page is actually gdm-screenshot Status in gdm3 package in Ubuntu: Fix Released Bug description: There is no manual page for gdm3. The one that is shipped: $ dpkg-query -S /usr/share/man/man8/gdm3.8.gz gdm3: /usr/share/man/man8/gdm3.8.gz is actually $ man gdm3 | sed 1q GDM-SCREENSHOT.1(8)Debian GNU/LinuxGDM-SCREENSHOT.1(8) (also note bogus .1 at the end of the man page title name). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2019976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019958] Re: 23.04 : all windows and shell animations are suddenly gone away
Oh you fixed it already: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2019983/comments/3 ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/2019958 Title: 23.04 : all windows and shell animations are suddenly gone away Status in gnome-shell package in Ubuntu: Invalid Bug description: Hi, once of a sudden, all shell and windows animations are gone away. maximizing / minimizing windows / app's or activities views, all animations. Login logout session → no change. Disabling / removing gnome-shell extensions change nothing either. Same on next reboot. It was ok during live-session ( trying without installing ). It was ok a long moment after installation. I can't « see » which event stopped animations. org.gnome.desktop.interface enable-animations true django@ASGARD:~$ gnome-shell --force-animations libmutter-Message: 14:51:45.811: Running GNOME Shell (using mutter 44.0) as a X11 window and compositing manager org.gnome.Shell already exists on bus and --replace not specified django@ASGARD:~$ ↑ is the X11 window expected here ? ↑ ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 17 14:35:13 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-16 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017337] Re: [ASUS Zenbook UX303UB] Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech touchpad
** Also affects: libinput via https://gitlab.freedesktop.org/libinput/libinput/-/issues/893 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2017337 Title: [ASUS Zenbook UX303UB] Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech touchpad Status in libinput: Unknown Status in libinput package in Ubuntu: Confirmed Bug description: Multi touch broken on lunar (23.04) (xorg + wayland) for Focaltech touchpad Since the upgrade of my laptop (ASUS Zenbook UX303UB), multi touch has been acting erraticly in the following situations: - two finger scrolling - one finger clicks left mouse, other finger drags when two fingers are moving onto the surface, the cursor is fleeing to the right/top of the screen. (See attached screencast) The issue happens regardless of xorg/wayland. I enclosed a screencast video that demonstrates the issue. In this scenario, I am moving a window downwards using two methods: - Click and drag with one finger : working - Click the left click area with one finger, and drag using the other : not working, cursor is fleeing - When two fingers are present, and one of them is moving, I am experiencing the "fleeing cursor" issue Workaround : using left edge scrolling works as temporary workaround for scrolling, but click drag using a single finger is really cumbersome. Here is the output of the `xinput` command on Xorg: ``` ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ FocalTechPS/2 FocalTech Touchpadid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Asus Wireless Radio Control id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Video Bus id=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCam: USB2.0 HD id=11 [slave keyboard (3)] ↳ Asus WMI hotkeysid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` Here is the output of the `xinput` command on wayland: ``` WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:15 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:15id=7[slave pointer (2)] ⎜ ↳ xwayland-pointer-gestures:15id=8[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:15id=9[slave keyboard (3)] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/2017337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020003] Re: Thunderbird shows accent marks instead of punctuation
Thanks for updating us, closed as requested.
** Changed in: thunderbird (Ubuntu)
Status: New => Invalid
--
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/2020003
Title:
Thunderbird shows accent marks instead of punctuation
Status in thunderbird package in Ubuntu:
Invalid
Bug description:
I upgraded from 20.04 LTS to 22.04.2 LTS. Since then, thunderbird and
some other applications show accent marks rather than punctuation
marks in the title bar.
For example, wavecable.com is displayed as wavecable^com where ^ is an
accent mark.
This has happened since the upgrade.
If I change language to English_en, I get lots of arabic characters.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:102.11.0+build1-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-71.78~20.04.1-generic 5.15.92
Uname: Linux 5.15.0-71-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: tomdean2304 F pulseaudio
/dev/snd/controlC1: tomdean2304 F pulseaudio
/dev/snd/controlC0: tomdean2304 F pulseaudio
BuildID: 20230503190012
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed May 17 15:54:00 2023
ForcedLayersAccel: False
IfupdownConfig:
auto enp68s0f0
iface enp68s0f0 inet dhcp
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2021-05-10 (737 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
IpRoute:
default via 192.168.1.1 dev enp68s0f0
default dev enp68s0f1 scope link metric 1003 linkdown
169.254.0.0/16 dev enp68s0f1 proto kernel scope link src 169.254.9.3
linkdown
192.168.1.0/24 dev enp68s0f0 proto kernel scope link src 192.168.1.105
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources:
prefs.js
user.js
Profiles: Profile0 (Default) - LastVersion=102.11.0/20230503190012 (In use)
RebootRequiredPkgs: Error: path contained symlinks.
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to jammy on 2023-05-16 (1 days ago)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.15
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FC
dmi.board.asset.tag: Default string
dmi.board.name: TRX40 AORUS XTREME
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.:bvrFC:bd11/23/2021:br5.15:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSXTREME:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSXTREME:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: TRX40 AORUS XTREME
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2020003/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020051] [NEW] libreoffice draw doesn't start
Public bug reported: When starting Libreoffice Draw from the app launcher, the application doesn't start and the mouse just keeps loading forever. When starting from the commandline with "libreoffice --draw", it exits immediately. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libreoffice-draw 4:7.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 18 09:57:43 2023 InstallationDate: Installed on 2022-09-03 (256 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to lunar on 2023-05-02 (15 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "libreoffice draw doesn't start" https://bugs.launchpad.net/bugs/2020051/+attachment/5673773/+files/libreoffice.webm -- 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/2020051 Title: libreoffice draw doesn't start Status in libreoffice package in Ubuntu: New Bug description: When starting Libreoffice Draw from the app launcher, the application doesn't start and the mouse just keeps loading forever. When starting from the commandline with "libreoffice --draw", it exits immediately. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libreoffice-draw 4:7.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 18 09:57:43 2023 InstallationDate: Installed on 2022-09-03 (256 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to lunar on 2023-05-02 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2020051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020049] [NEW] gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_fin
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: mutter (Ubuntu) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: New ** Tags: lunar triple-buffering -- 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/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
Looks like triple buffering, probably. ** Summary changed: - /usr/bin/gnome-shell:11:clutter_stage_view_get_onscreen:meta_stage_impl_add_onscreen_frame_info:add_onscreen_frame_info:post_finish_frame:try_post_latest_swap + gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Tags added: triple-buffering ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019200] Re: fullscreen unredirection broken in gnome 44
Sorry, while I was busy travelling I forgot https://gitlab.gnome.org/GNOME/mutter/-/issues/2770 existed. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2770 https://gitlab.gnome.org/GNOME/mutter/-/issues/2770 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2770 Importance: Unknown Status: Unknown ** No longer affects: mutter -- 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/2019200 Title: fullscreen unredirection broken in gnome 44 Status in mutter package in Ubuntu: Confirmed Bug description: Gnome broke fullscreen unredir in mutter 12 resulting in serious performance regressions shown in : https://www.phoronix.com/review/ubuntu-2304-laptops/2 this MR fixes it https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2941 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2019200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017907] Re: cups-browsed high CPU usage
*** This bug is a duplicate of bug 2018504 *** https://bugs.launchpad.net/bugs/2018504 ** This bug has been marked a duplicate of bug 2018504 cups-browsed is using an excessive amount of CPU -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/2017907 Title: cups-browsed high CPU usage Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Using Lunar wifi connected to an enterprise network. cups-browsed uses a lot of CPU %, I need to kill it to save my battery. 2.0rc1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2017907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018538] Re: All PDFs when printed come out mirror image
In the time being, I've ended up having to use [cpdf](https://github.com/coherentgraphics/cpdf-binaries) to make a mirrored copy of the PDF I want to print. It's not ideal, but at least I can print PDFs I can read them without looking at it through a mirror. The command I use to flip them is ` ./cpdf -i input.pdf -hflip -o out.pdf ` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Confirmed Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020078] [NEW] firefox-snap causes system-wide freeze
Public bug reported: May 18 10:03:02 jonsmith kernel: [ 290.566068] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566228] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566389] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566550] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566708] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566899] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.694431] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20220331/psargs-330) May 18 10:03:02 jonsmith kernel: [ 290.694455] May 18 10:03:02 jonsmith kernel: [ 290.694458] No Local Variables are initialized for Method [BRT6] May 18 10:03:02 jonsmith kernel: [ 290.694460] May 18 10:03:02 jonsmith kernel: [ 290.694463] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) May 18 10:03:02 jonsmith kernel: [ 290.694465] Arg0: 409b1dbf Integer 0001 May 18 10:03:02 jonsmith kernel: [ 290.694477] Arg1: ad7ffa02 Integer May 18 10:03:02 jonsmith kernel: [ 290.694486] May 18 10:03:02 jonsmith kernel: [ 290.694490] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.694650] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.694810] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.695006] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.695174] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.695348] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:03 jonsmith kernel: [ 291.373091] audit: type=1107 audit(1684384383.334:60): pid=1089 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= peer_label="unconfined" May 18 10:03:03 jonsmith kernel: [ 291.373091] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' May 18 10:03:03 jonsmith kernel: [ 291.373813] audit: type=1107 audit(1684384383.334:61): pid=1089 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= peer_label="unconfined" May 18 10:03:03 jonsmith kernel: [ 291.373813] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' May 18 10:03:03 jonsmith kernel: [ 291.377907] audit: type=1107 audit(1684384383.338:62): pid=1089 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= peer_label="unconfined" May 18 10:03:03 jonsmith kernel: [ 291.377907] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' May 18 10:03:03 jonsmith kernel: [ 291.378569] audit: type=1107 audit(1684384383.338:63): pid=1089 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= peer_label="unconfined" May 18 10:03:03 jonsmith kernel: [ 291.378569] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' May 18 10:03:04 jonsmith kernel: [ 292.511267] audit: type=1400 audit(1684384384.470:64): apparmor="DENIED" operation="open" class="fi
[Desktop-packages] [Bug 2020078] Re: firefox-snap causes system-wide freeze
I have Ubuntu 22.04 installed on my system with 16GB RAM and 1TB disk space. Running a large number of resource-heavy apps/processes does (and should, logically) cause system freezes/hangups, after which the system must be rebooted. But when running Firefox, no matter how low the resource consumption from other background apps, the system freezes with a high probability, sometimes with as low as 3 open tabs. If browser cache is a problem, I tend to browse in Private Mode most often, yet that does not stop a system crash. I have kept track of CPU consumption in the System Monitor, and my system has crashed several times without there having been more than 20% RAM usage. Firefox also doesn't have any crash reports from these instances. I have tried several fixes suggested by Mozilla (turning off hardware acceleration etc) but none have resulted in any improvements in my situation. I remember running 4-5 windows each with at least 5 tabs without ever encountering a crash. Please help me fix this issue. Please find the last few lines from the system log above. I forced shutdown after the last line using the power button because of a system freeze. -- 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/2020078 Title: firefox-snap causes system-wide freeze Status in firefox package in Ubuntu: New Bug description: May 18 10:03:02 jonsmith kernel: [ 290.566068] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566228] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566389] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566550] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566708] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.566899] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.694431] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20220331/psargs-330) May 18 10:03:02 jonsmith kernel: [ 290.694455] May 18 10:03:02 jonsmith kernel: [ 290.694458] No Local Variables are initialized for Method [BRT6] May 18 10:03:02 jonsmith kernel: [ 290.694460] May 18 10:03:02 jonsmith kernel: [ 290.694463] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) May 18 10:03:02 jonsmith kernel: [ 290.694465] Arg0: 409b1dbf Integer 0001 May 18 10:03:02 jonsmith kernel: [ 290.694477] Arg1: ad7ffa02 Integer May 18 10:03:02 jonsmith kernel: [ 290.694486] May 18 10:03:02 jonsmith kernel: [ 290.694490] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.694650] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.694810] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.695006] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.695174] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:02 jonsmith kernel: [ 290.695348] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) May 18 10:03:03 jonsmith kernel: [ 291.373091] audit: type=1107 audit(1684384383.334:60): pid=1089 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.9" pid=2650 label="snap.snap-store.ubuntu-software" peer_pid= peer_label="unconfined" May 18 10:03:03 jonsmith kernel: [ 291.373091] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' May 18 10:03:03 jonsmith kernel: [ 291.373813] audit: type=1107 audit(1684384383.334:61): pid=1089 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" mask="send" name=":1.9" pid=2650
[Desktop-packages] [Bug 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4
Looks positive on my end with mesa proposed -- 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/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Bug description: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018458] Re: Screen tearing when playing video
** Attachment added: "xrandr-xorg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2018458/+attachment/5673844/+files/xrandr-xorg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2018458 Title: Screen tearing when playing video Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm on ubuntu 23.04, when i'm playing a movie with VLC, or MPV, when there is a fast movement on video the picture blurs and shifts, this bug is only on X11, on waywand everything is ok this is my system: 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: lunar DistroRelease: Ubuntu 23.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a0] MachineType: LENOVO 21E6006WBM Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: wayland-session lunar ubuntu Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2023 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: R1SET47W(1.18) dmi.board.asset.tag: Not Available dmi.board.name: 21E6006WBM dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR1SET47W(1.18):bd02/25/2023:br1.18:efr1.18:svnLENOVO:pn21E6006WBM:pvrThinkPadE15Gen4:rvnLENOVO:rn21E6006WBM:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E6_BU_Think_FM_ThinkPadE15Gen4: dmi.product.family: ThinkPad E15 Gen 4 dmi.product.name: 21E6006WBM dmi.product.sku: LENOVO_MT_21E6_BU_Think_FM_ThinkPad E15 Gen 4 dmi.product.version: ThinkPad E15 Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/xorg-server/+bug/2018458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018458] Re: Screen tearing when playing video
the problem seems to be only on full screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2018458 Title: Screen tearing when playing video Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm on ubuntu 23.04, when i'm playing a movie with VLC, or MPV, when there is a fast movement on video the picture blurs and shifts, this bug is only on X11, on waywand everything is ok this is my system: 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: lunar DistroRelease: Ubuntu 23.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a0] MachineType: LENOVO 21E6006WBM Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: wayland-session lunar ubuntu Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2023 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: R1SET47W(1.18) dmi.board.asset.tag: Not Available dmi.board.name: 21E6006WBM dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR1SET47W(1.18):bd02/25/2023:br1.18:efr1.18:svnLENOVO:pn21E6006WBM:pvrThinkPadE15Gen4:rvnLENOVO:rn21E6006WBM:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E6_BU_Think_FM_ThinkPadE15Gen4: dmi.product.family: ThinkPad E15 Gen 4 dmi.product.name: 21E6006WBM dmi.product.sku: LENOVO_MT_21E6_BU_Think_FM_ThinkPad E15 Gen 4 dmi.product.version: ThinkPad E15 Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/xorg-server/+bug/2018458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020110] [NEW] Migrate netplan settings to this package
Public bug reported: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020110] Re: Migrate netplan settings to this package
Test package building in ppa:waveform/ubuntu-settings for mantic (https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-settings) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020009] Re: F9 no longer hides side pane
Illustration for use-case of F9 in 22.04 which seems no longer available in 23.04 ** Attachment added: "no side pane in nautilus thanks to F9 in 22.04" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2020009/+attachment/5673904/+files/nautilus_side_by_side.png -- 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/2020009 Title: F9 no longer hides side pane Status in nautilus package in Ubuntu: New Bug description: Hi, 23.04 Ubuntu freshly installed. In Nautilus F9 key no longer hides side pane as it used to do. This keyboard shortcut is mentioned though in [ Ctrl ] + [ ? ] Expected : ability to hide side pane Use-case : easier on eyes and mouse moves when moving elements between two opened windows of Nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2020009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
Can you maybe further expand on how this is "does not appear to be a bug" because I cannot fathom any set of circumstances in which "Someone has intentionally removed a program, let's re-install it even though they've explicitly stated they don't want it" is NOT a bug. This is absurd. How is it not a bug? How? Canonical thinks this is legitimate behavior? If this is legitimately the position of Canonical right now, I will recommend people switch away from the system as it's no longer possible to predict its behavior upon how it's been configured, and Canonical thinks that's entirely OK. This is a bug. The ticket needs to be reopened. -- 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/1999308 Title: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox Status in firefox package in Ubuntu: Invalid Bug description: I have looked on various forums including the search features of Launchpad, help.ubuntu..com, and Google for answers on this but not been able to. I have uninstalled the snap of firefox multiple times, installing the real Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a few days later (once hours later) for snap to uninstall the real thing and install its snap version instead. I have tried a basic sudo snap remove firefox and when that didn't work sudo snap disable firefox sudo snap remove --purget firefox The former should be enough - that's a direct expression of my preferences, some thing like "You should have typed sudo snap remove --do-not-reinstall --disable-auto-ignore-preferences firefox" would not resolve this bug. When installing using apt-get, the correct version is being installed, and snap afterwards does not show the presence of firefox: Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] Name Version RevTracking Publisher Notes authy 2.2.2 12 latest/stable twilio-authy - bare 1.0 5 latest/stable canonical✓ base chromium 108.0.5359.94 2238 latest/stable canonical✓ - code 5235c6bb114latest/stable vscode✓classic core 16-2.57.6 14399 latest/stable canonical✓ core core18 202211032632 latest/stable canonical✓ base core20 202211231738 latest/stable canonical✓ base cups 2.4.2-4 836latest/stable openprinting✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - onlyoffice-desktopeditors 7.2.1 133latest/stable onlyoffice✓- snap-store 41.3-66-gfe1e325638 latest/stable/… canonical✓ - snapd 2.57.6 17883 latest/stable canonical✓ snapd /var/lib/snapd/seed/snaps contains (once firefox is removed): core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap snapd_8542.snap snap-store_467.snap https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/ claims that a similar issue affects Ubuntu MATE 21.04 and the solution was to type "sudo apt-mark manual firefox", which I have done, but that has not resolved the problem. I'm not here to explain why I wouldn't want the snap version, it is clearly a bug for snap to accept a command to uninstall something and then automatically reinstall it days later without the permission of the user, and especially galling that it removes the real version at the same time. I have lost data (passwords and history) because of this bug, because one of the many faults of the snap version is that it ignores the user's real ~/.mozilla profile and creates a shadow profile instead inside of the snap system. Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated user preferences, and it causes the loss of data. I am unclear on what package is causing th
[Desktop-packages] [Bug 2020110] Re: Migrate netplan settings to this package
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/443210 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2020110 Title: Migrate netplan settings to this package Status in ubuntu-settings package in Ubuntu: New Bug description: The current netplan configuration that specifies Network Manager as the renderer comes from a livecd-rootfs hack and results in an "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was decided at the engineering sprint to migrate this to /lib/netplan (with a slightly tweaked filename starting 00- for precedence) owned by ubuntu-settings which will ease maintenance (and image builds) in future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles
Invalid for cloud-init because the affected code is for rendering NetworkManager config on (non-Ubuntu) systems that are not using netplan. ** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections&literal=1&perpkg=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017229] Re: Update evolution-data-server to 3.48.1
This bug was fixed in the package evolution-data-server - 3.48.1-0ubuntu1 --- evolution-data-server (3.48.1-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2017229) * debian/*.symbols: Add new symbols -- Jeremy Bicha Fri, 21 Apr 2023 12:41:37 +0200 ** Changed in: evolution-data-server (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Lunar: Fix Released Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 (LP: #2017231) 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 evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu Other Info -- There will be new evolution-data-server bugfix releases monthly until September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017229] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2017229 Title: Update evolution-data-server to 3.48.1 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Lunar: Fix Released Bug description: Impact -- This is a new stable release in the stable 3.48 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.48.1/NEWS It is required to update the evolution app to 3.48.1 (LP: #2017231) 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 evolution-data-server is included in all the Ubuntu Desktop flavors except for Kubuntu, Lubuntu, and Xubuntu Other Info -- There will be new evolution-data-server bugfix releases monthly until September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2017229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983794] Re: Evolution not deleting autosave files
This is still needing a kinetic verification.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
Fix Committed
Status in evolution source package in Kinetic:
Confirmed
Status in libcanberra source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019751] Re: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation
Is kinetic being skipped on purpose, or is it not affected? -- 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/2019751 Title: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell source package in Lunar: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Committed Bug description: [ Impact ] GNOME Shell startup animation may not complete during startup, leading to a non-functional GNOME shell because the workarea could be clipped or input events are ignored. [ Test case ] 1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749 2. It's expected to launch a gnome-shell nested instance and perform monitor changes 3. The shell should animate to the final state and everything should be usable: - Clicking in shell widgets should work - No area is hidden or clipped [ Regression potential ] GNOME Shell may not start properly, input events are ignored and/or the desktop area is clipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965208] Re: Ubuntu dock is visible too early during the login animation
The bug description says the problem also occurs in kinetic wayland. Is kinetic being skipped on purpose, or will it also get an upload? -- 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/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Bug description: [ Impact ] Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. [ Test case ] Run: env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode Observe that the dock should be hidden while the startup animation happens, and doesn't hide and snow again [ Regression potential ] Dock is never shown or animation is not properly executed. --- In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965208] Re: Ubuntu dock is visible too early during the login animation
Oh, sorry, I just saw the kinetic upload and release, n/m. -- 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/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Bug description: [ Impact ] Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. [ Test case ] Run: env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode Observe that the dock should be hidden while the startup animation happens, and doesn't hide and snow again [ Regression potential ] Dock is never shown or animation is not properly executed. --- In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020127] Re: x apps fail to launch from terminal shell
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020127 Title: x apps fail to launch from terminal shell Status in xorg package in Ubuntu: New Bug description: New upgrade to 23.04 In terminal typing xeyes, idle or other X app including ubuntu-bug fails to launch with error Invalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0 Desktop and remote access from another machine to a shell on this host with ssh -X work correctly echo $XAUTHORITY is /home/dave/.Xauthority File exists and contains 2 cookies Clue: export XAUTHORITY=$(ls /run/user/1000/.mutter-Xwayland*) ubuntu-bug links to a working per session cookie, and I'm able to type this. Expected behaviour: display just works when an X application is started from a shell. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 18 18:44:46 2023 DistUpgraded: 2023-05-16 20:52:31,229 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 5.19.0-42-generic, x86_64: installed virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] [1002:6818] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Pitcairn XT [Radeon HD 7870 GHz Edition] [1787:2321] InstallationDate: Installed on 2021-03-06 (802 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. Z490 AORUS ELITE AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=c3300897-9f55-4525-91f6-ac8cfbe405f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-16 (1 days ago) dmi.bios.date: 08/28/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z490 AORUS ELITE AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/28/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490AORUSELITEAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490AORUSELITEAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490 AORUS ELITE AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/xorg/+bug/2020127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019751] Re: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation
Hello Marco, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/79ubuntu2.23.04.1 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- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. 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. ** Tags added: verification-needed verification-needed-lunar ** Tags added: verification-needed-jammy -- 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/2019751 Title: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell source package in Lunar: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Committed Bug description: [ Impact ] GNOME Shell startup animation may not complete during startup, leading to a non-functional GNOME shell because the workarea could be clipped or input events are ignored. [ Test case ] 1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749 2. It's expected to launch a gnome-shell nested instance and perform monitor changes 3. The shell should animate to the final state and everything should be usable: - Clicking in shell widgets should work - No area is hidden or clipped [ Regression potential ] GNOME Shell may not start properly, input events are ignored and/or the desktop area is clipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019751] Please test proposed package
Hello Marco, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/72~ubuntu5.22.04.2 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2019751 Title: Desktop area may get clipped to a small rectangle if the hypervisor changes X11 screen resolution during the login animation Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in gnome-shell source package in Lunar: Triaged Status in gnome-shell-extension-ubuntu-dock source package in Lunar: Fix Committed Bug description: [ Impact ] GNOME Shell startup animation may not complete during startup, leading to a non-functional GNOME shell because the workarea could be clipped or input events are ignored. [ Test case ] 1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749 2. It's expected to launch a gnome-shell nested instance and perform monitor changes 3. The shell should animate to the final state and everything should be usable: - Clicking in shell widgets should work - No area is hidden or clipped [ Regression potential ] GNOME Shell may not start properly, input events are ignored and/or the desktop area is clipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2019751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019230] Re: Standard Notes Black Display
Looks like I was using Wayland -- 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/2019230 Title: Standard Notes Black Display Status in mutter package in Ubuntu: Incomplete Bug description: When I launch the application "Standard Notes" the application window appears as solid black. I have had to change from using the Nvidia graphics driver under 22.10 to the Nouveau driver since upgrading to 23.04 because the Nvidia 390 driver wasn't working (I have a GeForce GT 730 graphics card). 1) Ubuntu Release: 23.04 2) xorg package: 1:7.7+23ubuntu2 3) What I expected to happen: the Standard Notes would launch normally and would be usable. 4) What happened instead: the Standard Notes window launches but is a solid blob of black - the application is completely unusable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 11 17:55:20 2023 DistUpgraded: 2023-05-02 13:20:29,911 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 730] [1043:84f6] InstallationDate: Installed on 2019-05-04 (1467 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=0d1374ee-63ea-4275-8996-fad19b20d6e1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-02 (9 days ago) dmi.bios.date: 01/18/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-A 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.:bvr2012:bd01/18/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/2019230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992847] Re: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons
Hello Marco, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/72~ubuntu5.22.04.2 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. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: In Progress => 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1992847 Title: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Bug description: [ Impact ] Left or right icons to switch the application grid is not visible or not properly centered in the overview when using auto-hiding dock [ Test case ] 1. Enable auto-hide in dock 1a. Increase the icons size (to make the bug clearer) 2. Open the app grid (super+a) 3. Try to navigate right/left using the right/left arrows 4. They should be usable and properly centered in the available space [ Regression potential ] App grid has not the proper size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1992847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983130] Re: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so.
Hello Gab, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/72~ubuntu5.22.04.2 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. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: In Progress => 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1983130 Title: Ubuntu dock set to auto-hide hides after a right-click menu is closed even when there are no reasons for it to do so. Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Bug description: [ Impact ] Dash to dock hides when a right-click menu is closed, even if there's no need for it. [ Test case ] 1. From settings -> Appearance: Enable dock auto-hide 2. Open a window, ensuring the dock is visible 3. Right click on a dock icon, and then click outside the menu to close it 4. The dock should be visible again and not hide (unless is expected) [ Regression potential ] The dock does not hide after closing the menu if a window is below it --- Description: Ubuntu 22.04 LTS Release: 22.04 Expected behavior: Dock set to auto-hide would remain shown after either a right-click menu option is selected, or a right-click menu is cancelled. Actual behavior: Dock hides after a right-click menu closes even when there are no windows in its space. Additional notes: Dock can be temporarily reset to its normal behavior when one of these actions are performed: - when a window enters the dock's usual space - when the "show applications" menu is opened and closed - when a maximized window is opened and closed/minimized To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1983130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
Hello Marcelo, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/72~ubuntu5.22.04.2 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. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy) Status: In Progress => 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Bug description: [ Impact ] Search [ Test case ] 1. From settings: a. Enable non-fractional scaling of 200% b. Show the dock on the left side c. Enable dock auto-hide 2. Hit Super key and search for any result 3. Hitting Enter key or clicking on an application icon should launch it [ Regression potential ] App grid has wrong sizes or not properly visible --- The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: BugDistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A ve
[Desktop-packages] [Bug 1965208] Re: Ubuntu dock is visible too early during the login animation
Hello Daniel, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/72~ubuntu5.22.04.2 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. ** Tags added: verification-needed verification-needed-jammy -- 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/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Bug description: [ Impact ] Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. [ Test case ] Run: env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode Observe that the dock should be hidden while the startup animation happens, and doesn't hide and snow again [ Regression potential ] Dock is never shown or animation is not properly executed. --- In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971608]
Are you still able to reproduce this with latest Nightly? It might have been fixed by https://github.com/mozilla/pdf.js/pull/16363 or https://github.com/mozilla/pdf.js/pull/16416. -- 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/1971608 Title: Firefox PDF font rendering is often messed up Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Fix Committed Bug description: I don't know whether it is an ubuntu bug or a firefox bug but since I am running the mozilla-supported ubuntu snap of firefox 99.0.1 (on 22.04 jammy) (firefox 100 not yet available on snap), posting it here. Many pdfs have messed-up fonts on this firefox. Following a reddit thread, I tried disabling browser.display.use_document_fonts in about:config. Then the pdfs render correctly, but html webpages have messed-up fonts. Reddit post with screenshots and sample URL here; previous reddit thread linked therein. https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/ Others (on this and previous thread) report it doesn't happen on other platforms. On this thread, someone confirms it on a Ubuntu VM, and someone else says it doesn't happen on Mint (based on Ubuntu but I think doesn't use snaps). To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971608]
I tried the two pdfs in the original report as well as the pdf in my (duplicate) bug report 1768783, and they all render correctly with 113.0.1 on Ubuntu. Thanks very much. :) -- 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/1971608 Title: Firefox PDF font rendering is often messed up Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Fix Committed Bug description: I don't know whether it is an ubuntu bug or a firefox bug but since I am running the mozilla-supported ubuntu snap of firefox 99.0.1 (on 22.04 jammy) (firefox 100 not yet available on snap), posting it here. Many pdfs have messed-up fonts on this firefox. Following a reddit thread, I tried disabling browser.display.use_document_fonts in about:config. Then the pdfs render correctly, but html webpages have messed-up fonts. Reddit post with screenshots and sample URL here; previous reddit thread linked therein. https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/ Others (on this and previous thread) report it doesn't happen on other platforms. On this thread, someone confirms it on a Ubuntu VM, and someone else says it doesn't happen on Mint (based on Ubuntu but I think doesn't use snaps). To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971608]
Thanks! Marking this as duplicate of bug 1766039 then. *** This bug has been marked as a duplicate of bug 1766039 *** -- 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/1971608 Title: Firefox PDF font rendering is often messed up Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Fix Committed Bug description: I don't know whether it is an ubuntu bug or a firefox bug but since I am running the mozilla-supported ubuntu snap of firefox 99.0.1 (on 22.04 jammy) (firefox 100 not yet available on snap), posting it here. Many pdfs have messed-up fonts on this firefox. Following a reddit thread, I tried disabling browser.display.use_document_fonts in about:config. Then the pdfs render correctly, but html webpages have messed-up fonts. Reddit post with screenshots and sample URL here; previous reddit thread linked therein. https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/ Others (on this and previous thread) report it doesn't happen on other platforms. On this thread, someone confirms it on a Ubuntu VM, and someone else says it doesn't happen on Mint (based on Ubuntu but I think doesn't use snaps). To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971608] Re: Firefox PDF font rendering is often messed up
** Changed in: firefox Status: Confirmed => Invalid -- 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/1971608 Title: Firefox PDF font rendering is often messed up Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Fix Committed Bug description: I don't know whether it is an ubuntu bug or a firefox bug but since I am running the mozilla-supported ubuntu snap of firefox 99.0.1 (on 22.04 jammy) (firefox 100 not yet available on snap), posting it here. Many pdfs have messed-up fonts on this firefox. Following a reddit thread, I tried disabling browser.display.use_document_fonts in about:config. Then the pdfs render correctly, but html webpages have messed-up fonts. Reddit post with screenshots and sample URL here; previous reddit thread linked therein. https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/ Others (on this and previous thread) report it doesn't happen on other platforms. On this thread, someone confirms it on a Ubuntu VM, and someone else says it doesn't happen on Mint (based on Ubuntu but I think doesn't use snaps). To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 446657] Re: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends
** Changed in: bluez (Fedora) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/446657 Title: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends Status in GNOME Bluetooth: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in bluez package in Fedora: Won't Fix Bug description: Binary package hint: gnome-bluetooth Gnome's bluetooth applet should get a bluetooth device's on/off status through dbus from SetProperty setting sent by bluetoothd. This information was given in http://permalink.gmane.org/gmane.linux.bluez.kernel/4302 There is a setting controlling this feature: RememberPowered=true in /etc/bluetooth/main.conf Questions: Is the dbus message is even sent? If it is sent, why gnome-bluetooth doesn't do anything for it? Does bluez's SetProperty actually find the last (if even saved) bluetooth status? ProblemType: Bug Architecture: i386 Date: Thu Oct 8 20:54:15 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: wl Package: gnome-bluetooth 2.28.1-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: gnome-bluetooth Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/446657/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754284] Re: Fullscreen windows are tearing in Xorg sessions
** No longer affects: mutter (Ubuntu)
--
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/1754284
Title:
Fullscreen windows are tearing in Xorg sessions
Status in Mutter:
New
Status in OEM Priority Project:
New
Status in X.Org X server:
New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
Fullscreen windows (like Totem) are tearing in gnome-shell Xorg
sessions.
This is probably to do with composite unredirecting... In compiz we
have a workaround to avoid this tearing by disallowing unredirect
("bypass") in known problematic video players. But I'm not sure if
mutter has such a workaround/whitelist/blacklist we can use.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1754284/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018458] Re: Screen tearing when playing video
*** This bug is a duplicate of bug 1754284 *** https://bugs.launchpad.net/bugs/1754284 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1754284, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1754284 Fullscreen windows are tearing in Xorg sessions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2018458 Title: Screen tearing when playing video Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm on ubuntu 23.04, when i'm playing a movie with VLC, or MPV, when there is a fast movement on video the picture blurs and shifts, this bug is only on X11, on waywand everything is ok this is my system: 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: lunar DistroRelease: Ubuntu 23.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a0] MachineType: LENOVO 21E6006WBM Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Tags: wayland-session lunar ubuntu Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2023 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: R1SET47W(1.18) dmi.board.asset.tag: Not Available dmi.board.name: 21E6006WBM dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR1SET47W(1.18):bd02/25/2023:br1.18:efr1.18:svnLENOVO:pn21E6006WBM:pvrThinkPadE15Gen4:rvnLENOVO:rn21E6006WBM:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E6_BU_Think_FM_ThinkPadE15Gen4: dmi.product.family: ThinkPad E15 Gen 4 dmi.product.name: 21E6006WBM dmi.product.sku: LENOVO_MT_21E6_BU_Think_FM_ThinkPad E15 Gen 4 dmi.product.version: ThinkPad E15 Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/xorg-server/+bug/2018458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019906] Re: 23.04 : condensed, bold and black fonts can't be used for interface and title bar
** Summary changed: - 23.04 : condensed fonts can't be used for interface and title bar + 23.04 : condensed, bold and black fonts can't be used for interface and title bar ** Package changed: gnome-tweaks (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: lunar -- 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/2019906 Title: 23.04 : condensed, bold and black fonts can't be used for interface and title bar Status in fonts-ubuntu package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, fresh lunar lobster installation here, from legacy iso image ( ubiquity installer. ) As I usually do, I tried to change the font for interface, as I much prefer « condensed » fonts rather than large, round, regular ones. In 20.04 or 22.04 or 22.10 gnome-tweaks allowed to do that. Today in 23.04, it only changes font in gnome-shell ( top panel, activities and app's views ) but not in other app's, not in the whole interface as it used to do. In dconf-editor I did not find entries regarding « global » interface font. Is this intended behavior ? Ability to change font type and size is also a matter of accessibility. For references : ⋅ https://askubuntu.com/questions/1468338/23-04-how-change-font-in-interface-gnome-shell-window-title-bar ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2079313 This affects many users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/2019906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019230] Re: Standard Notes Black Display
*** This bug is a duplicate of bug 1987976 *** https://bugs.launchpad.net/bugs/1987976 Alright then this sounds like the same root cause as bug 1987976. ** This bug has been marked a duplicate of bug 1987976 firefox black window on wayland -- 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/2019230 Title: Standard Notes Black Display Status in mutter package in Ubuntu: Incomplete Bug description: When I launch the application "Standard Notes" the application window appears as solid black. I have had to change from using the Nvidia graphics driver under 22.10 to the Nouveau driver since upgrading to 23.04 because the Nvidia 390 driver wasn't working (I have a GeForce GT 730 graphics card). 1) Ubuntu Release: 23.04 2) xorg package: 1:7.7+23ubuntu2 3) What I expected to happen: the Standard Notes would launch normally and would be usable. 4) What happened instead: the Standard Notes window launches but is a solid blob of black - the application is completely unusable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 11 17:55:20 2023 DistUpgraded: 2023-05-02 13:20:29,911 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 730] [1043:84f6] InstallationDate: Installed on 2019-05-04 (1467 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=0d1374ee-63ea-4275-8996-fad19b20d6e1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-02 (9 days ago) dmi.bios.date: 01/18/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-A 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.:bvr2012:bd01/18/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/2019230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020127] Re: x apps fail to launch from terminal shell
Thanks for the bug report. I can't seem to reproduce the issue here. Perhaps you just need to delete ~/.Xauthority or perhaps there's something in your local config setting it? Try: grep XAUTHORITY ~/.* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2020127 Title: x apps fail to launch from terminal shell Status in xorg package in Ubuntu: New Bug description: New upgrade to 23.04 In terminal typing xeyes, idle or other X app including ubuntu-bug fails to launch with error Invalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0 Desktop and remote access from another machine to a shell on this host with ssh -X work correctly echo $XAUTHORITY is /home/dave/.Xauthority File exists and contains 2 cookies Clue: export XAUTHORITY=$(ls /run/user/1000/.mutter-Xwayland*) ubuntu-bug links to a working per session cookie, and I'm able to type this. Expected behaviour: display just works when an X application is started from a shell. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 18 18:44:46 2023 DistUpgraded: 2023-05-16 20:52:31,229 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 5.19.0-42-generic, x86_64: installed virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] [1002:6818] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Pitcairn XT [Radeon HD 7870 GHz Edition] [1787:2321] InstallationDate: Installed on 2021-03-06 (802 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. Z490 AORUS ELITE AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=c3300897-9f55-4525-91f6-ac8cfbe405f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-16 (1 days ago) dmi.bios.date: 08/28/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z490 AORUS ELITE AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/28/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490AORUSELITEAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490AORUSELITEAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490 AORUS ELITE AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/xorg/+bug/2020127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020009] Re: F9 no longer hides side pane
Big disappointment here → https://gitlab.gnome.org/GNOME/nautilus/-/issues/2427 How someone can say « There is no need to hide it in large windows » ? ? ? It depends on many factors : ⋅ screen size, ⋅ user comfort about his eyes and hands moves ( may be visually impaired, may have slow or unsure hands moves, whatever… ) ⋅ d'n'd gets easier without « obstacle » on the way between 2 windows ⋅ it's probably easier on touchscreen too ( I can't test this ) ⋅ it helps focus on the task So, hopelessly → https://gitlab.gnome.org/GNOME/nautilus/-/issues/2965 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2427 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2427 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2965 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2965 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2965 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2020009 Title: F9 no longer hides side pane Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: Hi, 23.04 Ubuntu freshly installed. In Nautilus F9 key no longer hides side pane as it used to do. This keyboard shortcut is mentioned though in [ Ctrl ] + [ ? ] Expected : ability to hide side pane Use-case : easier on eyes and mouse moves when moving elements between two opened windows of Nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2020009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020150] [NEW] no sound after selecting motherboard audio jack after headphones plugged in to front panel
Public bug reported: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic] # Personal remarks Auto Mute Mode on alsamixer should be disabled by default or a way to configure it via the Sound Settings GUI in Ubuntu I don't see any scenario where a user selected Audio output should be muted and current behavior. the current issue I'm describing is exactly the same as "User Journey 2: Changing output port from panel UI" in this Ubuntu Design doc: https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa headphones no-sound realtek-alc1220a sound-settings ** Tags removed: alc1220a ** Tags added: realtek-alc1220a -- 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/2020150 Title: no sound after selecting motherboard audio jack after headphones plugged in to front panel Status in alsa-driver package in Ubuntu: New Bug description: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic] # Personal remarks Auto Mute Mode on alsamixer should be disabled by default or a way to configure it via the Sound Settings GUI in Ubuntu I don't see any scenario where a user selected Audio output should be muted and current behavior. the current issue I'm describing is exactly the same as "User Journey 2: Changing output port from panel UI" in this Ubuntu Design doc: https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2020150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020150] Re: no sound after selecting motherboard audio jack after headphones plugged in to front panel
** Description changed: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic] # Personal remarks Auto Mute Mode on alsamixer should be disabled by default or a way to configure it via the Sound Settings GUI in Ubuntu - I don't see any scenario where a user selected Audio output should be + I don't see any scenario where a user-selected Audio output should be muted and current behavior. the current issue I'm describing is exactly the same as "User Journey 2: Changing output port from panel UI" in this Ubuntu Design doc: https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz + + # Another issue related to user experience with this same User Journey as above: + after using the workaround when the volume level on the headphones is high and the volume on the speakers was low, and you change the audio device from headphones to the speakers, the audio volume would be very loud on the speakers for a fraction of a second (perceived as a loud pop) ** Description changed: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/jammy,now 1.20.1-1 amd64 [installed,automatic] # Personal remarks Auto Mute Mode on alsamixer should be disabled by default or a way to configure it via the Sound Settings GUI in Ubuntu I don't see any scenario where a user-selected Audio output should be muted and current behavior. - the current issue I'm describing is exactly the same as "User Journey 2: Changing output port from panel UI" + the current issue I'm describing is exactly the same as "User Journey #2: Changing output port from panel UI" in this Ubuntu Design doc: https://docs.google.com/document/d/1Vb1jUVLoHXBK9drley6Vd5bYGguBbCTEWVcZz7R-LFI/edit#heading=h.8h8mt4f5unfz # Another issue related to user experience with this same User Journey as above: after using the workaround when the volume level on the headphones is high and the volume on the speakers was low, and you change the audio device from headphones to the speakers, the audio volume would be very loud on the speakers for a fraction of a second (perceived as a loud pop) ** Description changed: # Symptom No sound coming from line out (motherboard jack) while headphones are plugged in(front panel) even after selecting Line out(motherboard jack) in sound settings. # Workaround run `alsamixer` in terminal press F6 to choose sound card select HD-Audio Generic use left/right arrow keys to select "Auto Mute Mode" use up/down to set to "Disabled" ESC to close run `sudo alsactl store` to save the current settings # System info Ubuntu 22.04 LTS I have ASUS X570 E Gaming motherboard (SupremeFX S1220A) (I'm assuming thats the same chip as Realtek ALC1220A) $ apt list --installed | grep alsa alsa-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] alsa-topology-conf/jammy,jammy,now 1.2.5.1-2 all [installed,automatic] alsa-ucm-conf/jammy-updates,jammy-updates,now 1.2.6.3-1ubuntu1.5 all [installed,automatic] alsa-utils/jammy,now 1.2.6-1ubun
[Desktop-packages] [Bug 1965208] Re: Ubuntu dock is visible too early during the login animation
Seems I can't reproduce the bug on jammy anymore. Neither real hardware nor nested are showing the bug. So I am hesitant to verify a fix for a problem I can't reproduce. -- 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/1965208 Title: Ubuntu dock is visible too early during the login animation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Bug description: [ Impact ] Ubuntu dock is visible too early during the login animation: It appears immediately, disappears, then appears again. [ Test case ] Run: env GNOME_SHELL_SESSION_MODE='ubuntu' GNOME_SHELL_SLOWDOWN_FACTOR=3 \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode Observe that the dock should be hidden while the startup animation happens, and doesn't hide and snow again [ Regression potential ] Dock is never shown or animation is not properly executed. --- In jammy this problem only occurred in Xorg sessions, but in kinetic it now occurs in Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1965208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020161] [NEW] Printing Job is processed but failed to be printed using driverless
Public bug reported: Since about a week, all my Ubuntu 23.04 failed to print driverless. I have installed an IPP connection that works, but the default driverless stops with Idle - "job processing failed". I use a HP MFP280nmw. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri May 19 08:16:21 2023 InstallationDate: Installed on 2023-04-04 (44 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: TUXEDO TUXEDO InfinityBook Pro Gen7 (MK1) Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=d0cb7813-e17a-4964-afed-4ff96fbb89a4 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-04-04 (44 days ago) dmi.bios.date: 01/16/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.05A08 dmi.board.asset.tag: Standard dmi.board.name: PHxARX1_PHxAQF1 dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: TUXEDO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.05A08:bd01/16/2023:br5.25:efr1.37:svnTUXEDO:pnTUXEDOInfinityBookProGen7(MK1):pvrStandard:rvnNB02:rnPHxARX1_PHxAQF1:rvrStandard:cvnTUXEDO:ct10:cvrStandard:skuIBP1XI07MK1: dmi.product.name: TUXEDO InfinityBook Pro Gen7 (MK1) dmi.product.sku: IBP1XI07MK1 dmi.product.version: Standard dmi.sys.vendor: TUXEDO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2020161 Title: Printing Job is processed but failed to be printed using driverless Status in cups package in Ubuntu: New Bug description: Since about a week, all my Ubuntu 23.04 failed to print driverless. I have installed an IPP connection that works, but the default driverless stops with Idle - "job processing failed". I use a HP MFP280nmw. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri May 19 08:16:21 2023 InstallationDate: Installed on 2023-04-04 (44 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: TUXEDO TUXEDO InfinityBook Pro Gen7 (MK1) Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=d0cb7813-e17a-4964-afed-4ff96fbb89a4 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-04-04 (44 days ago) dmi.bios.date: 01/16/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.05A08 dmi.board.asset.tag: Standard dmi.board.name: PHxARX1_PHxAQF1 dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: TUXEDO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.05A08:bd01/16/2023:br5.25:efr1.37:svnTUXEDO:pnTUXEDOInfinityBookProGen7(MK1):pvrStandard:rvnNB02:rnPHxARX1_PHxAQF1:rvrStandard:cvnTUXEDO:ct10:cvrStandard:skuIBP1XI07MK1: dmi.product.name: TUXEDO InfinityBook Pro Gen7 (MK1) dmi.product.sku: IBP1XI07MK1 dmi.product.version: Standard dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2020161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020161] Re: Printing Job is processed but failed to be printed using driverless
I can recreate this all time on 4 Ubuntu 23.04 machines. I dont have a 22.10 or 22.04 to test here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2020161 Title: Printing Job is processed but failed to be printed using driverless Status in cups package in Ubuntu: New Bug description: Since about a week, all my Ubuntu 23.04 failed to print driverless. I have installed an IPP connection that works, but the default driverless stops with Idle - "job processing failed". I use a HP MFP280nmw. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri May 19 08:16:21 2023 InstallationDate: Installed on 2023-04-04 (44 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: TUXEDO TUXEDO InfinityBook Pro Gen7 (MK1) Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=d0cb7813-e17a-4964-afed-4ff96fbb89a4 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-04-04 (44 days ago) dmi.bios.date: 01/16/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.05A08 dmi.board.asset.tag: Standard dmi.board.name: PHxARX1_PHxAQF1 dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: TUXEDO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.05A08:bd01/16/2023:br5.25:efr1.37:svnTUXEDO:pnTUXEDOInfinityBookProGen7(MK1):pvrStandard:rvnNB02:rnPHxARX1_PHxAQF1:rvrStandard:cvnTUXEDO:ct10:cvrStandard:skuIBP1XI07MK1: dmi.product.name: TUXEDO InfinityBook Pro Gen7 (MK1) dmi.product.sku: IBP1XI07MK1 dmi.product.version: Standard dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2020161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762410] Re: hyphen-{hr, pl, ru}, Recommends: libreoffice-writer, all other hypen packages Suggests:
** Changed in: openoffice.org-hyphenation-pl (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to openoffice.org-hyphenation-pl in
Ubuntu.
https://bugs.launchpad.net/bugs/1762410
Title:
hyphen-{hr,pl,ru}, Recommends: libreoffice-writer, all other hypen
packages Suggests:
Status in hyphen-ru package in Ubuntu:
Fix Released
Status in myspell-hr package in Ubuntu:
Fix Released
Status in openoffice.org-hyphenation-pl package in Ubuntu:
Fix Released
Status in hyphen-ru package in Debian:
New
Status in myspell-hr package in Debian:
Fix Released
Status in openoffice.org-hyphenation-pl package in Debian:
Fix Released
Bug description:
hyphen-{hr,pl,ru} are unlike any other i18n hyphen data package in
that they Recommends: libreoffice-writer but all others Suggests:
## Expected results
Choosing a minimal install on Ubuntu 18.04 will never have any
LibreOffice components installed.
## Actual results
Choosing a minimal install and either Croatian, Polish or Russian
locale on Ubuntu 18.04 will leave LibreOffice Writer and it's
dependencies installed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hyphen-ru/+bug/1762410/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976] Re: firefox black window on wayland
** Tags added: fixed-in-mutter-44.2 fixed-upstream -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
