[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Also be careful to not get confused with bug 1878076. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007262] Re: Ubuntu's GNOME desktop is higher latency than necessary
** Also affects: mutter (Ubuntu Lunar) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Kinetic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Kinetic) Status: New => Triaged ** Changed in: mutter (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Jammy) Status: New => Triaged -- 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/2007262 Title: Ubuntu's GNOME desktop is higher latency than necessary Status in mutter package in Ubuntu: In Progress Status in mutter source package in Jammy: Triaged Status in mutter source package in Kinetic: Triaged Status in mutter source package in Lunar: In Progress Bug description: [ Impact ] Ubuntu's GNOME desktop is higher latency than necessary. It's stuck in triple buffering when it should be dropping to double buffering during light rendering. [ Test Plan ] 1. Add this to /etc/environment: MUTTER_DEBUG=kms 2. Reboot and log into a Wayland session. 3. Open a Terminal and run: journalctl -f /usr/bin/gnome-shell | grep 'Swap buffers' 4. Drag the Terminal window rapidly with the mouse (a high sample rate mouse will also help). Observed bug: "KMS: Swap buffers: 2 frames pending (triple-buffering)" Expected fix: "KMS: Swap buffers: 1 frames pending (double-buffering)" If you don't at first confirm the bug prior to the fix then try dragging the window to the top bar before wiggling it or opening the overview to make the render load higher. The fix will make the log messages return to double buffering much sooner and stay there more reliably. [ Where problems could occur ] Any part of the smoothness of the desktop experience could be impacted since the fix involves changing the frame clock for frame scheduling. [ Other Info ] Upstream fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441/diffs?commit_id=17ea73d0570318926899c4e3e4821a8b7b21edae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
A draft fix for GTK4 is here: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4945 ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Triaged ** Changed in: gtk4 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Status in gtk4 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Sounds like you mean https://gitlab.gnome.org/GNOME/gtk/-/issues/4880 .. If that does fix this issue then it will be in GTK 4.7.2/4.8.0 and later, which is already in Ubuntu 22.10 and later. But that requires apps to use GTK4 instead of GTK3 in order to get the fix. So no there is no definite plan for this bug, but Ubuntu 22.04 is supported for another 9 years so never say never. ** Changed in: gtk4 (Ubuntu Kinetic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4880 https://gitlab.gnome.org/GNOME/gtk/-/issues/4880 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/4880 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end
While 22.04 isn't fixed yet, please try editing /etc/environment and add: MESA_LOADER_DRIVER_OVERRIDE=i965 then reboot. It might be a suitable workaround. ** Changed in: mesa (Ubuntu Jammy) Importance: Undecided => High -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Triaged Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
I see that there's an upstream patch that's apparently pending. Do we know when that'll make it into the distro? Will it enter 22.04 LTS or miss it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007381] Re: Xorg freeze
Thanks for the bug report. Please check for crashes by following these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment But judging by the model of CPU and the version of Ubuntu, I think you're most likely to be experiencing bug 1972977. P.S. Your changes in 20-intel.conf are not usually recommended because Driver "intel" is deprecated and causes serious issues on newer Intel systems. On this machine however, it's probably fine and might even be a workaround to bug 1972977. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2007381 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and flashing cursor in top corner then stopped and started again with log in screen. As duel boot started laptop in Windows 10 and no problems so software problem. Reseached and found a fix which was putting in file, 1 - Creating a file "/etc/X11/xorg.conf.d/20-intel.conf" Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection This seems to have fixed the problem. I was running System Profile to watch Temps and also Mate System monitor with Firefox in the background. It did for a moment give a black screen but recovered so not sure if this was the problem resurfacing. Without this being a duel boot I would have had great difficulty identifying if it was software or a overheating/grapics card problem. Most users would scrap their hardware if they were presented with this problem. Hopefully my problem is fixed but if not could you please advise me further. All the Best DAvid ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Wed Feb 15 12:00:06 2023 DistUpgraded: 2022-08-17 16:23:45,139 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.15.0-58-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.15.0-60-generic, x86_64: installed rtl8821ce/5.5.2.1, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [1179:ff50] Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1179:ff50] InstallationDate: Installed on 2021-08-21 (542 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: TOSHIBA Satellite M300 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=98dc102b-f3cc-4067-b9a3-75250f24163c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-08-17 (181 days ago) dmi.bios.date: 03/13/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.80 dmi.board.name: Satellite M300 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.80:bd03/13/2008:svnTOSHIBA:pnSatelliteM300:pvrPSMD0L-01N00M:rvnTOSHIBA:rnSatelliteM300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:sku: dmi.product.name: Satellite M300 dmi.product.version: PSMD0L-01N00M dmi.sys.vendor: TOSHIBA 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.3-2ubuntu2.7 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:
[Desktop-packages] [Bug 2007268] Re: Backlight does not turn off during screen blanking
*** This bug is a duplicate of bug 2003237 *** https://bugs.launchpad.net/bugs/2003237 /home/manveru/.local/share/gnome-shell/extensions/multi-monitors-add- on@spin83 is logging a lot of errors so is likely to cause bugs. Please remove unsupported extensions: cd ~/.local/share/gnome-shell rm -rf extensions and then log in again to confirm if the bug still occurs. Your log also shows that prior to using MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 you were experiencing bug 1968040. So at least that should be fixed now. -- 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/2007268 Title: Backlight does not turn off during screen blanking Status in mutter package in Ubuntu: Incomplete Bug description: In the 2022/2023 energy crisis era, this shall not happen. But... I haven't found solution other than "switch to X", which is not an options with my scaling settings for both 4K screens I'm using. On idle when the system blanks screen backlight remains on, wasting energy and burning LEDs in my screens. Please provide solution that would let Gnome set DPMS properly and actually send screens to proper sleep when OS goes idle (enables screen saver). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.20.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 11:59:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-58-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-60-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev d1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2023-01-04 (40 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zrhf1w@/vmlinuz-5.15.0-58-generic root=ZFS=rpool/ROOT/ubuntu_zrhf1w ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO 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.3-2ubuntu2.7 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007485] Re: [Precision 7920 Tower, Realtek ALC3234, Speaker, Internal] No sound at all
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- 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/2007485 Title: [Precision 7920 Tower, Realtek ALC3234, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I am not able to hear any sound from my Dell Precision Tower 7920 running Ubuntu 22.04. I have performed all the basic tests listed here: https://help.ubuntu.com/community/SoundTroubleshooting Thanks. Piyoosh ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jays2422197 F pulseaudio /dev/snd/pcmC0D0p: jays2422197 F...m pulseaudio /dev/snd/controlC1: jays2422197 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 23:47:01 2023 InstallationDate: Installed on 2023-01-24 (22 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jays2422197 F pulseaudio /dev/snd/pcmC0D0p: jays2422197 F...m pulseaudio /dev/snd/controlC1: jays2422197 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Precision 7920 Tower, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2022 dmi.bios.release: 2.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.29.0 dmi.board.name: 0RV0G2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.29.0:bd12/15/2022:br2.29:svnDellInc.:pnPrecision7920Tower:pvr:rvnDellInc.:rn0RV0G2:rvrA01:cvnDellInc.:ct3:cvr:sku073A: dmi.product.family: Precision dmi.product.name: Precision 7920 Tower dmi.product.sku: 073A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007485] [NEW] [Precision 7920 Tower, Realtek ALC3234, Speaker, Internal] No sound at all
Public bug reported: I am not able to hear any sound from my Dell Precision Tower 7920 running Ubuntu 22.04. I have performed all the basic tests listed here: https://help.ubuntu.com/community/SoundTroubleshooting Thanks. Piyoosh ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jays2422197 F pulseaudio /dev/snd/pcmC0D0p: jays2422197 F...m pulseaudio /dev/snd/controlC1: jays2422197 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 23:47:01 2023 InstallationDate: Installed on 2023-01-24 (22 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jays2422197 F pulseaudio /dev/snd/pcmC0D0p: jays2422197 F...m pulseaudio /dev/snd/controlC1: jays2422197 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Precision 7920 Tower, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2022 dmi.bios.release: 2.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.29.0 dmi.board.name: 0RV0G2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.29.0:bd12/15/2022:br2.29:svnDellInc.:pnPrecision7920Tower:pvr:rvnDellInc.:rn0RV0G2:rvrA01:cvnDellInc.:ct3:cvr:sku073A: dmi.product.family: Precision dmi.product.name: Precision 7920 Tower dmi.product.sku: 073A dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2007485 Title: [Precision 7920 Tower, Realtek ALC3234, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I am not able to hear any sound from my Dell Precision Tower 7920 running Ubuntu 22.04. I have performed all the basic tests listed here: https://help.ubuntu.com/community/SoundTroubleshooting Thanks. Piyoosh ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jays2422197 F pulseaudio /dev/snd/pcmC0D0p: jays2422197 F...m pulseaudio /dev/snd/controlC1: jays2422197 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 23:47:01 2023 InstallationDate: Installed on 2023-01-24 (22 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jays2422197 F pulseaudio /dev/snd/pcmC0D0p: jays2422197 F...m pulseaudio /dev/snd/controlC1: jays2422197 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Precision 7920 Tower, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2022 dmi.bios.release: 2.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.29.0 dmi.board.name: 0RV0G2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.29.0:bd12/15/2022:br2.29:svnDellInc.:pnPrecision7920Tower:pvr:rvnDellInc.:rn0RV0G2:rvrA01:cvnDellInc.:ct3:cvr:sku073A: dmi.product.family: Precision dmi.product.name: Precision 7920 Tower dmi.product.sku: 073A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007485/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 2006756] Autopkgtest regression report (pango1.0/1.50.6+ds-2ubuntu1)
All autopkgtests for the newly accepted pango1.0 (1.50.6+ds-2ubuntu1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/1:7.3.7-0ubuntu0.22.04.1 (arm64) libreoffice/unknown (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#pango1.0 [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 pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: Fix Committed Bug description: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004021] Re: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio)
** Also affects: gstreamer (Ubuntu) Importance: Undecided Status: New ** Also affects: gstreamer via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2004021 Title: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio) Status in GStreamer: Unknown Status in Totem: Fix Released Status in gstreamer package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: When playing videos in 22.04, moving the position will often cause the video to stop. The audio will work as expected. I found mention of this behavior here as well: https://gitlab.gnome.org/GNOME/totem/-/issues/526 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/2004021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1031.35)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1031.35) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) 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#linux-restricted-modules-aws [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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1020.21~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 (5.19.0-1020.21~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) 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#linux-restricted-modules-aws-5.19 [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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-oem-5.17/5.17.0-1028.29)
All autopkgtests for the newly accepted linux-restricted-modules-oem-5.17 (5.17.0-1028.29) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) 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#linux-restricted-modules-oem-5.17 [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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1021.22~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 (5.19.0-1021.22~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) 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#linux-restricted-modules-azure-5.19 [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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
debdiff for jammy ** Patch added: "pulseaudio_15.99.1+dfsg1-1ubuntu2.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007331/+attachment/5647523/+files/pulseaudio_15.99.1+dfsg1-1ubuntu2.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Confirmed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
debdiff for kinetic ** Patch added: "pulseaudio_16.1+dfsg1-1ubuntu3.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007331/+attachment/5647522/+files/pulseaudio_16.1+dfsg1-1ubuntu3.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Confirmed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
debdiff for lunar ** Patch added: "pulseaudio_16.1+dfsg1-2ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007331/+attachment/5647521/+files/pulseaudio_16.1+dfsg1-2ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Confirmed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
The feature not working for snaps is unsurprising but also an important one for us to track. Please either create a new bug for that or reopen and reword this bug to be about snapped apps only. ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: Incomplete => Invalid ** Changed in: xwayland (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-510 package in Ubuntu: Invalid Status in xwayland package in Ubuntu: Invalid Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6221 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6221 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6221 Importance: Unknown Status: Unknown -- 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/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in GNOME Shell: Unknown Status in Mutter: Fix Released Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-525 package in Ubuntu: Triaged Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1739635] Re: Can we please get Mouse Acceleration as a GUI control?
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #94 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/94 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/94 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1739635 Title: Can we please get Mouse Acceleration as a GUI control? Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Can we please get a GUI control for adjusting and turning off Mouse Acceleration? This is really important for gaming. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 21 08:54:59 2017 InstallationDate: Installed on 2015-07-20 (884 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1739635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1739635] Re: Can we please get Mouse Acceleration as a GUI control?
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1739635 Title: Can we please get Mouse Acceleration as a GUI control? Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Can we please get a GUI control for adjusting and turning off Mouse Acceleration? This is really important for gaming. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 21 08:54:59 2017 InstallationDate: Installed on 2015-07-20 (884 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1739635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785692] Re: [Feature Request] Mouse Acceleration controls
*** This bug is a duplicate of bug 1739635 *** https://bugs.launchpad.net/bugs/1739635 ** This bug has been marked a duplicate of bug 1739635 Can we please get Mouse Acceleration as a GUI control? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1785692 Title: [Feature Request] Mouse Acceleration controls Status in gnome-control-center package in Ubuntu: New Bug description: Can we please get the ability to adjust Mouse Acceleration back? This is important for touchpads and gaming on Linux (yes, that's a thing). It's not exactly a complicated feature to re-add, and I'm not even sure why it was removed in the first place. Users need a GUI way to set this that is consistent. The community methods are hacky and inconsistent. Please? :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
Thanks for the latest test, M.Hanny Sabbagh. A rewritten patch is now on its way to the coming Ubuntu 23.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings
I'm still seeing the bug in a clean install of Xubuntu 22.04.1 ...with additional problems that I assume are related, such as choosing "change layout option" to be "both alt together" lets me switch from the second layout in my list to the first layout, but not from the first layout back to the second layout. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier in Ubuntu. https://bugs.launchpad.net/bugs/1805197 Title: cannot switching keyboard layout with xfce4-keyboard-settings Status in Xfce4 Settings: Confirmed Status in libxklavier package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: Triaged Bug description: This is on xubuntu 18.04: With xfce4-keyboard-settings I have loaded the keyboard layouts "English (US)" and "German". Both are listed in the "Keybord layout" table. When I change the order with [key up] or [key down] nothing happens, I still have the old keyboard layout active. To switch the layout I have to DELETE the other one! This was not the case with xubuntu 16.04: just changing the order was sufficent there. To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
@Egmont: Thank you for the valuable feedback. First I would like to ask you to forgive me if some of my words are not clear or vague; I am not a native English speaker so it is a little bit hard when I write long responses like this. I hope I am correctly delivering my ideas to you and others. I just would like to confirm again that my proposal is related to changing the default text behavior in VTE *only for Arabic/RTL-based languages*. Languages like Arabic, Persian, Urdu, Hebrew... etc and only these. Other users of English, French, Italian and other languages do not need to endure this change (because they do not need autodetection or RTL text). Hence, we are talking about a change that would not affect 95% of the user base. I understand your concern and that we may still need to do further testing. And I will work on providing more test cases for various applications. Still, I wholeheartedly believe that any Arabic/RTL user would be quite happy with this proposed change because it makes the RTL text rendering so much better regardless of the application, terminal emulator or Linux distribution used. (I will provide more of these examples). Ideally, there shouldn't be a text in other languages when the system language is set to Arabic. E.g the output of "apt" should be fully translated to Arabic, and the interface text for "nano" should be translated too, which ultimately should result in a much better UX for Arabic users. That is, the entire command line interface be translated to Arabic and supportive of RTL text. Everything from Python/C/Rush syntax errors or outputs, all the way up to tools like apt, nano, vi or emacs. This is a very long journey and it may take many years until we reach that point. However, in order to get there, we need to start somewhere. One of the main reasons perhaps why no Arabic users provided feedback all these years is that Arabic or RTL support needs a huge investment in terms of effort to make it feasible for the end user. And so far no one stepped up to do that effort. We need efforts in both the fields of translation + RTL support to make this happen. Sadly, we are missing on both. I believe if we succeed in supporting RTL applications in the terminal and fixing the bugs we are currently facing, then this could open the door for a wide range of CLI-based computing for RTL languages speakers. We could have command line tools that fully support these languages (even RTL TUIs!), instead of just English as we have today. We could finally print correctly formatted Python error messages in Arabic instead of being afraid to translate it; because we know it wouldn't render correctly in the LTR terminal. I want to add a few additional reasons on why feedback is small regarding your work on RTL: - I honestly didn't hear about it although I am invested in Linux and open source software for 13 years in the Arabic Linux communities. I was surprised to know that RTL support is already there in VTE. I think that I came across a social media post once that talks about it in 2020, but because of Coronavirus and how all of our lives were missed up, I just couldn't give it enough attention at that time. - The political factor is also important. I don't want to talk about politics here of course, but currently, all RTL-speaking nations are in chaos; the middle east is full of wars and issues (Arabic), and the people of Iran (Persian) have their issues too. Afghanistan/Pakistan both have their problems as well with the recent events (Urdu), Israel (Hebrew)... And so on. In such circumstances, the interest in open source software or Linux, yet in terminal-based applications, or even more in bugs related to text rendering (RTL) in the terminal, would be quite small and considered to be luxurious for most people. The open source userbase from these countries in general is already small, so it's rare to find someone capable of following these topics and providing further feedback. I am writing this reply to you from Turkey, where 40K people were killed last week in the earthquake that happened (also in Syria). So overall, nothing is stable in these lands, including the land itself. - The dominant majority of Arabic users at least are using English as a system-wide language. When I made polls asking them why, they say that there are many bugs and problems in Arabic support in general on Linux, so they just give up on the whole thing and decide to use English everywhere, although it is not their main language. (For such users btw, our proposal does not affect them). - I would like to repeat the fact that the Arabic/RTL-based languages user base is quite small; I rarely see someone using Linux here (other than developers). Most people use Windows or macOS just like everywhere. However, if we wanted to promote Linux more in these communities, then we need to make sure that there are no blocking bugs or issues related to Arabic with open source software. And
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "nano output with autodetect.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5647494/+files/nano%20output%20with%20autodetect.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "cat output with autodetect.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5647491/+files/cat%20output%20with%20autodetect.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "cat output with LTR.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5647492/+files/cat%20output%20with%20LTR.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
** Attachment added: "nano output with LTR.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5647493/+files/nano%20output%20with%20LTR.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE
@Gunnar: Thank you for the continous help. I have tested the new update and indeed it now respects the font size of Monospace font in GNOME Tweaks (image attached). Thanks again! ** Attachment added: "gnome-terminal new monospace.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+attachment/5647490/+files/gnome-terminal%20new%20monospace.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
It was reported more than a year ago. Will it be fixed? Why is it "Unassigned"? Is somebody working on it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
Feature Freeze Exceptions are for the development release of Ubuntu and
only necessary after Feature Freeze which for the Lunar Lobster is
February 23th. Is this feature change intended for Lunar?
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[FeatureFreeze Exceptions] Support to install nvidia driver by
allowing list
Status in OEM Priority Project:
Incomplete
Status in ubuntu-drivers-common package in Ubuntu:
Incomplete
Bug description:
> If the upload is a new upstream microrelease, the relevant part of
the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom
file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in
the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for
more details.
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows
"DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when
enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it
shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed
[Desktop-packages] [Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
Confirmed, Ubutu 22.10 fresh installation. Login language not changed with the keyboard. Default language setting doesn't work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language Status in gdm: New Status in GNOME Screensaver: New Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Unity: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Lock screen (gnome-screensaver) uses last active window's language (keyboard layout) instead of default keyboard language. Steps to reproduce this bug: 1. In the system Text Entry settings: 1a. add two or more languages to the input sources list, e.g. English (as first and default) and Russian (as second); 1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock). 1c. Select "Allow different sources for each window" radio button. 1d. Select "New windows use the default source" radio button. 2. Run any application (e.g. gedit) and switch keyboard to second input language (Russian). 3. Lock the screen (Ctrl+Alt+L) or just wait idle time. 4. See what language set by default for password input in the lock screen. Expected: lock screen uses first input language (English) by default. What happened instead: lock screen uses last active window's language (Russian). Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds) gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1286910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language Status in gdm: New Status in GNOME Screensaver: New Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Unity: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Lock screen (gnome-screensaver) uses last active window's language (keyboard layout) instead of default keyboard language. Steps to reproduce this bug: 1. In the system Text Entry settings: 1a. add two or more languages to the input sources list, e.g. English (as first and default) and Russian (as second); 1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock). 1c. Select "Allow different sources for each window" radio button. 1d. Select "New windows use the default source" radio button. 2. Run any application (e.g. gedit) and switch keyboard to second input language (Russian). 3. Lock the screen (Ctrl+Alt+L) or just wait idle time. 4. See what language set by default for password input in the lock screen. Expected: lock screen uses first input language (English) by default. What happened instead: lock screen uses last active window's language (Russian). Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds) gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1286910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002941] Re: [BPO] libreoffice 7.4.4 for jammy
Yes, the s390x builder are quire unhappy for some time. So I agree there is no point to keep this open. ** Changed in: libreoffice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/2002941 Title: [BPO] libreoffice 7.4.4 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+sourcepub/14441833/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20230117_121308_55f21@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20230117_004531_c08ab@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/armhf/libr/libreoffice/20230117_192827_df4b4@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20230116_230929_28cc3@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20230117_034834_09f33@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2002941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002941] Re: [BPO] libreoffice 7.4.4 for jammy
The s390 build seems completely broken, most likely due to no fault of the libreoffice package; the infrastructure seems to be broken, as it repeatedly fails to build and also fails to produce any build log. @ricotz do you want to mark this as fix-released since the other archs are completed and published? -- 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/2002941 Title: [BPO] libreoffice 7.4.4 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1542/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+sourcepub/14441833/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/amd64/libr/libreoffice/20230117_121308_55f21@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/arm64/libr/libreoffice/20230117_004531_c08ab@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/armhf/libr/libreoffice/20230117_192827_df4b4@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/ppc64el/libr/libreoffice/20230116_230929_28cc3@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-ppa/jammy/s390x/libr/libreoffice/20230117_034834_09f33@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2002941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Can confirm the bug on HP Envy 15t-ew000. However I searched the web for a solution and it seems like someone on the hp forums might have gotten it to work by writing a custom patch for the kernel as given here https://lore.kernel.org/lkml/20220811053950.11810-1-faenkhau...@gmail.com/ Source: https://h30434.www3.hp.com/t5/Notebook-Audio/No-sound-from-internal-speakers-using-Linux/m-p/8601304/highlight/true#M120589 -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide
** Tags removed: server-triage-discuss -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007413] Re: specifying number of copies doesn't work
** Attachment added: "printers.conf" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2007413/+attachment/5647479/+files/printers.conf -- 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/2007413 Title: specifying number of copies doesn't work Status in cups package in Ubuntu: New Bug description: When printing to the printer "m479" shown in the attached config files, specifying the number of copies to print doesn't work, i.e., I always get one copy. This is true both from GUI print dialogs and from lp on the command line. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 11:18:58 2023 InstallationDate: Installed on 2019-01-02 (1505 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for driverless: dnssd://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipp._tcp.local/?uuid=4fdf33cc-d7b2-45f9-9abe-dae7fdcadfd0 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for m479: dnssd://HP%20Color%20LaserJet%20Pro%20M478f-9f%20%5B3279B8%5D._ipp._tcp.local/?uuid=79d14a5b-3a77-5110-ffd7-f7efed848aa6 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/driverless.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/m479.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/driverless.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/m479.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2007413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007413] [NEW] specifying number of copies doesn't work
Public bug reported: When printing to the printer "m479" shown in the attached config files, specifying the number of copies to print doesn't work, i.e., I always get one copy. This is true both from GUI print dialogs and from lp on the command line. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 11:18:58 2023 InstallationDate: Installed on 2019-01-02 (1505 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for driverless: dnssd://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipp._tcp.local/?uuid=4fdf33cc-d7b2-45f9-9abe-dae7fdcadfd0 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for m479: dnssd://HP%20Color%20LaserJet%20Pro%20M478f-9f%20%5B3279B8%5D._ipp._tcp.local/?uuid=79d14a5b-3a77-5110-ffd7-f7efed848aa6 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/driverless.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/m479.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/driverless.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/m479.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2007413 Title: specifying number of copies doesn't work Status in cups package in Ubuntu: New Bug description: When printing to the printer "m479" shown in the attached config files, specifying the number of copies to print doesn't work, i.e., I always get one copy. This is true both from GUI print dialogs and from lp on the command line. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 11:18:58 2023 InstallationDate: Installed on 2019-01-02 (1505 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for driverless: dnssd://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipp._tcp.local/?uuid=4fdf33cc-d7b2-45f9-9abe-dae7fdcadfd0 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for m479: dnssd://HP%20Color%20LaserJet%20Pro%20M478f-9f%20%5B3279B8%5D._ipp._tcp.local/?uuid=79d14a5b-3a77-5110-ffd7-f7efed848aa6 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/driverless.ppd', '/etc/cups/ppd/duplex.ppd', '/etc/cups/ppd/m479.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/driverless.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied grep: /etc/cups/ppd/m479.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
[Desktop-packages] [Bug 2007411] [NEW] gnome-control-center-goa-helper hangs after toggling a rocker switch
Public bug reported: 1. Open Settings. 2. Go to Online Accounts. 3. Add a Google account, or if you already have one, click on it, to open the Google Account window. 4. Toggle one of the rocker switches from on to off or vice versa. 5. Observe that at this point the window becomes unresponsive and can't be closed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 11:15:03 2023 InstallationDate: Installed on 2019-01-02 (1505 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2007411 Title: gnome-control-center-goa-helper hangs after toggling a rocker switch Status in gnome-control-center package in Ubuntu: New Bug description: 1. Open Settings. 2. Go to Online Accounts. 3. Add a Google account, or if you already have one, click on it, to open the Google Account window. 4. Toggle one of the rocker switches from on to off or vice versa. 5. Observe that at this point the window becomes unresponsive and can't be closed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 15 11:15:03 2023 InstallationDate: Installed on 2019-01-02 (1505 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2007411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004021] Re: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio)
The issue mentioned in issue/526 gives a very detailed description of the issue: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 ** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #1477 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2004021 Title: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio) Status in Totem: Fix Released Status in totem package in Ubuntu: New Bug description: When playing videos in 22.04, moving the position will often cause the video to stop. The audio will work as expected. I found mention of this behavior here as well: https://gitlab.gnome.org/GNOME/totem/-/issues/526 To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/2004021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide
** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004021] Re: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio)
There is a fix for this? As of today (2-15-2022) my fully-patched 22.04 instance still suffers from this issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2004021 Title: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio) Status in Totem: Fix Released Status in totem package in Ubuntu: New Bug description: When playing videos in 22.04, moving the position will often cause the video to stop. The audio will work as expected. I found mention of this behavior here as well: https://gitlab.gnome.org/GNOME/totem/-/issues/526 To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/2004021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006756] Re: composite emoji shows extra vertical color lines
I installed pango 1.50.6+ds-2ubuntu1 on Ubuntu 22.04 LTS and successfully completed the test case. ** 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 pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006756 Title: composite emoji shows extra vertical color lines Status in pango1.0 package in Ubuntu: Fix Released Status in pango1.0 source package in Jammy: Fix Committed Bug description: Impact -- Composite emoji (such as [Rightwards Hand: Medium-Dark Skin Tone]) are not rendered correctly. By "composite emoji", I mean emoji that are made up of multiple Unicode characters joined by "ZWJ". Composite emoji are used for skin tones, gender, flags, and a few other emoji. The incorrect rendering can be seen in Ubuntu 22.04's default text editor, gedit, as extra vertical red and black lines after the character. Screenshot attached. Test Case - Install the update Close Text Editor if it is open Open Text Editor Paste this character in Text Editor: It should display correctly without any extra vertical lines after it. Other Info -- This was originally noticed while verifying https://launchpad.net/bugs/1990677 What Could Go Wrong --- This is a one line fix cherry-picked from pango 1.50.8 (plus 30+ lines for a test case). pango is a text rendering library in GTK. GTK is used for most of the apps in the default install for Ubuntu Desktop and several other Ubuntu desktop flavors. pango is also used by mutter which is a key component of GNOME Shell which provides the basic desktop environment for default Ubuntu. A critical enough bug in pango could make the desktop and apps unusuable because text wouldn't be readable. This is mitigated through build tests and autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/2006756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990200] Re: goa-daemon crashed with SIGABRT
Since the update, I've suspended and woken up the computer numerous times, and I haven't seen the error once. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librest in Ubuntu. https://bugs.launchpad.net/bugs/1990200 Title: goa-daemon crashed with SIGABRT Status in gnome-online-accounts: New Status in gnome-online-accounts package in Ubuntu: Invalid Status in librest package in Ubuntu: Fix Released Status in librest source package in Kinetic: Fix Committed Bug description: * Impact The gnome-online-accounts sometime crash after resuming from suspend * Test case Install the librest update, restart your system and verify that configured online accounts keep working. Taking a Google account example, calendar events should show in gnome-calendar and the top panel widget, evolution should list your email account and nautilus should be able to browse your gdrive folder. We should also confirm that error reports stop with the library update * Regression potential The patch makes the code better handle an empty payload. The librest rdepends in the archive are gnome-initial-setup/gnome-online- accounts/gnome-maps so we should verify that those keep working as expected. - Unknown cause of this crash. Was alerted to it after waking the system from sleep mode. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 Date: Mon Sep 19 19:26:29 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-09-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () at /lib/x86_64-linux-gnu/librest-1.0.so.0 () at /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT 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/gnome-online-accounts/+bug/1990200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007381] Re: Xorg freeze
Additional info, not sure if it has any relivance but the last update installed a new wi fi driver for RTL8821CE card. It seemed to take a very long time to install. -- 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/2007381 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and flashing cursor in top corner then stopped and started again with log in screen. As duel boot started laptop in Windows 10 and no problems so software problem. Reseached and found a fix which was putting in file, 1 - Creating a file "/etc/X11/xorg.conf.d/20-intel.conf" Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection This seems to have fixed the problem. I was running System Profile to watch Temps and also Mate System monitor with Firefox in the background. It did for a moment give a black screen but recovered so not sure if this was the problem resurfacing. Without this being a duel boot I would have had great difficulty identifying if it was software or a overheating/grapics card problem. Most users would scrap their hardware if they were presented with this problem. Hopefully my problem is fixed but if not could you please advise me further. All the Best DAvid ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Wed Feb 15 12:00:06 2023 DistUpgraded: 2022-08-17 16:23:45,139 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.15.0-58-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.15.0-60-generic, x86_64: installed rtl8821ce/5.5.2.1, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [1179:ff50] Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1179:ff50] InstallationDate: Installed on 2021-08-21 (542 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: TOSHIBA Satellite M300 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=98dc102b-f3cc-4067-b9a3-75250f24163c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-08-17 (181 days ago) dmi.bios.date: 03/13/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.80 dmi.board.name: Satellite M300 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.80:bd03/13/2008:svnTOSHIBA:pnSatelliteM300:pvrPSMD0L-01N00M:rvnTOSHIBA:rnSatelliteM300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:sku: dmi.product.name: Satellite M300 dmi.product.version: PSMD0L-01N00M dmi.sys.vendor: TOSHIBA 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.3-2ubuntu2.7 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2007381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007381] [NEW] Xorg freeze
Public bug reported: Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and flashing cursor in top corner then stopped and started again with log in screen. As duel boot started laptop in Windows 10 and no problems so software problem. Reseached and found a fix which was putting in file, 1 - Creating a file "/etc/X11/xorg.conf.d/20-intel.conf" Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection This seems to have fixed the problem. I was running System Profile to watch Temps and also Mate System monitor with Firefox in the background. It did for a moment give a black screen but recovered so not sure if this was the problem resurfacing. Without this being a duel boot I would have had great difficulty identifying if it was software or a overheating/grapics card problem. Most users would scrap their hardware if they were presented with this problem. Hopefully my problem is fixed but if not could you please advise me further. All the Best DAvid ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Wed Feb 15 12:00:06 2023 DistUpgraded: 2022-08-17 16:23:45,139 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.15.0-58-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.15.0-60-generic, x86_64: installed rtl8821ce/5.5.2.1, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [1179:ff50] Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1179:ff50] InstallationDate: Installed on 2021-08-21 (542 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: TOSHIBA Satellite M300 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=98dc102b-f3cc-4067-b9a3-75250f24163c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-08-17 (181 days ago) dmi.bios.date: 03/13/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.80 dmi.board.name: Satellite M300 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.80:bd03/13/2008:svnTOSHIBA:pnSatelliteM300:pvrPSMD0L-01N00M:rvnTOSHIBA:rnSatelliteM300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:sku: dmi.product.name: Satellite M300 dmi.product.version: PSMD0L-01N00M dmi.sys.vendor: TOSHIBA 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.3-2ubuntu2.7 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 freeze jammy 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/2007381 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and flashing cursor in top corner then stopped and started again with log in screen. As duel boot started laptop in Windows 10 and no problems so software problem. Reseached and found a fix which was putting in file, 1 - Creating a file "/etc/X11/xorg.conf.d/20-intel.conf" Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection This seems to have fixed the problem. I was running System Profile to watch Temps and also Mate System monitor with Firefox in
[Desktop-packages] [Bug 2004480] Re: Can't authenticate to Office 365 with oauth
** Changed in: thunderbird (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2004480 Title: Can't authenticate to Office 365 with oauth Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Invalid Bug description: Upstream issue :https://bugzilla.mozilla.org/show_bug.cgi?id=1810760 Thunderbird blog post: https://blog.thunderbird.net/2023/01/important- message-for-microsoft-office-365-enterprise-users/ They say they released a "second build" of version 102.7.1. This is the version I have on Ubuntu 22.04 but I guess I have the "first build" installed? Could you backport the fix please? To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2004480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003237] Re: Backlight stays on with black screen when monitor should be sleeping
Worth adding, my screen doesn't show "No signal". -- 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/2003237 Title: Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. Please see the attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003237] Re: Backlight stays on with black screen when monitor should be sleeping
I've dumped my log in #2007268. Setting the variable didn't change anything in terms of backlight as in @szx case. -- 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/2003237 Title: Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. Please see the attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007268] Re: Backlight does not turn off during screen blanking
*** This bug is a duplicate of bug 2003237 *** https://bugs.launchpad.net/bugs/2003237 The wake-up from sleep is around 11:26. There's a lot of stuff before, so maybe you can find something. I've added the flag to the environment, but from what I see the backlight remains on (it's sunny day, so hard to spot, but shading screen seem to show lights in corners). Hope that helps. ** Attachment added: "XZ dump of `sudo journalctl` since reboot today" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007268/+attachment/5647411/+files/bug-dump.txt.xz -- 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/2007268 Title: Backlight does not turn off during screen blanking Status in mutter package in Ubuntu: Incomplete Bug description: In the 2022/2023 energy crisis era, this shall not happen. But... I haven't found solution other than "switch to X", which is not an options with my scaling settings for both 4K screens I'm using. On idle when the system blanks screen backlight remains on, wasting energy and burning LEDs in my screens. Please provide solution that would let Gnome set DPMS properly and actually send screens to proper sleep when OS goes idle (enables screen saver). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.20.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 11:59:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-58-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-60-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev d1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2023-01-04 (40 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zrhf1w@/vmlinuz-5.15.0-58-generic root=ZFS=rpool/ROOT/ubuntu_zrhf1w ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO 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.3-2ubuntu2.7 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007379] [NEW] Set GTK_IM_MODULE in Ubuntu on Xorg sessions
Public bug reported: [ Impact ] gnome-settings-daemon underwent a code refactoring before the release of version 42 as regards the IBus integration on x11. Initially there was the striking bug #1969637, but also with that one fixed, an issue due to the refactoring remains. These steps illustrate the problem: * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you only can input latin letters * Log out and log in again * Find that you now can input Chinese as expected The need for the last relogin is an inconvenience and a regression compared to how it worked before gnome-settings-daemon 42. The proposed upload makes im-config set the GTK_IM_MODULE variable to 'ibus' for Ubuntu on Xorg sessions, which makes it work as smoothly as it did previously. [ Test Plan ] * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Install im-config from jammy-proposed * Reboot and log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you instantly can input Chinese [ Where problems could occur ] This means that we — again — make im-config interfere with the IM configuration on GNOME desktops. Via bug #1893551 we kind of did the opposite in order to reduce the frequency of ibus crashes. But the situation now is different: - This is more narrow-scoped and limited to x11 - The upstream GNOME code has undergone significant changes - The measure is greenlighted by the upstream IBus maintainer (I think Fedora does it too) But with that said, I'm going to be attentive to the frequency of ibus crashes going forward. [ Other Info ] I prefer to skip kinetic for these reasons: - Not so much time left before EOL - Low importance - A jammy user with an IBus IM already set up, and who upgrades to kinetic, won't encounter a problem. ** Affects: im-config (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: im-config (Ubuntu Jammy) Importance: Low Assignee: Gunnar Hjalmarsson (gunnarhj) Status: In Progress ** Affects: im-config (Ubuntu Kinetic) Importance: Undecided Status: Won't Fix ** Affects: im-config (Debian) Importance: Unknown Status: Unknown ** Also affects: im-config (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: im-config (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: im-config (Ubuntu Kinetic) Status: New => Won't Fix ** Changed in: im-config (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: im-config (Ubuntu Jammy) Status: New => In Progress ** Changed in: im-config (Ubuntu Jammy) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Bug watch added: Debian Bug tracker #1031227 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031227 ** Also affects: im-config (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031227 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/2007379 Title: Set GTK_IM_MODULE in Ubuntu on Xorg sessions Status in im-config package in Ubuntu: Fix Committed Status in im-config source package in Jammy: In Progress Status in im-config source package in Kinetic: Won't Fix Status in im-config package in Debian: Unknown Bug description: [ Impact ] gnome-settings-daemon underwent a code refactoring before the release of version 42 as regards the IBus integration on x11. Initially there was the striking bug #1969637, but also with that one fixed, an issue due to the refactoring remains. These steps illustrate the problem: * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin package is installed. * Log in to an Ubuntu on Xorg session * Go to Settings -> Keyboard and add Chinese (Intelligent Pinyin) to the input sources * Switch to Intelligent Pinyin * Find that you only can input latin letters * Log out and log in again * Find that you now can input Chinese as expected The need for the last relogin is an inconvenience and a regression compared to how it worked before gnome-settings-daemon 42. The proposed upload makes im-config set the GTK_IM_MODULE variable to 'ibus' for Ubuntu on Xorg sessions, which makes it work as smoothly as it did previously. [ Test Plan ] * Prepare an Ubuntu desktop so it has only non-IBus items in the list of input sources, while the ibus-libpinyin
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
@seb128, The situation is a bit unclear there, the pipewire SRU got superseeded by a revert right, does that resolve the issue? -> Yes, the revert one the pipewrie(0.3.48-1ubuntu3) could resolve this issue. Or is the request still trying to address the initially problem? -> Yes, our OEM projects need the reverted SRU patchtes for Bug #1985057, so I added them back, but these patches also need change gstreamer at the same time. Which component do you request to be updated exactly? pipewire with the previous failed SRU + extra fixes and gstreamers? -> Yes, pipewire and gstreamers. Did anyone verify the impact on gnome-shell as pointed in #38? -> I could check it, reply you later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: In Progress Status in gstreamer1.0 source package in Jammy: In Progress Status in pipewire source package in Jammy: In Progress Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer:
[Desktop-packages] [Bug 2003237] Re: Backlight stays on with black screen when monitor should be sleeping
Adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 did not have any visible effect -- 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/2003237 Title: Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. Please see the attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003237] Re: Backlight stays on with black screen when monitor should be sleeping
** Attachment added: "journalctl output (screen went off around 15:41)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003237/+attachment/5647407/+files/journal.txt -- 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/2003237 Title: Backlight stays on with black screen when monitor should be sleeping Status in mutter package in Ubuntu: Confirmed Bug description: My Screen Blank setting is set to 15 minutes. My Lock Screen settings are also set to automatically lock the system after the blank screen timeout is reached. After 15 minutes Ubuntu does lock me out, but the monitor does not power off as it's supposed to - the screen is simply black. Please see the attached video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 18 23:48:13 2023 DistUpgraded: 2022-06-02 20:38:07,324 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2018-03-17 (1768 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=19f4e829-52cc-4c6f-8221-24750af577f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-06-02 (230 days ago) dmi.bios.date: 05/29/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4211 dmi.board.asset.tag: Default string dmi.board.name: H110M-D dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4211:bd05/29/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-D:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
okay, I can confirmed it works with latest packages from Jammy. In both 'Launch using Discrete Graphics Card' and '__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia' cases. But it doesn't work for firefox (mine is a snap version) so I think we are good to close this or switch to affect firefox. ** Changed in: oem-priority Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Invalid Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
