[Touch-packages] [Bug 2061584] Re: Rendering issues in VirtualBox with 3d on (GTK ngl backend)
Are we sure this can't just be grouped in with bug 2061118? Bug 2063923 for example is not VMware but shows a video with the same looking artifacts as bug 2061118. -- 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/2061584 Title: Rendering issues in VirtualBox with 3d on (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Triaged Status in mesa source package in Noble: Triaged Bug description: GTK4 apps are rendering very badly with Ubuntu 24.04 LTS Beta when ran in VirtualBox. This includes the Welcome to Ubuntu app (gnome-initial-setup), gnome- text-editor, and drawing the background (which uses gnome-shell- extension-desktop-icons-ng on Ubuntu). This issue was triggered by GTK4's switch to ngl as the default renderer instead of gl. However, some other similar issues (LP: #2061118, LP: #2060679) are being fixed in mesa instead of in gtk4 itself. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061584/+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 2064213] [NEW] Release BlueZ 5.75 to Oracular
Public bug reported: Release BlueZ 5.75 to Oracular: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.75.tar.xz ** Affects: bluez (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Tags: oracular ** Changed in: bluez (Ubuntu) Milestone: None => ubuntu-24.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2064213 Title: Release BlueZ 5.75 to Oracular Status in bluez package in Ubuntu: Triaged Bug description: Release BlueZ 5.75 to Oracular: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.75.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2064213/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
Here's the fix for Oracular. ** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix ** Patch added: "webkit2gtk_2.44.0-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2037015/+attachment/5772919/+files/webkit2gtk_2.44.0-2ubuntu1.debdiff -- 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/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Won't Fix Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
** Changed in: mesa (Ubuntu) Status: Triaged => Won't Fix -- 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/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Won't Fix Status in webkit2gtk package in Ubuntu: In Progress Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2064196] Re: Can't change display position to "right of"
I wonder if this is due to bug 2060268... ** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu) ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- 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/2064196 Title: Can't change display position to "right of" Status in gnome-control-center package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: I have two monitors (Iiyama and Philips). In 22.04 I had two separate pulpits on each monitors. Currently in "Settings -> Displays" I can set it to "duplicate" or "joined". joined option is inconvenient because, every window I open is by default in the center of the gap between two monitors. I'am able to change it manually via nvidia-settings but it isn't persistent. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.239.06 Sat Feb 3 06:03:07 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 08:05:32 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e] InstallationDate: Installed on 2024-04-28 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: MSI MS-7758 ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064196/+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 2064177] Re: Window borders and shadows missing from GTK3 dialogs
** Summary changed: - Window borders and shadows missing from GTK dialogs + Window borders and shadows missing from GTK3 dialogs ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs Status in gnome-shell package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I have a fresh Ubuntu 24.04 instalation and some of the windows have a few problems. Some are probably caused by theming, as the windows' borders (or their color) makes them impossible to discern from the background windows. Just earlier I discovered another bug, related to detecting the click and window I clicked. I am trying to see the sub-content of a software update but the system reacts as I clicked the window below. In the recording you can see this happening both with the Terminal and with Firefox. I have plenty of screenshots and also a screen recording that show the bugs. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 00:37:47 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-26 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+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 2064146] Re: Screen shows orange snap to place wrongly
*** This bug is a duplicate of bug 2063970 *** https://bugs.launchpad.net/bugs/2063970 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2063970, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-tiling- assistant (Ubuntu) ** This bug has been marked a duplicate of bug 2063970 Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. -- 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/2064146 Title: Screen shows orange snap to place wrongly Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: I have "Active screen edge" -feature enabled. First bug: I had 2 instances of transparent orange snap to place appear for no reason in a strange place. Second bug: I have transparent orange snap to place appear twice when trying to snap window to left, top and right. Bottom appears only once correctly. The animation is also shown twice. Screen capture is not possible during this window snap so I took photos on phone. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:51:51 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22be] InstallationDate: Installed on 2024-04-29 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: LENOVO 20UBCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=ef15c653-655e-4eb6-8f55-41ec14bbdb78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2023 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET43W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2WET43W(1.33):bd11/06/2023:br1.33:efr1.15:svnLENOVO:pn20UBCTO1WW:pvrThinkPadX1YogaGen5:rvnLENOVO:rn20UBCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20UB_BU_Think_FM_ThinkPadX1YogaGen5: dmi.product.family: ThinkPad X1 Yoga Gen 5 dmi.product.name: 20UBCTO1WW dmi.product.sku: LENOVO_MT_20UB_BU_Think_FM_ThinkPad X1 Yoga Gen 5 dmi.product.version: ThinkPad X1 Yoga Gen 5 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2064146/+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 2064169] Re: Keyboard shortcuts
When the problem is happening please run: gsettings list-recursively | grep keybindings > keybindings.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2064169 Title: Keyboard shortcuts Status in gnome-shell package in Ubuntu: Incomplete Bug description: I don't know if the section is correct, but when using the ubuntu keyboard shortcuts I added. Increase sound volume, when you put the super+up on, it ends up doing the behavior of another one that I had already removed to give way to this new one I made. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 17:28:25 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0781] Subsystem: Dell GM108M [GeForce 940MX] [1028:0781] InstallationDate: Installed on 2024-04-28 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Dell Inc. Inspiron 7460 ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=ddb1ca08-8d86-4cc1-a5ef-6f59217ebac6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0JXYRN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd07/23/2021:br1.15:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn0JXYRN:rvrA00:cvnDellInc.:ct10:cvr:sku0781: dmi.product.family: Inspiron dmi.product.name: Inspiron 7460 dmi.product.sku: 0781 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064169/+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 2064017] Re: Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related)
Please try adding kernel parameter: i915.enable_psr=0 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2064017 Title: Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related) Status in linux package in Ubuntu: Incomplete Bug description: My machine information is following : HP EliteBook 840 G3 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] xrandr -q active mode on laptop display : 1368x768 60.01 Tried using 6.8.8-060808 kernel (instead of the lubuntu 24.04 default shipped kernel 6.8.0-31), same issue. Rolling back the kernel to 6.7 fixed the problem,maybe there were some video driver changes from kernel 6.7 to 6.8 ? While using the 6.8 kernel I did some experiments: disabled picom in startup , no effect Tried changing display resolution, just moves vertical position of band. (at the above resolution 1368x768 vertical mouse pointer flicker range is around 640 ( measured running watch -t -n 0.0001 xdotool getmouselocation from a bash terminal) Tried moving refresh rate slightly around 60 Hz by creating a new modeline using cvt tool and adding new mode with xrandr, no effect. tried connecting external display on laptop VGA port and duplicating screen and the issue seems to disappear. tried capturing a video of the desktop using ffmpeg with x11grab, but it does not show the issue. I attached a short video of the laptop display flicker I recorded using my phone ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Sun Apr 28 09:44:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079] InstallationDate: Installed on 2024-04-25 (3 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 004: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP EliteBook 840 G3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.release: 1.42 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.42 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.78 dmi.chassis.asset.tag: 5CG7042V5J dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.120 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr:skuZ2A57UT#ABA: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: Z2A57UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064017/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
** Tags added: noble ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen Status in Ubuntu AppIndicators: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
The crash (bug 2062146) is now awkwardly entangled with this bug. It occurs at the same time as, or usually instead of corruption. Bisected in Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033#note_2385595 Prior to that regression, I still believe the corruption probably started around: https://github.com/WebKit/WebKit/commit/8b0ce3683045d93cd365e91a4299f7e9babfc126 If you need a workaround for both issues then the best I have found is environment: WEBKIT_DMABUF_RENDERER_FORCE_SHM=1 ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11033 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033 -- 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/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
** No longer affects: yelp (Ubuntu) -- 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/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: In Progress Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Also tracking in https://gitlab.freedesktop.org/mesa/mesa/-/issues/11008 -- 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/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Bug 2061079 being so similar makes me think long term we will find that GTK4 is doing something wrong. We just don't know what it's doing wrong yet. ** Changed in: gtk4 (Ubuntu Noble) Status: Invalid => Confirmed ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11008 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11008 -- 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/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Users of the Nvidia 470 driver please see bug 2061079. -- 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/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Generalised to cover non-VMware (bug 2063923). ** Summary changed: - Rendering issues in vmware with 3d on (GTK ngl backend) + Rendering issues in virtual machines (GTK ngl backend) ** Tags added: noble vmwgfx -- 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/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2063923] Re: Graphic shows strange
*** This bug is a duplicate of bug 2061118 *** https://bugs.launchpad.net/bugs/2061118 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2061118, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gtk4 (Ubuntu) ** This bug has been marked a duplicate of bug 2061118 Rendering issues in virtual machines (GTK ngl backend) -- 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/2063923 Title: Graphic shows strange Status in gtk4 package in Ubuntu: New Bug description: In Ubuntu 24.04 LTS, GNOME Applications are written in Flutter, but it doesn't look proper. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:32:00 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio 1.0 GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio 1.0 GPU [1af4:1100] InstallationDate: Installed on 2024-04-27 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=e54ffc83-f536-4520-a7c1-9f8dc8cca485 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2063923/+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 2063536] Re: flickering screen
I can see 'gjs' crashing constantly so please try: gnome-extensions disable d...@rastersoft.com If that doesn't fix it then please provide a video of the problem. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2063536 Title: flickering screen Status in Ubuntu: Incomplete Bug description: automatically refresh and hang ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 08:44:25 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtbth/3.9.8, 6.5.0-27-generic, x86_64: installed rtbth/3.9.8, 6.5.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-S GT2 [UHD Graphics 630] [1462:7d82] InstallationDate: Installed on 2024-04-16 (9 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Micro-Star International Co., Ltd. MS-7D82 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=5d5b2975-ec40-4c41-919c-f0c2ecc1a822 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.22 dmi.board.asset.tag: Default string dmi.board.name: PRO H410M-B(MS-7D82) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.22:bd03/24/2022:br5.19:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D82:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROH410M-B(MS-7D82):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D82 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063536/+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 2063831] Re: Clicking on bottom half of applications switches to background application
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: focus -- 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/2063831 Title: Clicking on bottom half of applications switches to background application Status in mutter package in Ubuntu: New Bug description: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of Eclipse, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063831/+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 1869655] Re: Boot animations start too late to be useful
More than rotated framebuffers, defaulting to simpledrm means Plymouth
doesn't know the physical monitor dimensions. So it uses heuristics and
that leads to the logo scale not matching the login screen which would
be a regression of bug 2054769. Actually it already happens on some slow
booting machines occasionally. But that too can be worked around with:
plymouth.force-scale={1,2}
And no, checking for rotation sensors is not a good idea because it
would give the wrong result for laptop/tablet convertibles that don't
have rotated framebuffers.
--
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/1869655
Title:
Boot animations start too late to be useful
Status in Plymouth:
New
Status in grub2 package in Ubuntu:
Invalid
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in plymouth package in Ubuntu:
Triaged
Bug description:
Boot animations start too late to be useful
Modern systems spend all their boot time (a couple of seconds)
decompressing the kernel. During that time the user only sees the
static BIOS logo (ACPI BGRT). Then when Plymouth can finally start
animating, the startup process is already finished and there's
virtually no time left to show any useful animations.
This could be fixed in:
grub: By adding a splash under the BIOS logo to show some progress
_before_ a Linux kernel is even started
and/or
plymouth: By preferencing legacy framebuffer devices (like EFI) over
DRM, if we find those are available a few seconds sooner. That would
also fix bug 1868240 completely, and bug 1836858 mostly as the flicker
moves to when the login screen starts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1869655/+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 2046856] Re: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** Summary changed: - package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 + package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- 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/2046856 Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Issue in upgrade of version, more details to be added ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20221022 CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Dec 19 01:45:42 2023 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046856/+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 2047975] Re: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
** Summary changed: - package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 + package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** Tags added: mantic -- 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/2047975 Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: Confirmed Bug description: upgraded from 22.04 -> 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 253.5-1ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jan 3 21:06:55 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-27 (311 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.1ubuntu5 apt 2.7.6 SourcePackage: systemd Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+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 2046857] Re: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** This bug is no longer a duplicate of bug 2046856 package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- 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/2046857 Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Duplicate of 2046856 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: systemd-resolved 252.5-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20221022 CloudSubPlatform: config-disk (/dev/vdb) Date: Tue Dec 19 01:56:08 2023 DpkgTerminalLog: Setting up systemd-resolved (252.5-2ubuntu3) ... Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf... cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file dpkg: error processing package systemd-resolved (--configure): installed systemd-resolved package post-installation script subprocess returned error exit status 1 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: systemd Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046857/+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 2062550] Re: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit statu
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** Summary changed: - package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 + package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- 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/2062550 Title: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Upgrade from 22.04 LTS to 23.10 ProblemType: Package DistroRelease: Ubuntu 23.10 Package: systemd-resolved 253.5-1ubuntu6.1 ProcVersionSignature: Ubuntu 6.5.0-1020.21-oem 6.5.13 Uname: Linux 6.5.0-1020-oem x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 19 16:01:52 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-24 (178 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.7.3ubuntu0.1 SourcePackage: systemd Title: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2024-04-19 (0 days ago) mtime.conffile..etc.systemd.resolved.conf: 2023-10-30T21:36:27.073262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2062550/+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 2063533] Re: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 ** Summary changed: - package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 + package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] ** This bug has been marked a duplicate of bug 2047975 package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+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 2063452] Re: Xorg freeze
It looks like the kernel ran out of memory and the main culprit is a 'java' process. This is not an Ubuntu bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/2063452 Title: Xorg freeze Status in Ubuntu: Invalid Bug description: My Ubuntu system crashes every time I use an application. It freezes, and I have to force the system to shut down in order to restart it for use, but the problem persists.Please help me ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 13:40:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD Graphics] [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Mobile] [1462:12eb] InstallationDate: Installed on 2023-12-01 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=0cd75e64-7400-4f1e-bbce-c9c2c1a67e8a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2021 dmi.bios.release: 3.14 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.30E dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.30E:bd10/15/2021:br3.14:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063452/+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 2063503] Re: NVidia drivers won't install completely
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-550 (Ubuntu) ** Also affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New -- 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/2063503 Title: NVidia drivers won't install completely Status in nvidia-graphics-drivers-545 package in Ubuntu: New Status in nvidia-graphics-drivers-550 package in Ubuntu: New Bug description: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 The following packages will be REMOVED: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386 libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded. 2 not fully installed or removed. Need to get 360 MB of archives. After this operation, 14.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 amd64 550.67-0ubuntu3 [35.8 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB] Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB] Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB] Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB] Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB] Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB] Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB] Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB] Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB] Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB] Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB] Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB] Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB] Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-common-550 amd64
[Touch-packages] [Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
** Description changed: + [ Impact ] + + Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as + during install. + + [ Test Plan ] + + 1. Open the default Help app by clicking the question mark icon in the + dock or by running 'yelp'. + + 2. Verify it didn't crash and the window contents are not corrupt. + + [ Where problems could occur ] + + The fix is limited to webkit2gtk so can only affect apps such as yelp or + the Raspberry Pi installer. + + [ Other Info ] + During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. ** Description changed: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] - 1. Open the default Help app by clicking the question mark icon in the + 1. Log into a Xorg session on a Raspberry Pi 4/400. + + 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. - 2. Verify it didn't crash and the window contents are not corrupt. + 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. -- 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/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
Confirmed this fix is now working: https://salsa.debian.org/webkit-team/webkit/-/merge_requests/20 -- 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/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
** Changed in: mesa (Ubuntu) Status: Invalid => Triaged -- 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/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: In Progress Status in yelp package in Ubuntu: New Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2061856] Re: Apps are closing immediately instead of launching
** Package changed: xorg (Ubuntu) => ubuntu -- 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/2061856 Title: Apps are closing immediately instead of launching Status in Ubuntu: Incomplete Bug description: Ola Bomdia Eu estou com um problema no terminal shell do ubuntu ele esta fechando assim que clico para abrir elefecha automaticamente ja tentetei usar outro terminal e tambem faz a mesma coisa eu tenho o fish instalado tambem mas esta fazendo a mesma coisa fechando automaticamente, o unico que funciona e o terminal do vscode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Apr 16 12:04:00 2024 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Core Processor Integrated Graphics Controller [1019:1324] InstallationDate: Installed on 2023-07-23 (267 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) Lsusb: Bus 002 Device 006: ID 04f3:0210 Elan Microelectronics Corp. Optical Mouse Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEGAWARE H55H-CM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=3cfdb2f5-e8ec-4728-844a-29c984321037 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MW-H55H-CM dmi.board.vendor: MEGAWARE dmi.board.version: 1.0 dmi.chassis.asset.tag: M0418501001 dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/18/2010:svnMEGAWARE:pnH55H-CM:pvrMEGAWARE:rvnMEGAWARE:rnMW-H55H-CM:rvr1.0:cvnMEGAWARE:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: H55H-CM dmi.product.version: MEGAWARE dmi.sys.vendor: MEGAWARE version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.15 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Apr 4 13:22:01 2024 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPS/2+USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061856/+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 2063228] Re: screen sometimes blinking
Please try adding a kernel parameter: i915.enable_psr=0 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/2063228 Title: screen sometimes blinking Status in linux package in Ubuntu: Incomplete Bug description: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 14-ce2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2022 dmi.bios.release: 15.27 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063228/+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 2063222] Re: Ghost "unknown display" since upgrading to 24.04 beta
*** This bug is a duplicate of bug 2060268 *** https://bugs.launchpad.net/bugs/2060268 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2060268, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** This bug has been marked a duplicate of bug 2060268 Phantom monitor (simpledrm) shown in Settings after installing the Nvidia driver -- 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/2063222 Title: Ghost "unknown display" since upgrading to 24.04 beta Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: X11 GNOME NVIDIA 4080 with their driver -> GNOME settings has a "ghost" display called "Unknown Display", its resolution is 1024 x 768 I only have one display attached - a 4K 27" DELL plugged into the NVIDIA ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 08:55:55 2024 DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 [1462:7d25] NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 4080] [1462:5111] InstallationDate: Installed on 2022-04-30 (724 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago) dmi.bios.date: 11/13/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.F0 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A WIFI (MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
[Touch-packages] [Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
The plan is to SRU since the installer is not the only app affected. It's non-fatal, 23.10 was released with the same bug. But I expect to have it fixed in time for 24.04.1 ** Summary changed: - Screen corruption of slides during install on Raspberry Pi + Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: webkit2gtk (Ubuntu) Milestone: ubuntu-24.04 => noble-updates -- 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/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2061856] Re: gnome terminal
There appear to be repeating file system problems so I recommend
investigating those first. I can't tell if it's a harddisk or an optical
drive...
[19894.148839] SQUASHFS error: xz decompression failed, data probably corrupt
[19894.148842] SQUASHFS error: squashfs_read_data failed to read block 0xa8810
[19894.152622] SQUASHFS error: xz decompression failed, data probably corrupt
[19894.152626] SQUASHFS error: squashfs_read_data failed to read block 0x1190b4
[19900.707383] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[19900.707391] ata1.00: BMDMA stat 0x24
[19900.707396] ata1.00: failed command: READ DMA EXT
[19900.707405] ata1.00: cmd 25/00:08:10:f4:cd/00:00:12:00:00/e0 tag 0 dma 4096
in
res 51/40:00:11:f4:cd/40:00:12:00:00/e0 Emask 0x9
(media error)
[19900.707410] ata1.00: status: { DRDY ERR }
[19900.707416] ata1.00: error: { UNC }
[19900.713332] ata1.00: configured for UDMA/133
[19900.713361] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[19900.713368] sd 0:0:0:0: [sda] tag#0 Sense Key : Medium Error [current]
[19900.713374] sd 0:0:0:0: [sda] tag#0 Add. Sense: Unrecovered read error -
auto reallocate failed
[19900.713380] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 12 cd f4 10 00 00 08
00
[19900.713383] print_req_error: I/O error, dev sda, sector 315487249
[19900.713423] ata1: EH complete
[19905.840133] SQUASHFS error: xz decompression failed, data probably corrupt
[19905.840140] SQUASHFS error: squashfs_read_data failed to read block 0x16ab64
[19905.847696] SQUASHFS error: xz decompression failed, data probably corrupt
[19905.847699] SQUASHFS error: squashfs_read_data failed to read block 0x15789c
[19905.848108] SQUASHFS error: xz decompression failed, data probably corrupt
** Summary changed:
- gnome terminal
+ Apps are closing immediately instead of launching
--
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/2061856
Title:
Apps are closing immediately instead of launching
Status in xorg package in Ubuntu:
Incomplete
Bug description:
Ola Bomdia Eu estou com um problema no terminal shell do ubuntu ele
esta fechando assim que clico para abrir elefecha automaticamente ja
tentetei usar outro terminal e tambem faz a mesma coisa eu tenho o
fish instalado tambem mas esta fazendo a mesma coisa fechando
automaticamente, o unico que funciona e o terminal do vscode.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18
Uname: Linux 4.15.0-213-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 16 12:04:00 2024
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Core Processor Integrated Graphics Controller [8086:0042]
(rev 12) (prog-if 00 [VGA controller])
Subsystem: Elitegroup Computer Systems Core Processor Integrated Graphics
Controller [1019:1324]
InstallationDate: Installed on 2023-07-23 (267 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386
(20170215.2)
Lsusb:
Bus 002 Device 006: ID 04f3:0210 Elan Microelectronics Corp. Optical Mouse
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MEGAWARE H55H-CM
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic
root=UUID=3cfdb2f5-e8ec-4728-844a-29c984321037 ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MW-H55H-CM
dmi.board.vendor: MEGAWARE
dmi.board.version: 1.0
dmi.chassis.asset.tag: M0418501001
dmi.chassis.type: 3
dmi.chassis.vendor: MEGAWARE
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/18/2010:svnMEGAWARE:pnH55H-CM:pvrMEGAWARE:rvnMEGAWARE:rnMW-H55H-CM:rvr1.0:cvnMEGAWARE:ct3:cvr1.0:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: H55H-CM
dmi.product.version: MEGAWARE
dmi.sys.vendor: MEGAWARE
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core:
[Touch-packages] [Bug 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
Thanks for the bug report. Most likely the problem is an HDMI connection
problem. Please try a new HDMI cable if you can. If you can't then
please try temporarily running the external monitor at a lower
resolution to see if the flicker then goes away.
If the flicker still persists then please attach a video of the issue
(recording on a phone is fine).
** Tags added: flicker multimonitor
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2062950
Title:
RE: Flickering problems on external monitor with HDMI after installing
Ubuntu 23.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504
I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062950/+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 2063005] Re: Onscreen keyboard is disabled by default
Sorry, I missed the "X11 session" part. Bug confirmed. ** No longer affects: gsettings-desktop-schemas (Ubuntu) ** Summary changed: - Onscreen keyboard is disabled by default + Some shell elements don't respond to touchscreen in Xorg sessions ** Changed in: gnome-shell (Ubuntu) Importance: Low => Medium ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+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 2063005] Re: Onscreen keyboard is disabled by default
Looks like it's been disabled for at least 6 years: https://gitlab.gnome.org/GNOME/gsettings-desktop- schemas/-/blob/master/schemas/org.gnome.desktop.a11y.applications.gschema.xml.in?ref_type=heads so whether or not it gets toggled automatically is probably up to gnome- shell. ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: New => Won't Fix ** Changed in: gnome-shell (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Onscreen keyboard is disabled by default Status in gnome-shell package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+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 2063005] Re: touchscreen input critical regressions in GNOME 45 to 46
Partially confirmed. It looks like the onscreen keyboard is always disabled by default. You have to enable it in: Settings > Accessibility > Typing > Screen Keyboard = ON After I did that, all the features mentioned here started working. ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Summary changed: - touchscreen input critical regressions in GNOME 45 to 46 + Onscreen keyboard is disabled by default ** Tags added: osk ** Also affects: gsettings-desktop-schemas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Onscreen keyboard is disabled by default Status in gnome-shell package in Ubuntu: Confirmed Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063005/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi
Untested draft fix: https://salsa.debian.org/webkit-team/webkit/-/merge_requests/19 -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2062146] Re: MiniBrowser crashed with SIGSEGV
** Also affects: yelp (Ubuntu) Importance: Undecided Status: New ** Summary changed: - MiniBrowser crashed with SIGSEGV + Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile ** Changed in: webkit2gtk (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: webkit2gtk (Ubuntu) Status: New => In Progress ** Changed in: webkit2gtk (Ubuntu) Importance: Undecided => High ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Changed in: mesa (Ubuntu) Status: New => Triaged -- 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/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: In Progress Status in yelp package in Ubuntu: New Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi
I have a hunch the problems might have started in WebKit 2.43.2 which included a backport of: https://github.com/WebKit/WebKit/commit/8b0ce3683045d93cd365e91a4299f7e9babfc126 That's forcing us to take a whole new code path which clearly we're just discovering is a bit buggy on some platforms. To work around it, you can export: WEBKIT_DMABUF_RENDERER_FORCE_SHM=1 which should have better performance than another workaround: WEBKIT_DISABLE_DMABUF_RENDERER=1 Both of those also solve bug 2060938 and bug 2062146 which I suspect is a newer crash caused by the newer Mesa in Noble. So if people find the installer is reliably crashing recently then that might explain it. -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi
** Bug watch added: bugs.webkit.org/ #272827 https://bugs.webkit.org/show_bug.cgi?id=272827 ** Also affects: webkit via https://bugs.webkit.org/show_bug.cgi?id=272827 Importance: Unknown Status: Unknown ** No longer affects: ubiquity (Ubuntu) -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi Status in Webkit: Unknown Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2062504] Re: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
This looks like a confused installation. The GPU is Intel, but you have
an Nvidia driver installed, and an AMD kernel workaround on the command
line.
But none of that should hurt...
What will hurt is the unsupported "oibaf" packages you have replaced the
official graphics drivers with. Sorry, but we cannot support such
changes. Please remove the PPA from your system or just reinstall the OS
without making any such changes. Then report new bugs for any issues you
find.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
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/2062504
Title:
Flickering problems on external monitor with HDMI after installing
Ubuntu 23.10
Status in Ubuntu:
Invalid
Bug description:
I just installed ubuntu 23.10 on my thinkpad L13. It works fine on my
laptop monitor. But when I connect an HDMI cable to my other monitor,
then the screen flickers on the laptop and nothing shows on the other
monitor
I know it can't be the problem with the other monitor as I bought it
brand new last week, and the cable works fine on this same laptop when
I run in windows, and it works fine on other laptops with windows/mac
I already installed the driver with `sudo apt install nvidia-
driver-535 nvidia-dkms-535` and rebooted, but that didn't help. I then
installed driver 550 and I still have the flickering
This laptop uses an intel Alder Lake-UP3 GT2
I also tried editing `etc/default/grub` by adding 'nomodeset' or
'radeon.modeset=0' within the quotation marks in the line
GRUB_CMDLINE_LINUX_DEFAULT but that didn't help either
can anyone help?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 18 23:17:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/550.54.14, 6.5.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-13 (6 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=bc80dc13-87d7-4310-bd10-43d45de6d3a7 ro quiet splash radeon.modeset=0
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120+git2404140851.1179ed~oibaf~m
version.libgl1-mesa-dri: libgl1-mesa-dri 24.1~git2404150600.4a1904~oibaf~m
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2062504/+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 2062146] Re: MiniBrowser crashed with SIGSEGV
See also bug 2060938. ** Tags added: raspi raspigfx -- 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/2062146 Title: MiniBrowser crashed with SIGSEGV Status in Mesa: Unknown Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2062146] Re: MiniBrowser crashed with SIGSEGV
#0 0x7721ad7c in v3d_load_utile (gpu_stride=16, gpu=0x2840e000, cpu_stride=4096, cpu=0x1e880f90) at ../src/broadcom/common/v3d_cpu_tiling.h:108 #1 v3d_move_pixels_general_percpp (gpu=0x28126000, cpu=0x1e800010, cpu_stride=4096, cpp=4, image_h=768, box=0xf986a674, get_pixel_offset=0x7721a930 , is_load=true, gpu_stride=) at ../src/broadcom/common/v3d_tiling.c:289 #2 0x771dc420 in v3d_resource_transfer_map (pctx=, prsc=0xf9963be0, level=, usage=, box=, pptrans=) at ../src/gallium/drivers/v3d/v3d_resource.c:327 #3 0x762fcb40 in pipe_texture_map (transfer=0xc86d4490, h=730, w=1024, y=0, x=0, access=1, layer=0, level=0, resource=, context=0xf98e8c40) at ../src/gallium/auxiliary/util/u_inlines.h:557 #4 dri2_map_image (context=0xf9964910, image=0xf985df70, x0=0, y0=0, width=1024, height=730, flags=1, stride=0xc86d459c, data=0xc86d45a0) at ../src/gallium/frontends/dri/dri2.c:1964 #5 0x847a46a8 in gbm_dri_bo_map (_bo=0xf9872e20, x=0, y=0, width=1024, height=730, flags=1, stride=0xc86d459c, map_data=0xc86d45a0) at ../src/gbm/backends/dri/gbm_dri.c:1122 #6 0x89d7f644 in WebKit::AcceleratedBackingStoreDMABuf::BufferGBM::didUpdateContents () at /usr/src/webkit2gtk-2.44.0-2/Source/WebKit/UIProcess/gtk/AcceleratedBackingStoreDMABuf.cpp:368 #7 0x89d809fc in WebKit::AcceleratedBackingStoreDMABuf::frame () at /usr/src/webkit2gtk-2.44.0-2/Source/WebKit/UIProcess/gtk/AcceleratedBackingStoreDMABuf.cpp:531 ** Information type changed from Private to Public ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11033 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033 Importance: Unknown Status: Unknown -- 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/2062146 Title: MiniBrowser crashed with SIGSEGV Status in Mesa: Unknown Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi
And webkit2gtk's MiniBrowser has the same crash: bug 2062146 (both in Xorg sessions) -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+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 1869655] Re: Boot animations start too late to be useful
No longer in progress. You can get to 100% fixed by adding kernel parameter 'plymouth.use-simpledrm' but I'm not totally sure that's something everyone will want. ** Changed in: plymouth (Ubuntu) Status: In Progress => Triaged ** Changed in: plymouth (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/1869655 Title: Boot animations start too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Triaged Bug description: Boot animations start too late to be useful Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+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 2062082] Re: 24.04 Wayland vs Nautilus performance problem
Thanks for the bug report. Please try: 1. sudo rm /dev/dri/card0 # to work around bug 2060268, and then log in again. Did that solve it? 2. When the problem starts happening please open a Terminal and run: journalctl -b0 > journal.txt xlsclients > xclients.txt and attach the resulting text files here. 3. While the problem is happening run 'top' in a Terminal window and tell us which process (if any) is using high CPU. ** Package changed: xorg (Ubuntu) => nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/2062082 Title: 24.04 Wayland vs Nautilus performance problem Status in nautilus package in Ubuntu: Incomplete Bug description: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes,
[Touch-packages] [Bug 2062082] Re: 24.04 Wayland vs Nautilus performance problem
** Tags added: nvidia nvidia-wayland -- 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/2062082 Title: 24.04 Wayland vs Nautilus performance problem Status in xorg package in Ubuntu: New Bug description: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] InstallationDate: Installed on 2024-04-11 (6 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=
[Touch-packages] [Bug 2062082] Re: 24.04 Wayland vs Nautilus performance problem
-- 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/2062082 Title: 24.04 Wayland vs Nautilus performance problem Status in xorg package in Ubuntu: New Bug description: Apologies if I have misfiled this bug - this is a report of an issue affecting Wayland in Ubuntu 24.04 beta. Using 24.04 beta logging in with Wayland. Nautilus has very significant performance issues. Doesn't happen when logging in with Xorg instead of Wayland. Opening Nautilus windows - including normal windows navigation, and the file download location dialogue in things like Chrome - extremely slow. Takes approx. 10 seconds to process user double clicking to open folder. Attempting to drag folder across screen usually doesn't work, or takes a very long time. Not very skilled at debugging, but programmes like Gimp, which has its own built-in folder explorer for choosing a location to save an image, do not have this problem. Ubuntu 24.04 with X does not have this problem. No performance issues have been noticed with folder navigation, stat'ing files etc. over the command line. It is only nautilus and Wayland that give me this issue, so I suspect it is not an issue with my SSD. The following output was observed when starting nautilus over the command line: /home/me/ $ nautilus . ** Message: 23:43:50.560: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen After approx. 10 seconds, the folder opened on screen. I double clicked on a sub directory, and it took about 9 seconds to open. I have attempted to show that this is not an issue with my SSD here: /home/me/ $ date; cd workspace/; touch foo.txt; ls foo*; cd ../; date; Wed Apr 17 11:58:16 PM BST 2024 foo.txt Wed Apr 17 11:58:16 PM BST 2024 As you can see, no unusual slowdown was observed. Obtaining the following setting for my bug report, I note that the 'Settings' GUI utility is among the areas affect by my very significant system slowdown. I have copied some details about my system including its graphics card in case that helps. # System Details Report --- ## Report details - **Date generated:** 2024-04-17 23:59:54 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX B550-F GAMING - **Memory:** 32.0 GiB - **Processor:** AMD Ryzen™ 7 5800X × 16 - **Graphics:**zink Vulkan 1.3(NVIDIA GeForce GTX 1050 Ti (NVIDIA_PROPRIETARY)) - **Disk Capacity:** 2.0 TB ## Software Information: - **Firmware Version:**2006 - **OS Name:** Ubuntu Noble Numbat (development branch) - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..09.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 545.29.06 Thu Nov 16 01:59:08 UTC 2023 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 23:44:47 2024 DistUpgraded: 2024-04-11 13:09:51,904 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] InstallationDate: Installed on 2024-04-11 (6 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine:
[Touch-packages] [Bug 2061886] Re: Under VMWare resolution does not change automaticaly
** Package changed: xorg (Ubuntu) => xserver-xorg-video-vmware (Ubuntu) ** Tags added: vmwgfx -- 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/2061886 Title: Under VMWare resolution does not change automaticaly Status in xserver-xorg-video-vmware package in Ubuntu: New Bug description: When resizing a VMWare Workstation, under Ubuntu20 the resolution would change automaticaly. It does not in the Ubuntu 24 Beta. During installation I have enabled download of third party driver. I can see vmtoold running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 16 14:03:39 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2024-04-16 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=93447c69-bef1-4d4b-917b-41be1fbda0ea ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.21100432.B64.2301110304 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.21100432.B64.2301110304:bd01/11/2023:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/2061886/+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 2038313] Re: MESA-INTEL: warning: Haswell Vulkan support is incomplete
** Tags removed: lunar ** Tags added: noble -- 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/2038313 Title: MESA-INTEL: warning: Haswell Vulkan support is incomplete Status in mesa package in Ubuntu: Confirmed Bug description: upscayl software do not work BACKEND REPORTED: Selected File Path: /home/anders/Downloads/1695568515335.png Selected Image Path: /home/anders/Downloads/1695568515335.png Selected Image Directory: /home/anders/Downloads imagePath: /home/anders/Downloads/1695568515335.png Extension: png Resetting Upscaled Image Path UPSCAYL BACKEND REPORTED: Updating Overwrite: false BACKEND REPORTED: ✅ Upscayl Variables: [object Object] BACKEND REPORTED: Upscayl Command: -i,/home/anders/Downloads/1695568515335.png,-o,/home/anders/Downloads/1695568515335_upscayl_4x_ultrasharp.png,-s,4,-m,/tmp/.mount_upscaygPuzIl/resources/models,-n,ultrasharp,,,-f,png BACKEND REPORTED: Updating Child Processes: [object Object] BACKEND REPORTED: Updating Stopped: false BACKEND REPORTED: image upscayl: MESA-INTEL: warning: Haswell Vulkan support is incomplete UPSCAYL_PROGRESS: MESA-INTEL: warning: Haswell Vulkan support is incomplete BACKEND REPORTED: image upscayl: [0 Intel(R) HD Graphics 4600 (HSW GT2)] queueC=0[1] queueG=0[1] queueT=0[1] [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 int8-p/s/a=1/0/0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 ballot=1 shuffle=1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] queueT=0[1] [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 ballot=1 shuffle=1 UPSCAYL_PROGRESS: [0 Intel(R) HD Graphics 4600 (HSW GT2)] queueC=0[1] queueG=0[1] queueT=0[1] [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 int8-p/s/a=1/0/0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 ballot=1 shuffle=1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] queueT=0[1] [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 ballot=1 shuffle=1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 3 14:45:19 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. 4th Gen Core Processor Integrated Graphics Controller [10cf:17af] InstallationDate: Installed on 2023-09-06 (26 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 1c4f:0034 SiGma Micro XM102K Optical Wheel Mouse Bus 001 Device 002: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 9: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: FUJITSU LIFEBOOK E554 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=cdedb299-9f30-4ac9-aec9-82dafceeaf91 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2017 dmi.bios.release: 1.11 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.11 dmi.board.name: FJNB281 dmi.board.vendor: FUJITSU dmi.board.version: F2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU
[Touch-packages] [Bug 2061257] Re: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg
*** This bug is a duplicate of bug 2038313 *** https://bugs.launchpad.net/bugs/2038313 Thanks for the bug report. I suppose it's possible all these issues are related, but we shouldn't assume they are so quickly... The Vulkan error message is being tracked in bug 2038313. As for Nextcloud, Vivaldi and Slack, they are all Chromium-based (or Electron which uses Chromium). So it's possible that Chromium's Wayland backend is a common point of failure. Although the error message itself is definitely coming from Mesa. Since the only relevant Ubuntu package I can see is already tracked in bug 2038313 I will mark this as a duplicate of that, but you should also log bugs against each of the affected apps in their respective trackers. ** Package changed: wayland (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 2038313 MESA-INTEL: warning: Haswell Vulkan support is incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2061257 Title: After 24.04 upgrade, many graphical app failures under Wayland; no issues with Xorg Status in Ubuntu: Confirmed Bug description: Many applications seem to fail under a Wayland session that work correctly with an Xorg session. E.g. - The nextcloud client app fails to contact the server and functions in the app will not launch with Wayland while they work perfectly in Xorg - The Vivaldi browser exits with: MESA-INTEL: warning: Haswell Vulkan support is incomplete libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed. It works correctly under Xorg. - The Slack app works correct in Xorg not in Wayland. - The Firefox snap works fine in both. I assume that these are related? Esp. that latter suggests to me that there is some library problem? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 19:58:00 2024 DistUpgraded: 2024-04-13 16:25:15,367 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-11-11 (885 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20ARA0S100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 2.24 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:br2.24:efr1.9:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061257/+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 2061245] Re: Ubuntu 24.04 - GNOME on Xorg session crashes on launch
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 Patrick and Rich; both of your logs look like bug 1858336 which redirects to bug 1861609 but I'm not sure that's right for everyone... Also Patrick; yours looks like it is caused by a broken/missing Nvidia driver so please use the 'Additional Drivers' app to install a fresh one. ** This bug has been marked a duplicate of bug 1861609 Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] -- 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/2061245 Title: Ubuntu 24.04 - GNOME on Xorg session crashes on launch Status in xorg package in Ubuntu: Confirmed Bug description: I just upgraded an existing 23.10 installation to 24.04 LTS development branch/beta. Whereas GNOME on Xorg worked fine on 23.10, upon completed upgrade/reboot my system defaulted to GNOME on Wayland*. Attempting to login under Xorg caused the system to freeze and subsequently prompted me to login again. I cannot launch GNOME on 24.04 using Xorg, only Wayland. Upon deleting "20-nvidia.conf", located at "/etc/X11/xorg.conf.d/", attempting to launch an Xorg/X11 session greeted me with a black screen, and I was subsequently returned to login a few seconds later. (*The Wayland session, while functional, contained a lot of tearing, stuttering, and a lack of animations.) Ubuntu 24.04 LTS Dev. DE: GNOME Graphics driver: Nvidia 535 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 14:58:57 2024 DistUpgraded: 2024-04-13 14:14:00,343 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1ec7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:13aa] InstallationDate: Installed on 2023-12-15 (121 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: Micro-Star International Co., Ltd. MS-7B17 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=d1172f3e-66ff-4508-a818-d3f88ec03bdb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago) dmi.bios.date: 03/26/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.50 dmi.board.asset.tag: Default string dmi.board.name: MPG Z390 GAMING EDGE AC (MS-7B17) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd03/26/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B17:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGEDGEAC(MS-7B17):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B17 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061245/+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 2061172] Re: the nightlight doesn't work
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: gamma nightlight -- 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/2061172 Title: the nightlight doesn't work Status in mutter package in Ubuntu: New Bug description: when i turn the nightlight on its get off immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2061172/+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 2061118] Re: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend)
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #6542 https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 ** Changed in: gtk Status: Fix Released => Unknown ** Changed in: gtk Remote watch: gitlab.gnome.org/GNOME/gtk/-/issues #6624 => gitlab.gnome.org/GNOME/gtk/-/issues #6542 -- 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/2061118 Title: Rendering issues in vmware/virtualbox with 3d on (GTK ngl backend) Status in GTK+: Unknown Status in Mesa: New Status in gtk4 package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in open-vm-tools package in Ubuntu: Invalid Status in gtk4 source package in Noble: Triaged Status in mesa source package in Noble: Triaged Status in open-vm-tools source package in Noble: Invalid Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061022] Re: Intermittent keyboard lag with Tecknet EKB01002BK01 keyboard
*** This bug is a duplicate of bug 2059847 *** https://bugs.launchpad.net/bugs/2059847 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2059847, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 2059847 Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" -- 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/2061022 Title: Intermittent keyboard lag with Tecknet EKB01002BK01 keyboard Status in mutter package in Ubuntu: New Bug description: This bug manifests itself slightly differently across different scenarios. To summarise, scrolling through a long file/directory listing in Midnight Commander (e.g. > 40 items) causes the cursor to lag, stutter and pause. In 23.10 if the up/down key is depressed there is a delay of about 0.25 seconds before moving onto the previous/next item. In 24.04, the cursor will stick on the previous/last item until it is released. This behavior is not exhibited in a console session [e.g. via Ctrl+Alt+F5], with Ubuntu 22.04 LTS or under Wayland. It also does not seem to affect the Tecknet EMK01707 keyboard under Ubuntu 23.10. This behavior has been observed using both Guake terminal [Version 3.10] and Gnome terminal [Version 3.52.0 for GNOME 46]. [Affected Ubuntu versions] Ubuntu 23.10 Ubuntu 24.04 [To recreate] Open mc in terminal and browse through a long directory/file listing (> 40 items). This behavior will manifest immediately or after a few cycles. [Expected behavior] The cursor should scroll linearly throughout a list without pauses, juddering, lag or requiring the user to release the key. [Workarounds] 1. Switch to Wayland 2. Use a different keyboard. The problem was not apparent using a Tecknet EMK01707 keyboard under 23.10, however this has not been tested under Noble Numbat. [Further information] MC version: GNU Midnight Commander 4.8.30 Built with GLib 2.80.0 Built with S-Lang 2.3.3 with terminfo database Built with libssh2 1.11.0 With builtin Editor and Aspell support With subshell support as default With support for background operations With mouse support on xterm and Linux console With support for X11 events With internationalization support With multiple codepages support With ext2fs attributes support Virtual File Systems: cpiofs, tarfs, sfs, extfs, ext2undelfs, ftpfs, sftpfs, fish Data types: char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64; [Related bugs] This seems related to https://bugs.launchpad.net/debian/+source/xserver-xorg-input- evdev/+bug/1002951 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.fabric-imex-mgmt: DeviceFileMinor: 4323 DeviceFileMode: 256 DeviceFileModify: 1 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 550.67 Tue Mar 12 23:54:15 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 11 19:11:20 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/550.67, 6.8.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:2375] InstallationDate: Installed on 2024-04-10 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410) MachineType: To Be Filled By O.E.M. To Be Filled By
[Touch-packages] [Bug 2061344] Re: Issues with GNOME Display Settings in Ubuntu 24.04 beta
*** This bug is a duplicate of bug 2060659 *** https://bugs.launchpad.net/bugs/2060659 Thanks for the bug report. These issues have already been reported in bug 2060659 and bug 2060268. Please be sure to report each issue as a separate bug in future. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 2060659 X11 fractional scaling support is missing in 46.0 -- 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/2061344 Title: Issues with GNOME Display Settings in Ubuntu 24.04 beta Status in mutter package in Ubuntu: New Bug description: Two issues with GNOME Display Settings since upgrading to Ubuntu 24.04 beta 1 - I am unable to select Fractional Scaling and set it to 150%. The Fractional Scaling checkbox appears to do nothing - 1) selecting it does not enable the Apply button 2) does not update the list of supported scaling factors to include fractional values. 2 - There is a ghost display I have one display plugged into a NVDIA 4080, using proprietary driver. There is a ghost "Unknown Display" in Display Settings at resolution 1024x768. Expectations: 1 - I should be able to enable Fractional Scaling and set it to 150% 2 - There should be no ghost "Unknown Display" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 19:14:31 2024 DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/535.171.04, 6.5.0-27-generic, x86_64: installed nvidia/535.171.04, 6.8.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 [1462:7d25] NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 4080] [1462:5111] InstallationDate: Installed on 2022-04-30 (715 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-22-generic SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-15 (0 days ago) dmi.bios.date: 11/13/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.F0 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A WIFI (MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Touch-packages] [Bug 2037015] Re: Screen corruption of slides during install on Raspberry Pi
Yelp also crashes soon after displaying the corruption: bug 2060938 -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi
** Changed in: webkit2gtk (Ubuntu) Status: Confirmed => In Progress ** Changed in: webkit2gtk (Ubuntu) Importance: Undecided => Medium ** Changed in: webkit2gtk (Ubuntu) Milestone: None => ubuntu-24.04 -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+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 2060809] Re: davinci not opening bro
The integrated GPU of your Intel i5-6400 is all that I can see, which understandably may not be enough to run Davinci. What error do you see exactly? Also note that errors have been reported on your installation media, probably meaning the USB drive used to install Ubuntu was faulty. You may want to reinstall Ubuntu using a different thumb drive. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2060809 Title: davinci not opening bro Status in Ubuntu: Incomplete Bug description: gpu no to supporter ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 10 18:14:28 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 530 [8086:2212] InstallationDate: Installed on 2024-04-08 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: ZEBRONICS H110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.name: H110 dmi.board.vendor: ZEBRONICS dmi.board.version: Ver:2.32 dmi.chassis.type: 3 dmi.chassis.vendor: ZEBRONICS dmi.chassis.version: H110 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/11/2023:br5.12:svnZEBRONICS:pnH110:pvr:rvnZEBRONICS:rnH110:rvrVer2.32:cvnZEBRONICS:ct3:cvrH110:sku: dmi.product.name: H110 dmi.sys.vendor: ZEBRONICS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2060809/+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 1970069] Re: Annoying boot messages interfering with splash screen
I've installed the 20240410 iso on a couple of machines and this bug is as good as fixed. The systemd task would be nice to complete but that's more for the sake of bug 1914409. Right now I have more important bugs to focus on... ** Changed in: systemd (Ubuntu) Status: In Progress => Triaged -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi
** Changed in: webkit2gtk (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+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 2060730] Re: totem cannot install codecs via packagekit
** Tags added: noble raspi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit Status in packagekit package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: While attempting to play a video on Ubuntu noble desktop for raspberry pi, totem attempts to locate a package for the H.264 codec but cannot find a service providing org.freedesktop.PackageKit. This is strange given that packagekit is installed, provides packagekit.service, which declares that it provides that name over DBus. Specifically, the following is output by totem: ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder) ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder) ** Message: 21:13:39.414: PackageKit: xid = 0 ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit) ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files ** Message: 21:13:39.441: No installation candidate for missing plugins found. The packagekit.service is defined as: $ systemctl cat packagekit.service # /usr/lib/systemd/system/packagekit.service [Unit] Description=PackageKit Daemon # PK doesn't know how to do anything on ostree-managed systems; # currently the design is to have dedicated daemons like # eos-updater and rpm-ostree, and gnome-software talks to those. ConditionPathExists=!/run/ostree-booted Wants=network-online.target [Service] Type=dbus BusName=org.freedesktop.PackageKit User=root ExecStart=/usr/libexec/packagekitd And just to demonstrate packagekit is actually running: $ systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static) Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s ago Main PID: 1565 (packagekitd) Tasks: 4 (limit: 3864) Memory: 6.2M (peak: 6.7M) CPU: 180ms CGroup: /system.slice/packagekit.service └─1565 /usr/libexec/packagekitd Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - PackageKit Daemon... Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - PackageKit Daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2060730/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi 4
That's expected; it's just a different graphics memory layout with a different GPU. ** Summary changed: - Screen corruption of slides during install on Raspberry Pi 4 + Screen corruption of slides during install on Raspberry Pi -- 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/2037015 Title: Screen corruption of slides during install on Raspberry Pi Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+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 2056666] Re: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine
Also bug 2060555. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/205 Title: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine Status in bluez package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: New Bug description: headphone is not showing up in my ubuntu bluetooth so i cant connect my headphone to my computer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 14:10:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=bed00b3d-206b-4607-8c0b-63d4f55998ef ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-ADA dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrE8CN38WW:bd12/05/2022:br1.38:efr1.38:svnLENOVO:pn82C7:pvrLenovoV15-ADA:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-ADA:skuLENOVO_MT_82C7_BU_idea_FM_V15-ADA: dmi.product.family: V15-ADA dmi.product.name: 82C7 dmi.product.sku: LENOVO_MT_82C7_BU_idea_FM_V15-ADA dmi.product.version: Lenovo V15-ADA dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:CD:C4:D1:98:3A ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:35089 acl:0 sco:0 events:1074 errors:0 TX bytes:48329 acl:0 sco:0 commands:549 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/205/+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 2060555] Re: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones
See also bug 205 having trouble with the same chip. ** Also affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2060555 Title: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones Status in bluez package in Ubuntu: Incomplete Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: The keyboard and mouse are dell brand and they were able to connect to my system and now they cannot. My headdpone are JBL ear pods and they were able to be detected but never connected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 09:42:46 2024 InstallationDate: Installed on 2024-03-31 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP ProBook x360 435 G7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2023 dmi.bios.release: 13.0 dmi.bios.vendor: HP dmi.bios.version: S80 Ver. 01.13.00 dmi.board.name: 8735 dmi.board.vendor: HP dmi.board.version: KBC Version 09.2D.00 dmi.chassis.asset.tag: 5CG0340N3Z dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.45 dmi.modalias: dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA: dmi.product.family: 103C_5336AN HP ProBook x360 dmi.product.name: HP ProBook x360 435 G7 dmi.product.sku: 17G39UT#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 1C:BF:C0:C6:9F:CA ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:173926 acl:0 sco:0 events:4200 errors:0 TX bytes:58386 acl:0 sco:0 commands:1483 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2060555/+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 2060555] Re: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones
Please reboot, try to connect them again, and after it fails run: journalctl -b0 > journal.txt and attach the resulting text file here. Please also specify how long ago and in which Ubuntu release it was working. ** Summary changed: - I cant connect my bluetooth keyboard, mouse and jbl headpones + [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2060555 Title: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones Status in bluez package in Ubuntu: Incomplete Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: The keyboard and mouse are dell brand and they were able to connect to my system and now they cannot. My headdpone are JBL ear pods and they were able to be detected but never connected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 09:42:46 2024 InstallationDate: Installed on 2024-03-31 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP ProBook x360 435 G7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2023 dmi.bios.release: 13.0 dmi.bios.vendor: HP dmi.bios.version: S80 Ver. 01.13.00 dmi.board.name: 8735 dmi.board.vendor: HP dmi.board.version: KBC Version 09.2D.00 dmi.chassis.asset.tag: 5CG0340N3Z dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.45 dmi.modalias: dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA: dmi.product.family: 103C_5336AN HP ProBook x360 dmi.product.name: HP ProBook x360 435 G7 dmi.product.sku: 17G39UT#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 1C:BF:C0:C6:9F:CA ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:173926 acl:0 sco:0 events:4200 errors:0 TX bytes:58386 acl:0 sco:0 commands:1483 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2060555/+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 2060291] Re: [Intel N95] Horizonral line artifact/ghosting when scaling windows to a certain width
** Summary changed:
- Horizonral line artifact/ghosting when scaling windows to a certain width
+ [Intel N95] Horizonral line artifact/ghosting when scaling windows to a
certain width
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
** Package changed: mesa (Ubuntu) => linux (Ubuntu)
** Package changed: nautilus (Ubuntu) => mesa (Ubuntu)
--
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/2060291
Title:
[Intel N95] Horizonral line artifact/ghosting when scaling windows to
a certain width
Status in linux package in Ubuntu:
New
Status in mesa package in Ubuntu:
New
Bug description:
When scaling some windows in some programs down horizontal lines
appear that seem to be part of the texture memory somewhere else on
the screen.
This only occurs in some programs like nautilus and gedit, but not in
others like terminal or Firefox.
It did however occur when I opened the dialog in firefox to attach the
screen capture.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 5 03:44:15 2024
DistUpgraded: 2024-04-04 22:25:39,405 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/470.239.06, 5.15.0-101-generic, x86_64: installed
nvidia/470.239.06, 6.5.0-26-generic, x86_64: installed
GraphicsCard:
Intel Corporation Alder Lake-N [UHD Graphics] [8086:46d2] (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation Alder Lake-N [UHD Graphics] [8086:7270]
InstallationDate: Installed on 2022-12-15 (477 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64
(20210915)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 0461:4e8d Primax Electronics, Ltd HP USB Optical Mouse
Bus 001 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet
K-2024 Multimedia Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=7e20054f-50f7-4011-8c9c-516960719274 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2024-04-05 (0 days ago)
dmi.bios.date: 02/06/2023
dmi.bios.release: 5.26
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: ADLNV104
dmi.board.asset.tag: Default string
dmi.board.name: MINI S
dmi.board.vendor: AZW
dmi.board.version: 10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrADLNV104:bd02/06/2023:br5.26:svnAZW:pnMINIS:pvrDefaultstring:rvnAZW:rnMINIS:rvr10:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
dmi.product.family: Default string
dmi.product.name: MINI S
dmi.product.sku: 01
dmi.product.version: Default string
dmi.sys.vendor: AZW
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060291/+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 2060204] Re: Resolution drop on third monitor on USB C
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) -- 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/2060204 Title: Resolution drop on third monitor on USB C Status in mutter package in Ubuntu: New Bug description: I have a laptop with an integrated intel intel gpu, 2/3 days ago it was working fine; I have 1 monitor plugged with hdmi and the other one with USB-c Now, the one plugged with USB-C get a lower resolution 1024*768 (not changeable) if the HDMI is plugged at the same time (it works well if I only have the USB c plugged) Feel free to ask if you need information cat /var/log/apt/history.log (relevant lines) Start-Date: 2024-03-29 14:21:01 Commandline: apt upgrade -y Requested-By: roudonro (1000) Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04) End-Date: 2024-03-29 14:21:15 Start-Date: 2024-04-02 16:06:48 Commandline: apt upgrade gnome-calendar Requested-By: roudonro (1000) Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 (2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), update-notifier-common:amd64 (3.192.54.6, 3.192.54.8) End-Date: 2024-04-02 16:06:51 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 09:15:15 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21] InstallationDate: Installed on 2024-03-27 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Dell Inc. Latitude 5520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2023 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0DPC2R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21: dmi.product.family: Latitude dmi.product.name: Latitude 5520 dmi.product.sku: 0A21 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060204/+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 2060132] Re: tesr
Errors messages about buggy ACPI BIOS implementations are normal and not
something we can fix. Although those messages will be hidden when bug
1970069 is fully resolved.
Is there something specific you would like this bug to be about, like
the bluetoothd messages?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
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/2060132
Title:
tesr
Status in Ubuntu:
Incomplete
Bug description:
tesr
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
DeviceFileMinor: 4323
DeviceFileMode: 256
DeviceFileModify: 1
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 550.54.14 Thu Feb 22
01:44:30 UTC 2024
GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-4ubuntu3)
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Apr 3 15:03:00 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer GA107M [GeForce RTX 3050 Mobile]
[1558:5e00]
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev c6) (prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer Cezanne [Radeon Vega Series / Radeon Vega
Mobile Series] [1558:5e00]
InstallationDate: Installed on 2024-03-16 (18 days ago)
InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
LANGUAGE=
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=aa02f2dd-89eb-4b06-a98f-3fe963c633ae ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/10/2022
dmi.bios.release: 7.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.05RME1
dmi.board.asset.tag: Tag 12345
dmi.board.name: NHxxEx
dmi.board.vendor: MEDION
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: MEDION
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd05/10/2022:br7.5:svnMEDION:pnCrawlerE25:pvrNotApplicable:rvnMEDION:rnNHxxEx:rvr1.0:cvnMEDION:ct10:cvrN/A:skuML-21000830031834:
dmi.product.family: Erazer
dmi.product.name: Crawler E25
dmi.product.sku: ML-210008 30031834
dmi.product.version: Not Applicable
dmi.sys.vendor: MEDION
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2060132/+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 2059418] Re: T60 Bluetooth earbuds not being 'set up' on new machine
** Summary changed: - Bluetooth earbuds not being 'set up' on new machine + T60 Bluetooth earbuds not being 'set up' on new machine ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2059418 Title: T60 Bluetooth earbuds not being 'set up' on new machine Status in bluez package in Ubuntu: New Bug description: The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly under completely patched Ubuntu 22.04 on my old machine but now refuse to be setup on a new box running completely patched Ubuntu 22.04 . Other old bluetooth gadgets attached without issue. The end result at the very bottom of this page indicates ‘requestor exited before bonding was completed’ . root@bill:~# bluetoothctl --version bluetoothctl: 5.64 root@bill:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:11627 acl:0 sco:0 events:466 errors:0 TX bytes:78563 acl:0 sco:0 commands:422 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'bill' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: (0xc) Revision: 0x40d LMP Version: (0xc) Subversion: 0x7225 Manufacturer: Realtek Semiconductor Corporation (93) root@bill:~# bluetoothctl Agent registered [CHG] Controller BC:C7:46:9D:25:98 Pairable: yes [bluetooth]# show Controller BC:C7:46:9D:25:98 (public) Name: bill Alias: bill Class: 0x007c0104 Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink (110b--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0a (10) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [bluetooth]# devices Device 74:45:CE:BA:24:65 WH-CH710N At this point I started the earbuds (T60) having a problem getting set up. [CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes [CHG] Controller BC:C7:46:9D:25:98 Discovering: yes [NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C [CHG] Device 34:95:04:4B:07:3C RSSI: -86 [NEW] Device 0B:20:24:A3:E7:56 T60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -52 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -64 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG]
[Touch-packages] [Bug 2059418] Re: Bluetooth earbuds not being 'set up' on new machine
It seems a few different manufacturers have products called 'T60' so please mention the brand in the bug title. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2059418 Title: Bluetooth earbuds not being 'set up' on new machine Status in bluez package in Ubuntu: Incomplete Bug description: The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly under completely patched Ubuntu 22.04 on my old machine but now refuse to be setup on a new box running completely patched Ubuntu 22.04 . Other old bluetooth gadgets attached without issue. The end result at the very bottom of this page indicates ‘requestor exited before bonding was completed’ . root@bill:~# bluetoothctl --version bluetoothctl: 5.64 root@bill:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:11627 acl:0 sco:0 events:466 errors:0 TX bytes:78563 acl:0 sco:0 commands:422 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'bill' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: (0xc) Revision: 0x40d LMP Version: (0xc) Subversion: 0x7225 Manufacturer: Realtek Semiconductor Corporation (93) root@bill:~# bluetoothctl Agent registered [CHG] Controller BC:C7:46:9D:25:98 Pairable: yes [bluetooth]# show Controller BC:C7:46:9D:25:98 (public) Name: bill Alias: bill Class: 0x007c0104 Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink (110b--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0a (10) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [bluetooth]# devices Device 74:45:CE:BA:24:65 WH-CH710N At this point I started the earbuds (T60) having a problem getting set up. [CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes [CHG] Controller BC:C7:46:9D:25:98 Discovering: yes [NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C [CHG] Device 34:95:04:4B:07:3C RSSI: -86 [NEW] Device 0B:20:24:A3:E7:56 T60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -52 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -64 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
In case anyone is wondering, you won't start to see an improvement until you have at least: linux >= 6.8.0-20.20 and plymouth >= 24.004.60-1ubuntu6 -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2059848] Re: Error in the calendar as shown in the print I attached
Please rename the video using Latin characters because Launchpad can't handle other character sets and we're unable to download the video. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2059848 Title: Error in the calendar as shown in the print I attached Status in Ubuntu: Incomplete Bug description: The error happens when I click on the last days of the calendar ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 16:28:25 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1787:5220] InstallationDate: Installed on 2024-03-29 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Semp Toshiba Informatica Ltda STI 007467 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic root=UUID=cffe7efc-9ab3-4fe8-93ad-c666ead76093 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends, Inc. dmi.bios.version: 1.0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: STI 007467 dmi.board.vendor: Semp Toshiba Informatica Ltda dmi.chassis.type: 3 dmi.chassis.vendor: Semp Toshiba Informatica Ltda dmi.modalias: dmi:bvnAmericanMegatrends,Inc.:bvr1.0:bd09/05/2012:br8.15:svnSempToshibaInformaticaLtda:pnSTI007467:pvrRev.10/00:rvnSempToshibaInformaticaLtda:rnSTI007467:rvr:cvnSempToshibaInformaticaLtda:ct3:cvr:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: STI 007467 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: Rev. 10/00 dmi.sys.vendor: Semp Toshiba Informatica Ltda version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2059848/+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 2059651] Re: network-manager gets uninstalled on apt full-upgrade
Yes this bug no longer happens, confirmed on two machines. But there are other issues with many hundreds of packages being released so please log new bugs as you find them. ** No longer affects: ubuntu-meta (Ubuntu) ** Package changed: network-manager (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in Ubuntu: Fix Released Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2059651/+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 2037509] Re: Gnome/Ubuntu desktop wayland
Thanks for the bug report. Please attach screenshots, photos or a video of the problem so we can better understand the issue. ** Package changed: ubuntu-meta (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037509 Title: Gnome/Ubuntu desktop wayland Status in Ubuntu: Incomplete Bug description: Good day, I hasten to inform you about a problem that has not left your distribution for several releases in a row. When the Wayland secant is launched, some window elements for control are not active. In particular, the open new tab/settings expand/collapse buttons in browsers and ower applications do not work. Snap and Deb are equally susceptible to this problem. The solution is to login to X11 and immediately log out and log into Wayland again. In the current builds of the Minotaur, the problem appeared quite recently, with the release of the public beta; in the builds for developers, this problem did not occur. I will be very upset if this problem goes into release. Please correct it if possible. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:14:33 2023 InstallationDate: Installed on 2023-06-21 (98 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230620) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2037509/+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 2059651] [NEW] network-manager gets uninstalled on apt full-upgrade
Public bug reported: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. ** Affects: network-manager (Ubuntu) Importance: High Status: New ** Affects: ubuntu-meta (Ubuntu) Importance: High Status: New ** Tags: noble ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+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 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2059341] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2059341 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: I have a server running ubuntu 22.04.4 LTS and the system boots fine and all the hardware is detected, but the HDMI output is freezing on the line: "r8169 000:03:00.0 emp3s0: renamed from eth0". I have managed to get past this previously by adding "nomodeset" to the GRUB boot options but I need the graphics driver for hardware transcoding as that's its main use so need to try and think of another way around this issue. I can ssh into the server fine, it seems to be working fine otherwise. I've seen that it might be when the igpu takes over. Here is my hardware: CPU: i5-13500T, RAM: 64GB DDR4, MOBO: ASRock B760M-ITX, HDDs: 1TB m.2 gen3, 12TB HDD, 8TB HDD, PSU: Corsair SF750.! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Mar 27 22:51:48 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation AlderLake-S GT1 [1849:4680] InstallationDate: Installed on 2024-03-22 (5 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0033 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 14: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 14: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: ASRock B760M-ITX/D4 WiFi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fdded36-c076-4a14-a7b9-ef9a6fe5a11f ro i915.alpha_support=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.05 dmi.board.name: B760M-ITX/D4 WiFi 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:bvnAmericanMegatrendsInternational,LLC.:bvr3.05:bd06/09/2023:br5.27:svnASRock:pnB760M-ITX/D4WiFi:pvrToBeFilledByO.E.M.:rvnASRock:rnB760M-ITX/D4WiFi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: B760M-ITX/D4 WiFi dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: ASRock version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 2059149] Re: Xorg crash
It appears the recurring problem here is: simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem) WARNING: CPU: 19 PID: 4751 at drivers/gpu/drm/drm_gem_shmem_helper.c:319 drm_gem_shmem_vmap+0x1a5/0x1e0 ** Summary changed: - Xorg crash + Crash ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/2059149 Title: Crash Status in linux package in Ubuntu: Incomplete Bug description: X display crashes when disconnecting and reconnecting my monitors. This appears to be different than my KVM issue. I am not seeing drm gpu error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 11:36:54 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102GL [RTX A5000] [10de:2231] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102GL [RTX A5000] [10de:147e] InstallationDate: Installed on 2022-04-07 (719 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=c56061b9-1478-4914-a919-96eb077fff48 ro quiet splash nvidia-drm.modeset=1 initcall_blacklist=acpi_cpufreq_init amd_pstate=active amd_pstate.shared_mem=1 acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd09/26/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+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 2043915] Re: Booting into live session results in try/install page white screen
Please see bug 2056160 for the time being. -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2058876] Re: display freeze
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
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/2058876
Title:
display freeze
Status in Ubuntu:
Incomplete
Bug description:
The display keeps freezing. Sometime mouse keeps freezing. Sometime
after a sleep, when the laptop wake ups, the display not working or it
remain blank. again I have to restart it. It is very annoying as your
workspace i.e. all the opened apps got deleted. Again you have to
restart. It hampers the work. I am using NVIDIA driver 535 (tested)
display driver, which is recommended. I have gtx 1650 graphics. Ryzen
5 4000 series processor.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17
22:55:48 UTC 2024
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 09:29:55 2024
DistUpgraded: 2024-01-13 13:01:05,362 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: I don't know
GraphicsCard:
NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [1025:1447]
Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) (prog-if
00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Renoir [1025:1455]
InstallationDate: Installed on 2023-08-30 (208 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_IN
LANGUAGE=en_IN:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=33f81450-d6fa-4803-aba2-9ddca9a4a12a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-13 (72 days ago)
dmi.bios.date: 02/04/2021
dmi.bios.release: 1.4
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Stonic_RNS
dmi.board.vendor: RO
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.04:bd02/04/2021:br1.4:efr1.2:svnAcer:pnNitroAN515-44:pvrV1.04:rvnRO:rnStonic_RNS:rvrV1.04:cvnAcer:ct10:cvrV1.04:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-44
dmi.product.sku:
dmi.product.version: V1.04
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 2058838] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg crash + Crash -- 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/2058838 Title: Crash Status in Ubuntu: Incomplete Bug description: When switching KVM my X session crashes. Syslog gets cleared as well for some reason. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 23:58:33 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA102GL [RTX A5000] [10de:2231] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102GL [RTX A5000] [10de:147e] InstallationDate: Installed on 2022-04-07 (717 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=c56061b9-1478-4914-a919-96eb077fff48 ro quiet splash nvidia-drm.modeset=1 initcall_blacklist=acpi_cpufreq_init amd_pstate=active amd_pstate.shared_mem=1 acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd09/26/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
That commit is not meant to reflect the outcome of discussions that happened after it (comment #93). It's just an intermediate "UNRELEASED" commit reflecting intermediate development. My intent with shared repos like this is to show what is being worked on before anything is released to the archive. The tags still accurately reflect what reached or was proposed to the archive. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Thanks. I've reflected those changes in git: https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest/ -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()
** Tags added: fixed-in-mesa-24.1 fixed-upstream -- 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/2054851 Title: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference() Status in Mesa: New Status in mesa package in Ubuntu: Fix Committed Status in mesa package in Debian: Confirmed Bug description: Idont know ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Feb 23 10:38:05 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-10-01 (146 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CO.UTF-8 LANGUAGE=es_CO:es PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 Signal: 11 SignalName: SIGSEGV SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2054851/+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 1970069] Re: Annoying boot messages interfering with splash screen
That change is in plymouth, but hooks/framebuffer is in initramfs-tools. If you're suggesting moving the code from plymouth into initramfs-tools then I kind of understand, but it's not directly related to fixing this bug. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
If you are suggesting moving the logic from plymouth into initramfs- tools then please start by duplicating the code you'd like moved into initramfs-tools. That would be efficient since you have commit access to initramfs-tools, and would mean I only have to deal with plymouth here. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2058314] Re: software-properties-gtk (ValueError) /usr/bin/software-properties-gtk@100 → __init__ → __init__ → backup_sourceslist → __init__
*** This bug is a duplicate of bug 2053228 *** https://bugs.launchpad.net/bugs/2053228 ** Summary changed: - /usr/bin/software-properties-gtk:ValueError:/usr/bin/software-properties-gtk@100:__init__:__init__:backup_sourceslist:__init__ + software-properties-gtk (ValueError) /usr/bin/software-properties-gtk@100 → __init__ → __init__ → backup_sourceslist → __init__ ** This bug has been marked a duplicate of bug 2053228 software-properties-gtk does not start -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2058314 Title: software-properties-gtk (ValueError) /usr/bin/software-properties- gtk@100 → __init__ → __init__ → backup_sourceslist → __init__ Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.42, the problem page at https://errors.ubuntu.com/problem/3f3a7a239df521d94b27fbe6096dc4a05f967d35 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058314/+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 2053228] Re: software-properties-gtk does not start
Also tracking in:
https://errors.ubuntu.com/problem/3f3a7a239df521d94b27fbe6096dc4a05f967d35
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Triaged
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2058313] Re: whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload-all@220 → main → collect_info → process_report → add_gdb_info → gdb_command
** Summary changed: - /usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@220:main:collect_info:process_report:add_gdb_info:gdb_command + whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload-all@220 → main → collect_info → process_report → add_gdb_info → gdb_command -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2058313 Title: whoopsie-upload-all (TypeError) /usr/share/apport/whoopsie-upload- all@220 → main → collect_info → process_report → add_gdb_info → gdb_command Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.28.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/def1584660098f405d12c36422a9561aa02aa911 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2058313/+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 2058253] Re: Notebook screen the look is "matte" in KDE
If it looks correct in GNOME then please briefly log into GNOME and run: xrandr --verbose > gnome-xrandr.txt and attach the resulting text file here. Also if KDE has any monitor colour profile settings then try toggling those. ** Summary changed: - Notebook screen the look is "matte" + Notebook screen the look is "matte" in KDE ** Package changed: xorg (Ubuntu) => kwin (Ubuntu) ** Changed in: kwin (Ubuntu) Status: New => Incomplete -- 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/2058253 Title: Notebook screen the look is "matte" in KDE Status in kwin package in Ubuntu: Incomplete Bug description: Hi, feedback: In general, on the notebook screen, the look is "matte", smoke in the images, videos, games, on the desktop, etc., especially when the screen brightness increases. When compared to Ubuntu with gnome, windows 11, it has greater clarity, stronger colors, etc. In Kubuntu I didn't find the option to increase the sharpness, to improve etc., so I wanted to leave feedback here, to help with the project. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-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: Mon Mar 18 10:56:50 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9a78] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3f9c] InstallationDate: Installed on 2024-01-13 (64 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: LENOVO 82MD ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-26-generic root=UUID=58277c11-b933-4491-8d44-0caa0d498477 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2023 dmi.bios.release: 1.57 dmi.bios.vendor: LENOVO dmi.bios.version: GGCN57WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ITL6 dmi.ec.firmware.release: 1.57 dmi.modalias: dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6: dmi.product.family: IdeaPad 3 15ITL6 dmi.product.name: 82MD dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6 dmi.product.version: IdeaPad 3 15ITL6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2058253/+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 1970069] Re: Annoying boot messages interfering with splash screen
It seems unlikely my all-in-one kernel fix will be accepted upstream.
While I could propose it as an Ubuntu patch, another alternative is to
just let the linux task track bug 2049390 (Fix Committed). Then most
people will only need the above Plymouth patch to get a complete fix.
The remaining tasks beyond that are:
initramfs-tools: Required to keep the initrd size under control after
the Plymouth fix is released.
systemd: Would still be nice to implement a redundant fix to suppress
the "clean" message. That would fix bug 1914409 and when combined with
loglevel=3, would also prevent this bug 1970069.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
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/1970069
Title:
Annoying boot messages interfering with splash screen
Status in initramfs-tools package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in plymouth package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Bug description:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many
machines, when the user should be seeing only the BIOS logo and/or
Plymouth splash screens.
[ Workaround ]
On most machines you can hide the problem by using these kernel parameters
together:
quiet splash loglevel=3 fastboot
[ Original Description ]
Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
as clean as it used to be.
Basically, the flow used to be in 20.04:
GRUB > Splash screen > Login prompt
Currently in 22.04:
GRUB > Splash screen > Messages (in the attached file) > Splash screen
again for a sec > Login prompt
All of those messages already existed in 20.04, the difference is that
they were not appearing during boot.
I was able to get rid of the "usb" related messages by just adding
"loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".
Regarding the fsck related message, I can get rid of them by adding
"fsck.mode=skip".
However, I do not want to just disable fsck or set the loglevel to 0.
This is not a sustainable solution.
Something definitely changed here. These messages are not of enough
relevance to be shown at boot by default, and they should remain
hidden like they were in Focal.
Obviously a minor issue, but important to the whole look and feel of
the OS for desktop.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1869655] Re: Boot animations start too late to be useful
The patch proposed in https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/comments/91 will help here, but since it might not be the last plymouth change required for this issue, it doesn't mention bug 1869655. -- 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/1869655 Title: Boot animations start too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Bug description: Boot animations start too late to be useful Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+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 1970069] Re: Annoying boot messages interfering with splash screen
Here's a fix for plymouth/noble. The source is in: https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest We skipped ubuntu5 because that technically existed in bug 2054769 for 10 days already. Also note this will cause some temporary initrd bloat while the initramfs-tools change is pending in comment #90. ** Patch added: "plymouth_24.004.60-1ubuntu6.debdiff" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5756732/+files/plymouth_24.004.60-1ubuntu6.debdiff -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1869655] Re: Boot animations start too late to be useful
** Changed in: plymouth (Ubuntu) Status: Won't Fix => In Progress ** Changed in: plymouth (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1869655 Title: Boot animations start too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Bug description: Boot animations start too late to be useful Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+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 1970069] Re: Annoying boot messages interfering with splash screen
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs- tools/+git/initramfs-tools/+merge/462482 ** Merge proposal unlinked: https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481 -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=3 fastboot [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1869655] Re: Boot animations start too late to be useful
** Merge proposal unlinked: https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481 -- 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/1869655 Title: Boot animations start too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Won't Fix Bug description: Boot animations start too late to be useful Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+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
