[Desktop-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
I have this happened to me in the Kubuntu 23.04 Live installer also. nvidia 3060ti ko. Safe graphics works as a workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018714] Re: [BPO] libreoffice 7.4.7 for bionic, focal and jammy
** Description changed: [Impact] * LibreOffice 7.4.7 is in its seventh bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.7_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2018600 and its backport is currently provided by the LibreOffice Still PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+packages [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.7-0ubuntu0.22.10.1 * Backport targets are the Bionic/18.04, Focal/20.04 and Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_74/1827/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Bionic/18.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14738812/+listing-archive-extra - * [amd64] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20230509_091428_b3633@/log.gz * [arm64] ... - * [armhf] ... - * [i386l] ... - * [ppc64el] ... + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20230509_113953_615bf@/log.gz + * [i386l] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20230509_111407_9f2bc@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20230509_110221_c7d8a@/log.gz * [s390x] ... Focal/20.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14738813/+listing-archive-extra - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/amd64/libr/libreoffice/20230508_165949_20fb6@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/arm64/libr/libreoffice/20230508_213248_aef40@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/armhf/libr/libreoffice/20230508_193232_364c7@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-still/focal/ppc64el/libr/libreoffice/20230508_173145_777fc@/log.gz * [s390x] ... Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/14738814/+listing-archive-extra - * [amd64] ... - * [arm64] ... - * [armhf] ... - * [ppc64el] ... - * [s390x] ... + * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20230508_203244_68a30@/log.gz + * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20230508_201428_74484@/log.gz + * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/armhf/libr/libreoffice/20230508_200026_a1551@/log.gz + * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20230508_182200_559ad@/log.gz + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20230510_045054_7b793@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- You received this bug notification because you are a me
[Desktop-packages] [Bug 1396446] Re: HP DeskJet 842C will not print with Print Quality set to "Normal Grayscale, " but "Draft Grayscale" and "Normal Color" work.
I had to modify the *hpPrinterPlatform value from "dj895" to "dj970" in the PPD file. After that it works fine for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1396446 Title: HP DeskJet 842C will not print with Print Quality set to "Normal Grayscale," but "Draft Grayscale" and "Normal Color" work. Status in HPLIP: Confirmed Status in cups package in Ubuntu: Invalid Status in hplip package in Ubuntu: Confirmed Status in hplip package in Arch Linux: New Bug description: In Document Print Status, the job status is "Stopped." In the Job Attributes, job-printer-state-message is "Filter failed." See attached for an extract from /var/log/cups/error_log. If I reprint from the Document Print Status GUI, after a moment's pause, I get a dialog box saying "Print Error — There was a problem processing document…" and the name of the document. I have deleted and re-added this printer several times with the Settings Manager → Printers GUI. The printer is an HP DeskJet 842C, which comes up as an 840C on screen. The test page works (I assume because it's in colour mode). I am running Xubuntu. This printer worked with Xubuntu 10.04.2. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 hplip: Installed: 3.14.3-0ubuntu3.2 Candidate: 3.14.3-0ubuntu3.2 Version table: *** 3.14.3-0ubuntu3.2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.14.3-0ubuntu3 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages cups: Installed: 1.7.2-0ubuntu1.2 Candidate: 1.7.2-0ubuntu1.2 Version table: *** 1.7.2-0ubuntu1.2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1.7.2-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hplip 3.14.3-0ubuntu3.2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Nov 25 23:33:52 2014 InstallationDate: Installed on 2011-03-27 (1339 days ago) InstallationMedia: Xubuntu 10.04.2 "Lucid Lynx" - Release amd64 (20110215.1) Lpstat: device for DeskJet_840C: hp:/usb/DeskJet_840C?serial=MX0CR1Y104LB MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: DeskJet_840C: HP Deskjet 840c, hpcups 3.14.3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=78f80a62-5dce-4bc0-bef4-fc21c095ad2f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to trusty on 2014-11-13 (13 days ago) dmi.bios.date: 09/08/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88TD-V EVO/USB3 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.:bvr1601:bd09/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1396446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019116] [NEW] Performance mode not available
Public bug reported: Performance mode not available as a profile. Only Power Saver and Balanced are there. ** Affects: power-profiles-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2019116 Title: Performance mode not available Status in power-profiles-daemon package in Ubuntu: New Bug description: Performance mode not available as a profile. Only Power Saver and Balanced are there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2019116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
@seb128 FYI: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2877 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2877 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2877 -- 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/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in nautilus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
And: https://github.com/ibus/ibus/issues/2486 https://gitlab.gnome.org/GNOME/gtk/-/issues/5347 ** Bug watch added: github.com/ibus/ibus/issues #2486 https://github.com/ibus/ibus/issues/2486 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #5347 https://gitlab.gnome.org/GNOME/gtk/-/issues/5347 -- 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/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016308] Re: gnome-shell crashed with signal 6: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
I am using NetBeans 12.5 another way to replicate this bug: add two JFrame and configure a button in one of the JFrame with the following code: new NewJFrame().setVisible(true); this.dispose(); Wayland session: the OS freezes and closes the session. Xorg session : the OS freezes but it does not close the session and keeps the program open -- 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/2016308 Title: gnome-shell crashed with signal 6: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: Hello, This bug is triggered by Sweethome 3D but the underlying problem seems to be a libmutter issue. Setup: Ubuntu 23.04 Ryzen 6000 AMD 680 Gnome 44 Sweethome 3D 7.0.2 (from the repositories) Whenever I load a file in Sweethome 3D my desktop session is killed instantly. I am either thrown back to the desktop login or it stays black. This seems like a severe problem to me. Under no circumstances should an app like Sweethome 3D be able to crash mutter. I don't know how to give any logs. But I attach a sample file for Sweethome 3D. Actually it crashes with any file. Steps to reproduce: Start Sweethome 3D Draw some walls to make Draw a room Save to file Quit Sweethome 3D Start Sweethome 3D Load the file Crash To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
** Also affects: nautilus via https://github.com/ibus/ibus/issues/2486 Importance: Unknown Status: Unknown ** Project changed: nautilus => ibus -- 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/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: Unknown Status in nautilus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017598] Re: lightdm login screen still shows 22.04 as OS version, even if the system is sucessfully upgraded to Ubuntu 23.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => lightdm (Ubuntu) ** Changed in: lightdm (Ubuntu) Status: Confirmed => New -- 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/2017598 Title: lightdm login screen still shows 22.04 as OS version, even if the system is sucessfully upgraded to Ubuntu 23.04 Status in lightdm package in Ubuntu: New Bug description: lightdm login screen still shows 22.04 as OS version, even if the system is sucessfully upgraded to Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.6 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CrashDB: ubuntu CrashReports: 640:1000:121:8294592:2023-04-25 00:10:36.608921177 +0300:2023-04-25 00:10:33.136958258 +0300:/var/crash/_opt_microsoft_msedge_msedge.1000.crash 640:1000:121:217318:2023-04-24 23:09:08.806661658 +0300:2023-04-24 23:09:03.966707577 +0300:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:121:16599485:2023-04-24 23:33:08.750004640 +0300:2023-04-24 23:33:04.370014218 +0300:/var/crash/_opt_Citrix_ICAClient_wfica.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 00:31:34 2023 InstallationDate: Installed on 2022-09-24 (212 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2017598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018985] Re: package ubuntu-minimal 1.501 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Can you please run apport-collect 2018985 so that the ubuntu-release- upgrader logs are attached to this bug? ** Package changed: ubuntu-meta (Ubuntu) => ubuntu-release-upgrader (Ubuntu) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2018985 Title: package ubuntu-minimal 1.501 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: after restart same crash ProblemType: Package DistroRelease: Ubuntu 23.04 Package: ubuntu-minimal 1.501 ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6 Uname: Linux 6.2.0-1004-raspi aarch64 ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue May 9 11:25:37 2023 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert ImageMediaBuild: 20221018.1 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: ubuntu-meta Title: package ubuntu-minimal 1.501 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2018985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019137] [NEW] gnome-software should (?) be separated from the packagekit
Public bug reported: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug-in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Confirmed Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019137] Re: gnome-software should (?) be separated from the packagekit
** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Confirmed Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1184665] Re: Foomatic/ljet4d has duplex printing always ON, short-edge duplex not available at all
Launchpad has imported 11 comments from the remote bug at http://bugs.ghostscript.com/show_bug.cgi?id=694279. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2013-05-31T13:49:42+00:00 Till Kamppeter wrote: Original bug report at Ubuntu: https://bugs.launchpad.net/bugs/1184665 The PCL-5 support in GS (ljet4/ljet4d, perhaps also ljet3/ljet3d) has a problem. One cannot switch one-sided/duplex-long-edge/duplex-short-edge via the standard -dDuplex and -dTumble options, duplex can only be switched by selecting ljet4 or ljet4d, short-edge is not available at. Reply at: https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/1184665/comments/6 On 2013-05-31T15:11:34+00:00 Henry-stiles wrote: The PCL produced is correct, with -dTumble the driver produces the command (ESC & l) 2 S and 1 S when it is off, the expected result. Doe the user have PCL output from the native driver which selects Tumble and works? If so attach it to the bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/1184665/comments/9 On 2013-05-31T15:58:26+00:00 Till Kamppeter wrote: The CUPS error_log attached to the Ubuntu bug report contains the following Ghostscript command lines (search for "renderer command"): Job 111: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=ljet4d -dDuplex -dMediaPosition=0 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -r600x600 -sOutputFile=- -f /var/spool/cups/tmp/foomatic-E6dq3t Job 112: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=ljet4d -dDuplex -dTumble -dMediaPosition=0 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -r600x600 -sOutputFile=- -f /var/spool/cups/tmp/foomatic-a4gEnk Job 113: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=ljet4d -dDuplex -dTumble -dMediaPosition=0 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -r600x600 -sOutputFile=- -f /var/spool/cups/tmp/foomatic-Eb3AuL Job 114: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=ljet4d -dDuplex -dTumble -dMediaPosition=0 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -r600x600 -sOutputFile=- -f /var/spool/cups/tmp/foomatic-KFdOXu Job 115: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dNOPAUSE -dNOINTERPOLATE -sDEVICE=ljet4 -dMediaPosition=0 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -r600x600 -sOutputFile=- -f /var/spool/cups/tmp/foomatic-r2we33 Job 116: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=ljet4d -dDuplex -dMediaPosition=0 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -r600x600 -sOutputFile=- -f /var/spool/cups/tmp/foomatic-n45KYl Job 111: ljet4d Duplex Job 112: ljet4d Duplex Tumble Job 113: ljet4d Duplex Tumble Job 114: ljet4d Duplex Tumble Job 115: ljet4 Job 116: ljet4d Duplex The user tells that all ljet4d jobs come out duplex long-edge, all ljet4 jobs one-sided. The command line shows that the -dTumble option gets actually supplied. Reply at: https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/1184665/comments/10 On 2013-05-31T16:20:24+00:00 Henry-stiles wrote: The GS output contains the proper pcl commands to select Tumble as confirmed in comment #1; there must be a problem with the printer interpreting the PCL tumble command. I don't see what else we can do with this problem without sample printer codes that select tumble successfully. Maybe there is a proprietary or device dependent escape sequence on the printer. Reply at: https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/1184665/comments/11 On 2013-05-31T16:26:34+00:00 Till Kamppeter wrote: Another problem the user reports is that if he uses ljet4d and unselects duplex by options that the printer still prints duplex. Reply at: https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/1184665/comments/13 On 2013-05-31T16:33:54+00:00 Henry-stiles wrote: (In reply to comment #4) > Another problem the user reports is that if he uses ljet4d and unselects > duplex by options that the printer still prints duplex. Right ljet4d always duplexes, if she changes the option to not duplex then the ljet4 device must be selected somehow. Is there are a problem with doing that? Reply at: https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/1184665/comments/14 -
[Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
** Changed in: ibus Status: Unknown => New -- 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/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: New Status in nautilus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016308] Re: gnome-shell crashed with signal 6: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
I can confirm the existence of this bug, also with a java application (Cameo System Modeler) when using Wayland. When I start the application it starts with a loading screen, and when it finishes with loading and wants to dispose the loading screen (probably a JFrame, ad Diego mentioned) I get a crash and Ubuntu logs out. I can reproduce this issue consistently. Switching to X solves the problem, no more crash, I can use Cameo. Linux zsolt-ThinkPad-T480 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 23.04 Release:23.04 Codename: lunar 2023-05-10T19:05:44.827550+02:00 zsolt-ThinkPad-T480 gnome-shell[23330]: ** 2023-05-10T19:05:44.827869+02:00 zsolt-ThinkPad-T480 gnome-shell[23330]: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window) 2023-05-10T19:05:44.827930+02:00 zsolt-ThinkPad-T480 gnome-shell[23330]: Bail out! libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window) 2023-05-10T19:05:44.827981+02:00 zsolt-ThinkPad-T480 gnome-shell[23330]: GNOME Shell crashed with signal 6 2023-05-10T19:05:44.828047+02:00 zsolt-ThinkPad-T480 gnome-shell[23330]: == Stack trace for context 0x55df27bb9660 == 2023-05-10T19:05:46.021067+02:00 zsolt-ThinkPad-T480 systemd[22932]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=6/ABRT -- 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/2016308 Title: gnome-shell crashed with signal 6: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: Hello, This bug is triggered by Sweethome 3D but the underlying problem seems to be a libmutter issue. Setup: Ubuntu 23.04 Ryzen 6000 AMD 680 Gnome 44 Sweethome 3D 7.0.2 (from the repositories) Whenever I load a file in Sweethome 3D my desktop session is killed instantly. I am either thrown back to the desktop login or it stays black. This seems like a severe problem to me. Under no circumstances should an app like Sweethome 3D be able to crash mutter. I don't know how to give any logs. But I attach a sample file for Sweethome 3D. Actually it crashes with any file. Steps to reproduce: Start Sweethome 3D Draw some walls to make Draw a room Save to file Quit Sweethome 3D Start Sweethome 3D Load the file Crash To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
Hi, I have a thinkbook 16p Gen4 using archlinux with 6.3.1 kernel. The sound only works on 2 out of the 4 speakers (No bass, low volume). Accoding to https://psref.lenovo.com/Product/ThinkBook/ThinkBook_16p_G4_IRH, the audio chip is ACL3306-CG. I wonder if this is the same chip as the ACL3306, or it will require another driver? Also, I wonder if my problem is caused by the audio chip or the smart amplifier? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700085] Re: Mouse cursor is tiny on HiDPI screens
similar problem now in 23.04 almost 6 yrs later When i hover over the desktop cursor is tiny with 4k display and 200% scaling @wayland. so tiny that it is unusable. When i hover over the panel or open file manager cursor is fine. Looks very ugly to have cursor changing size on hovering at the border of panel/desktop background -- 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/1700085 Title: Mouse cursor is tiny on HiDPI screens Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I am on Artful and have switched to GNOME as GNOME is the default desktop now and Unity shows some instabilities. I am using a Lenovo Thinkpad X1 Carbon (2nd gen.) notebook with 14-inch QHD (2560x1440) display, so I am well over the good old 72-dpi CRT resolution. With some effort I have at least got a somewhat useful scaling of the GUI elements (esp. text size), mainly by getting into Unity7, getting into the Display Settings there, removing my ~1.5 scaling factor, returning to GNOME, installing the advanced settings manager (gnome- tweak-tool or so) and setting a scaling factor of ~2). Large text in accessibilty does not work for me as it makes the text huge. Now the mouse cursor does no bother on all these changes. It stays always in its 72-dpi hard-coded size which is really tiny under GNOME on my QHD screen. It gets easily totally invisible for me, especially on text fields where it gets a skinny vertical bar. Therefore there are two fixes needed: 1. Mouse cursor needs to scale with scale factor for the desktop, so that it is in a good size relation with the rest of the desktop. Please take this into account for fractional scaling efforts. 2. Even a standard-sized mouse cursor can be too small for people with vision problems, so the accessibility options need a possibility to apply a (fractional) adjustable scaling factor to the mouse cursor's standard size. Please take these changes into account ASAP, ideally on 17.10 at the latest. Please consider backporting upstream fixes for achieving this goal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019154] [NEW] [Strix GL703GS_GL703GS, Realtek ALC295, Speaker, Internal] fails after a while
Public bug reported: When starting a youtube video, sound works for a very short while then fades and disappears ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dewey 1700 F pulseaudio /dev/snd/pcmC0D0p: dewey 1700 F...m pulseaudio /dev/snd/controlC1: dewey 1700 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 10 23:25:43 2023 InstallationDate: Installed on 2023-04-01 (39 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [Strix GL703GS_GL703GS, Realtek ALC295, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703GS.314 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703GS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703GS.314:bd08/16/2021:br5.13:svnASUSTeKCOMPUTERINC.:pnStrixGL703GS_GL703GS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703GS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Strix dmi.product.name: Strix GL703GS_GL703GS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2019154 Title: [Strix GL703GS_GL703GS, Realtek ALC295, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: When starting a youtube video, sound works for a very short while then fades and disappears ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dewey 1700 F pulseaudio /dev/snd/pcmC0D0p: dewey 1700 F...m pulseaudio /dev/snd/controlC1: dewey 1700 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 10 23:25:43 2023 InstallationDate: Installed on 2023-04-01 (39 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [Strix GL703GS_GL703GS, Realtek ALC295, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703GS.314 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703GS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703GS.314:bd08/16/2021:br5.13:svnASUSTeKCOMPUTERINC.:pnStrixGL703GS_GL703GS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703GS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Strix dmi.product.name: Strix GL703GS_GL703GS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2019154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012388] Re: X11 window at top-right of the screen is invisible and steals mouse clicks
I followed the advice of Disabling the Gnome extension Ubuntu AppIndicators and rebooting which worked, but today I am seeing the following, if I click around the area in the circle it opens anydesk. This time, it ONLY happens to anydesk, not telegram or any other app in there. https://imgur.com/a/xGfBu4H -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window at top-right of the screen is invisible and steals mouse clicks Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019137] Re: gnome-software should (?) be separated from the packagekit
Not sure what you mean, but a GNOME Software with no PackageKit would mean that users are completely unable to install or remove any application from the Ubuntu archive, in addition to flavors not being able to use offline upgrades anymore. So this sounds like a suggestion with tons of huge drawbacks and annoyances to users, and no (?) advantage at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2019137 Title: gnome-software should (?) be separated from the packagekit Status in gnome-software package in Ubuntu: Confirmed Bug description: Given that the Snap Store is currently the default in Ubuntu instead of GNOME Software, the only reason GNOME Software (along with the Snap Store) can be installed is to support Flatpak applications. In the current instance, if you want to add flatpak support, GNOME Software is installed with both the apt packagekit add-on and the flatpak plugin, which is duplication of work (Software Updater already works on updates, and Snap Store works on showing deb apps). And since the future app store explicitly refuses [1], [2] to support flatpak applications, users who need this package format will be forced to put GNOME Software with everything I pointed out above. Therefore, it would be very nice if the developers removed the packagekit add-on from the "gnome-software part" and made it a "plug- in for gnome-software". I, unfortunately, have no such experience with packaging deb packages at the moment, and it turns out that it will obviously be necessary to work out both the code part (which, as far as I can see, won't be very difficult [3]), as well as the part where we will have to figure out where and how to insert the plugin as mandatory (for example, when the user completely gives up on snap packages) and as optional (because the Snap Store already stands). Also, let me know if this needs to be sent to upstream (Debian) instead of here. --- 1. https://github.com/ubuntu-flutter-community/software/issues/126 2. https://github.com/ubuntu-flutter-community/software/issues/30 3. https://build.opensuse.org/request/show/1031279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2019165] [NEW] It takes 56 seconds to open a window/program
Public bug reported: Yes, even more than that, it takes 56 seconds to open a program, to display a context menu, to open a new tab, but everything is okay within the window, such as typing. It happens in gnome terminal, file manager (nautilus), settings, firefox, etc. But it doesn't happen to chromium. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-common 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-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 530.41.03 Release Build (dvs-builder@U16-T02-35-3) Thu Mar 16 19:33:35 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04.1) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 11 08:58:18 2023 Dependencies: lsb-base 11.1.0ubuntu4 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] [103c:878e] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106M [GeForce RTX 2060 Max-Q] [103c:878e] InstallationDate: Installed on 2021-06-05 (704 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2019165 Title: It takes 56 seconds to open a window/program Status in xorg package in Ubuntu: New Bug description: Yes, even more than that, it takes 56 seconds to open a program, to display a context menu, to open a new tab, but everything is okay within the window, such as typing. It happens in gnome terminal, file manager (nautilus), settings, firefox, etc. But it doesn't happen to chromium. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-common 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-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 530.41.03 Release Build (dvs-builder@U16-T02
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Hardware decode on candidate/hwacc worked out of the box for me, thanks! - VaapiVideoDecoder - Xorg - VERSION="21.1 (Vera)" - Intel Kabylake (Gen9) - Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the Chromium snap, sudo snap install --channel candidate/hwacc chromium 2. Start Chromium, snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples. 4. Enter about:media-internals in the address bar, click the corresponding box (if the video is playing, it will have the "(kPlay)" identifier) and note if the page says VaapiVideoDecoder for kVideoDecoderName. You can alternatively check with intel_gpu_top (from intel-gpu-tools package) that the video engine bars are non zero during playback. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp