[Desktop-packages] [Bug 2015529] Re: can't install hp-plugin
*** This bug is a duplicate of bug 2012178 *** https://bugs.launchpad.net/bugs/2012178 Why is this bug staying unresolved for so long, despite the solution being trivial? I appreciate the hard work of the whole Ubuntu team but IMHO resolving bugs like this is at least as important as the new Snap CUPS agenda. -- 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/2015529 Title: can't install hp-plugin Status in hplip package in Ubuntu: Confirmed Bug description: Kubuntu 23.04. I need to install plug-in in order to scan documents properly. No problem with previous Kubuntu versions. - | PLUG-IN INSTALLATION FOR HPLIP 3.22.10 | -- Option Description -- -- d Download plug-in from HP (recommended) p Specify a path to the plug-in (advanced) q Quit hp-plugin (skip installation) Enter option (d=download*, p=specify path, q=quit) ? d --- | DOWNLOAD PLUGIN | --- Checking for network connection... Downloading plug-in from: Downloading plug-in: [\] 0% Traceback (most recent call last): File "/usr/bin/hp-plugin", line 363, in status, plugin_path, error_str = pluginObj.download(plugin_path, plugin_download_callback) ^ File "/usr/share/hplip/installer/pluginhandler.py", line 257, in download core = core_install.CoreInstall() ^^ File "/usr/share/hplip/installer/core_install.py", line 240, in __init__ self.passwordObj = password.Password(ui_mode) ^^ File "/usr/share/hplip/base/password.py", line 94, in __init__ self.__readAuthType() # self.__authType ^ File "/usr/share/hplip/base/password.py", line 119, in __readAuthType distro_name = get_distro_std_name(os_name) ^^^ NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'? ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: hplip 3.22.10+dfsg0-1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: W [07/Apr/2023:00:00:13 +0200] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [07/Apr/2023:00:00:13 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP-Color-LaserJet-Pro-MFP-M176n-Gray..\' already exists W [07/Apr/2023:08:52:52 +0200] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 CurrentDesktop: KDE Date: Fri Apr 7 09:00:55 2023 InstallationDate: Installed on 2023-03-19 (18 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230319) Lpstat: device for HP-Color-LaserJet-Pro-MFP-M176n: hp:/usb/HP_Color_LaserJet_Pro_MFP_M176n?serial=CND7G8NJJL MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Color-LaserJet-Pro-MFP-M176n.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Color-LaserJet-Pro-MFP-M176n.ppd: Permission denied ProcEnviron: LANG=it_IT.UTF-8 LANGUAGE=it:en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=baca8e64-c620-410c-8401-dc64ddeef942 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LX 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.:bvr4105:bd07/01/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage
[Desktop-packages] [Bug 2022841] [NEW] desktop crashed on login after sleep and clipboard extension not work
Public bug reported: desktop crashed on login after sleep and clipboard extension not work ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 09:07:41 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-03 (547 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-10 (205 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2022841 Title: desktop crashed on login after sleep and clipboard extension not work Status in gnome-shell package in Ubuntu: New Bug description: desktop crashed on login after sleep and clipboard extension not work ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 09:07:41 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-03 (547 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2022-11-10 (205 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2022841/+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 2022840] [NEW] [HDA-Intel - HDA NVidia, playback] stutters with mouse movement
Public bug reported: audio playing from the speakers of the monitor stutters every once a while. Messing with pulseaudio didn't help. Changing Displayport cable didn't help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logtenk1804 F pulseaudio /dev/snd/controlC1: logtenk1804 F pulseaudio /dev/snd/pcmC1D8p: logtenk1804 F...m pulseaudio /dev/snd/timer: logtenk1804 f pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 20:05:59 2023 InstallationDate: Installed on 2023-05-12 (22 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=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_Card: HDA NVidia - HDA NVidia Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [HDA-Intel - HDA NVidia, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: O54KT1AA dmi.board.name: 3733 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN 3422199553532 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrO54KT1AA:bd09/03/2021:br1.26:efr1.11:svnLENOVO:pn90RS001FUS:pvrLegionT526IOB6:rvnLENOVO:rn3733:rvrSDK0T76463WIN3422199553532:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_90RS_BU_Lenovo_FM_LegionT526IOB6: dmi.product.family: Legion T5 26IOB6 dmi.product.name: 90RS001FUS dmi.product.sku: LENOVO_MT_90RS_BU_Lenovo_FM_Legion T5 26IOB6 dmi.product.version: Legion T5 26IOB6 dmi.sys.vendor: LENOVO ** 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/2022840 Title: [HDA-Intel - HDA NVidia, playback] stutters with mouse movement Status in alsa-driver package in Ubuntu: New Bug description: audio playing from the speakers of the monitor stutters every once a while. Messing with pulseaudio didn't help. Changing Displayport cable didn't help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logtenk1804 F pulseaudio /dev/snd/controlC1: logtenk1804 F pulseaudio /dev/snd/pcmC1D8p: logtenk1804 F...m pulseaudio /dev/snd/timer: logtenk1804 f pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 20:05:59 2023 InstallationDate: Installed on 2023-05-12 (22 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=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_Card: HDA NVidia - HDA NVidia Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [HDA-Intel - HDA NVidia, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: O54KT1AA dmi.board.name: 3733 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN 3422199553532 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrO54KT1AA:bd09/03/2021:br1.26:efr1.11:svnLENOVO:pn90RS001FUS:pvrLegionT526IOB6:rvnLENOVO:rn3733:rvrSDK0T76463WIN3422199553532:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_90RS_BU_Lenovo_FM_LegionT526IOB6: dmi.product.family: Legion T5 26IOB6 dmi.product.name: 90RS001FUS dmi.product.sku: LENOVO_MT_90RS_BU_Lenovo_FM_Legion T5 26IOB6 dmi.product.version: Legion T5 26IOB6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 2022824] Re: random blue/pink frames in the desktop
** Description changed: I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop. every 1-2 minutes, there will be a random blue/pink frame(i'm not sure of the color because it only appears for a short time). I don't get this problem in fullscreen games running with dxvk and the random frames didn't show when I recorded my desktop with obs studio. I also got this - problem in gnome(on wayland). When I have a dxvk game running, I don't - get this issue. + problem in gnome(on wayland). When I have a dxvk game running or when I + have 2 monitors connected, I don't get this issue. One thing to note is + that when I have 2 monitors connected, my gpu will boost its vram clock + to 2000mhz. what I tried: -rebooting -updating -disabling blur in kde settings -lowering my refresh rate from 144hz to 120hz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 3 00:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1043:05d7] + Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] [1043:05d7] InstallationDate: Installed on 2023-06-01 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=ca576fb0-08b4-45d8-aadd-83e9df696ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: B450M Pro4-F dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2022824 Title: random blue/pink frames in the desktop Status in xorg package in Ubuntu: New Bug description: I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop. every 1-2 minutes, there will be a random blue/pink frame(i'm not sure of the color because it only appears for a short time). I don't get this problem in fullscreen games running with dxvk and the random frames didn't show when I recorded my desktop with obs studio. I also got this problem in gnome(on wayland). When I have a dxvk game running or when I have 2 monitors connected, I don't get this issue. One thing to note is that when I have 2 monitors connected, my gpu will boost its vram clock to 2000mhz. what I tried: -rebooting -updating -disabling blur in kde settings -lowering my refresh rate from 144hz to 120hz ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission
[Desktop-packages] [Bug 2022835] [NEW] package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: W [01/Jun/2023:00:00:26 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:09:56 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:13:20 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 Date: Sat Jun 3 13:13:20 2023 ErrorMessage: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for HP_Color_LaserJet_E55040_5A6F72: implicitclass://HP_Color_LaserJet_E55040_5A6F72/ device for HP_LaserJet_P4014_319155: implicitclass://HP_LaserJet_P4014_319155/ device for HP_LaserJet_P4014_319155@NPI319155.local: implicitclass://HP_LaserJet_P4014_319155%40NPI319155.local/ device for L5190: dnssd://EPSON%20L5190%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-e0bb9e531389 MachineType: Dell Inc. Latitude 5430 Papersize: letter PpdFiles: HP_Color_LaserJet_E55040_5A6F72: HP Color LaserJet E55040, driverless, cups-filters 1.28.15 L5190: EPSON L5190 Series, driverless, cups-filters 1.28.15 HP_LaserJet_P4014_319155@NPI319155.local: HP LaserJet P4014, driverless, cups-filters 1.28.15 HP_LaserJet_P4014_319155: HP LaserJet P4014, driverless, cups-filters 1.28.15 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=2efb7e3e-d9e5-4dda-a70f-e5c6425f913c ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=2efb7e3e-d9e5-4dda-a70f-e5c6425f913c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: cups Title: package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2022 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 03G0RF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd06/20/2022:br1.4:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn03G0RF:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2022835 Title: package cups 2.4.1op1-1ubuntu4.2 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 Status in cups package in Ubuntu: New Bug description: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: W [01/Jun/2023:00:00:26 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:09:56 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 W [03/Jun/2023:13:13:20 -0400] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 Date: Sat Jun 3 13:13:20 2023 ErrorMessage: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-09-28 (247 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lpstat: device for HP_Color_LaserJet_E55040_5A6F72: implicitclass://HP_Color_LaserJet_E55040_5A6F72/ device for HP_LaserJet_P4014_319155:
[Desktop-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics
Okay we'll wait for a later build. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After Mesa upgrades, Chrome won't show graphics Status in chromium-browser package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in chromium-browser source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in chromium-browser source package in Lunar: Invalid Status in mesa source package in Lunar: New Bug description: [Impact] After patching Mesa with some driver updates, Chromium/Brave started seeing corrupt graphics. This was due to GPU acceleration being enabled in the browser by default now, and the old GPU shader cache is invalid in some ways and the browser is not able to recognize that the driver has changed, since the upstream version string hasn't changed. This is shown for instance with 'glxinfo -B' or under 'chrome:gpu' from the browser. The fix is to make the upstream VERSION to have the full packaging version, this will then be used for the core profile version string as well. [Test case] - run stock jammy, install brave-browser from brave.com, launch brave- browser, check that 'brave://gpu' shows things are accelerated, then exit the browser - enable proposed, install libgl1-mesa-dri et al - launch brave-browser again, verify that gfx are not corrupted and brave://gpu is showing acceration being used with the pulled update, graphics would be severely corrupted [Where things could go wrong] There could be apps that expect the Mesa version string to only contain a.b.c, and break in some ways when that's no longer the case. -- After today's Ubuntu 22.04 Mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The Mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There are several useful pointers and bypasses listed in that AskUbuntu link (one being to remove affected users' GPUCache directories, which does not destroy their profiles and seems to work in many but not all cases). Not sure if this is an issue with Mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013235] Re: Drag and Drop not working in Qt-Applications on Gnome 44
Tracked for OpenShot with https://github.com/OpenShot/openshot- qt/issues/5221 ** Also affects: openshot Importance: Undecided Status: New -- 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/2013235 Title: Drag and Drop not working in Qt-Applications on Gnome 44 Status in Kdenlive: Invalid Status in Mutter: Fix Released Status in OpenShot Video Editor: New Status in mutter package in Ubuntu: Fix Committed Bug description: Drag and drop items within Qt applications not working since upgrade to Ubuntu Lunar developmental release. The items can be picked up then the cursor changed to the "forbid" sign and no further interaction to the app. Confirmed affected apps: 3d Slicer, Krita. Upstream bug report: https://gitlab.gnome.org/GNOME/mutter/-/issues/2715 To manage notifications about this bug go to: https://bugs.launchpad.net/kdenlive/+bug/2013235/+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 1199397] Re: Xorg crashed with SIGABRT in raise()
A cash discount is a reduction in the purchase price offered to a customer who pays for goods or services with cash or by making immediate payment. It is a common practice used by businesses to encourage customers to pay quickly and avoid the need for credit or delayed payment terms.https://www.cashdiscount360.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1199397 Title: Xorg crashed with SIGABRT in raise() Status in xorg-server package in Ubuntu: Invalid Bug description: The system become unresponsive. Mouse freeze; num lock responded after 10-15 seconds... I had to reboot: Alt+Sysrq+B ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-core 2:1.14.1-0ubuntu0.8 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 CurrentDmesg: [ 20.515744] Adding 512544k swap on /dev/zram1. Priority:5 extents:1 across:512544k SSFS Date: Tue Jul 9 17:41:28 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2013-05-02 (68 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130502) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7360 MarkForUpload: True ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=86fe6e26-730a-49ee-9ef7-096ce5dedeb0 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 malloc () from /lib/x86_64-linux-gnu/libc.so.6 Title: Xorg crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/11/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7360 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.:bvrV1.10:bd11/11/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7360:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7360:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7360 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Tue Jul 9 17:43:19 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.1-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1199397/+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 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Confirmed ** Changed in: libdrm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]]
[Desktop-packages] [Bug 2021907] Re: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11, 2
** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/2021907 Title: Black display on boot and Mobility Radeon HD 4670 related freezes and crashes on iMac 11,2 Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: I have a mid-2010 iMac (iMac 11,2), with a Mobility Radeon HD 4670, running Linux Mint 21.1 Xfce Edition, and it has several issues. I've decided to report the issue here since it seems to be a kernel bug, and since Mint is based on Ubuntu where its kernels are built, I thought it'd be wise to report here and escalating to the LKML if necessary. Firstly, its display turns off when it boots, unless an external display is connected, in which case both displays work fine. But the backlight can't be controlled by typical programs (brightness buttons don't work, and xbacklight says 'No outputs have backlight property') apart from light (https://github.com/haikarainen/light); but that only works on kernels 5.15.*, not on 6.3.4, on that kernel only the brightness value changes, but to no effect. Upon bootup, I can see: uhci_hcd :00:1a.0: Found HC with no IRQ. Check BIOS/PCI :00:1a.0 setup! uhci_hcd :00:1a.0: init :00:1a.0 fail, -19 uhci_hcd :00:1d.0: Found HC with no IRQ. Check BIOS/PCI :00:1d.0 setup! uhci_hcd :00:1d.0: init :00:1d.0 fail, -19 at the top of the screen for a few seconds before the Mint splash screen takes over. The device's internal display turns off upon wake up from suspend, giving the following output in dmesg: PM: suspend entry (deep) Filesystems sync: 0.020 seconds Freezing user space processes ... (elapsed 0.002 seconds) done. OOM killer disabled. Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. printk: Suspending console(s) (use no_console_suspend to debug) sd 1:0:0:0: [sda] Synchronizing SCSI cache sd 1:0:0:0: [sda] Stopping disk ACPI: EC: interrupt blocked ACPI: PM: Preparing to enter system sleep state S3 ACPI: EC: event blocked ACPI: EC: EC stopped ACPI: PM: Saving platform NVS memory Disabling non-boot CPUs ... smpboot: CPU 1 is now offline smpboot: CPU 2 is now offline smpboot: CPU 3 is now offline ACPI: PM: Low-level resume complete ACPI: EC: EC started ACPI: PM: Restoring platform NVS memory Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x1 Disabled fast string operations CPU1 is up smpboot: Booting Node 0 Processor 2 APIC 0x4 Disabled fast string operations CPU2 is up smpboot: Booting Node 0 Processor 3 APIC 0x5 Disabled fast string operations CPU3 is up ACPI: PM: Waking up from system sleep state S3 ACPI: EC: interrupt unblocked ACPI: EC: event unblocked sd 1:0:0:0: [sda] Starting disk [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [drm] PCIE GART of 1024M enabled (table at 0x0014C000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c598 debugfs: File 'radeon_ring_gfx' in directory '0' already present! debugfs: File 'radeon_ring_dma1' in directory '0' already present! [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 2 usecs debugfs: File 'radeon_ring_uvd' in directory '0' already present! [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 0 usecs ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata1.00: supports DRM functions and may not be fully accessible ata1.00: configured for UDMA/133 ata2.00: ACPI cmd ef/10:03:00:00:00:a0(SET FEATURES) filtered out ata2.00: configured for UDMA/100 firewire_core :05:00.0: rediscovered device fw0 [drm] ib test on ring 5 succeeded [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed [drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed [drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed
[Desktop-packages] [Bug 2017716] Re: Folders and files frequently need to be clicked twice
** Changed in: nautilus 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/2017716 Title: Folders and files frequently need to be clicked twice Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Nautilus randomly drops about half of my mouse clicks. Clicked folders or files will sometimes open at once, yet the next time(s) fail to respond until clicked a second time. I am seeing this both on X11 and on wayland. Single or double click policy does not make any difference. I have experimented with different mouse speeds but have not seen any noticeable difference. This behaviour is, in fact, something that I already noticed when I was trying out Ubuntu 22.10. It was enough to send me back to 22.04. I was really hoping that the issue would be solved by now, but clearly it is not. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 02:25:07 2023 InstallationDate: Installed on 2022-10-29 (178 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (13 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2017716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp