[Desktop-packages] [Bug 2007652] [NEW] PWA don't launch as applications, just another chromium window
Public bug reported: I have recently converted from deb to snap package of chromium and PWAs launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: PWA don't launch as applications, just another chromium window Status in chromium-browser package in Ubuntu: New Bug description: I have recently converted from deb to snap package of chromium and PWAs launch just as another window of chromium and are not recognized as separate application by the window manager (for example when switching using Super+Tab) or dock (grouped under chromium windows). This is either a regression of the snap package vs deb or ubuntu 20.04 vs ubuntu 18.04 (I am not able to differentiate between these two since both happened together). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006625] Re: Merge modemmanager 1.20.4-1 (main) from Debian unstable (main)
This bug was fixed in the package modemmanager - 1.20.4-1ubuntu1 --- modemmanager (1.20.4-1ubuntu1) lunar; urgency=medium * Merge from Debian unstable. The remaining difference is the change for building without libqrtr, since it is currently not in main (see the 1.20.0-1ubuntu1 entry below) (LP: #2006625) modemmanager (1.20.4-1) unstable; urgency=medium * New upstream version 1.20.4 * d/control: bump Standards-Version, no change required modemmanager (1.20.2-1) unstable; urgency=medium * d/watch: only watch for stable releases. ModemManager has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.20.2 * d/patches: drop upstreamed patch modemmanager (1.20.0-1ubuntu1) lunar; urgency=medium * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build -- Amin Bandali Wed, 08 Feb 2023 10:50:32 -0500 ** Changed in: modemmanager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2006625 Title: Merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Status in modemmanager package in Ubuntu: Fix Released Bug description: Please merge modemmanager 1.20.4-1 (main) from Debian unstable (main) Changelog entries since current lunar version 1.20.0-1ubuntu1: modemmanager (1.20.4-1) unstable; urgency=medium * New upstream version 1.20.4 * d/control: bump Standards-Version, no change required -- Arnaud Ferraris Tue, 03 Jan 2023 13:34:49 +0100 modemmanager (1.20.2-1) unstable; urgency=medium * d/watch: only watch for stable releases. ModemManager has a x.y.z version numbering scheme where y is even for stable releases and odd for development ones. Stable release candidates have x.y-rcz version numbers with y being an even number. This change ensures we only watch for stable releases, including RCs. * New upstream version 1.20.2 * d/patches: drop upstreamed patch -- Arnaud Ferraris Mon, 19 Dec 2022 13:59:08 +0100 Remaining differences with modemmanager from Debian unstable: * Build without libqrtr for now, the MIR is blocked since we don't have hardware available to do the required testing of the feature, include some workarounds to fix the build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2006625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
@gunnarhj >That's not what I see. I just made an English install of the coming Ubuntu 23.04 in VirtualBox and updated the packages. I was busy. i installed and tested it today however noto sinhala font doesn't come with CD image. that's the problem. 23.04 https://cdimage.ubuntu.com/daily-live/20230216/ >* Opened a terminal and run: sudo apt install fonts-noto-core Every user must be aware to follow this step otherwise it still uses LKLUG. Also, this can be problematic for office/limited environments. so this is not the expected solution :( >> should i propose a small font package like LKLUG? What would the point be with doing so? Above -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Released Status in language-selector source package in Kinetic: Fix Released Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004063] Re: Mouse and shell become laggy after some time and progressively gets worse
Yep go ahead and close it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2004063 Title: Mouse and shell become laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: Invalid Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1605319] Re: Nvida does wierd
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1605319 Title: Nvida does wierd Status in xorg package in Ubuntu: Expired Bug description: when i start the nvidia x servers it dont show me the full settings list, try to reinstall it but it dint change ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 21 18:44:29 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics Controller [1025:0971] Subsystem: Acer Incorporated [ALI] GK208M [GeForce 920M] [1025:0971] InstallationDate: Installed on 2016-07-17 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Acer Aspire E5-772G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire E5-772G dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.name: Aspire E5-772G dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jul 21 18:36:47 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nouveau" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nouveau" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4509 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1605319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004063] Re: Mouse and shell become laggy after some time and progressively gets worse
The bug would auto-close after 2 months if there are no comments anyway. But we can close it now and if you find the problem reoccurs (and that it's not caused by Chrome) then we can reopen it. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2004063 Title: Mouse and shell become laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: Invalid Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007604] Re: Error al intentar abrir archivos en Visual Studio Code
Sorry, Visual Studio Code is not supported here. You will need to report the bug to Microsoft at: https://github.com/microsoft/vscode/issues ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2007604 Title: Error al intentar abrir archivos en Visual Studio Code Status in Ubuntu: Invalid Bug description: Buenas tardes, intento abrir un archivo desde Visual Studio Code, pero no me permite acceder a la pestaña de "Abrir archivo", tambien se congela el programa en cuestion hasta que quito la pestaña "Abrir archivo". Saludos 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 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 16:17:04 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-09-26 (143 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=dad03207-69a0-4d8a-9bdf-3ee6427bd77f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A85XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/31/2013:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85XM-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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/+bug/2007604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
At this stage we can't assume those log messages are relevant to the leak. Can you say how big the RSS of the gnome-shell process gets while show-trash is false? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004063] Re: Mouse and shell become laggy after some time and progressively gets worse
I might have to close this. After experiencing it over a few weeks I opened the task mainly because I saw a few other bug reports that seemed similar and it was super annoying. However since my last reply on 2/6 there was a Chrome update that forced a browser restart and since that time the symptom has not come back. I can't say that the Chrome update solved the problem however it might have. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2004063 Title: Mouse and shell become laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: Incomplete Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
The original schedule of this feature hopes could be in last year.
Unfortunately, I've no time to cook this in previous months.
This ticket should be converted to a SRU ticket now.
Sorry for the noise.
** Summary changed:
- [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
+ [Draft][SRU] Support to install nvidia driver by allowing list
** Changed in: oem-priority
Status: Incomplete => Confirmed
--
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:
[Draft][SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
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,
[Desktop-packages] [Bug 2007580] Re: Extneral monitors stop working after screen lock
Thanks for the bug report. Next time the bug occurs, please use the workaround to recover and then run: journalctl -b0 > journal.txt And attach the resulting text file here. ** 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/2007580 Title: Extneral monitors stop working after screen lock Status in Ubuntu: Incomplete Bug description: External monitors connected to dock WD19TB. It took me some time to get the external monitor to work with my dock after install of 22. After installing displaylink drivers and using wayland things seemed to go smoothly. When locking the desktop I am often forced to switch tty then back to get monitors to work. This morning this workaround does not seem to be doing the trick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 .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 Open Kernel Module for x86_64 525.78.01 Release Build (dvs-builder@U16-J11-10-2) Mon Dec 26 05:50:21 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) 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: Thu Feb 16 09:11:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.12.0, 5.15.0-60-generic, x86_64: installed evdi/1.12.0, 5.19.0-32-generic, x86_64: installed nvidia/525.78.01, 5.15.0-60-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/525.78.01, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0] InstallationDate: Installed on 2023-02-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20TJS2BA00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=69d7fb7b-23e3-4a4c-8566-7df3bbb927be ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET42W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TJS2BA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrN2VET42W(1.27):bd01/03/2023:br1.27:efr1.11:svnLENOVO:pn20TJS2BA00:pvrThinkPadP1Gen3:rvnLENOVO:rn20TJS2BA00:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TJ_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TJS2BA00 dmi.product.sku: LENOVO_MT_20TJ_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: A query to find an object was unsuccessful 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 22.2.5-0ubuntu0.1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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
[Desktop-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
This bug was fixed in the package lightdm - 1.30.0-0ubuntu8 --- lightdm (1.30.0-0ubuntu8) lunar; urgency=medium * debian/config-error-dialog.sh: - Use --no-markup option in zenity call (LP: #1887252) -- Gunnar Hjalmarsson Wed, 08 Feb 2023 22:29:55 +0100 ** Changed in: lightdm (Ubuntu) Status: Fix Committed => Fix Released -- 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/1887252 Title: config-error-dialog.sh should pass --no-markup Status in gdm3 package in Ubuntu: Fix Committed Status in lightdm package in Ubuntu: Fix Released Bug description: I modified my ~/.profile to call "logger". This resulted in in producing some output on stderr like ``` <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... ``` This showed an empty zenity prompt. Logs suggest zenity was failing because it was treating `<13>` as pango markup. ``` from markup due to error parsing markup: Error on line 3 char 6: “13” is not a valid ``` We should not assume the error message strings contain valid markup, since their source is unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007623] Re: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)
The attachment "debdiff to 0.3.15-2 in unstable" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2007623 Title: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Status in grilo-plugins package in Ubuntu: New Bug description: Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Changelog entries since current lunar version 0.3.15-1ubuntu1: grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Alberto Garcia Tue, 31 Jan 2023 16:45:49 +0100 Remaining differences with grilo-plugins from Debian unstable: - Split package into -base and -extra (Closes: #805609) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007623] Re: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)
** Patch added: "debdiff to 0.3.15-2 in unstable" https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+attachment/5647912/+files/grilo-plugins_0.3.15-2ubuntu1-from-0.3.15-2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2007623 Title: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Status in grilo-plugins package in Ubuntu: New Bug description: Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Changelog entries since current lunar version 0.3.15-1ubuntu1: grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Alberto Garcia Tue, 31 Jan 2023 16:45:49 +0100 Remaining differences with grilo-plugins from Debian unstable: - Split package into -base and -extra (Closes: #805609) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007623] [NEW] Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)
Public bug reported: Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Changelog entries since current lunar version 0.3.15-1ubuntu1: grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Alberto Garcia Tue, 31 Jan 2023 16:45:49 +0100 Remaining differences with grilo-plugins from Debian unstable: - Split package into -base and -extra (Closes: #805609) ** Affects: grilo-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2007623 Title: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Status in grilo-plugins package in Ubuntu: New Bug description: Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Changelog entries since current lunar version 0.3.15-1ubuntu1: grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Alberto Garcia Tue, 31 Jan 2023 16:45:49 +0100 Remaining differences with grilo-plugins from Debian unstable: - Split package into -base and -extra (Closes: #805609) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007621] [NEW] gio open exits with success even though the underlying exec failed
Public bug reported: This is a sort of annoyingly complex interaction, so bear with me. The observed problem is that xdg-open does not exit with a non-zero exit code when it fails to open. ``` $ unset DISPLAY $ xdg-open http://example.com exo-open: Cannot open display: . $ echo $? 0 ``` It turns out to not exactly be xdg-open's fault, though: ``` $ sh -x $(which xdg-open) http://example.com 2>&1 | tail -n10 + return 0 + open_xfce http://example.com + exo-open --help + gio help open + gio open http://example.com exo-open: Cannot open display: . + [ 0 -eq 0 ] + exit_success + [ 0 -gt 0 ] + exit 0 ``` So, from this we see that xdg-open uses `exo-open --help` to see if exo- open works, but it fails due to the DISPLAY, so it falls back to gio open. gio open ends up turning around and calling exo-open again, but gio swallows the exit code, so xdg-open thinks it worked. ``` $ exo-open http://example.com exo-open: Cannot open display: . $ echo $? 1 $ gio open http://example.com exo-open: Cannot open display: . $ echo $? 0 ``` Versions: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ xdg-open --version xdg-open 1.1.3 $ exo-open --version | head -n1 exo-open 4.16.3 $ gio --version 2.72.4 Specifically: exo-utils: Installed: 4.16.3-1 Candidate: 4.16.3-1 Version table: *** 4.16.3-1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status libglib2.0-bin: Installed: 2.72.4-0ubuntu1 Candidate: 2.72.4-0ubuntu1 Version table: *** 2.72.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.72.1-1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages xdg-utils: Installed: 1.1.3-4.1ubuntu3~22.04.1 Candidate: 1.1.3-4.1ubuntu3~22.04.1 Version table: *** 1.1.3-4.1ubuntu3~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.1.3-4.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2007621 Title: gio open exits with success even though the underlying exec failed Status in glib2.0 package in Ubuntu: New Bug description: This is a sort of annoyingly complex interaction, so bear with me. The observed problem is that xdg-open does not exit with a non-zero exit code when it fails to open. ``` $ unset DISPLAY $ xdg-open http://example.com exo-open: Cannot open display: . $ echo $? 0 ``` It turns out to not exactly be xdg-open's fault, though: ``` $ sh -x $(which xdg-open) http://example.com 2>&1 | tail -n10 + return 0 + open_xfce http://example.com + exo-open --help + gio help open + gio open http://example.com exo-open: Cannot open display: . + [ 0 -eq 0 ] + exit_success + [ 0 -gt 0 ] + exit 0 ``` So, from this we see that xdg-open uses `exo-open --help` to see if exo-open works, but it fails due to the DISPLAY, so it falls back to gio open. gio open ends up turning around and calling exo-open again, but gio swallows the exit code, so xdg-open thinks it worked. ``` $ exo-open http://example.com exo-open: Cannot open display: . $ echo $? 1 $ gio open http://example.com exo-open: Cannot open display: . $ echo $? 0 ``` Versions: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ xdg-open --version xdg-open 1.1.3 $ exo-open --version | head -n1 exo-open 4.16.3 $ gio --version 2.72.4 Specifically: exo-utils: Installed: 4.16.3-1 Candidate: 4.16.3-1 Version table: *** 4.16.3-1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status libglib2.0-bin: Installed: 2.72.4-0ubuntu1 Candidate: 2.72.4-0ubuntu1 Version table: *** 2.72.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.72.1-1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages xdg-utils: Installed: 1.1.3-4.1ubuntu3~22.04.1 Candidate: 1.1.3-4.1ubuntu3~22.04.1 Version table: *** 1.1.3-4.1ubuntu3~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.1.3-4.1ubuntu1 500
[Desktop-packages] [Bug 2007620] Re: In the nautilus compressor dialogue descriptions are cut off on X11 22.04 LTS
This is the patch which was applied in the gnome-42 branch of nautilus: https://gitlab.gnome.org/GNOME/nautilus/-/commit/441124cfef1b95623ac182f818a761ace8d1258c It was fixed with the release of nautilus 42.5. ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2018 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2018 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2018 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2007620 Title: In the nautilus compressor dialogue descriptions are cut off on X11 22.04 LTS Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: Hello, I found a bug in the nautilus file archiver/compressor feature. If you right click on a file/folder, then go to "Compress" then you will see the corrupted descriptions when you select the package format (.zip etc.) I made a screenshot of it. At least in German and maybe in other languages where you have a long description text. According to my tests it happens - only on X11, not on Wayland - on every scaling factor (100% original, 150% fractional, 200%) I read the changelogs of nautilus and it seems that this bug was fixed in nautilus 42.5: "* Really fix the cropped compress format popover on X11 (Ondrej Holy)" Source: https://gitlab.gnome.org/GNOME/nautilus/-/blob/gnome-42/NEWS (nautilus on Ubuntu Jammy uses only version 42.2) So it would be nice if this patch could be transferred to Ubuntu 22.04 LTS, because I currently can't read the descriptions. With best reagards Malsabku To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2007620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006675] Re: Memory leak when hdmi switcher is not sending data/not outputting
It did not seem to do anything to relieve the issue. Attached is about an hour and 10 minutes in that state after a reboot. ** Attachment added: "gslog_notrash.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+attachment/5647906/+files/gslog_notrash.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/2006675 Title: Memory leak when hdmi switcher is not sending data/not outputting Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Main problem: Gnome-shell has a memory leak when my hdmi switcher is on a channel that is currently not inputting hdmi (i.e. desktop on hdmi 2 but hdmi 3 is selected with nothing inserted). This memory leak does not happen if signal is being sent through the hdmi switcher either from the desktop itself or from some other device. It also does not happen if I properly turn the monitor off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 9 00:01:33 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-28 (407 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2006675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007620] [NEW] In the nautilus compressor dialogue descriptions are cut off on X11 22.04 LTS
Public bug reported: Hello, I found a bug in the nautilus file archiver/compressor feature. If you right click on a file/folder, then go to "Compress" then you will see the corrupted descriptions when you select the package format (.zip etc.) I made a screenshot of it. At least in German and maybe in other languages where you have a long description text. According to my tests it happens - only on X11, not on Wayland - on every scaling factor (100% original, 150% fractional, 200%) I read the changelogs of nautilus and it seems that this bug was fixed in nautilus 42.5: "* Really fix the cropped compress format popover on X11 (Ondrej Holy)" Source: https://gitlab.gnome.org/GNOME/nautilus/-/blob/gnome-42/NEWS (nautilus on Ubuntu Jammy uses only version 42.2) So it would be nice if this patch could be transferred to Ubuntu 22.04 LTS, because I currently can't read the descriptions. With best reagards Malsabku ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Attachment added: "Here you see the cut-off descriptions." https://bugs.launchpad.net/bugs/2007620/+attachment/5647907/+files/Bildschirmfoto%20vom%202023-02-16%2023-37-49.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2007620 Title: In the nautilus compressor dialogue descriptions are cut off on X11 22.04 LTS Status in nautilus package in Ubuntu: New Bug description: Hello, I found a bug in the nautilus file archiver/compressor feature. If you right click on a file/folder, then go to "Compress" then you will see the corrupted descriptions when you select the package format (.zip etc.) I made a screenshot of it. At least in German and maybe in other languages where you have a long description text. According to my tests it happens - only on X11, not on Wayland - on every scaling factor (100% original, 150% fractional, 200%) I read the changelogs of nautilus and it seems that this bug was fixed in nautilus 42.5: "* Really fix the cropped compress format popover on X11 (Ondrej Holy)" Source: https://gitlab.gnome.org/GNOME/nautilus/-/blob/gnome-42/NEWS (nautilus on Ubuntu Jammy uses only version 42.2) So it would be nice if this patch could be transferred to Ubuntu 22.04 LTS, because I currently can't read the descriptions. With best reagards Malsabku To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2007620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
This part is missing from the compiler command line -DDRI_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri\" I've verified that this can be fixed by adding a configuration to minigbm's BUILD.gn I will create a patch that addresses this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: Triaged Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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?
So there are now Mouse Acceleration settings coming to a Release version of GNOME/Ubuntu? If so, which version is being targetted @jbicha ? -- 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 2004021] Re: Moving video position /scrubbing in Totem (Videos) causes video to freeze (but not audio)
Just realized this affects anything using gstreamer. Makes Pitivi fairly unusable. ** Also affects: pitivi (Ubuntu) Importance: Undecided Status: New -- 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 pitivi 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 2007604] Re: Error al intentar abrir archivos en Visual Studio Code
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2007604 Title: Error al intentar abrir archivos en Visual Studio Code Status in xorg package in Ubuntu: New Bug description: Buenas tardes, intento abrir un archivo desde Visual Studio Code, pero no me permite acceder a la pestaña de "Abrir archivo", tambien se congela el programa en cuestion hasta que quito la pestaña "Abrir archivo". Saludos 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 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 16:17:04 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-09-26 (143 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=dad03207-69a0-4d8a-9bdf-3ee6427bd77f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A85XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/31/2013:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85XM-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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/2007604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007604] [NEW] Error al intentar abrir archivos en Visual Studio Code
You have been subscribed to a public bug: Buenas tardes, intento abrir un archivo desde Visual Studio Code, pero no me permite acceder a la pestaña de "Abrir archivo", tambien se congela el programa en cuestion hasta que quito la pestaña "Abrir archivo". Saludos 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 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 16:17:04 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-09-26 (143 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=dad03207-69a0-4d8a-9bdf-3ee6427bd77f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A85XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/31/2013:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85XM-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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 jammy third-party-packages ubuntu wayland-session -- Error al intentar abrir archivos en Visual Studio Code https://bugs.launchpad.net/bugs/2007604 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993370] Re: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic
This bug also affects the latest Jammy daily ISO. ** Also affects: software-properties (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Kinetic) Status: New => Fix Committed ** Summary changed: - Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic + Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Jammy 22.04.2 and Kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1993370 Title: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Jammy 22.04.2 and Kinetic Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Jammy: New Status in software-properties source package in Kinetic: Fix Committed Bug description: Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel Core i5, UEFI, no secure boot, Broadcom WiFi. OS: Ubuntu Studio Kinetic, Final ISO Steps to reproduce: 1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the system normally. (No encryption, allow Internet access during installation using some method of connectivity other than WiFi.) 2. Reboot and log into the newly installed system. 3. Open a terminal and run "sudo software-properties-kde". 4. Click "Additional Drivers" in the window that pops up. 5. Click "Using Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary)". Expected result: The Apply Changes button should become clickable, allowing the user to install the driver. Actual result: The button remains grayed out, and the following error message is printed in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 1063, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: software-properties-qt 0.99.27 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Oct 18 21:33:51 2022 InstallationDate: Installed on 2022-10-19 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007600] [NEW] Not possible to dismiss/cancel authentication dialog
Public bug reported: In system settings -> Online accounts I started adding google. During the authentication it said I needed to approve the sign on with the youtube app on my mobile device. I don't have the youtube app installed on my phone and don't want it so I decided to cancel the sign on. Problem is it is not possible to cancel the sign on to google. There is no cancel button and if I close the window a new, identical, window opens up. I also tried to kill it with ctrl-alt-esc and it just opens up a new window right away. What I expect: Closing the window should cancel the sign-on attempt and a new window should not open. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: signon-ui-x11 0.17+18.04.20171027+really20160406-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Feb 16 11:48:08 2023 ExecutablePath: /usr/bin/signon-ui SourcePackage: signon-ui UpgradeStatus: Upgraded to kinetic on 2022-10-23 (116 days ago) ** Affects: signon-ui (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/2007600 Title: Not possible to dismiss/cancel authentication dialog Status in signon-ui package in Ubuntu: New Bug description: In system settings -> Online accounts I started adding google. During the authentication it said I needed to approve the sign on with the youtube app on my mobile device. I don't have the youtube app installed on my phone and don't want it so I decided to cancel the sign on. Problem is it is not possible to cancel the sign on to google. There is no cancel button and if I close the window a new, identical, window opens up. I also tried to kill it with ctrl-alt-esc and it just opens up a new window right away. What I expect: Closing the window should cancel the sign-on attempt and a new window should not open. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: signon-ui-x11 0.17+18.04.20171027+really20160406-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Feb 16 11:48:08 2023 ExecutablePath: /usr/bin/signon-ui SourcePackage: signon-ui UpgradeStatus: Upgraded to kinetic on 2022-10-23 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/2007600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
** Tags removed: beta-failed dev-failed ** Tags added: beta-ok dev-ok -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Triaged Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: Candidate: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-candidate Beta: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta Dev: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Hi M.Hanny, Thanks a lot for spreading the word about BiDi support in VTE! Really no need to apologize about your English! I'm not a native English speaker either, and your English is at least as good as mine. We have no communication issues at all! --- > 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 [...] This is a very long journey and it may take many years until we reach that point. I disagree with you in this point. There will always be English text in the output of "apt", such as package names, I don't think they will ever be translatable (and would arguably be a mistake to go in this direction). For rapidly changing data, such as package descriptions, it's practically impossible for all translations to be fully up-to-date all the time. Think of software like dmesg printing system logs, software printing hardware information (such as identification strings of various components), think of software showing system directories' and files' names etc. Think of commands that print whois data, show a mysql table along with the column names, show source code etc. Think of ssh'ing to a remote host. Think of the long tail of utilities you find on the web that someone quickly hacked together but there's no demand to get translated to languages other than English. Although not relevant to the world of terminal emulation, I've just checked the completeness of the Arabic translation of the GNOME desktop at https://l10n.gnome.org/teams/ar/, and it's very very far from being fully green. You'll never have a terminal emulation experience that is fully in a foreign (I mean non-English, not necessarily RTL) language, for two reasons. One is that due to the very nature of things there'll always be tons of English stuff in the terminal, the second is that it's a utopic and reasonably unreachable dream to have all software's UI strings be fully translated to all languages. A 100% fully Japanese, or fully Hungarian, or fully Arabic experience in terminal emulators, no English word whatsoever, is neither "ideal" nor in my opinion is reachable in our lives. > However, in order to get there, we need to start somewhere. [...] this could open the door for a wide range of CLI-based computing for RTL languages speakers [...] I agree with this one, and I hope I could make an important step here. > The political factor is also important. I don't want to talk about politics here of course I don't want to talk about politics either. My work was driven by getting closer to equality for people, no matter if I agree or disagree with certain things they do; as well as by the technical challenge itself. That being said, you raised excellent points here. > 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 [...] I fully understand this. Prior to my work, nobody had an idea how to do BiDi in terminals, nobody saw the whole picture. As I show in my document, everyone who thought they knew how to do it made fundamental mistakes, proving that they only saw a fraction of the story -- except for ECMA TR/53 which at least saw the big picture correctly, but that one also made big mistakes elsewhere, and is an old piece of work preceding the UBA, not suitable for straight adoptation. I believe my work is the first and only one so far that shows how BiDi can actually be done in terminals in a way that it really works. But again, it's not a magic wand solution for all the problems, it's a platform for app developers to build upon. Funny story, perfectly rhyming with what you experienced here, and maybe pushing it a little bit further. I gained my BiDi knowledge and experience in 2009-2010 when for half a year I worked on porting the (now discontinued) iGoogle webpage to RTL. Those days Internet Explorer 6 was the market leader, IE7 was gaining some popularity, and IE8 was brand new. IE6, as we all know, was a terrible browser. But when you tried to do RTL in it, it was even magnitudes worse! IE7 was significantly better, but nowhere near perfect when it came to RTL. In IE8 I could not find a single RTL bug. (In all cases: asking the browser to use its latest rendering engine, rather than some compatibility mode.) Working around the IE6 RTL layout issues (and even crashes!) took a whole lot of development effort. IE7 caused less pain. With IE8 there was no pain at all (apart from the necessary migration and layout fixes as we asked the browser to use its new rendering engine rather than compat mode). At one point I suggested that we just add a banner asking users to upgrade to IE8, saving us tons of development effort. The idea was rejected because market share of IE6 was even bigger in RTL areas than at the rest of the world. Why? Because RTL in IE6 was so bad that
[Desktop-packages] [Bug 1998703] Re: img2pdf FTBFS unmet dependency libgs-common
Built succesfully now that the newer version of ghostscript has been merged from Debian. (https://bugs.launchpad.net/ubuntu/+source/ghostscript/10.0.0~dfsg1-0ubuntu1) ** Changed in: img2pdf (Ubuntu) Status: New => Fix Committed ** Changed in: ghostscript (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1998703 Title: img2pdf FTBFS unmet dependency libgs-common Status in ghostscript package in Ubuntu: Fix Committed Status in img2pdf package in Ubuntu: Fix Committed Bug description: img2pdf currently fails to build in Lunar [1] due to a missing build dependency libgs-common. This package is part of ghostscript in Debian, but appears missing in the Ubuntu build. The package is possibly missing because ghostscript has been packaged directly in Ubuntu. [1] https://launchpad.net/ubuntu/+source/img2pdf/0.4.4-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1998703/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007580] Re: Extneral monitors stop working after screen lock
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2007580 Title: Extneral monitors stop working after screen lock Status in xorg package in Ubuntu: New Bug description: External monitors connected to dock WD19TB. It took me some time to get the external monitor to work with my dock after install of 22. After installing displaylink drivers and using wayland things seemed to go smoothly. When locking the desktop I am often forced to switch tty then back to get monitors to work. This morning this workaround does not seem to be doing the trick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 .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 Open Kernel Module for x86_64 525.78.01 Release Build (dvs-builder@U16-J11-10-2) Mon Dec 26 05:50:21 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) 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: Thu Feb 16 09:11:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.12.0, 5.15.0-60-generic, x86_64: installed evdi/1.12.0, 5.19.0-32-generic, x86_64: installed nvidia/525.78.01, 5.15.0-60-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/525.78.01, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0] InstallationDate: Installed on 2023-02-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20TJS2BA00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=69d7fb7b-23e3-4a4c-8566-7df3bbb927be ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET42W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TJS2BA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrN2VET42W(1.27):bd01/03/2023:br1.27:efr1.11:svnLENOVO:pn20TJS2BA00:pvrThinkPadP1Gen3:rvnLENOVO:rn20TJS2BA00:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TJ_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TJS2BA00 dmi.product.sku: LENOVO_MT_20TJ_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: A query to find an object was unsuccessful 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 22.2.5-0ubuntu0.1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/2007580/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 2007580] [NEW] Extneral monitors stop working after screen lock
You have been subscribed to a public bug: External monitors connected to dock WD19TB. It took me some time to get the external monitor to work with my dock after install of 22. After installing displaylink drivers and using wayland things seemed to go smoothly. When locking the desktop I am often forced to switch tty then back to get monitors to work. This morning this workaround does not seem to be doing the trick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 .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 Open Kernel Module for x86_64 525.78.01 Release Build (dvs-builder@U16-J11-10-2) Mon Dec 26 05:50:21 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) 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: Thu Feb 16 09:11:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.12.0, 5.15.0-60-generic, x86_64: installed evdi/1.12.0, 5.19.0-32-generic, x86_64: installed nvidia/525.78.01, 5.15.0-60-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/525.78.01, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0] InstallationDate: Installed on 2023-02-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20TJS2BA00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=69d7fb7b-23e3-4a4c-8566-7df3bbb927be ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET42W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TJS2BA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrN2VET42W(1.27):bd01/03/2023:br1.27:efr1.11:svnLENOVO:pn20TJS2BA00:pvrThinkPadP1Gen3:rvnLENOVO:rn20TJS2BA00:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TJ_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TJS2BA00 dmi.product.sku: LENOVO_MT_20TJ_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: A query to find an object was unsuccessful 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 22.2.5-0ubuntu0.1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 jammy ubuntu wayland-session -- Extneral monitors stop working after screen lock https://bugs.launchpad.net/bugs/2007580 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007563] Re: Update ubuntu-drivers-common 02/2023
** Also affects: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Triaged => Won't Fix ** Description changed: - Kinetic + + == Changelogs == + + === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. - * tests/quirkreader-test.py: - - Fix E275 missing whitespace after keyword. - * Quirks/quirkreader.py: - - Handle UnicodeDecodeError. - - Line 55 fix E275 missing whitespace after keyword. - - [ Alex-S-H-P ] - * UbuntuDrivers/detect.py: - - Remove redundant variable. - - [ Jeremy Szu ] - * README, README.md, - UbuntuDrivers/detect.py, - tests/test_ubuntu_drivers.py: - - Add support for force installing the NVIDIA driver on unsupported - devices. - The device and its target driver branch are both specified in the - /etc/custom_supported_gpus.json file. - Support for runtimepm can also be set in the file. - - Support autokgstest for force install nvidia. - - Add autopkgtest in README section. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment - when catching ValueError. + when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). + + === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === + +* UbuntuDrivers/detect.py: + - Make sure -open drivers have a lower priority (LP: #1988836). -- 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/2007563 Title: Update ubuntu-drivers-common 02/2023 Status in ubuntu-drivers-common package in Ubuntu: Won't Fix Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Kinetic: In Progress Bug description: == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2007563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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-lowlatency/5.15.0-66.73+1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-66.73+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-lowlatency [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 2000644] Re: switching workspaces with shortcut sometimes freezes screen
Same as Gauthier for me, I have the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2000644 Title: switching workspaces with shortcut sometimes freezes screen Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The bottom panel with dots to show which workspace you are on when switching with ctrl+alt+arrow sometimes doesn't disappear and gets stuck in a half faded or not faded state. In that state the mouse appear stuck and the screen freezes until the super key is pressed to show overview or the workspace is switched again. Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand, Nvidia driver 525.60.11 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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-lowlatency/5.15.0-66.73)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-66.73) 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-lowlatency [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 2007573] [NEW] playing only audio of an mp4 file
Public bug reported: Totem is not playing mp4 files. Only sound is heard but video is not. Other media players like VLC and Xine play it quite well. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 17:47:16 2023 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2007573 Title: playing only audio of an mp4 file Status in gstreamer1.0 package in Ubuntu: New Bug description: Totem is not playing mp4 files. Only sound is heard but video is not. Other media players like VLC and Xine play it quite well. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.3-1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 17:47:16 2023 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2007573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
Setting as verification done since it works correctly here on J/K/L and the previous post also confirms the fix is working for flavors ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Jammy: Fix Committed Status in evince source package in Kinetic: Fix Committed Status in evince package in Debian: Fix Released Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007572] [NEW] plymouth doesn't show at bootup
Public bug reported: plymouth animation doesn't show up at boot up however it shows up at shut down. At boot up only a text mode animation is there. could this be resolved? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: plymouth 22.02.122-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 17:42:12 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=UUID=99d05df1-2234-4b35-9f2c-dbfb7b37e21e ro quiet splash vt.handoff=7 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=UUID=99d05df1-2234-4b35-9f2c-dbfb7b37e21e ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1701:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2007572 Title: plymouth doesn't show at bootup Status in plymouth package in Ubuntu: New Bug description: plymouth animation doesn't show up at boot up however it shows up at shut down. At boot up only a text mode animation is there. could this be resolved? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: plymouth 22.02.122-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 17:42:12 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=UUID=99d05df1-2234-4b35-9f2c-dbfb7b37e21e ro quiet splash vt.handoff=7 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=UUID=99d05df1-2234-4b35-9f2c-dbfb7b37e21e ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1701:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLXV2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2007572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894715] Re: sane-utils update-inetd: warning: cannot add service, /etc/inetd.conf does not exist
this is 3 years ago. are we really only 4 people using scanners anymore? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1894715 Title: sane-utils update-inetd: warning: cannot add service, /etc/inetd.conf does not exist Status in sane-backends package in Ubuntu: Confirmed Bug description: Following warning displayed during install Setting up sane-utils (1.0.29-0ubuntu5.1) ... update-inetd: warning: cannot add service, /etc/inetd.conf does not exist ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 09:31:24 2020 InstallationDate: Installed on 2019-03-30 (526 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190318) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: sane-backends UpgradeStatus: Upgraded to focal on 2020-05-15 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1894715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006641] Re: hwacc branches fail to build
** Merge proposal linked: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437382 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006641 Title: hwacc branches fail to build Status in chromium-browser package in Ubuntu: Triaged Bug description: Currently the hwacc branches of snap_from_source fail to build. This is caused by the fact that the guide-0.9.1 patches are against 107 chromium, and no longer apply cleanly. build logs here: Candidate: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-candidate Beta: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-beta Dev: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-hwacc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007564] [NEW] Kernel livepatch option coundn't be enabled after 'Enable Ubuntu Pro'
Public bug reported: 'Kernel Livepatch' should be displayed an enabled from below bug. But the check button is in 'Disabled' status with gray color. https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2003527 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-2007068 sutton -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2007564 Title: Kernel livepatch option coundn't be enabled after 'Enable Ubuntu Pro' Status in software-properties package in Ubuntu: New Bug description: 'Kernel Livepatch' should be displayed an enabled from below bug. But the check button is in 'Disabled' status with gray color. https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2003527 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2007564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Update Released
The verification of the Stable Release Update for metacity has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: Fix Committed Status in metacity source package in Jammy: Fix Released Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003176] Re: SRU: metacity crashes while minimizing a windows that has undocked child
This bug was fixed in the package metacity - 1:3.44.0-1ubuntu1 --- metacity (1:3.44.0-1ubuntu1) jammy; urgency=medium * Backport upstream patch to fix metacity crash when a parent window is minimized while a docked window is undocked (LP: #2003176). * Backport upstream patch to fix restoring docked window when the parent window is unminimized. -- Mustafa Kemal GILOR Wed, 18 Jan 2023 15:50:17 +0300 ** Changed in: metacity (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/2003176 Title: SRU: metacity crashes while minimizing a windows that has undocked child Status in metacity package in Ubuntu: New Status in metacity source package in Focal: Fix Committed Status in metacity source package in Jammy: Fix Released Bug description: [General information about the SRU] * It includes the fix for the bug https://gitlab.gnome.org/GNOME/metacity/-/issues/31 * The fix is already included in 3.46.0 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/77f1d55479bfef479f76011a1ee5636f9bf6b08b#9f621eb5fd3bcb2fa5c7bd228c9b1ad42edc46c8 * The reproducer also revealed another issue with docked windows, undocked windows are not being restored after parent window is minimized and restored * The fix for restore is included in 3.46.1 release: https://gitlab.gnome.org/GNOME/metacity/-/commit/3db07fafa1c7ff9749b6a82ccb36d8b62f2304d9 * Focal(3.36.1) and Jammy (3.44.0) needs both fixes to be backported [Impact] This affects users using applications that have docked windows [Test Case] * Install gnome-session-flashback (metacity) and reproducer's dependencies `sudo apt install lightdm gnome-session-flashback pyside2-tools python3-pyside2.qtwidgets` * Start a graphical session with metacity * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Result: Metacity will crash * Fix: install fix from ppa: * sudo add-apt-repository ppa:mustafakemalgilor/lp-2003176-0 * sudo apt update * sudo reboot # or alternatively, restart display manager * run python3 Untitled.py * Undock one of the application's child windows * Minimize main window * Expectation: it should not crash and the application should be minimized. [Regression Potential] The fix is small in size and localized, it should not cause any regressions. - Bug Version: 1:3.36.1-1 / 1:3.44.0-1 Metacity is running without the composite manager. Users cannot minimize an application with an undocked child window ProblemType: Bug DistroRelease: Ubuntu 20.04 / Ubuntu 22.04 Package: metacity 1:3.36.1-1 / 1:3.44.0-1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007563] [NEW] Update ubuntu-drivers-common 02/2023
Public bug reported: Kinetic [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. * tests/quirkreader-test.py: - Fix E275 missing whitespace after keyword. * Quirks/quirkreader.py: - Handle UnicodeDecodeError. - Line 55 fix E275 missing whitespace after keyword. [ Alex-S-H-P ] * UbuntuDrivers/detect.py: - Remove redundant variable. [ Jeremy Szu ] * README, README.md, UbuntuDrivers/detect.py, tests/test_ubuntu_drivers.py: - Add support for force installing the NVIDIA driver on unsupported devices. The device and its target driver branch are both specified in the /etc/custom_supported_gpus.json file. Support for runtimepm can also be set in the file. - Support autokgstest for force install nvidia. - Add autopkgtest in README section. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError. [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: Triaged -- 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/2007563 Title: Update ubuntu-drivers-common 02/2023 Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Kinetic [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. * tests/quirkreader-test.py: - Fix E275 missing whitespace after keyword. * Quirks/quirkreader.py: - Handle UnicodeDecodeError. - Line 55 fix E275 missing whitespace after keyword. [ Alex-S-H-P ] * UbuntuDrivers/detect.py: - Remove redundant variable. [ Jeremy Szu ] * README, README.md, UbuntuDrivers/detect.py, tests/test_ubuntu_drivers.py: - Add support for force installing the NVIDIA driver on unsupported devices. The device and its target driver branch are both specified in the /etc/custom_supported_gpus.json file. Support for runtimepm can also be set in the file. - Support autokgstest for force install nvidia. - Add autopkgtest in README section. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError. [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2007563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
@Brian, no, there was a misunderstanding, and this was not meant for
Lunar. Please unsubscribe the Release team, as I can't seem to be able
to do it.
--
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 but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
Done
---
[Additional
[Desktop-packages] [Bug 2004518] Re: segfault when closing on the ubuntu pro tab
This bug was fixed in the package gnome-initial-setup - 42.0.1-1ubuntu2.3 --- gnome-initial-setup (42.0.1-1ubuntu2.3) jammy; urgency=medium [ Nathan Teodosio ] * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch: - fix a crash in the dispose handler (lp: #2004518) -- Sebastien Bacher Wed, 01 Feb 2023 23:56:07 +0100 ** Changed in: gnome-initial-setup (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/2004518 Title: segfault when closing on the ubuntu pro tab Status in gnome-initial-setup package in Ubuntu: Invalid Status in gnome-initial-setup source package in Jammy: Fix Released Bug description: * Impact The initial setup crashes sometime when being closed * Test case - start the initial setup wizard $ rm ~/.config/gnome-initial-setup-done $ /usr/libexec/gnome-initial-setup --existing-user go to the ubuntu one screen, then close the wizard from the launcher context menu, it shouldn't crash check also that the error tracker doesn't include reports of the issue with the new version, https://errors.ubuntu.com/problem/ac3dc4faf9f0e4bea7d15189809571375b3c04d7 * Regression potential THe change is in the dispose functions of the ubuntu pro page, so issue would trigger when going to next page or when closing the wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2004518/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968100] Re: Reporting firefox bug redirect to general mozilla page
Possibly related (duplicate)- https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1959866 QA test of Lubuntu 22.04 daily today; calamares crashed & I tried to `ubuntu-bug calamares` but `ubuntu-bug` failed to open firefox again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1968100 Title: Reporting firefox bug redirect to general mozilla page Status in firefox package in Ubuntu: Confirmed Bug description: When reporting a bug on firefox snap. A dialog is shown, that will redirect to https://support.mozilla.org/en-US/products/firefox and not the bug reporting website. If someone tries to file a bug this is pretty inconvenient. Starting a search there on 'report bug' shows as 2nd item. Reporting bugs is hard. The first item is about bugs fixed in a release. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 7 10:55:35 2022 InstallationDate: Installed on 2022-03-17 (21 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to jammy on 2022-03-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1968100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985089] Re: Resizing two edge tiled windows is laggy
This is in lunar already: https://launchpad.net/ubuntu/+source/mutter/43.2-6ubuntu1 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/1985089 Title: Resizing two edge tiled windows is laggy Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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-gcp/5.15.0-1030.37)
All autopkgtests for the newly accepted linux-restricted-modules-gcp (5.15.0-1030.37) 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-gcp [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
