[Touch-packages] [Bug 2022825] Re: motd-news.timer trigger motd-news.service even if disable
When you disable it like UBUNTU says: https://ubuntu.com/legal/motd. Its not working , and modt keep getting errors when i run commend "systemctl status" But when i disable the timer, issue get solved, and systemctl not showing units faild. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2022825 Title: motd-news.timer trigger motd-news.service even if disable Status in base-files package in Ubuntu: Incomplete Bug description: Hello, guys, how are you? I notice motd-news.timer activate motd-news.service even when motd-new.service disable. I follow this doc's from UBUNTU: https://ubuntu.com/legal/motd /etc/default/motd-news has an ENABLED=1 setting that to 0 for disable. It's not working too… When you reboot the server and put sudo systemctl status motd-news.service Service look dead. (disable) but he got trigger by motd-news.timer after 10 - 20 minutes (screenshot): https://ibb.co/yXTpzGq if you look on the screenshot, you will see: TriggeredBy: ● motd-news.timer I can disable the motd-news.timer service, but i don't know if it will affect other services of UBUNTU. Anyway It's still a bug, even if i disable the timer service, it's not should be this way. Happened on 2 Different machines of UBUNTU 22.04 (Google Cloud Platform) Be happy for your recommendation before i disable the motd-new.timer with systemctl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2022825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2022825] Re: motd-news.timer trigger motd-news.service even if disable
The /etc/default/motd-news file is read by the /etc/update- motd.d/50-motd-news script which is launched by motd-news.service. It is normal that setting the option in this file will not stop motd- news.service from running - however, it makes the script a no-op that does not access the network. Are you seeing the motd-news.service access the network and make changes to files when ENABLED=0 is set? This is what is guaranteed by https://ubuntu.com/legal/motd. You are free to disable the timer service as well if that is your preference. The documentation tells users how to disable the service without having to know systemd service interfaces. ** Changed in: base-files (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2022825 Title: motd-news.timer trigger motd-news.service even if disable Status in base-files package in Ubuntu: Incomplete Bug description: Hello, guys, how are you? I notice motd-news.timer activate motd-news.service even when motd-new.service disable. I follow this doc's from UBUNTU: https://ubuntu.com/legal/motd /etc/default/motd-news has an ENABLED=1 setting that to 0 for disable. It's not working too… When you reboot the server and put sudo systemctl status motd-news.service Service look dead. (disable) but he got trigger by motd-news.timer after 10 - 20 minutes (screenshot): https://ibb.co/yXTpzGq if you look on the screenshot, you will see: TriggeredBy: ● motd-news.timer I can disable the motd-news.timer service, but i don't know if it will affect other services of UBUNTU. Anyway It's still a bug, even if i disable the timer service, it's not should be this way. Happened on 2 Different machines of UBUNTU 22.04 (Google Cloud Platform) Be happy for your recommendation before i disable the motd-new.timer with systemctl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2022825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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]
[Touch-packages] [Bug 2022836] [NEW] package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de er
Public bug reported: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2023c-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 3 13:13:18 2023 ErrorMessage: el subproceso instalado paquete tzdata 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) PackageArchitecture: all 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: tzdata Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2022836 Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 Status in tzdata package in Ubuntu: New Bug description: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2023c-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 3 13:13:18 2023 ErrorMessage: el subproceso instalado paquete tzdata 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) PackageArchitecture: all 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: tzdata Title: package tzdata 2023c-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete tzdata script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2022836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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:
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1957194] Re: resume from hibernation broken when resume image is autodetected another case
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1957194
Title:
resume from hibernation broken when resume image is autodetected
another case
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
My issue very similar to
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297
I am assuming that the code at about line 162 in
`/usr/share/initramfs-tools/init` like that:
```
resume=*)
RESUME="${x#resume=}"
case $RESUME in
UUID=*)
RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
esac
;;
```
Only works if user wants to set resume partition as `UUID=some` at
file like `/etc/initramfs-tools/conf.d/resume`. But in the case when
initramfs hook resume automatically save `UUID=some` in initrd
`conf/conf.d/zz-resume-auto` file it doesn't matter. Including for
operate `DEV=$(readlink -f "$resume")` correctly in
`/usr/share/initramfs-tools/scripts/local-premount/resume`
Therefore I decide to add similar code to `/usr/share/initramfs-
tools/scripts/local-premount/resume` to fix an issue with resuming.
See a patch in attachment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1957194/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2022830] Re: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/2022830 Title: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 128 Status in dictionaries-common package in Ubuntu: New Bug description: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: dictionaries-common 1.28.14 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 CasperMD5CheckResult: pass Date: Sat Jun 3 14:48:07 2023 DuplicateSignature: package:dictionaries-common:1.28.14 Setting up wpolish (20210105-1) ... dpkg: error processing package wpolish (--configure): installed wpolish package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed dictionaries-common package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-06-03 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all 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: dictionaries-common Title: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/2022830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2022830] [NEW] package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status
Public bug reported: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: dictionaries-common 1.28.14 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 CasperMD5CheckResult: pass Date: Sat Jun 3 14:48:07 2023 DuplicateSignature: package:dictionaries-common:1.28.14 Setting up wpolish (20210105-1) ... dpkg: error processing package wpolish (--configure): installed wpolish package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed dictionaries-common package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-06-03 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all 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: dictionaries-common Title: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/2022830 Title: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 128 Status in dictionaries-common package in Ubuntu: New Bug description: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: dictionaries-common 1.28.14 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 CasperMD5CheckResult: pass Date: Sat Jun 3 14:48:07 2023 DuplicateSignature: package:dictionaries-common:1.28.14 Setting up wpolish (20210105-1) ... dpkg: error processing package wpolish (--configure): installed wpolish package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed dictionaries-common package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2023-06-03 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all 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: dictionaries-common Title: package dictionaries-common 1.28.14 failed to install/upgrade: installed dictionaries-common package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/2022830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to libdrm 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]]
[Touch-packages] [Bug 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1
dpkg: error processing package libssl3:amd64 (--configure): installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: libssl3:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2008846 Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 Status in needrestart package in Ubuntu: New Status in openssl package in Ubuntu: Incomplete Bug description: encounter error when attempting to do sudo update, upgrade, and full- upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libssl3:amd64 3.0.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 1 10:28:26 2023 ErrorMessage: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-01 (150 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: openssl Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2008846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to libdrm 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 [drm:radeon_dp_link_train
[Touch-packages] [Bug 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1
and also get this from plesk Hello, Winston Derek Some problems occurred with the System Updates tool on your server mystifying-swartz.212-227-218-70.plesk.page. Please resolve them manually. Reason: 2023-06-03 06:25:22 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2023-06-03 06:25:22 ERROR: Previous Plesk installer call finished unsuccessfully. PUM will not perform any update operations until Plesk installation is fixed. 2023-06-03 06:25:22 ERROR: Exited with returncode 50. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2008846 Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 Status in needrestart package in Ubuntu: New Status in openssl package in Ubuntu: Incomplete Bug description: encounter error when attempting to do sudo update, upgrade, and full- upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libssl3:amd64 3.0.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 1 10:28:26 2023 ErrorMessage: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-01 (150 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: openssl Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2008846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1
This is the current complete log if could help. Execution failed. Command: autoinstaller Arguments: Array ( [0] => --select-product-id [1] => plesk [2] => --select-release-current [3] => --upgrade-installed-components ) Details: Downloading file products.inf3: 0% Downloading file products.inf3: 100% was finished. Downloading file pool/PSA_18.0.52_11753/release.inf3: 0% Downloading file pool/PSA_18.0.52_11753/release.inf3: 100% was finished. Downloading file pool/PSA_18.0.51_11495/release.inf3: 0% Downloading file pool/PSA_18.0.51_11495/release.inf3: 100% was finished. Downloading file pool/PSA_18.0.50_11079/release.inf3: 0% Downloading file pool/PSA_18.0.50_11079/release.inf3: 100% was finished. Downloading file pool/PSA_18.0.49_10759/release.inf3: 0% Downloading file pool/PSA_18.0.49_10759/release.inf3: 100% was finished. Downloading file pool/PSA_18.0.48_10183/release.inf3: 0% Downloading file pool/PSA_18.0.48_10183/release.inf3: 100% was finished. Downloading file pool/PSA_18.0.47_10005/release.inf3: 0% Downloading file pool/PSA_18.0.47_10005/release.inf3: 100% was finished. Downloading file pool/PSA_18.0.46_9775/release.inf3: 0% Downloading file pool/PSA_18.0.46_9775/release.inf3: 100% was finished. Downloading file plesk.inf3: 0% Downloading file plesk.inf3: 100% was finished. Downloading file sitebuilder.inf3: 0% Downloading file sitebuilder.inf3: 100% was finished. Downloading file pool/WPB_18.0.51_64/release.inf3: 0% Downloading file pool/WPB_18.0.51_64/release.inf3: 100% was finished. Downloading file PHP82_17/release.inf3: 0% Downloading file PHP82_17/release.inf3: 100% was finished. Downloading file php82.inf3: 0% Downloading file php82.inf3: 100% was finished. Downloading file PHP81_17/release.inf3: 0% Downloading file PHP81_17/release.inf3: 100% was finished. Downloading file php81.inf3: 0% Downloading file php81.inf3: 100% was finished. Downloading file PHP80_17/release.inf3: 0% Downloading file PHP80_17/release.inf3: 100% was finished. Downloading file php80.inf3: 0% Downloading file php80.inf3: 100% was finished. Downloading file php72.inf3: 0% Downloading file php72.inf3: 100% was finished. Downloading file PHP74_17/release.inf3: 0% Downloading file PHP74_17/release.inf3: 100% was finished. Downloading file php74.inf3: 0% Downloading file php74.inf3: 100% was finished. Downloading file php73.inf3: 0% Downloading file php73.inf3: 100% was finished. Downloading file php71.inf3: 0% Downloading file php71.inf3: 100% was finished. Downloading file setemplates.inf3: 0% Downloading file setemplates.inf3: 100% was finished. Downloading file pp-sitebuilder.inf3: 0% Downloading file pp-sitebuilder.inf3: 100% was finished. Downloading file billing.inf3: 0% Downloading file billing.inf3: 100% was finished. Downloading file mysql.inf3: 0% Downloading file mysql.inf3: 100% was finished. Downloading file apache.inf3: 0% Downloading file apache.inf3: 100% was finished. Downloading file nginx.inf3: 0% Downloading file nginx.inf3: 100% was finished. Downloading file php70.inf3: 0% Downloading file php70.inf3: 100% was finished. Downloading file php56.inf3: 0% Downloading file php56.inf3: 100% was finished. Downloading file php55.inf3: 0% Downloading file php55.inf3: 100% was finished. Downloading file php54.inf3: 0% Downloading file php54.inf3: 100% was finished. Downloading file php53.inf3: 0% Downloading file php53.inf3: 100% was finished. Downloading file php52.inf3: 0% Downloading file php52.inf3: 100% was finished. Downloading file pmm.inf3: 0% Downloading file pmm.inf3: 100% was finished. Checking for installed packages... Downloading file pool/PSA_18.0.51_11495/plesk-18.0.51-ubt22.04-x86_64.inf3: 0% Downloading file pool/PSA_18.0.51_11495/plesk-18.0.51-ubt22.04-x86_64.inf3: 100% was finished. Downloading file PHP74_17/php74-ubt22.04-x86_64.inf3: 0% Downloading file PHP74_17/php74-ubt22.04-x86_64.inf3: 100% was finished. Downloading file PHP80_17/php80-ubt22.04-x86_64.inf3: 0% Downloading file PHP80_17/php80-ubt22.04-x86_64.inf3: 100% was finished. Downloading file PHP81_17/php81-ubt22.04-x86_64.inf3: 0% Downloading file PHP81_17/php81-ubt22.04-x86_64.inf3: 100% was finished. Downloading file PHP82_17/php82-ubt22.04-x86_64.inf3: 0% Downloading file PHP82_17/php82-ubt22.04-x86_64.inf3: 100% was finished. Downloading file pool/WPB_18.0.51_64/sitebuilder-18.0.51-deball-all.inf3: 0% Downloading file pool/WPB_18.0.51_64/sitebuilder-18.0.51-deball-all.inf3: 100% was finished. Registering i386 architecture support Synchronizing the Debian APT package index files... Hit:1 http://autoinstall.plesk.com/pool/PSA_18.0.51_11495 jammy InRelease Hit:2 http://autoinstall.plesk.com/PMM_0.1.11 jammy InRelease Hit:4 https://download.docker.com/linux/ubuntu jammy InRelease Hit:5 http://autoinstall.plesk.com/PHP74_17 jammy InRelease Hit:6 https://autoinstall.plesk.com/grafana/deb stable InRelease Hit:7 http://autoinstall.plesk.com/PHP80_17 jammy InRelease Hit:9 http://autoinstall.plesk.com/PHP81_17
[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
I may be mistaken in thinking that the Firefox I was using under 20.04 was not a snap. All the same, launching new Firefox windows with the same session on different workspaces was a normal part of my day-to-day workflow until I upgraded to 22.04 a couple of weeks ago. I now get an error when I try it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup Status in X2Go: New Status in Xpra Terminal Server: New Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in x2goserver package in Ubuntu: Confirmed Status in snapd package in Debian: New Status in snapd package in Fedora: New Bug description: I just upgraded from hirsute to impish using do-release-upgrade. On the upgraded system, I can't run either firefox or chromium (both of which worked fine under hirsute). Both fail with: /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where NNN is my uid With firefox, I was able to fix the problem with: snap remove --purge firefox apt purge firefox apt install firefox Now firefox works. But I tried the same thing substituting chromium- browser for firefox, and it didn't help: chromium fails with the same error message. I guess there must be something left over from the hirsute version of snapd that isn't getting noticed or cleared by the impish version? Someone suggested this might be related to bug 1850667, but that bug is marked fixed as of a couple months ago, and I just did this upgrade today. Also, it doesn't mention the error message I'm seeing. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: snapd 2.53+21.10ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 18 18:12:45 2021 InstallationDate: Installed on 2020-04-29 (568 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snapd UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
