[Desktop-packages] [Bug 2022824] [NEW] random blue/pink frames in the desktop
Public bug reported: I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop. every 1-2 minutes, there will be a random blue/pink frame(i'm not sure of the color because it only appears for a short time). I don't get this problem in fullscreen games running with dxvk and the random frames didn't show when I recorded my desktop with obs studio. I also got this problem in gnome(on wayland). When I have a dxvk game running, I don't get this issue. what I tried: -rebooting -updating -disabling blur in kde settings -lowering my refresh rate from 144hz to 120hz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 3 00:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1043:05d7] InstallationDate: Installed on 2023-06-01 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=ca576fb0-08b4-45d8-aadd-83e9df696ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: B450M Pro4-F dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy kubuntu 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/2022824 Title: random blue/pink frames in the desktop Status in xorg package in Ubuntu: New Bug description: I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop. every 1-2 minutes, there will be a random blue/pink frame(i'm not sure of the color because it only appears for a short time). I don't get this problem in fullscreen games running with dxvk and the random frames didn't show when I recorded my desktop with obs studio. I also got this problem in gnome(on wayland). When I have a dxvk game running, I don't get this issue. what I tried: -rebooting -updating -disabling blur in kde settings -lowering my refresh rate from 144hz to 120hz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 3 00:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1043:05d7] InstallationDate: Installed on 2023-06-01 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS
[Desktop-packages] [Bug 2020604] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.3)
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.3) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.33-1ubuntu2 (i386) mutter/42.5-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: New Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965215] Re: [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected
Same here on a HP 14 Stream laptop with this Realtek ALC236 sound card running Xubuntu 20.04. Also pluging in an external headset and microphone the laptop speakers do not mute and the headphones do not go live, they remain muted. Maybe worth noting that; Using pavucontrol having plugged in headset i can switch to headphones which then transmit sound and the external microphone opperates ok but even then pavucontrol states headset as un- plugged same as before plugging in. Laptop speakers mute once switched to headset and i presume the internal microphone is blanked. With regret i have deinstalled Xubuntu and reinstalled Arch Linux and so i cannot test further. It is obvious to me that this bug? is not distribution specific and is generic becouse exactly the same problem in Arch. I could test or check and report here from this Arch install if such information is useful to you. Best wishes to you, Chris -- 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/1965215 Title: [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 When inserted in the 3.5mm phone jack, the external microphone is not detected, and thus the audio input doesn't auto-switch from the internal microphone to the external microphone. The problem probably is related to the kernel version, as kernels 5.11.0-34, 5.11.0-36,5.11.0-37 and 5.11.0-38 works as expected, but kernels 5.4.0-104, 5.11.0-40, 5.11.0-41, 5.11.0-43, 5.11.0-44, 5.11.0-46, 5.13.0-30 and 5.13.0-35 don't. A similar problem happens for Debian 11. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thales 1485 F pulseaudio /dev/snd/pcmC0D0p: thales 1485 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 00:07:20 2022 InstallationDate: Installed on 2022-03-09 (7 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_Type: No auto-switch between inputs Title: [81FD, Realtek ALC236, Black Mic, Right] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2021 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: 8RCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.ec.firmware.release: 1.58 dmi.modalias: dmi:bvnLENOVO:bvr8RCN58WW:bd05/19/2021:br1.58:efr1.58:svnLENOVO:pn81FD:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81FD_BU_idea_FM_ideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81FD dmi.product.sku: LENOVO_MT_81FD_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I was getting some inconsistent and confusing results on my tests, so I decided to start from scratch with a fresh VM (qemu) and also a fresh Workspace (AWS). In a freshly installed Jammy VM (on qemu, not AWS), out of the box we have factional scaling disabled, so I tried changing scale to 200% and I do hit the error (but the scale DOES change): https://pastebin.ubuntu.com/p/yVwnmqbTTJ/ When I try to revert, I hit the error again and gnome freezes: https://pastebin.ubuntu.com/p/nYpqJDmr5x/ I then upgraded the packages in the PPA: sudo add-apt-repository ppa:vanvugt/mutter sudo apt update sudo apt upgrade Rebooted the VM When I still hit the error both when trying to change the scale to 200% (still does change it, though): https://pastebin.ubuntu.com/p/V7MmKCjc4W/ And also when trying to revert it (gnome freezes): https://pastebin.ubuntu.com/p/dbWZFQGr9t/ Package versions: https://pastebin.ubuntu.com/p/c4WsgPVnxr/ Also did the same tests with a fresh Workspace: Tested the very same thing in a Workspace: Out of the box fractional scaling is disabled, so I tried changing scale to 200% and I hit the error (but it does change): https://pastebin.ubuntu.com/p/gSZ5rfm7vF/ When I try to revert, I hit the error and then it causes the problem reported in https://launchpad.net/bugs/1924689: https://pastebin.ubuntu.com/p/NHY62YvxCG/ (So both Workspaces and local VM hit the same problem, but when reverting Workspaces will hit LP#1924689 and the local VM will freeze gnome) I then rebooted the Workspace without upgrading any package and tried the same steps again, and I still have the same problem. I then upgraded the packages in the PPA: sudo add-apt-repository ppa:vanvugt/mutter sudo apt update sudo apt upgrade Rebooted the Workspace, and I still hit the error both when trying to change the scale to 200% (still does change it, though): https://pastebin.ubuntu.com/p/977wzx6sxW/ And when I try to revert: https://pastebin.ubuntu.com/p/D2VZv2J7QV/ Packages: https://pastebin.ubuntu.com/p/mDKy4wWyWZ/ So, unless I'm missing something, apparently the same problem happens with fractional scaling disabled and also with the packages from the PPA. -- 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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: New Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24
[Desktop-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore
I've tested it with files from https://filesamples.com/formats/heif which was in the first returns of a google query for heif examples, that's not an official recommendation of that website though... ** Changed in: libheif (Ubuntu Lunar) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: New Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by
I installed gnome-shell 44.1-0ubuntu1 and mutter 44.1-0ubuntu1 on Ubuntu 23.04. In my earlier testing, I was unable to reproduce the crash described here after doing the update. Today, though, I was still able to reproduce the crash after doing the update and restarting my computer. Therefore, I am marking this bug verification-failed. I request that the SRU team still allow this bugfix update into lunar- updates. We had believed this fix was included in the 44.1 update. The 44.1 update still has many other bugfixes, and the failure to fix this bug isn't a new regression. ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-failed verification-failed-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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Fix Committed Bug description: Impact -- On a fresh boot, as soon as you open some applications and do the up touchpad gesture to enter the application grid and then back down to return to the desktop, journal spits out js stacktrace. If you don't trigger the crash then try opening and closing an app and trying again. Test Case - 1. Install the update 2. Open a terminal and run journalctl -f 3. You may need to wait a few moments for some background tasks like NetworkManager or PackageKit to finish what they're doing. The journal should be fairly quiet before proceeding. 3. Open another app 4. Perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 5. See journal for gnome-shell errors like seen below. 6. If nothing happens try opening an app, closing it and try again. What Could Go Wrong --- This is fixed in gnome-shell 44.1. See LP: #2020277 for more details. Sample stacktrace - Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36) Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 0x564398f2e170 == Apr 08 18:46:18 x1c gnome-shell[1782]: #0 56439bea4058 i resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77) Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Apr 08 18:46:18 x1c gnome-shell[1782]: Object .Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
** Tags removed: verification-needed ** Tags added: verification-done -- 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/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021484] Re: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway
** Changed in: ubuntu-settings (Ubuntu) Status: Incomplete => 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/2021484 Title: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway Status in ubuntu-settings package in Ubuntu: New Bug description: I'm logged as a normal user without admin privileges. When I try to edit a VPN I'm asked to introduce the credentials of the admin, nevertheless if I click cancel I can still access to the VPN configuration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-settings 20.04.6 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 29 11:16:38 2023 InstallationDate: Installed on 2022-05-04 (389 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2021484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022388] [NEW] the microfone dont work
Public bug reported: the problem is with the sound card . As such if I have sound but it sounds very low even if I turn it up to the maximum with the sound buttons (yep i use a laptop) and I have to turn it up manually with alsamixer. And the worst thing is that even if I save the configuration to save the changes from the terminal when I reboot the device all the alsamixer configuration restarts. heres is the specification of my computer : Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: sof-audio-pci-intel-tgl Sound API: ALSA v: k6.2.0-20-generic running: yes Sound Server-1: PipeWire v: 0.3.65 running: yes My hardware:System: Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64 Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010 serial: Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: UEFI: HUAWEI v: 2.30 date: 07/04/2022 Battery: ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%) volts: 7.5 min: 7.6 CPU: Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz): avg: 1364 min/max: 400/4200 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: Quanta ov9734_techfront_camera type: USB driver: uvcvideo Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2) Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi Drives: Local Storage: total: 476.94 GiB used: 149.06 GiB (31.3%) Info: Processes: 337 Uptime: 1h 35m Memory: 7.54 GiB used: 4.27 GiB (56.6%) Shell: Bash inxi: 3.3.25 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carlos 1967 F wireplumber /dev/snd/seq:carlos 1959 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 22:03:03 2023 InstallationDate: Installed on 2023-01-25 (128 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-04-21 (42 days ago) dmi.bios.date: 07/04/2022 dmi.bios.release: 2.30 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.30 dmi.board.asset.tag: N/A dmi.board.name: NBD-WXX9-PCB-B4 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnHUAWEI:bvr2.30:bd07/04/2022:br2.30:efr2.30:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B4:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: NBD-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2022388 Title: the microfone dont work Status in alsa-driver package in Ubuntu: New Bug description: the problem is with the sound card . As such if I have sound but it sounds very low even if I turn it up to the maximum with the sound buttons (yep i use a laptop) and I have to turn it up manually with alsamixer. And the worst thing is that even if I save the configuration to save the changes from the terminal when I reboot the device all the alsamixer configuration restarts. heres is the specification of my computer : Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: sof-audio-pci-intel-tgl Sound API: ALSA v: k6.2.0-20-generic running: yes Sound Server-1: PipeWire v: 0.3.65 running: yes My hardware:System: Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64 Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010 serial: Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: UEFI: HUAWEI v: 2.30 date: 07/04/2022 Battery: ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%) volts: 7.5 min: 7.6 CPU: Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz): avg: 1364 min/max: 400/4200 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe
[Desktop-packages] [Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
I have tested 72~ubuntu5.22.04.2.1 and found it to be working, with 200% scaling, and auto-hide, and dock position left. The issue appears to be resolved for me. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-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 Status in gnome-shell-extension-ubuntu-dock source package in Lunar: 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 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics
Thank you very much Steve (and Timo and everyone else that has helped). We will test it on a few systems this weekend. -- 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/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: New Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990089] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.33-1ubuntu2 (i386) mutter/42.5-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1990089 Title: Screen freeze when performing memory stress in Wayland mode Status in Linux: New Status in Mutter: Fix Released Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Released Status in mesa source package in Kinetic: Won't Fix Status in mesa source package in Lunar: Fix Released Bug description: [Impact] Running stress-ng freezes the screen under wayland on intel iris. Upstream has fixed it in 5aae8a05264c354aa93017d323ce238858f68227 iris: Retry DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM 646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if kernel can't allocate memory" which need to be backported for 22.2.5 [Test case] Install the update, then 1. stress-ng --stack 0 --timeout 300 2. check the screen and note that it shouldn't freeze anymore. [Where things could go wrong] This moves checking ENOMEM to the right place, so it's hard to see how it might cause issues. -- [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #20 0x7fcae0743c24 in
[Desktop-packages] [Bug 2003339] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.33-1ubuntu2 (i386) mutter/42.5-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)
All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: gtk+3.0/3.24.33-1ubuntu2 (i386) mutter/42.5-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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 Released 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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
Hello Andy, or anyone else affected, Accepted gjs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.72.2-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gjs (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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in gjs source package in Kinetic: Triaged Status in gjs source package in Lunar: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] gnome-shell often crashes on logout causing annoyance to the user as an error report dialog is displayed at the next login. [ Test Plan ] 1. Log into gnome-shell 2. Use gnome-shell for long enough to trigger a garbage collection cycle: Scroll the app grid and repeatedly open the calendar from the top bar for 30 seconds. 3. Log out. 4. Verify no new gnome-shell crash files appear in /var/crash/ [ Where problems could occur ] Only gnome-shell shutdown/logout is affected. [ Other Info ] https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics
Hello Sam, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.3 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: mesa (Ubuntu Jammy) Status: New => 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: New Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979037] Proposed package upload rejected
An upload of yaru-theme to jammy-proposed has been rejected from the upload queue for the following reason: "upload includes 450 lines of diff against cinnamon CSS which don't appear linked to any bugs in changelog". -- 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/1979037 Title: Monitor numbers are almost invisible in an Ubuntu/Yaru session Status in Yaru Theme: New Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] Monitor numbers (displayed in the top left corner of each screen while in the Screen Display settings) are almost invisible in an Ubuntu/Yaru session. But they are big and bold in a GNOME (Adwaita) session. Both using Wayland. [ Test case ] Run: env XDG_RUNTIME_DIR=/tmp/.test.runtime XDG_SESSION_TYPE=wayland \ MUTTER_DEBUG_NUM_DUMMY_MONITORS=2 \ GNOME_SHELL_SESSION_MODE=ubuntu \ dbus-run-session gnome-shell --nested --wayland --unsafe-mode In the nested shell, open Settings, go to Display panel The display OSDs should properly show Now repeat on the Appearance panel too [ Regression potential ] Nothing really, other OSDs may have wrong theming, but it's basically impossible To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1979037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966167] Proposed package upload rejected
An upload of yaru-theme to jammy-proposed has been rejected from the upload queue for the following reason: "upload includes 450 lines of diff against cinnamon CSS which don't appear linked to any bugs in changelog". -- 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/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019477] Proposed package upload rejected
An upload of yaru-theme to jammy-proposed has been rejected from the upload queue for the following reason: "upload includes 450 lines of diff against cinnamon CSS which don't appear linked to any bugs in changelog". -- 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/2019477 Title: Sliders temporary hide when hovered 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 ] The slider temporary hide when hovered (see https://github.com/ubuntu/yaru/pull/3634) [ Test case ] 1. Install gtk3-widget-factory from gtk-3-examples package 2. Run the Widgets Factory application, go to "Page 3" 3. Hover the transparency slider in the right-bottom side of the window 4. The item should not be hidden [ Regression potential ] Sliders are not properly themed during hover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2019477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/79ubuntu2.23.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- 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. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Lunar) Status: New => Fix Committed ** Tags added: verification-needed-lunar -- 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 Status in gnome-shell-extension-ubuntu-dock source package in Lunar: 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
[Desktop-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore
Where does one get a .heif file to use for the test case? ** Also affects: eog (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: gdk-pixbuf (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libheif (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: eog (Ubuntu Lunar) Status: New => Invalid ** Changed in: gdk-pixbuf (Ubuntu Lunar) Status: New => Invalid ** Changed in: libheif (Ubuntu Lunar) Status: New => Incomplete ** Changed in: libheif (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: Incomplete Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980889] Re: X crashes with qxl(0): error doing QXL_ALLOC
Same on Xubuntu 23.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1980889 Title: X crashes with qxl(0): error doing QXL_ALLOC Status in xserver-xorg-video-qxl package in Ubuntu: Confirmed Bug description: Have Lubuntu 22.04 installed in a virtual machine created with virt- manager. The X server will randomly crash with only Firefox and Thunderbird running, with one or the other minimized. Old bug reports found online suggested increasing the "vram" setting to 256 MiB (262144 in the XML file) fixed this problem, however at that setting, it crashed and this latest crash is when the "vram" was set to 512 MiB (524288 in the XML file). Below is the text from the Xorg.0.log.old file from the point of the crash. The crash of the X server terminated this particular log. [54.773] (II) event4 - spice vdagent tablet: device is a pointer [ 3431.844] (EE) qxl(0): error doing QXL_ALLOC [ 3431.844] (EE) [ 3431.844] (EE) Backtrace: [ 3431.861] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x56450cb3f2b9] [ 3431.863] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7fdab48da520] [ 3431.864] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 3431.864] (EE) 2: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) [0x7fdab413fb2d] [ 3431.865] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 3431.865] (EE) 3: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) [0x7fdab413ffc7] [ 3431.866] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 3431.867] (EE) 4: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) [0x7fdab414c7c0] [ 3431.869] (EE) 5: /usr/lib/xorg/Xorg (miCopyRegion+0x9b) [0x56450cb1c59b] [ 3431.870] (EE) 6: /usr/lib/xorg/Xorg (miDoCopy+0x456) [0x56450cb1ccf6] [ 3431.872] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 3431.872] (EE) 7: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) [0x7fdab414ca02] [ 3431.873] (EE) 8: /usr/lib/xorg/Xorg (DamageRegionAppend+0x3886) [0x56450caafa86] [ 3431.873] (EE) 9: /usr/lib/xorg/Xorg (SendGraphicsExpose+0x2cd) [0x56450c9c4efd] [ 3431.874] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x56450c9c94a5] [ 3431.874] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x56450c9cd524] [ 3431.876] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7fdab48c1d90] [ 3431.878] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7fdab48c1e40] [ 3431.878] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x56450c9b65f5] [ 3431.878] (EE) [ 3431.878] (EE) Segmentation fault at address 0x0 [ 3431.878] (EE) Fatal server error: [ 3431.879] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 3431.879] (EE) [ 3431.879] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 3431.879] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 3431.879] (EE) [ 3431.880] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1980889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021412] Re: nautilus hang creating a folder
I'm unable to reproduce the problem, can just attach journal around time of problem. I suppose the problem is related to a strange behavior described in bug https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2020806 ** Attachment added: "2021412.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2021412/+attachment/5677478/+files/2021412.txt -- 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/2021412 Title: nautilus hang creating a folder Status in nautilus package in Ubuntu: Incomplete Bug description: created a folder in another folder, ok: the new folder appears in the window, try create a second folder nautilus hang. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 28 08:07:58 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1063, 761)' InstallationDate: Installed on 2023-05-21 (6 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.1-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2021412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022107] Re: printing dubugging doesnt work!
What is so difficult to read in the dump posted which clearly states which description / version / release it is .. and that cups isnt available nor that the websites referred to fail. Expected result .. PRINTS Actual result DOESNT PRINT -- 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/2022107 Title: printing dubugging doesnt work! Status in cups package in Ubuntu: Incomplete Bug description: 1 cupsdisable OKI-C332-411ACB cupsdisable: Operation failed: client-error-not-found 2 wget http://people.canonical.com/~pitti/tmp/cups.upstart.debug --2023-06-01 21:57:49-- http://people.canonical.com/~pitti/tmp/cups.upstart.debug Resolving people.canonical.com (people.canonical.com)... 185.125.188.97 Connecting to people.canonical.com (people.canonical.com)|185.125.188.97|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://people.canonical.com/~pitti/tmp/cups.upstart.debug [following] --2023-06-01 21:57:49-- https://people.canonical.com/~pitti/tmp/cups.upstart.debug Connecting to people.canonical.com (people.canonical.com)|185.125.188.97|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2023-06-01 21:57:49 ERROR 403: Forbidden. Description: Ubuntu 20.04.6 LTS Release: 20.04 sudo: aa-complain: command not found /usr/lib/cups/backend/snmp network socket://192.168.1.201 "OKI DATA CORP C332" "C332" "MFG:OKI DATA CORP;CMD:PCL,XPS,IBMPPR,EPSONFX,POSTSCRIPT,PDF,PCLXL,HIPERMIP,URF;MDL:C332;CLS:PRINTER;DES:OKI C332;CID:OK_N_B800;" "" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 1 21:59:57 2023 InstallationDate: Installed on 2023-04-25 (37 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lpstat: device for OKI_C332_411ACB@oki-c332-411acb.local: implicitclass://OKI_C332_411ACB%40oki-c332-411acb.local/ Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Novatech N150ZU Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd'] failed with exit code 2: grep: /etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic root=UUID=2c0e4998-ac9a-4c3c-ab96-b2b45fe5eab7 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TNO dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Novatech dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Novatech dmi.chassis.version: N/A dmi.ec.firmware.release: 7.4 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TNO:bd06/24/2019:br7.7:efr7.4:svnNovatech:pnN150ZU:pvrNotApplicable:rvnNovatech:rnN150ZU:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Novatech To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2022107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
** Tags removed: foundations-todo -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-release-upgrader source package in Jammy: Fix Released Bug description: [Impact] By removing the firefox deb and installing the snap instead, ubuntu- release-upgrader is subverting the logic of the firefox transitional deb. [Test Case] Perform an upgrade from focal to jammy: $ do-release-upgrade On an affected system, the firefox deb will be removed by the upgrade, and the snap will be installed instead. On a fixed system, ubuntu- release-upgrader will not remove the firefox deb, and the deb will handle the transition to the snap. [Where problems could occur] If the patch was wrong, e.g. JSON syntax error or similar, it could mess up the remaining deb2snap entries. [Original Description] 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2011350] Re: ERROR:../src/nautilus-gtk4-helpers.c:116:gtk_widget_get_first_child: assertion failed: (GTK_IS_CONTAINER (widget))
My Ubuntu machine with Intel + Nvidia graphics with automatic session start randomly logs into X11 or Wayland (no idea why) and it looks like this Nautilus bug happens less often (if at all) on Wayland. Maybe it's X11-specific? -- 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/2011350 Title: ERROR:../src/nautilus-gtk4-helpers.c:116:gtk_widget_get_first_child: assertion failed: (GTK_IS_CONTAINER (widget)) Status in nautilus package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d6e8be4f90a24d66fd0bf410ccb31d3c6fd0eb9b --- Title: nautilus crashed with SIGABRT in g_assertion_message_expr() Sometimes Nautilus crashes when closing a window instead of exiting cleanly. It wouldn't be so bad if it didn't bring other windows down too. It usually happens when the window has multiple tabs. I tried to attach the crash log but it looks like apport only attached generic system info. I may have used the wrong apport command so I attached the .crash file manually. I'm not sure if it has all the necessary symbols tho. Description: Ubuntu 22.04.2 LTS Release: 22.04 Nautilus 1:42.2-0ubuntu2.1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-05 (1010 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: nautilus 1:42.2-0ubuntu2.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Tags: jammy Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-10-06 (157 days ago) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022369] [NEW] 200% scaling on wayland touchpad feels laggy
Public bug reported: I have an X1 carbon 9th gen with a 4k screen where I use 200% scaling. Unfortunately, the touchpad feels laggy and imprecise when trying to hit click targets. Switching to X11 helps as well as the flat acceleration profile in gnome tweaks. I feel like this is related to how gnome or libinput upscale mouse movement. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 16:57:16 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-15 (18 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022369 Title: 200% scaling on wayland touchpad feels laggy Status in gnome-shell package in Ubuntu: New Bug description: I have an X1 carbon 9th gen with a 4k screen where I use 200% scaling. Unfortunately, the touchpad feels laggy and imprecise when trying to hit click targets. Switching to X11 helps as well as the flat acceleration profile in gnome tweaks. I feel like this is related to how gnome or libinput upscale mouse movement. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 16:57:16 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-15 (18 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 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/2022369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Script tested with new version, no failure: apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.2.1 Candidate: 72~ubuntu5.22.04.2.1 Version table: *** 72~ubuntu5.22.04.2.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-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 Released 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
Tested again new version, all good: apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.2.1 Candidate: 72~ubuntu5.22.04.2.1 Version table: *** 72~ubuntu5.22.04.2.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-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 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.
Tested again new version, all good: apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.2.1 Candidate: 72~ubuntu5.22.04.2.1 Version table: *** 72~ubuntu5.22.04.2.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-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 1992847] Re: Left/right arrow in app-grid is not usable when using auto-hiding dock and big icons
This was already fixed by 72~ubuntu5.22.04.2, 72~ubuntu5.22.04.2.1 still works with this. apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.2.1 Candidate: 72~ubuntu5.22.04.2.1 Version table: *** 72~ubuntu5.22.04.2.1 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-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 2021412] Re: nautilus hang creating a folder
Thanks for your interest in helping to resolve this issue. In order to get to the bottom of this we need to figure out where the program is hanging. If you can follow the steps on https://wiki.ubuntu.com/Backtrace#Already_running_programs and attach the generated text file to this bug it would be of great help. ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2021412 Title: nautilus hang creating a folder Status in nautilus package in Ubuntu: Incomplete Bug description: created a folder in another folder, ok: the new folder appears in the window, try create a second folder nautilus hang. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:44.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 28 08:07:58 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1063, 761)' InstallationDate: Installed on 2023-05-21 (6 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230521) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.1-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2021412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017716] Re: Folders and files frequently need to be clicked twice
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2816 Importance: Unknown Status: Unknown ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged -- 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/2017716 Title: Folders and files frequently need to be clicked twice Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 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: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2017716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016743] Re: Unable to switch windows while drag-and-drop in Xorg sessions
Same problem here. Switching to Wayland fixes this, of course, but Wayland still falls short of providing (eg) the screenshot features of ksnip. Having to choose between no drag and drop while app-switching in Xorg or being obliged to live with the screenshot shortcomings of Wayland leaves Lunar Lobster incomplete. Good to see this has been escalated to Medium importance. -- Chris -- 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/2016743 Title: Unable to switch windows while drag-and-drop in Xorg sessions Status in gnome-shell package in Ubuntu: Triaged Bug description: Unable to switch windows while drag-and-drop. Atl-tab, super-tab, etc. are not working while trying to drag anything from one window to other. System configuration: Ubuntu 23.04, GNOME version 44.0 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 02:58:01 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-07 (10 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcEnviron: LANG=en_US.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/2016743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)
about firefox it has a custom titlebar - the UI packs the tabs on the titlebar in order to save screen space. google chrome is the same and also an exception to the bug. about the snap, it appear to have permission structures involving UI- related middleware (I am guessing), so fixing the interactive user UI session may have left the middleware unfixed/inconsistent? -- 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/2013216 Title: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: Impact -- Single clicking the title bar of windows without a complex title bar (namely a title bar with additional buttons besides the close/maximinze/minimize) does not transfer focus to them. Test Case - 1. Open gnome-terminal. 2. Run xedit. 3. Focus gnome-terminal. 4. Click Xedit's title bar. Expected: Xedit has focus. Observed: gnome-terminal retains focus. . 5. Focus Xedit. 6. Click gnome-terminal's title bar. Expected and observed: Xedit relinquishes focus and gnome-terminal gets focus. Other Info -- I can reproduce this in my main, up to date Lunar system in Xorg and also in a virtual machine with the 2023-03-24 09:02 iso (https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso). What Could Go Wrong --- This fix is included in the upstream mutter 44.1 release. See LP: #2020225 for more details. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 29 11:53:02 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-16 (316 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 44.0-2ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
Resurrected the removed upload into bionic-proposed. After some discussion we decided not to remove autopkgtest regression fix uploads from -proposed for series that are transitioning to ESM as they might be useful as a base for any ESM follow up uploads. -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Committed Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] Assume that test vm and host are ppc64 1. deploy ppc64 vm instance ( with 1 cpu ) 2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg ) 3. apt install network-manager rfkill 4. modify /etc/netplan/[conf], renderer as NetworkManager 5. netplan apply 6. run below command - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi enabled 0: fake: Wireless LAN Soft blocked: no Hard blocked: no 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no enabled 0: fake: Wireless LAN Soft blocked: yes Hard blocked: no 0: fake: Wireless LAN Soft blocked: no Hard blocked: no enabled second 'enabled' should be 'disabled' but not updated properly. Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between rfkill block/unblock and nmcli radio wifi will help updating status changes after rfkill block/unblock. [Regression Potential] This fixes testcase only, so any regression would cause incorrect test pass/fail, and might cause other missed bugs. [scope] this is needed for all releases. Debian does not include this autopkgtest, and so does not need this fix. [Other Info] this is caused by the 'systemd-rfkill.socket' listening to rfkill, and starting up 'systemd-rfkill.service' for any change. On a 1-cpu system (which all autopkgtest instances for network-manager are), this service startup sometimes blocks the uevent from reaching network- manager before the autopkgtest proceeds to call nmcli to check the rfkill status. This causes the test case to fail. There are (at least) 2 options to fix this: 1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest 2) call udevadm settle between the rfkill block/unblock and the nmcli call to check status This does not need to be fixed outside the test case, as normal nmcli use should be not done by users in a script immediately after changing rfkill state, nor is there anything that either rfkill or nmcli could even do to address this (technically, nmcli could internally issue a 'udevadm settle' every time it's called, but that seems paranoid and extreme). [original description] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. # original test case 2.1. Download network-manager package source code
[Desktop-packages] [Bug 1918377] Re: In Wayland after the screensaver, some maximized windows appear behind the ubuntu dock
*** This bug is a duplicate of bug 1917939 *** https://bugs.launchpad.net/bugs/1917939 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918377 Title: In Wayland after the screensaver, some maximized windows appear behind the ubuntu dock Status in gnome-shell package in Ubuntu: Confirmed Bug description: In Wayland, some maximized windows such as gnome-terminal and Eclipse get moved to behind the dock when the screensaver is unlocked, ie the window starts maximized and drawn next to the dock, but after locking and unlocking the screen it is now behind the dock (see attached screenshot). Other windows like nautilus don't have this problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 13:36:38 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022355] Re: package libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 failed to install/upgrade: installed libreoffice-gnome package post-installation script subprocess returned erro
** Tags removed: need-duplicate-check -- 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/2022355 Title: package libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 failed to install/upgrade: installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 Status in libreoffice package in Ubuntu: New Bug description: Was busy installing Ubuntu on m Hyper-V machine ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 2 14:57:07 2023 DuplicateSignature: package:libreoffice-gnome:1:7.3.7-0ubuntu0.22.04.2 Setting up libreoffice-gnome (1:7.3.7-0ubuntu0.22.04.2) ... dpkg: error processing package libreoffice-gnome (--configure): installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-06-02 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: libreoffice Title: package libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 failed to install/upgrade: installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2022355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022355] [NEW] package libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 failed to install/upgrade: installed libreoffice-gnome package post-installation script subprocess returned er
Public bug reported: Was busy installing Ubuntu on m Hyper-V machine ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 2 14:57:07 2023 DuplicateSignature: package:libreoffice-gnome:1:7.3.7-0ubuntu0.22.04.2 Setting up libreoffice-gnome (1:7.3.7-0ubuntu0.22.04.2) ... dpkg: error processing package libreoffice-gnome (--configure): installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-06-02 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: libreoffice Title: package libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 failed to install/upgrade: installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2022355 Title: package libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 failed to install/upgrade: installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 Status in libreoffice package in Ubuntu: New Bug description: Was busy installing Ubuntu on m Hyper-V machine ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 2 14:57:07 2023 DuplicateSignature: package:libreoffice-gnome:1:7.3.7-0ubuntu0.22.04.2 Setting up libreoffice-gnome (1:7.3.7-0ubuntu0.22.04.2) ... dpkg: error processing package libreoffice-gnome (--configure): installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 ErrorMessage: installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-06-02 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: libreoffice Title: package libreoffice-gnome 1:7.3.7-0ubuntu0.22.04.2 failed to install/upgrade: installed libreoffice-gnome package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2022355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017716] Re: Folders and files frequently need to be clicked twice
The issue seems to be related. The video shows a feature I had not noticed yet but that is certainly there: the problem does not manifest if I take the "precaution" of first moving the mouse outside nautilus before I click on a different folder. What I mean is: 1. open nautilus 2. click on a folder to open it 3. move back (I am using the side button on my mouse to do so) 4. move the cursor outside nautilus (no clicking required here) 5. return to the window and click on a different folder; it instantly opens Without step 4, step 5 is unpredictable - sometimes the folder opens at once, sometimes nothing happens and the folder needs to be clicked again at least once. -- 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/2017716 Title: Folders and files frequently need to be clicked twice Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 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: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2017716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
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.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- 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 removed: verification-done verification-done-jammy ** 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 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.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- 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: Triaged => Fix Committed ** Tags removed: verification-failed-jammy ** 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
[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.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- 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 removed: verification-done verification-done-jammy ** 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 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.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- 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 removed: verification-done verification-done-jammy ** 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 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 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.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- 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 removed: verification-done verification-done-jammy ** 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/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 Released 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 2022019] Re: Control sequence '\e]104; x\a' hangs in libvte
Upstream fixed it in
https://gitlab.gnome.org/GNOME/vte/-/commit/dce7b5f0 now
** Changed in: vte2.91 (Ubuntu)
Importance: Undecided => High
** Changed in: vte2.91 (Ubuntu)
Status: New => Fix Committed
** Tags added: rls-ll-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/2022019
Title:
Control sequence '\e]104;x\a' hangs in libvte
Status in vte2.91 package in Ubuntu:
Fix Committed
Bug description:
The command:
$ printf '\e]104;x\a'
will cause either gnome-terminal or xfce4-terminal to enter an infinite loop
inside libvte-2.91.so.0.
I believe the problem is in src/vteseq.cc in the Terminal::reset_color
function:
while (token != endtoken) {
int value;
if (!token.number(value))
continue;
int index;
if (get_osc_color_index(osc, value, index) &&
index != -1) {
reset_color(index, VTE_COLOR_SOURCE_ESCAPE);
}
++token;
}
When token doesn't point to a valid number, then "continue" bypasses
the ++token line and will just re-parse the same token over again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/2022019/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022322] Re: Gnome right butons bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/2022322 Title: Gnome right butons bug Status in xorg package in Ubuntu: Confirmed Bug description: In the superior right corner, there are a region (about 5x5 cm2) that mouse do nothing, mainly in minimize and close butons, but ocouring to in menus, just in this corner. Double click in title bar force the restore and then, moving the software window to far of this corner, works properly. Thanks. Mr. Wagner Yaegashi 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 06:13:24 2023 DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804] InstallationDate: Installed on 2022-05-01 (396 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-13 (20 days ago) dmi.bios.date: 07/14/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04REP.035.210714.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP350XAA-KD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9477A0K-C01-G001-S0001+10.0.17134 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04REP.035.210714.ZW:bd07/14/2021:br5.12:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP04REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-KD1BR:rvrSGL9477A0K-C01-G001-S0001+10.0.17134:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PREP: dmi.product.family: Notebook 3 Series dmi.product.name: 340XAA/350XAA/550XAA dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP dmi.product.version: P04REP dmi.sys.vendor: SAMSUNG ELECTRONICS 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 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/+bug/2022322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022107] Re: printing dubugging doesnt work!
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/2022107 Title: printing dubugging doesnt work! Status in cups package in Ubuntu: Incomplete Bug description: 1 cupsdisable OKI-C332-411ACB cupsdisable: Operation failed: client-error-not-found 2 wget http://people.canonical.com/~pitti/tmp/cups.upstart.debug --2023-06-01 21:57:49-- http://people.canonical.com/~pitti/tmp/cups.upstart.debug Resolving people.canonical.com (people.canonical.com)... 185.125.188.97 Connecting to people.canonical.com (people.canonical.com)|185.125.188.97|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://people.canonical.com/~pitti/tmp/cups.upstart.debug [following] --2023-06-01 21:57:49-- https://people.canonical.com/~pitti/tmp/cups.upstart.debug Connecting to people.canonical.com (people.canonical.com)|185.125.188.97|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2023-06-01 21:57:49 ERROR 403: Forbidden. Description: Ubuntu 20.04.6 LTS Release: 20.04 sudo: aa-complain: command not found /usr/lib/cups/backend/snmp network socket://192.168.1.201 "OKI DATA CORP C332" "C332" "MFG:OKI DATA CORP;CMD:PCL,XPS,IBMPPR,EPSONFX,POSTSCRIPT,PDF,PCLXL,HIPERMIP,URF;MDL:C332;CLS:PRINTER;DES:OKI C332;CID:OK_N_B800;" "" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 1 21:59:57 2023 InstallationDate: Installed on 2023-04-25 (37 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lpstat: device for OKI_C332_411ACB@oki-c332-411acb.local: implicitclass://OKI_C332_411ACB%40oki-c332-411acb.local/ Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Novatech N150ZU Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd'] failed with exit code 2: grep: /etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic root=UUID=2c0e4998-ac9a-4c3c-ab96-b2b45fe5eab7 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TNO dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Novatech dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Novatech dmi.chassis.version: N/A dmi.ec.firmware.release: 7.4 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TNO:bd06/24/2019:br7.7:efr7.4:svnNovatech:pnN150ZU:pvrNotApplicable:rvnNovatech:rnN150ZU:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Novatech To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2022107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021940] Re: firefox (114.0+build1-0ubuntu0.22.04.1~mt1) No GPU Hardware Acceleraton on Arm64
It has been fixed in the ppa now, closing
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
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/2021940
Title:
firefox (114.0+build1-0ubuntu0.22.04.1~mt1) No GPU Hardware
Acceleraton on Arm64
Status in firefox package in Ubuntu:
Fix Released
Bug description:
Ubuntu Jammy and Lunar. The latest upgrade to Firefox
114.0+build1-0ubuntu0.22.04.1~mt1 arm64 lead to GPU Hardware
Acceleration no longer available on Firefox. GPU Hardware
Acceleration is available on Firefox
113.0.2+build1-0ubuntu0.22.04.1~mt1 and earlier versions.
Could it be due to this:
* Install glxtest and vaapitest
Where it was not in Firefox 113.0.2+build1-0ubuntu0.22.04.1~mt1.
Publishing details
Published on 2023-05-30
Changelog
firefox (114.0+build1-0ubuntu0.23.04.1~mt1) lunar; urgency=medium
* New upstream release (114.0+build1)
* Install glxtest and vaapitest
- debian/firefox.install.in
{
"application": {
"name": "Firefox",
"osVersion": "Linux 5.15.112-ophub #1 SMP PREEMPT Wed May 17 22:26:56 EDT
2023",
"version": "114.0",
"buildID": "20230529085652",
"distributionID": "canonical",
"userAgent": "Mozilla/5.0 (X11; Ubuntu; Linux aarch64; rv:109.0)
Gecko/20100101 Firefox/114.0",
"safeMode": false,
"memorySizeBytes": 3498860544,
"diskAvailableBytes": 54004117504,
"supportURL": "https://support.mozilla.org/1/firefox/114.0/Linux/en-US/;,
"osTheme": "Yaru-dark / Yaru",
"numTotalWindows": 1,
"numFissionWindows": 1,
"numRemoteWindows": 1,
"fissionAutoStart": true,
"fissionDecisionStatus": "enabledByDefault",
"remoteAutoStart": true,
"policiesStatus": 0,
"keyLocationServiceGoogleFound": true,
"keySafebrowsingGoogleFound": true,
"keyMozillaFound": false
},
"securitySoftware": {
"registeredAntiVirus": "",
"registeredAntiSpyware": "",
"registeredFirewall": ""
},
"environmentVariables": {
"MOZ_ENABLE_WAYLAND": "1",
"DISPLAY": ":0",
"MOZ_APP_LAUNCHER": "/usr/bin/firefox",
"MOZ_ASSUME_USER_NS": "1",
"MOZ_LAUNCHED_CHILD": "",
"MOZ_APP_SILENT_START": "",
"XRE_PROFILE_PATH": "",
"XRE_PROFILE_LOCAL_PATH": "",
"XRE_START_OFFLINE": "",
"XRE_BINARY_PATH": "",
"XRE_RESTARTED_BY_PROFILE_MANAGER": ""
},
"modifiedPreferences": {
"accessibility.typeaheadfind.flashBar": 0,
"browser.contentblocking.category": "strict",
"browser.privatebrowsing.autostart": true,
"browser.search.region": "MY",
"browser.startup.homepage_override.mstone": "114.0",
"browser.startup.homepage_override.once":
"{\"message_id\":\"WNP_MOMENTS_14\",\"url\":\"https://www.mozilla.org/firefox/welcome/14\",\"expire\":166847040};,
"browser.startup.homepage_override.buildID": "20230529085652",
"browser.urlbar.quicksuggest.migrationVersion": 2,
"browser.urlbar.tipShownCount.searchTip_onboard": 4,
"browser.urlbar.quicksuggest.scenario": "history",
"browser.urlbar.placeholderName.private": "DuckDuckGo",
"doh-rollout.home-region": "MY",
"doh-rollout.balrog-migration-done": true,
"doh-rollout.doneFirstRun": true,
"extensions.lastAppVersion": "114.0",
"idle.lastDailyNotification": 1685513742,
"media.gmp-manager.lastEmptyCheck": 1685513619,
"media.gmp-manager.lastCheck": 1685513619,
"media.gmp-manager.buildID": "20230529085652",
"media.gmp.storage.version.observed": 1,
"network.dns.disablePrefetch": true,
"network.http.referer.disallowCrossSiteRelaxingDefault.top_navigation":
true,
"network.http.speculative-parallel-limit": 0,
"network.predictor.enabled": false,
"network.prefetch-next": false,
"places.database.lastMaintenance": 1685513742,
"privacy.purge_trackers.last_purge": "1685513742669",
"privacy.purge_trackers.date_in_cookie_database": "0",
"privacy.sanitize.pending":
"[{\"id\":\"shutdown\",\"itemsToClear\":[\"cache\",\"cookies\",\"offlineApps\"],\"options\":{}},{\"id\":\"newtab-container\",\"itemsToClear\":[],\"options\":{}}]",
"privacy.annotate_channels.strict_list.enabled": true,
"privacy.clearOnShutdown.downloads": false,
"privacy.clearOnShutdown.formdata": false,
"privacy.clearOnShutdown.history": false,
"privacy.clearOnShutdown.offlineApps": true,
"privacy.clearOnShutdown.sessions": false,
"privacy.donottrackheader.enabled": true,
"privacy.partition.network_state.ocsp_cache": true,
"privacy.query_stripping.enabled": true,
"privacy.query_stripping.enabled.pbmode": true,
"privacy.sanitize.sanitizeOnShutdown": true,
[Desktop-packages] [Bug 2022322] [NEW] Gnome right butons bug
Public bug reported: In the superior right corner, there are a region (about 5x5 cm2) that mouse do nothing, mainly in minimize and close butons, but ocouring to in menus, just in this corner. Double click in title bar force the restore and then, moving the software window to far of this corner, works properly. Thanks. Mr. Wagner Yaegashi 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 06:13:24 2023 DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804] InstallationDate: Installed on 2022-05-01 (396 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-13 (20 days ago) dmi.bios.date: 07/14/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04REP.035.210714.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP350XAA-KD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9477A0K-C01-G001-S0001+10.0.17134 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04REP.035.210714.ZW:bd07/14/2021:br5.12:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP04REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-KD1BR:rvrSGL9477A0K-C01-G001-S0001+10.0.17134:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PREP: dmi.product.family: Notebook 3 Series dmi.product.name: 340XAA/350XAA/550XAA dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP dmi.product.version: P04REP dmi.sys.vendor: SAMSUNG ELECTRONICS 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 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption lunar ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2022322 Title: Gnome right butons bug Status in xorg package in Ubuntu: New Bug description: In the superior right corner, there are a region (about 5x5 cm2) that mouse do nothing, mainly in minimize and close butons, but ocouring to in menus, just in this corner. Double click in title bar force the restore and then, moving the software window to far of this corner, works properly. Thanks. Mr. Wagner Yaegashi 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: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 06:13:24 2023 DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804] InstallationDate: Installed on 2022-05-01 (396 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks.
[Desktop-packages] [Bug 2022320] [NEW] the user logout and all activitities where lost, all applications where closed without saving
Public bug reported: here is a log part of the log I was training a neural network on my GPU when that happen. Jun 2 11:26:14 Experement snapd[1026]: devicemgr.go:2300: no NTP sync after 10m0s, trying auto-refresh anyway Jun 2 11:26:14 Experement snapd[1026]: autorefresh.go:594: Cannot prepare auto-refresh change: Post https://api.snapcraft.io/v2/snaps/refresh: dial tcp: lookup api.snapcraft.io: No address associated with hostname Jun 2 11:26:14 Experement snapd[1026]: stateengine.go:149: state ensure error: Post https://api.snapcraft.io/v2/snaps/refresh: dial tcp: lookup api.snapcraft.io: No address associated with hostname Jun 2 11:28:35 Experement google-chrome.desktop[2861]: [2854:2884:0602/112835.077228:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:29:22 Experement google-chrome.desktop[2861]: [2854:2884:0602/112922.423721:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:29:35 Experement google-chrome.desktop[2861]: [2854:2884:0602/112935.114565:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:29:50 Experement google-chrome.desktop[2861]: [2854:2884:0602/112950.414014:ERROR:registration_request.cc(251)] Registration URL fetching failed. Jun 2 11:30:01 Experement CRON[3581]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi) Jun 2 11:30:44 Experement google-chrome.desktop[2861]: [2854:2884:0602/113044.132395:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:30:51 Experement google-chrome.desktop[2861]: [2854:2884:0602/113051.623021:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:31:12 Experement systemd[1]: Started Run anacron jobs. Jun 2 11:31:12 Experement anacron[3582]: Anacron 2.3 started on 2023-06-02 Jun 2 11:31:12 Experement systemd[1]: Starting Cleanup of Temporary Directories... Jun 2 11:31:12 Experement anacron[3582]: Normal exit (0 jobs run) Jun 2 11:31:12 Experement systemd[1]: anacron.service: Deactivated successfully. Jun 2 11:31:12 Experement systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 2 11:31:12 Experement systemd[1]: Finished Cleanup of Temporary Directories. Jun 2 11:31:24 Experement google-chrome.desktop[2861]: [2854:2884:0602/113124.701284:ERROR:registration_request.cc(251)] Registration URL fetching failed. Jun 2 11:31:31 Experement google-chrome.desktop[2861]: [2854:2884:0602/113131.182781:ERROR:registration_request.cc(251)] Registration URL fetching failed. Jun 2 11:31:36 Experement google-chrome.desktop[2861]: [2854:2884:0602/113136.547141:ERROR:registration_request.cc(251)] Registration URL fetching failed. Jun 2 11:31:49 Experement google-chrome.desktop[2861]: [2854:2884:0602/113149.340472:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:38:35 Experement google-chrome.desktop[2861]: [2854:2884:0602/113835.095153:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:39:22 Experement google-chrome.desktop[2861]: [2854:2884:0602/113922.438095:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:39:35 Experement google-chrome.desktop[2861]: [2854:2884:0602/113935.128280:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:40:44 Experement google-chrome.desktop[2861]: [2854:2884:0602/114044.169402:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:40:51 Experement google-chrome.desktop[2861]: [2854:2884:0602/114051.659049:ERROR:checkin_request.cc(243)] Check-in request got net error: -105 Jun 2 11:41:49 Experement google-chrome.desktop[2861]: [2854:2884:0602/114149.373191:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105 Jun 2 11:42:07 Experement systemd[1209]: Started Application launched by gsd-media-keys. Jun 2 11:42:08 Experement dbus-daemon[1238]: [session uid=1000 pid=1238] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.104' (uid=1000 pid=3609 comm="/usr/bin/gnome-terminal.real --wait " label="unconfined") Jun 2 11:42:08 Experement systemd[1209]: Created slice Slice /app/org.gnome.Terminal. Jun 2 11:42:08 Experement systemd[1209]: Starting GNOME Terminal Server... Jun 2 11:42:08 Experement dbus-daemon[1238]: [session uid=1000 pid=1238] Successfully activated service 'org.gnome.Terminal' Jun 2 11:42:08 Experement systemd[1209]: Started GNOME Terminal Server. Jun 2 11:42:08 Experement systemd[1209]: Started VTE child process 3635 launched by gnome-terminal-server process 3612. Jun 2 11:45:11 Experement dbus-daemon[1238]: [session uid=1000 pid=1238] Activating service name='org.gnome.ControlCenter.SearchProvider'
[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
Till, sounds like we should at least SRU https://github.com/OpenPrinting/cups/commit/9b31bae and https://github.com/OpenPrinting/cups/commit/b0f1a00a to 22.04 to fix that issue, could you work on that and maybe check if that are more fixes worth SRUing as we do an upload? ** Changed in: cups (Ubuntu) Importance: Undecided => High ** Changed in: cups (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1971242 Title: printing PDF appears always grey, no color Status in CUPS: Fix Released Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020881] Re: Accessibility settings not persistent
Thank you for your bug report. Is the issue only about that option? Could you share the output of that command before and after restarting ? $ gsettings get org.gnome.desktop.a11y.keyboard mousekeys-enable ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020881 Title: Accessibility settings not persistent Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.2 LTS I enable Settings-Accessibility-Pointing and Clicking-Mouse Keys. This has to be enabled every time I boot up. This should persist. Previous Ubuntu versions retained this setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020245] Re: cannot login to different user - gdmflexiserver not found
it's not a gdm issue but a problem with lubuntu and the screensaver in use ** Package changed: gdm3 (Ubuntu) => xscreensaver (Ubuntu) -- 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/2020245 Title: cannot login to different user - gdmflexiserver not found Status in xscreensaver package in Ubuntu: New Bug description: when i want to start another user session from within the first one, i cannot do that. there is no option in the menu and from the lock-screen using the login button, it doesn't work because gdmflexiserver is not found . there is no package containing this command/binary *sigh* to make some fun out of this - wasn't linux been advertised as OS with multi-user/multi-session capability ? (which windows didn't have at that time?) seems that it's not important to many people.otherwise i can't explain, why this won't work by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/2020245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
This issue has sat with a status of 'Incomplete' for over three years now without any comment and did not expire due to the presence of a 'Bug watch'. Also the Ubuntu versions affected are all now out out of support so I'm closing the report as 'Invalid' as it no longer refers to any currently supported release of Ubuntu. Please feel free to re-open this bug report if this is still an issue when using a currently supported release of Ubuntu making sure that you tell us in which release(s) you still experience this issue. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Invalid Bug description: *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT* If you are having an issue and want it addressed, it is most helpful to file a new report. If you were led here by DisplayLink's website, you were led here in error as no useful debugging information has been provided by the original reporter, which is necessary to root cause, and solve the issue he reported. Posting comments about how you think you have the same problem isn't helpful here. My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020245] Re: cannot login to different user - gdmflexiserver not found
** Package changed: ubuntu => gdm3 (Ubuntu) -- 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/2020245 Title: cannot login to different user - gdmflexiserver not found Status in gdm3 package in Ubuntu: New Bug description: when i want to start another user session from within the first one, i cannot do that. there is no option in the menu and from the lock-screen using the login button, it doesn't work because gdmflexiserver is not found . there is no package containing this command/binary *sigh* to make some fun out of this - wasn't linux been advertised as OS with multi-user/multi-session capability ? (which windows didn't have at that time?) seems that it's not important to many people.otherwise i can't explain, why this won't work by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020881] Re: Accessibility settings not persistent
Further to comment #2, moving to gnome-settings-daemon. Possibly not the correct package but Ubuntu's Desktop Team will be made aware of the issue. ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2020881 Title: Accessibility settings not persistent Status in gnome-settings-daemon package in Ubuntu: New Bug description: Ubuntu 22.04.2 LTS I enable Settings-Accessibility-Pointing and Clicking-Mouse Keys. This has to be enabled every time I boot up. This should persist. Previous Ubuntu versions retained this setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2020881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 725792]
(In reply to Hossein from comment #26) > (In reply to خالد حسني from comment #25) > > This seems to be a more general issue, if one mixes RTL with LTR text or CTL > > with Asian or Latin, there will be a gap. My guess when the text is split > > into different portions the underline can be a little bit short (probably > > because of rounding). > Might be the case, because size of the gap changes in different zoom levels, > and it is something like one pixel or so. Indeed. > (In reply to خالد حسني from comment #24) > > *** Bug 155623 has been marked as a duplicate of this bug. *** > I think the above bug is different, because the gap is much bigger compared > to this one, and it would be hard to say that is because of rounding. You are right! I opened the file again and it looks very different than what I saw when I closed as duplicated. I wonder if I opened a different file by mistake. -- 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/725792 Title: [Upstream] Using numbers with RTL text breaks underline Status in LibreOffice: Confirmed Status in OpenOffice: New Status in abiword package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org Binary package hint: libreoffice 1) Natty: lsb_release -rd apDescription:Ubuntu Natty (development branch) Release:11.04 Maverick: lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 2) Natty: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu2 Candidate: 1:3.3.2-1ubuntu2 Version table: *** 1:3.3.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status Maverick: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu2~maverick1 Candidate: 1:3.3.2-1ubuntu2~maverick1 Version table: *** 1:3.3.2-1ubuntu2~maverick1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/725792/+attachment/1981833/+files/underlinebreak.odt && loimpress -nologo underlinebreak.odt all the characters on one line that are marked underlined have one, continuous underline. 4) What happens instead is that the underline breaks after a number. WORKAROUND: Use Abiword. Original Reporter Comments: -Write some underlined text in an RTL language(tested Hebrew and Arabic) -Write a number(still in the same underline) Result: the underline breaks. This does not happen in English. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openoffice.org-writer 1:3.2.1-7ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 NonfreeKernelModules: fglrx wl Architecture: amd64 Date: Sun Feb 27 00:18:21 2011 InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openoffice.org To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/725792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 725792]
(In reply to خالد حسني from comment #25) > This seems to be a more general issue, if one mixes RTL with LTR text or CTL > with Asian or Latin, there will be a gap. My guess when the text is split > into different portions the underline can be a little bit short (probably > because of rounding). Might be the case, because size of the gap changes in different zoom levels, and it is something like one pixel or so. (In reply to خالد حسني from comment #24) > *** Bug 155623 has been marked as a duplicate of this bug. *** I think the above bug is different, because the gap is much bigger compared to this one, and it would be hard to say that is because of rounding. -- 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/725792 Title: [Upstream] Using numbers with RTL text breaks underline Status in LibreOffice: Confirmed Status in OpenOffice: New Status in abiword package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org Binary package hint: libreoffice 1) Natty: lsb_release -rd apDescription:Ubuntu Natty (development branch) Release:11.04 Maverick: lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 2) Natty: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu2 Candidate: 1:3.3.2-1ubuntu2 Version table: *** 1:3.3.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status Maverick: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu2~maverick1 Candidate: 1:3.3.2-1ubuntu2~maverick1 Version table: *** 1:3.3.2-1ubuntu2~maverick1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/725792/+attachment/1981833/+files/underlinebreak.odt && loimpress -nologo underlinebreak.odt all the characters on one line that are marked underlined have one, continuous underline. 4) What happens instead is that the underline breaks after a number. WORKAROUND: Use Abiword. Original Reporter Comments: -Write some underlined text in an RTL language(tested Hebrew and Arabic) -Write a number(still in the same underline) Result: the underline breaks. This does not happen in English. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openoffice.org-writer 1:3.2.1-7ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 NonfreeKernelModules: fglrx wl Architecture: amd64 Date: Sun Feb 27 00:18:21 2011 InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openoffice.org To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/725792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 725792]
This seems to be a more general issue, if one mixes RTL with LTR text or CTL with Asian or Latin, there will be a gap. My guess when the text is split into different portions the underline can be a little bit short (probably because of rounding). -- 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/725792 Title: [Upstream] Using numbers with RTL text breaks underline Status in LibreOffice: Confirmed Status in OpenOffice: New Status in abiword package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org Binary package hint: libreoffice 1) Natty: lsb_release -rd apDescription:Ubuntu Natty (development branch) Release:11.04 Maverick: lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 2) Natty: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu2 Candidate: 1:3.3.2-1ubuntu2 Version table: *** 1:3.3.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status Maverick: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu2~maverick1 Candidate: 1:3.3.2-1ubuntu2~maverick1 Version table: *** 1:3.3.2-1ubuntu2~maverick1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/725792/+attachment/1981833/+files/underlinebreak.odt && loimpress -nologo underlinebreak.odt all the characters on one line that are marked underlined have one, continuous underline. 4) What happens instead is that the underline breaks after a number. WORKAROUND: Use Abiword. Original Reporter Comments: -Write some underlined text in an RTL language(tested Hebrew and Arabic) -Write a number(still in the same underline) Result: the underline breaks. This does not happen in English. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openoffice.org-writer 1:3.2.1-7ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 NonfreeKernelModules: fglrx wl Architecture: amd64 Date: Sun Feb 27 00:18:21 2011 InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openoffice.org To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/725792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 725792]
*** Bug 155623 has been marked as a duplicate of this bug. *** -- 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/725792 Title: [Upstream] Using numbers with RTL text breaks underline Status in LibreOffice: Confirmed Status in OpenOffice: New Status in abiword package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org Binary package hint: libreoffice 1) Natty: lsb_release -rd apDescription:Ubuntu Natty (development branch) Release:11.04 Maverick: lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 2) Natty: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu2 Candidate: 1:3.3.2-1ubuntu2 Version table: *** 1:3.3.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status Maverick: apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu2~maverick1 Candidate: 1:3.3.2-1ubuntu2~maverick1 Version table: *** 1:3.3.2-1ubuntu2~maverick1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/725792/+attachment/1981833/+files/underlinebreak.odt && loimpress -nologo underlinebreak.odt all the characters on one line that are marked underlined have one, continuous underline. 4) What happens instead is that the underline breaks after a number. WORKAROUND: Use Abiword. Original Reporter Comments: -Write some underlined text in an RTL language(tested Hebrew and Arabic) -Write a number(still in the same underline) Result: the underline breaks. This does not happen in English. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openoffice.org-writer 1:3.2.1-7ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 NonfreeKernelModules: fglrx wl Architecture: amd64 Date: Sun Feb 27 00:18:21 2011 InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: openoffice.org To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/725792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021528] Re: Update evolution-data-server to 3.48.2
This bug was fixed in the package evolution-data-server - 3.48.2-1 --- evolution-data-server (3.48.2-1) unstable; urgency=medium [ Amin Bandali ] * New upstream release (LP: #2021528) - Bug Fixes: + Camel: Set proper S/MIME signature verification status (https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/474) + IMAP: Cannot remove labels added in Thunderbird (https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/478) + WebDAV: Fails to discover iCloud address book (https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/479) + Wrong S/MIME certificate selection for encrypted email (https://gitlab.gnome.org/GNOME/evolution/-/issues/2345) [ Jeremy Bícha ] * Release to unstable -- Amin Bandali Mon, 29 May 2023 14:53:31 -0400 ** Changed in: evolution-data-server (Ubuntu) Status: Fix Committed => Fix Released ** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #474 https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/474 ** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #478 https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/478 ** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #479 https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/479 ** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #2345 https://gitlab.gnome.org/GNOME/evolution/-/issues/2345 -- 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/2021528 Title: Update evolution-data-server to 3.48.2 Status in evolution-data-server package in Ubuntu: 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.2/NEWS It is required to update the evolution app to 3.48.2 (LP: #) 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/2021528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
Should be this change: Fixed default color settings for CMYK printers as well (Issue #500) -- 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/1971242 Title: printing PDF appears always grey, no color Status in CUPS: Fix Released Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021484] Re: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway
Hello Seth. It can be edited, and even removed. More info that might be useful: I recently made some changes to limit the number of login attempts: sudo nano /etc/pam.d/common-auth auth[success=1 default=ignore] pam_unix.so nullok_secure authrequiredpam_deny.so authrequired pam_faillock.soonerr=fail deny=3 unlock_time=30 authrequiredpam_permit.so Another change was to set Wayland as Windowing System. Don't hesitate to ask me more info. Thanks for your time. -- 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/2021484 Title: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway Status in ubuntu-settings package in Ubuntu: Incomplete Bug description: I'm logged as a normal user without admin privileges. When I try to edit a VPN I'm asked to introduce the credentials of the admin, nevertheless if I click cancel I can still access to the VPN configuration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-settings 20.04.6 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 29 11:16:38 2023 InstallationDate: Installed on 2022-05-04 (389 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2021484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
