[Touch-packages] [Bug 2013135] Re: Dissapearing Mouse Cursor
Typing on the keyboard will also hide the mouse pointer, which seems correct to me. Can you explain what you mean in: > There doesn't appear to be a trigger for the random disappearances that is user input. ** 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/2013135 Title: Dissapearing Mouse Cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Touching the touch screen display removes the mouse cursor. It comes back after blindly navigating to the menu bar. This also happends randomly without touching the touchscreen. There doesn't appear to be a trigger for the random disappearances that is user input. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 18:19:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fc] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fc] InstallationDate: Installed on 2023-02-28 (28 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 7737 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1322e8b8-bc4a-464a-89b8-6bc305451ff5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.release: 0.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0H9X60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.ec.firmware.release: 0.4 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd10/09/2013:br0.4:efr0.4:svnDellInc.:pnInspiron7737:pvr:rvnDellInc.:rn0H9X60:rvrA00:cvnDellInc.:ct8:cvr0.1:skuInspiron7737: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7737 dmi.product.sku: Inspiron 7737 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 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013135/+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 2013071] Re: Session crash after initial login
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 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 1861609, 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. ** Tags added: qxl ** This bug has been marked a duplicate of bug 1861609 [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper -- 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/2013071 Title: Session crash after initial login Status in xorg package in Ubuntu: Confirmed Bug description: Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party software for graphics and Wi-Fi hardware and additional media formats" selected during install. When logging in for the first time, the session immediately crashes and returns to the login screen. Attempting to login again without rebooting is successful. Attempting to login again after rebooting reproduces the issue. The issue doesn't seem to present itself if "Install third-party software for graphics and Wi-Fi hardware and additional media formats" is not selected during install. Differences in installed packages: - chromium-codecs-ffmpeg-extra - gimp-help-common - gimp-help-en - gstreamer1.0-plugins-ugly - gstreamer1.0-vaapi - hyphen-en-us - liba52-0.7.4 - libmpeg2-4 - libopencore-amrnb0 - libopencore-amrwb0 - libreoffice-help-common - libreoffice-help-en-us - libsidplay1v5 - libva-wayland2 - mythes-en-us - thunderbird-locale-en - thunderbird-locale-en-us - ubuntu-restricted-addons - wbritish Since it seems unlikely that the language pack packages are interfering... maybe libva-wayland2 is to blame? ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 28 07:47:04 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2023-03-28 (0 days ago) InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap 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/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.1-2.fc37 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 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
[Touch-packages] [Bug 2013040] Re: Second screen blank on laptop
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags added: amdgpu hybrid multigpu multimmonitor nvidia ** Summary changed: - Second screen blank on laptop + Second screen blank on AMD+NVIDIA laptop -- 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/2013040 Title: Second screen blank on AMD+NVIDIA laptop Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: If I plugin the second screen (external monitor) using HDMI before logging into my session, the second screen is blank, although it receives a signal. In order to get the image, I have to either deactivate and reactivate it from Display Settings, or move any window to it. This happens using the following config: Laptop: Lenovo Legion 7 16ACHg6 CPU: AMD Ryzen 9 5900 HX APU RAM: 32 GB DDR4-3200 GPU: iGPU AMD Vega 8 + dGPU NVIDIA GeForce 3080 Mobile GPU (Max-P) Main laptop screen is powered by iGPU whereas external screen is powered by dGPU ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-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 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 11:10:36 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:3a58] InstallationDate: Installed on 2023-02-09 (46 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN59WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.59 dmi.modalias: dmi:bvnLENOVO:bvrGKCN59WW:bd11/21/2022:br1.59:efr1.59:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6 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/mutter/+bug/2013040/+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 2012879] Re: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_f
** Changed in: accountsservice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012879 Title: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 2012957] Re: Xorg freeze
*** This bug is a duplicate of bug 2007668 *** https://bugs.launchpad.net/bugs/2007668 This sounds like one of the symptoms of bug 2007668. I can confirm that Ubuntu 23.04 works more reliably on 12th gen chips, but that's not officially released yet. You might also have more luck by installing Ubuntu 22.04 and then upgrading the kernel like: sudo apt install linux-oem-22.04c ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 2007668 Intel 12th gen: Noisy screen corruption during cursor movement, and whole screen freezes, in 5.19 kernels -- 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/2012957 Title: Xorg freeze Status in linux package in Ubuntu: New Bug description: I'm not sure if this is an xorg bug because i'm pretty sure I'm using wayland, however ubuntu-bug says it's an xorg issue. I installed the GNOME desktop instead of the ubuntu one, however it does happen on the ubuntu desktop as well. It seems to happen less often on the GNOME desktop (though still multiple times a day) When I perform certain actions I can semi-reliably produce a total screen freeze. Some examples include using the search menu on gnome, opening a video in fullscreen, and clicking buttons in fractal (matrix client.) There are many more scenarios that I haven't listed. The screen will completely freeze but the computer will keep going normally (e.g. I can type, use the cursor, listen to audio, etc.) This can be remedied by pressing CONTROL+ALT+F3 which brings me into the console, then waiting about 5 seconds, then switching back with CONTROL+ALT+F2 This doesn't seem to be related to any computer load issues and occurs reliably after clicking on something/typing in a text field until the offending program is restarted. When the program is restarted, the issue sometimes goes away but sometimes persists. This has been happening since I installed ubuntu a couple weeks ago. I am able to provide more details if necessary and do some debugging things, but I'm not a technical user so will need babying. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: GNOME Date: Mon Mar 27 12:47:02 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Matsushita Electric Industrial Co., Ltd. Alder Lake-P Integrated Graphics Controller [10f7:8338] InstallationDate: Installed on 2023-03-15 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Panasonic Connect Co., Ltd. CFFV3-1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=f8060648-d61e-4101-984c-4f5a1ff087f8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2022 dmi.bios.release: 1.0 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: V1.00L15 dmi.board.asset.tag: No Asset Tag dmi.board.name: CFFV3-1L dmi.board.vendor: Panasonic Connect Co., Ltd. dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Connect Co., Ltd. dmi.chassis.version: 001 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrV1.00L15:bd05/09/2022:br1.0:efr1.0:svnPanasonicConnectCo.,Ltd.:pnCFFV3-1:pvr001:rvnPanasonicConnectCo.,Ltd.:rnCFFV3-1L:rvr1:cvnPanasonicConnectCo.,Ltd.:ct10:cvr001:skuCF-FV3DFNCR: dmi.product.family: Let'snote/TOUGHBOOK dmi.product.name: CFFV3-1 dmi.product.sku: CF-FV3DFNCR dmi.product.version: 001 dmi.sys.vendor: Panasonic Connect Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6 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
[Touch-packages] [Bug 1595238] Re: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/gl
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1595238 Title: Unity 8 Desktop Preview System Settings do not work on nouveau [ASSERT: "eglSwapBuffers(mEglDisplay, eglSurface) == EGL_TRUE" in file ../../../src/ubuntumirclient/glcontext.cpp, line 239] Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: When I try to open System Settings, the Ubuntu logo keeps turning and nothing happens. I installed unity8-desktop-session-mir on my Xenial 16.04.1 Desktop where I use NVIDIA driver GF108[GeForce GT 530]. I also created a new user account with English (US) language settings, because Unity 8 does not work well when I use my own account with my language settings. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595238/+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 1623507] Re: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear().
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- 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/1623507 Title: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear(). Status in Canonical System Image: New Status in Mir: Triaged Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: 16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:34:45 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988] InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- 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/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mesa: New Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1623508] Re: unity8 crashed with SIGSEGV
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1623508 Title: unity8 crashed with SIGSEGV Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: 16.10 first unity 8 run16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:32:07 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: unity8 --mode=full-shell Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1623508/+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 1631627] Re: Unity 8 freezes on Nouveau
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1631627 Title: Unity 8 freezes on Nouveau Status in Canonical System Image: Incomplete Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I installed Ubuntu 16.10 yesterday and Unity 8 constantly freezes after I do some clicking around the desktop (using Browser, System Settings and the like), I am running it on Nouveau driver for GTX970M, I refrained from installing proprietary drivers to test Unity 8, but it is unusable and after it freezes I can only power off my laptop as nothing works. Is this a known issue? Also Unity 7 does not load at all, but I will post a separate bug for that. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1631627/+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 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)
"Fix Released" in lunar, assuming it is the above issue. If it's not then please just change the status back. ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504 Importance: Unknown Status: Unknown ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** No longer affects: linux (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/2008897 Title: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Bug description: My desktop unexpectedly freezes or crashes every now and then (once or week or less). Typically the machine is not usable but this time I managed to log back in via the text console and grab the following text from dmesg: [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245291] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a01000 from client 0x1b (UTCL2) [11689.245294] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245296] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245298] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245299] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245301] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245302] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245304] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245311] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0c000 from client 0x1b (UTCL2) [11689.245313] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245315] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245316] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245318] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245319] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245320] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245322] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245329] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0b000 from client 0x1b (UTCL2) [11689.245331] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245333] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245334] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245336] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245337] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245339] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245340] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245347] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a06000 from client 0x1b (UTCL2) [11689.245349] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245350] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245351] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245352] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245354] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245355] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245356] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245362] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0a000 from client 0x1b (UTCL2) [11689.245363] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245364] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245366] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245367] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245368] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245369] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245370] amdgpu
[Touch-packages] [Bug 1672793] Re: unity-system-compositor crashed with SIGSEGV
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug is no longer a duplicate of bug 1553328 Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1672793 Title: unity-system-compositor crashed with SIGSEGV Status in Unity System Compositor: New Status in unity-system-compositor package in Ubuntu: New Bug description: I just got this on the first login to my new Ubuntu user profile ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: unity-system-compositor 0.9.1+17.04.20170216-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Tue Mar 14 20:14:24 2017 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2013-09-15 (1275 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 13 --to-dm-fd 22 --vt 8 ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f8dc76dd07f:mov0x8(%r15),%edx PC (0x7f8dc76dd07f) ok source "0x8(%r15)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so Title: unity-system-compositor crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.75-1ubuntu1 version.lightdm: lightdm 1.21.5-0ubuntu1 version.mesa: libegl1-mesa-dev 13.0.4-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1672793/+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 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)
Looks most likely to be https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504 which is fixed in Mesa 22.3.1. But then similar bugs still exist like bug 2012819. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7504 https://gitlab.freedesktop.org/mesa/mesa/-/issues/7504 -- 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/2008897 Title: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) Status in Mesa: Unknown Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Fix Released Bug description: My desktop unexpectedly freezes or crashes every now and then (once or week or less). Typically the machine is not usable but this time I managed to log back in via the text console and grab the following text from dmesg: [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245291] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a01000 from client 0x1b (UTCL2) [11689.245294] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245296] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245298] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245299] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245301] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245302] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245304] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245311] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0c000 from client 0x1b (UTCL2) [11689.245313] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245315] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245316] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245318] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245319] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245320] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245322] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245329] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0b000 from client 0x1b (UTCL2) [11689.245331] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245333] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245334] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245336] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245337] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245339] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245340] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245347] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a06000 from client 0x1b (UTCL2) [11689.245349] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245350] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245351] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245352] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245354] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245355] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245356] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245362] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0a000 from client 0x1b (UTCL2) [11689.245363] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245364] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245366] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245367] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245368] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245369] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245370] amdgpu :09:00.0:
[Touch-packages] [Bug 2008897] Re: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault)
** Summary changed: - Desktop freezes or crashes intermittently + Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) ** Package changed: kwin (Ubuntu) => linux (Ubuntu) ** Tags added: amdgpu ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2008897 Title: Desktop freezes or crashes intermittently (amdgpu: [gfxhub] page fault) Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: My desktop unexpectedly freezes or crashes every now and then (once or week or less). Typically the machine is not usable but this time I managed to log back in via the text console and grab the following text from dmesg: [11689.245277] gmc_v10_0_process_interrupt: 10 callbacks suppressed [11689.245284] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245291] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a01000 from client 0x1b (UTCL2) [11689.245294] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245296] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245298] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245299] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245301] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245302] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245304] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245308] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245311] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0c000 from client 0x1b (UTCL2) [11689.245313] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031 [11689.245315] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [11689.245316] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x1 [11689.245318] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245319] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [11689.245320] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245322] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245326] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245329] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0b000 from client 0x1b (UTCL2) [11689.245331] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245333] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245334] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245336] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245337] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245339] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245340] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245344] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245347] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a06000 from client 0x1b (UTCL2) [11689.245349] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245350] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245351] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245352] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245354] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245355] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245356] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245360] amdgpu :09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32771, for process kwin_x11 pid 1358 thread kwin_x11:cs0 pid 1369) [11689.245362] amdgpu :09:00.0: amdgpu: in page starting at address 0x800598a0a000 from client 0x1b (UTCL2) [11689.245363] amdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x [11689.245364] amdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [11689.245366] amdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 [11689.245367] amdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x0 [11689.245368] amdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [11689.245369] amdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x0 [11689.245370] amdgpu :09:00.0: amdgpu: RW: 0x0 [11689.245374]
[Touch-packages] [Bug 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]
** Tags added: fixed-in-accountsservice-23.12ish fixed-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice] Status in accountsservice: New Status in gnome-control-center: Unknown Status in accountsservice package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: This is now the #1 gnome-shell crasher in Ubuntu 23.04. https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C:
[Touch-packages] [Bug 1966905] Re: Segfault in g_type_check_instance_cast → free_fetch_user_request → fetch_user_incrementally → on_find_user_by_name_finished → g_task_return_now
** Summary changed: - Invalid memory access in accountsservice: free_fetch_user_request() + Segfault in g_type_check_instance_cast → free_fetch_user_request → fetch_user_incrementally → on_find_user_by_name_finished → g_task_return_now ** Description changed: + This is now the #1 gnome-shell crasher in Ubuntu 23.04. + https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun
[Touch-packages] [Bug 1966905] Re: Invalid memory access in accountsservice: free_fetch_user_request()
Tracking also in https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Invalid memory access in accountsservice: free_fetch_user_request() Status in accountsservice: New Status in gnome-control-center: Unknown Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a
[Touch-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
Upstream reckons this has fixed it for gnome-control-center: https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/1681 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2348 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2348 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2348 Importance: Unknown Status: Unknown ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released ** Tags added: fixed-in-gnome-control-center-44.rc ** Summary changed: - Memory access errors in gnome-shell from accountsservice + Invalid memory access in accountsservice: free_fetch_user_request() ** Description changed: https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 + https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E:
[Touch-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
See also bug 2012879 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Invalid memory access in accountsservice: free_fetch_user_request() Status in accountsservice: New Status in gnome-control-center: Unknown Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by
[Touch-packages] [Bug 2012879] Re: Crash in indicator-messages-service
Tracking in https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d ** Tags added: jammy kinetic ** Description changed: + https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d + Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: - LANG=en_AU.UTF-8 - LANGUAGE=en_AU:en - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + LANGUAGE=en_AU:en + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo ** Summary changed: - Crash in indicator-messages-service + indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() ** Package changed: indicator-messages (Ubuntu) => accountsservice (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2012879 Title: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+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 2012832] Re: Xorg crashes on second and next unbind operations of Arc GPU
Definitely a crash, but not yet actionable: [ 220.992] (II) config/udev: removing GPU device /sys/devices/pci:00/:00:06.2/:02:00.0/:03:01.0/:04:00.0/drm/card1 /dev/dri/card1 [ 220.992] xf86: remove device 1 /sys/devices/pci:00/:00:06.2/:02:00.0/:03:01.0/:04:00.0/drm/card1 [ 220.992] (EE) [ 220.992] (EE) Backtrace: [ 220.995] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x561dfa9a3809] [ 220.996] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f0ed6842520] [ 220.997] (EE) 2: ? (?+0x0) [0x0] [ 220.997] (EE) [ 220.997] (EE) Segmentation fault at address 0x0 [ 220.997] (EE) Fatal server error: [ 220.997] (EE) Caught signal 11 (Segmentation fault). Server aborting ** Package changed: xorg (Ubuntu) => xorg-server (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/2012832 Title: Xorg crashes on second and next unbind operations of Arc GPU Status in xorg-server package in Ubuntu: Incomplete Bug description: Hello folks, Experimenting with new Lenovo Yoga i7 with Intel Arc on board and found that even if it's possible to disable the GPU to save power, Xorg session crashes the session after the second attempt (the first after reboot works just fine). This works like that - after poweroff/poweron of the system I execute the next commands: 1. First attempt: * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Works great * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 2. Second attempt: * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/unbind # Here the Xorg crashes, but I can login again * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)", it's embedded graphics * echo -n ":04:00.0" | sudo tee /sys/bus/pci/drivers/i915/bind * DRI_PRIME=1 glxinfo | grep 'OpenGL renderer' # Shows: "OpenGL renderer string: Mesa Intel(R) Arc(tm) A370M Graphics (DG2)" 3. This and the next attempts are just the same as second one I collected the info and can reproduce this state after each reboot, so hopefully it will help you to find what's going wrong during second and next unbind operations. I can always help with additional information if you will need some. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Mar 26 12:25:03 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ae3] Subsystem: Lenovo Device [17aa:3ae3] InstallationDate: Installed on 2023-02-21 (33 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 82UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.8-060208-generic root=UUID=52e0f674-3384-4128-973b-d049407f961a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2022 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: J1CN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 16IAH7 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrJ1CN35WW:bd11/16/2022:br1.35:efr1.35:svnLENOVO:pn82UF:pvrYoga716IAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct31:cvrYoga716IAH7:skuLENOVO_MT_82UF_BU_idea_FM_Yoga716IAH7: dmi.product.family: Yoga 7 16IAH7 dmi.product.name: 82UF dmi.product.sku: LENOVO_MT_82UF_BU_idea_FM_Yoga 7 16IAH7 dmi.product.version: Yoga 7 16IAH7 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.0.0.20221126.1+2050~u22.04
[Touch-packages] [Bug 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
If you're not using Ubuntu 23.04 then you can get the fixed version 53 of the extension from: https://extensions.gnome.org/extension/615/appindicator-support/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 2012646] Re: [Shanghai Zhaoxin Semiconductor Co., Ltd. ZXE CRB] No backlight control
** Summary changed: - Ubuntu 23.04: Adjusting backlight is unavailable under `Software Rendering`. + [Shanghai Zhaoxin Semiconductor Co., Ltd. ZXE CRB] No backlight control ** 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/2012646 Title: [Shanghai Zhaoxin Semiconductor Co., Ltd. ZXE CRB] No backlight control Status in linux package in Ubuntu: New Bug description: Ubuntu 23.04: Adjusting backlight is unavailable under `Software Rendering`. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.65.01-0ubuntu3_amd64.deb CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 23 23:11:16 2023 DistUpgraded: 2023-03-05 10:20:01,054 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/23.01.00, 6.2.0-18-generic, x86_64: installed (WARNING! Diff between built and installed module!) rtpengine/10.5.3.5, 5.19.0-35-generic, x86_64: installed rtpengine/10.5.3.5, 6.2.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Zhaoxin ZX-E C-960 GPU [1d17:3a04] (prog-if 00 [VGA controller]) Subsystem: Zhaoxin ZX-E C-960 GPU [1d17:3a04] InstallationDate: Installed on 2022-10-16 (157 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: Shanghai Zhaoxin Semiconductor Co., Ltd. ZXE CRB ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=c377d279-f34f-4d82-ae9a-e256d706b9de ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-03-05 (18 days ago) dmi.bios.date: 01/26/2021 dmi.bios.release: 16.0 dmi.bios.vendor: Byosoft dmi.bios.version: R16 dmi.board.asset.tag: TBD dmi.board.name: ZEN1 dmi.board.vendor: Shanghai Zhaoxin Semiconductor Co., Ltd. dmi.board.version: TBD dmi.chassis.asset.tag: TBD dmi.chassis.type: 10 dmi.chassis.vendor: Shanghai Zhaoxin Semiconductor Co., Ltd. dmi.chassis.version: TBD dmi.ec.firmware.release: 3.0 dmi.modalias: dmi:bvnByosoft:bvrR16:bd01/26/2021:br16.0:efr3.0:svnShanghaiZhaoxinSemiconductorCo.,Ltd.:pnZXECRB:pvrTBD:rvnShanghaiZhaoxinSemiconductorCo.,Ltd.:rnZEN1:rvrTBD:cvnShanghaiZhaoxinSemiconductorCo.,Ltd.:ct10:cvrTBD:skuTBD: dmi.product.family: ZXE dmi.product.name: ZXE CRB dmi.product.sku: TBD dmi.product.version: TBD dmi.sys.vendor: Shanghai Zhaoxin Semiconductor Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 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/2012646/+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 2012288] Re: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications
** Package changed: xorg (Ubuntu) => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2012288 Title: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications Status in cups package in Ubuntu: New Bug description: I am trying to print. Context :: printer - The network printer I have "HP LaserJet Professional M1217nfw MFP" announces itself via Bonjour, supports SLP Config, LPD Printing and WS-Discovery. The printer is wired to ethernet, and receives it's IP address in IPV4 and IPV6 from the router, set statically at the router. Client - The client machine, Ubuntu 22.10 , is either on wireless (192.168.2.X - DHCP assigned randomly) or wired ethernet (192.168.2.Y - DHCP assigned statically). Sometimes the machine has both interfaces as well as receiving IPV6 addresses for both of these interfaces. It's unclear how printing occurs for discovery, but for comparison - Android "just works", iPhone "just works" , and Windows 10 "just works". Only Ubuntu is the outlier here. When printing a PDF from Chrome, I see there is a mismatch between the printers that Chrome sees, and the printers that are registered with the gnome(?) printers configuration settings. This leads me to believe that these 2 parts of printing are not in sync with one another(!!). Additional, possibly related behavior: When I remove all printers listed. And simply watch the Gnome(?) Printers settings section then a new printer is added automatically exactly this text, yes the duplicate 'HP': "HP HP Laserjet Professional M1217nfw MFP, driverless". This may be a cause of issues since I have not configured an additional printer, yet it appears. When I DO attempt to print to this auto-added printer I receive a vague error after some kind of timeout "Stopped Please restart when the problem is resolved" --- what problem ? What is causing the issue ? This error does not help identify the issue. Can you help me understand what is happening here and how this can be resolved ? If auto-adding a printer is going to magically work , then please include detailed, actionable error messages. Attached -- screenshot of printer subsystems mismatch. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: 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 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 20 11:54:41 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.19.0-31-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-35-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-31-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (64 days ago) dmi.bios.date: 02/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET83W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US 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:
[Touch-packages] [Bug 2009948] Re: Problem with xorg
Thanks for the bug report. I can't see anything obviously wrong in the attached files so please explain in more detail what the problem is. ** 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/2009948 Title: Problem with xorg Status in Ubuntu: Incomplete Bug description: Is not working. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-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 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: fail CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 09:08:31 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:0959] Subsystem: Dell GP108M [GeForce MX230] [1028:0959] InstallationDate: Installed on 2023-03-10 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Vostro 5490 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=b6242c65-c3ec-45af-912f-e70f66a54868 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2022 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0M9F58 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/08/2022:br1.20:svnDellInc.:pnVostro5490:pvr:rvnDellInc.:rn0M9F58:rvrA04:cvnDellInc.:ct10:cvr:sku0959: dmi.product.family: Vostro dmi.product.name: Vostro 5490 dmi.product.sku: 0959 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 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2009948/+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 2012118] Re: Black screen after unplugging external monitor
Thanks for the bug report. Please:
1. 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.
2. If step 1 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.
3. Next time the problem happens, after rebooting run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Tags added: amdgpu hybrid multigpu nvidia
** 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/2012118
Title:
Black screen after unplugging external monitor
Status in Ubuntu:
Incomplete
Bug description:
Steps to reproduce:
1. Plugin laptop into external monitor (HDMI).
2. Leave laptop idle until it sleeps.
3. Unplug laptop from monitor.
At this point the laptop is stuck with a black screen and I cannot
regain control using any of the Ctrl + Alt + F{N} chords. I am forced
to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-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 525.85.12 Sat Jan 28
02:10:06 UTC 2023
GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 18 01:17:24 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
nvidia/525.85.12, 5.19.0-32-generic, x86_64: installed
nvidia/525.85.12, 5.19.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GA104M [GeForce RTX 3070 Mobile / Max-Q]
[1043:118c]
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c4) (prog-if
00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Cezanne [1043:118c]
InstallationDate: Installed on 2022-08-16 (213 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA503QR_GA503QR
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic
root=UUID=cd0d16fc-2228-479b-a09a-e7a1f8e6ea1e ro quiet splash
mem_sleep_default=deep vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: GA503QR.413
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GA503QR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.9
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA503QR.413:bd11/03/2021:br5.19:efr3.9:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA503QR_GA503QR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA503QR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Zephyrus G15
dmi.product.name: ROG Zephyrus G15 GA503QR_GA503QR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
[Touch-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
Also tracking in https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 ** Description changed: + https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 + Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) - ==60511== + ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187)
[Touch-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
** Changed in: accountsservice (Ubuntu) Importance: Medium => High ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Memory access errors in gnome-shell from accountsservice Status in accountsservice: New Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA:
[Touch-packages] [Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
Tentatively declared fixed in lunar, but I don't know the full list of
commits/packages required to get the fix.
** Changed in: gnome-shell (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/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Fix Released
Status in mozjs102 package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
Seems like a fix exists, but it got stalled/forgotten: https://gitlab.gnome.org/GNOME/gsettings-desktop- schemas/-/merge_requests/55 ** No longer affects: curtin (Ubuntu) ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Confirmed => In Progress -- 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/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: New Status in gsettings-desktop-schemas package in Ubuntu: In Progress Status in subiquity package in Ubuntu: Won't Fix Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 2011615] Re: BIOS
Can you take a photo 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/2011615 Title: BIOS Status in Ubuntu: Incomplete Bug description: It seems to me that BIOS has driver problem. When booting the error BIOS message it is showed every time. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-37.38-generic 5.19.17 Uname: Linux 5.19.0-37-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 15:01:32 2023 DistUpgraded: 2023-02-23 21:00:51,671 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:16cd] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:16cd] InstallationDate: Installed on 2022-10-08 (157 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. X555LD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-37-generic root=UUID=893b4641-08f2-4efe-9a19-676c2512bbe7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-02-24 (18 days ago) dmi.bios.date: 01/23/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LD.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LD.403:bd01/23/2019:br4.6:svnASUSTeKCOMPUTERINC.:pnX555LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X555LD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6 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/2011615/+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 2011575] Re: Cursor used during log in after boot still on screen after log in on desktop
This is/was a common issue on AMD systems. I think the 5.14 OEM kernel here is missing this fix: https://gitlab.gnome.org/GNOME/mutter/-/issues/1344#note_932943 But if it's still happening in later kernels then it might be related to: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470 ** Tags added: amdgpu cursor ** Package changed: xorg (Ubuntu) => linux-oem-5.14 (Ubuntu) ** Summary changed: - Cursor used during log in after boot still on screen after log in on desktop + [amdgpu] Cursor used during log in after boot still on screen after log in on desktop ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1344 https://gitlab.gnome.org/GNOME/mutter/-/issues/1344 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6470 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470 -- 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/2011575 Title: [amdgpu] Cursor used during log in after boot still on screen after log in on desktop Status in linux-oem-5.14 package in Ubuntu: New Bug description: After booting up my laptop and logging in, the cursor that is used during the log in phase just freezes on the spot it last was after pressing the enter key to log in and stays there the whole usage time. It only disappears when I restart or shut down the laptop. It doesn't impair the usage of the desktop cursor, but stays on the screen, in front of every open window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21 Uname: Linux 5.14.0-1058-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 13:53:12 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev d1) (prog-if 00 [VGA controller]) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/2011575/+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 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
No crash reports from gnome-shell 44 yet. I'm hopeful this was fixed
by/around the same time as https://gitlab.gnome.org/GNOME/gnome-
shell/-/commit/1559f03a82317e06aa0596bf12feb8b761a58f52
--
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/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mozjs102 package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 1966905] Re: Memory access errors in gnome-shell from accountsservice
The #1 gnome-shell crash in 23.04 is currently: https://errors.ubuntu.com/problem/fa3beeb1c25d862ecb2a0900c2b2519503a6109d which actually sounds like this bug. See also bug 2011429. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Memory access errors in gnome-shell from accountsservice Status in accountsservice: New Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance
[Touch-packages] [Bug 1966905] Re: Memory access errors in gnome-shell from accountsservice
** Summary changed: - Valgrind memory errors in gnome-shell from accountsservice + Memory access errors in gnome-shell from accountsservice -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Memory access errors in gnome-shell from accountsservice Status in accountsservice: New Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA:
[Touch-packages] [Bug 1966905] Re: Valgrind memory errors in gnome-shell from accountsservice
** Summary changed: - Valgrind memory errors in gnome-shell 42 from accountsservice + Valgrind memory errors in gnome-shell from accountsservice ** Tags added: lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1966905 Title: Memory access errors in gnome-shell from accountsservice Status in accountsservice: New Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008)
[Touch-packages] [Bug 2011335] Re: Graphics Driver Problem
Your CD-ROM is experiencing read errors that might be blocking the kernel and delaying booting. So please try removing any disc you have inserted. Also the attached logs are from recovery mode so don't show the original problem. Please reproduce the issue by booting WITHOUT recovery mode, then reboot again and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2011335 Title: Graphics Driver Problem Status in Ubuntu: Incomplete Bug description: I am having an issue with Ubuntu Graphics Driver whenever I try to open my pc after booting ubuntu my monitor gets a blank screen, I don't know why this is happening. For Booting my Ubuntu successfully I have to go to the advanced option from the boot menu and then run ubuntu from there. I think it is a graphics driver problem as after booting ubuntu from advanced settings I get a message saying that the graphics driver will not boot for booting them restart the pc and run ubuntu normally. My PC Specs Monitor with VGA directly form the mother board Integrated graphics of Intel Core i3 10100 Mother board MSI M410 M-HV3 Ask Ubuntu question link https://askubuntu.com/questions/1458896/ubuntu-graphics-driver-problem-intel/1458901#1458901 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 12 17:42:17 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: anbox-ashmem/1, 5.19.0-32-generic, x86_64: installed anbox-ashmem/1, 5.19.0-35-generic, x86_64: installed anbox-binder/1: added GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd CometLake-S GT2 [UHD Graphics 630] [1458:d000] InstallationDate: Installed on 2022-11-14 (117 days ago) InstallationMedia: MachineType: Gigabyte Technology Co., Ltd. H410M H V3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=18c74b79-bde0-49d3-9a2f-9238bdfe8fee ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F6 dmi.board.asset.tag: Default string dmi.board.name: H410M H V3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF6:bd03/25/2022:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH410MHV3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH410MHV3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H510 MB dmi.product.name: H410M H V3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2011335/+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 2011279] Re: xorg
Please run the following command: journalctl -b0 > journal.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-desktop-icons-ng (Ubuntu) ** Summary changed: - xorg + The desktop icon is not displayed, and the right-click menu is incompletely loaded ** Changed in: gnome-shell-extension-desktop-icons-ng (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/2011279 Title: The desktop icon is not displayed, and the right-click menu is incompletely loaded Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Incomplete Bug description: 桌面标不显示，右键菜单加载不完整 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 07:57:08 2023 DistUpgraded: 2022-11-12 11:37:26,280 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.85.05, 6.1.0-16-generic, x86_64: installed 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: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22ca] Subsystem: Lenovo TU117M [GeForce MX450] [17aa:22ca] InstallationDate: Installed on 2022-01-02 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: LENOVO 20W0005VCD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=b4c00f4f-589b-42e2-b402-7ea8b75191a7 ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2022-11-12 (118 days ago) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET54W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005VCD dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET54W(1.54):bd11/21/2022:br1.54:efr1.42:svnLENOVO:pn20W0005VCD:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005VCD:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005VCD dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 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/gnome-shell-extension-desktop-icons-ng/+bug/2011279/+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 2011270] Re: Printing intermittenly fails -- autodetected network printer
** 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/2011270 Title: Printing intermittenly fails -- autodetected network printer Status in Ubuntu: New Bug description: It appears that print jobs passed to the auto-detected printer "adding" wizard do not always succeed. See in these error messages how hpcups is passed a null object to print. It's unclear what the interactions is between the auto-discovery gnome(?) applet, the hpcups system, and dbus. The net effect is that a print job is sent to the printer defined here, and it just gets stuck in "stopped". With no error message or way for the user to resolve the issue. I'm not sure where to begin debugging ... Error messages in question : Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:44:25 semiauto google-chrome.desktop[496973]: Warning: disabling flag --expose_wasm due to conflicting flags Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 79: unable to open /var/lib/hp/hplip.state: No such file or directory Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 129: validate_plugin_version() Failed to get Plugin version from [/var/lib/hp/hplip.state] Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 173: Plugin version is not matching Mar 10 16:44:34 semiauto hpcups[515382]: prnt/hpcups/HPCupsFilter.cpp 505: m_Job initialization failed with error = 48 Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 244: Invalid Library handler pLibHandler = NULL. Mar 10 16:45:01 semiauto CRON[515541]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 10 16:45:09 semiauto gnome-shell[333439]: Window manager warning: Ping serial 447743079 was reused for window W713, previous use was for window 0xc00014. Mar 10 16:45:20 semiauto systemd[4596]: vte-spawn-4d0c2df5-8c91-461c-ac5d-b95a2bc252a9.scope: Consumed 33.860s CPU time. Mar 10 16:45:20 semiauto gnome-shell[333439]: JS ERROR: TypeError: this.actor is null#012_syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:138:25#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:150:35#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:316:60#012_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1596:21#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:1564:39#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActor/<@resource:///org/gnome/shell/ui/environment.js:239:64 Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:45:23 semiauto systemd[4596]: app-gnome-virtualbox-495654.scope: Consumed 11min 33.878s CPU time. Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Settings.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Characters' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Notes.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Successfully activated service 'org.gnome.Settings.SearchProvider' Make and model auto-reported is: "HP LaserJet Professional m1217nfw MFP, hpcups 3.22.6, requires proprietary plugin" yes, it has commas. URI is reported as: dnssd://HP%20LaserJet%20Professional%20M1217nfw%20MFP._pdl-datastream._tcp.local/ and "location" is aparrently blank. I can troubleshoot further. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg
[Touch-packages] [Bug 2010924] Re: MT7921K --> BLE funktion don't working
Thanks for the bug report. This is a kernel bug, but your kernel "6.2.0-76060200-generic" is not an officially supported one. Can you check to see if the same bug exists in a supported Ubuntu kernel? ** Package changed: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/2010924 Title: MT7921K --> BLE funktion don't working Status in linux package in Ubuntu: Incomplete Bug description: Hi, i have MT7921K BT chip that BLE function is not working with linux, but normal BT is working. I try several distros and some live-iso and get same effect. BLE just not working with this device. I have other BT adapters and BLE is working for them. This is a probe for my PC: https://linux-hardware.org/?probe=969ab4279f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2010924/+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 2004241] Re: Update to glib >= 2.75.1
** Changed in: glib2.0 (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 Status in glib2.0 package in Ubuntu: Fix Committed Bug description: Update to glib >= 2.75.1 because that's what mutter 44 now requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+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 2004241] Re: Update to glib >= 2.75.1
** Changed in: glib2.0 (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 Status in glib2.0 package in Ubuntu: Fix Committed Bug description: Update to glib >= 2.75.1 because that's what mutter 44 now requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+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 2009785] Re: [RTL8821CE] WLAN functionality cannot be controlled any more
Thanks for the bug report. If the built-in driver 'rtw88_8821ce' isn't working then please try the add-on driver: sudo apt update sudo apt full-upgrade sudo apt install rtl8821ce-dkms and then reboot. ** Summary changed: - WLAN functionality cannot be controlled any more + [RTL8821CE] WLAN functionality cannot be controlled any more ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (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/2009785 Title: [RTL8821CE] WLAN functionality cannot be controlled any more Status in linux-hwe-5.19 package in Ubuntu: New Bug description: After the latest upgrade and a reboot, the WLAN connectivity features have disappeared from the menu on the upper right hand side menu, and the system does not connect to the local WLAN at my home; in short: WLAN DOES NOT WORK ANY MORE (Luckily, Ethernet connectivity is still available so I can send this using USB tethering.) New, however is Bluetooth connectivity control. Turning this off, turns on airplane mode; turning airplane mode off returns the Bluetooth control menu entry. $ lspci -nnk -d::0280 02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] DeviceName: WLAN Subsystem: Hewlett-Packard Company RTL8821CE 802.11ac PCIe Wireless Network Adapter [103c:831a] Kernel modules: rtw88_8821ce THIS DOES NOT REPORT A KERNEL DRIVER IN USE. Thank you Wolfgang ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 9 05:12:28 2023 DistUpgraded: 2022-11-14 12:08:39,894 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-67-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:86c1] InstallationDate: Installed on 2020-12-19 (809 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP 250 G7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=ac8de2b3-079a-406a-af37-4891044b3642 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-11-14 (114 days ago) dmi.bios.date: 07/31/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86C1 dmi.board.vendor: HP dmi.board.version: 89.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 89.35 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/31/2020:br15.33:efr89.35:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn86C1:rvr89.35:cvnHP:ct10:cvrChassisVersion:sku1B7K9ES#ABD: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 1B7K9ES#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009785/+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 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
Interesting because the upstream bug has different fixes proposed at the moment... https://gitlab.gnome.org/GNOME/gtk/-/issues/326 https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4945 https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4960 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #326 https://gitlab.gnome.org/GNOME/gtk/-/issues/326 -- 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/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Status in gtk4 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+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 2004241] Re: Update to glib >= 2.75.1
It's still trivial to patch mutter to not need this, so low priority. ** Changed in: glib2.0 (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 Status in glib2.0 package in Ubuntu: Triaged Bug description: Update to glib >= 2.75.1 because that's what mutter 44 now requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+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 2009435] Re: Xorg freeze
** Package changed: xorg (Ubuntu) => nautilus (Ubuntu) ** Summary changed: - Xorg freeze + Nautilus freeze -- 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/2009435 Title: Nautilus freeze Status in nautilus package in Ubuntu: New Bug description: Files application hangs when switched to from other application. Only occurs when mounted to internal HDD. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 6 08:50:17 2023 DistUpgraded: 2022-09-30 11:53:10,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-67-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Lexa PRO [Radeon RX 550] [1da2:e367] InstallationDate: Installed on 2020-10-24 (862 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=9db35888-ce9e-4ddd-96ab-979cf2de8c9e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-09-30 (156 days ago) dmi.bios.date: 11/13/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-K:rvrRevX.0x: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: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2009435/+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 2009564] Re: Touchpad disabling while typing does not work
I assume you mean: org.gnome.desktop.peripherals.touchpad disable-while-typing true Does it work any better if you log into Ubuntu on Xorg instead? ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: libinput (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/2009564 Title: Touchpad disabling while typing does not work Status in libinput package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: It makes my laptop much less usable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-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 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 7 00:44:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: backport-iwlwifi/9858, 5.19.0-32-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) backport-iwlwifi/9858, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/525.85.05, 5.15.0-56-generic, x86_64: installed nvidia/525.85.05, 5.19.0-32-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:201f] NVIDIA Corporation Device [10de:24e0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:201f] InstallationDate: Installed on 2023-01-03 (62 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Razer x Lambda TensorBook (2022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=4cd4fe61-a6ef-48c5-acc8-b96e7da91171 ro button.lid_init_state=open i915.enable_fbc=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2022 dmi.bios.release: 1.0 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: CH580 dmi.board.vendor: Razer x Lambda dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer x Lambda dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnRazer:bvr1.00:bd07/29/2022:br1.0:efr1.0:svnRazerxLambda:pnTensorBook(2022):pvr8.04:rvnRazerxLambda:rnCH580:rvr4:cvnRazerxLambda:ct10:cvr:skuRZ09-0421NEL9: dmi.product.family: 1A58201F Razer x Lambda TensorBook dmi.product.name: TensorBook (2022) dmi.product.sku: RZ09-0421NEL9 dmi.product.version: 8.04 dmi.sys.vendor: Razer x Lambda version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
[Touch-packages] [Bug 2009293] Re: Amd Radeon
Thanks for the bug report. The attached files show the 'oibaf' PPA is in use (has replaced Ubuntu's official graphics packages) which is not supported by Ubuntu and is known to cause bugs. Please remove the 'oibaf' PPA from the machine and if that does not fix the issue then open a new bug showing the problem in Davinci Resolve. ** 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/2009293 Title: Amd Radeon Status in Ubuntu: Invalid Bug description: Não consigo faze com que minha placa amd radeon seja reconhecida pelo Ubuntu. Com isso o Davinci Resolve não funciona ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 5 11:13:12 2023 DistUpgraded: 2022-11-06 19:24:12,783 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:390c] InstallationDate: Installed on 2022-10-30 (126 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: LENOVO 80R0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=9d78ad90-d581-4749-a2d1-eb27cd7319ee ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-11-06 (118 days ago) dmi.bios.date: 07/31/2015 dmi.bios.release: 1.95 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN95WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.ec.firmware.release: 1.95 dmi.modalias: dmi:bvnLENOVO:bvrB0CN95WW:bd07/31/2015:br1.95:efr1.95:svnLENOVO:pn80R0:pvrLenovoG50-80:rvnLENOVO:rnLancer5A1:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoG50-80:skuLENOVO_MT_80R0_BU_idea_FM_LenovoG50-80: dmi.product.family: IDEAPAD dmi.product.name: 80R0 dmi.product.sku: LENOVO_MT_80R0_BU_idea_FM_Lenovo G50-80 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115+git2302220500.332809~oibaf~j version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2009293/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Changed in: mesa (Ubuntu Lunar) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Tags added: fixed-in-mesa-24 fixed-upstream ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux (Ubuntu Kinetic) ** No longer affects: linux (Ubuntu Lunar) ** No longer affects: mutter (Ubuntu) ** No longer affects: mutter (Ubuntu Jammy) ** No longer affects: mutter (Ubuntu Kinetic) ** No longer affects: mutter (Ubuntu Lunar) ** Changed in: mesa (Ubuntu Lunar) Status: Confirmed => In Progress -- 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/1990089 Title: Screen freeze when performing memory stress in Wayland mode Status in Linux: New Status in Mutter: Fix Released Status in OEM Priority Project: Incomplete Status in mesa package in Ubuntu: In Progress Status in mesa source package in Jammy: Confirmed Status in mesa source package in Kinetic: Confirmed Status in mesa source package in Lunar: In Progress Bug description: [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #20 0x7fcae0743c24 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fcae0743293 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fcadf8d0849 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #24 0x55773f1a4f12 in ?? () #25 0x7fcadf429d90 in __libc_start_call_main (main=main@entry=0x55773f1a4a70, argc=argc@entry=1, argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70, argc=1, argv=0x7fffc54053e8, init=, fini=, rtld_fini=, stack_end=0x7fffc54053d8)
[Touch-packages] [Bug 2009069] Re: Open applications showing behind desktop icons when logging in after inactivity or after logout
Do you have anything in ~/.local/share/gnome-shell/extensions/ ? ** Package changed: xorg (Ubuntu) => gnome-shell-extension-desktop- icons-ng (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/2009069 Title: Open applications showing behind desktop icons when logging in after inactivity or after logout Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: At first login after boot everything is normal. But when logging out/suspending and logging back in, the last open windows are shown behind the desktop symbols. However I can not interact with the windows. If I use Alt+Tab or click on the window in the Dock then it is normal again. After login, I would expect the windows to be either minimized and only see the desktop or only see the windows without icons in front of them. AskUbuntu question: https://askubuntu.com/q/1444241/768152 Example image: https://i.stack.imgur.com/RV3Go.png Description: Ubuntu 22.04.2 LTS Release: 22.04 xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome: Installed: (none) Candidate: 1:42+3 Version table: 1:42+3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 2 19:11:36 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: XFX Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1eae:6505] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1636] InstallationDate: Installed on 2022-04-24 (312 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=dbd1ea14-b055-4884-bf22-d9205098ff35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MPG B550 GAMING PLUS (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.90:bd03/17/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGB550GAMINGPLUS(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2009069/+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 2008797] Re: Mouse problems
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Mouse problems + USB mouse doesn't work after resuming from sleep ** Tags added: suspend-resume -- 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/2008797 Title: USB mouse doesn't work after resuming from sleep Status in linux package in Ubuntu: New Bug description: Basic problem is that the usb mouse connects at the start, but after sleep, suddenly stops. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.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 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 20:56:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GA107M [GeForce RTX 3050 Mobile] [103c:88ec] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:88ec] InstallationDate: Installed on 2023-02-28 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: HP Victus by HP Laptop 16-e0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=42da8321-31cc-4d70-aeb1-d0e0f86cc2f9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2021 dmi.bios.release: 15.4 dmi.bios.vendor: AMI dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88EC dmi.board.vendor: HP dmi.board.version: 80.22 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 80.22 dmi.modalias: dmi:bvnAMI:bvrF.04:bd06/17/2021:br15.4:efr80.22:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EC:rvr80.22:cvnHP:ct10:cvrChassisVersion:sku494P3PA#ACJ: dmi.product.family: 103C_5335M7 HP VICTUS dmi.product.name: Victus by HP Laptop 16-e0xxx dmi.product.sku: 494P3PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 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/2008797/+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 2008733] Re: Window leak-through
Thanks for the bug report. Unfortunately your graphics packages are not from Ubuntu, they are from System76. So the bug should probably be reported to them. Although I would still be curious to see a photo or video of the issue. ** 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/2008733 Title: Window leak-through Status in Ubuntu: Invalid Bug description: I notice that since upgrading to Ubuntu 22.04 LTS I am getting a lot of leak-through with open windows. That is when I move the mouse over a window it brings up an informational popup from a window obscured by the active window. Additionally, the active edges of the windows seem to have large boundaries around the active window. That is if I click on a window showing on the screen, but the edge is close to the active window, it will not activate the window on which I clicked. There was a little of the behavior in 20.04 when the windows edges were close, but it is extreme in 22.04 in that even with a 15 to 20 mm of the underlying window showing it will not recognize that I have selected a different active window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.0.12-76060006-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 27 12:31:43 2023 DistUpgraded: 2022-12-01 16:49:16,796 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Gazelle ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.12-76060006-generic root=UUID=ac9c0a24-9264-4620-9dca-59a3e7976588 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-12-02 (87 days ago) dmi.bios.date: 09/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02RSA2-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle dmi.board.vendor: System76, Inc. dmi.board.version: gaze11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02RSA2-1:bd09/09/2016:br5.11:svnSystem76,Inc.:pnGazelle:pvrgaze11:rvnSystem76,Inc.:rnGazelle:rvrgaze11:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Gazelle dmi.product.sku: Not Applicable dmi.product.version: gaze11 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-10-20T08:48:37.54 version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1pop0~1648761328~22.04~166056a~dev version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.4-1pop1~1675300365~22.04~6b66c01~dev version.libgl1-mesa-glx: libgl1-mesa-glx 22.3.4-1pop1~1675300365~22.04~6b66c01~dev version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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 xserver.bootTime: Sat Jan 19 19:22:02 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1191 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2008733/+subscriptions -- Mailing list:
[Touch-packages] [Bug 2008541] Re: very high power draw from battery when watching videos
What player/app are you using? Please also try 'mpv'. ** 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/2008541 Title: very high power draw from battery when watching videos Status in Ubuntu: Incomplete Bug description: when I watch a video in fullscreen, my laptop can draw as many as 25w. For comparaison, on windows 11, a similar video will take only 8w from the battery. obviously, the cpu temps and fan speed are much higher on ubuntu tan on windows. Also, this might be unrelated, but when I plug in or unplug the charger on my laptop, the power draw reported takes time to climb up to the actual power draw/ charge rate ( up to 45 sec). In this vase, my laptop can think that it still has a couple of days left worth of battery life left ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 25 00:52:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.2.0, 5.15.0-60-generic, x86_64: installed openrazer-driver/3.2.0, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev d1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-12-03 (84 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CH000GUS ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=32b06683-a98d-4585-81c7-edb51198f58c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CH000GUS dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.24:svnLENOVO:pn21CH000GUS:pvrThinkPadT16Gen1:rvnLENOVO:rn21CH000GUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CH_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21CH000GUS dmi.product.sku: LENOVO_MT_21CH_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 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 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2008541/+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 1977748] Re: Build Cairo with OpenGL support
I'm going to say no to this because: * Well-written code doesn't need Cairo to use GL to get the best performance. Just don't re-render Cairo parts on important code paths. * Even if there were no known bugs in the GL backend, it would still pose an unnecessary risk to the stability of mature components like GTK and GNOME Shell. Probably more. * You can already build Cairo with OpenGL yourself and use that custom build in your project. ** Changed in: cairo (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 cairo in Ubuntu. https://bugs.launchpad.net/bugs/1977748 Title: Build Cairo with OpenGL support Status in cairo package in Ubuntu: Won't Fix Bug description: Instructed by "ask a question" I tried to file a wayland-targeted bug, but apport-bug thinks I'm running Xorg. See https://answers.launchpad.net/ubuntu/+question/702075 PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy $ ps -ef | grep Xwayland xx 24931685 0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 -initfd 7 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 06:40:48 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes 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:0991] InstallationDate: Installed on 2021-10-02 (246 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2022 dmi.bios.release: 3.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.6.0 dmi.board.name: 0MK6WC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1977748/+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 1977748] Re: Build Cairo with OpenGL support
I remember talking to the GNOME developers about this, I think it was in person at a conference last year. From what I recall, they said the OpenGL backend had issues so there was good reason to leave it disabled. I don't know if it's the same reason as in comment #5, but it probably doesn't matter because: * Apps using Cairo efficiently that keep the Cairo results in an OpenGL texture most of the time already work just fine. It's only the render and upload (glTexImage2D) stages that would be slower with the current CPU rendering but a well-written app will never bottleneck on that. Examples: GTK and GNOME Shell. * If you really need the OpenGL backend for some reason then you can build Cairo within your project and embed it: ./configure --enable-gl=yes --enable-static=yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1977748 Title: Build Cairo with OpenGL support Status in cairo package in Ubuntu: Triaged Bug description: Instructed by "ask a question" I tried to file a wayland-targeted bug, but apport-bug thinks I'm running Xorg. See https://answers.launchpad.net/ubuntu/+question/702075 PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy $ ps -ef | grep Xwayland xx 24931685 0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 -initfd 7 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 06:40:48 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes 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:0991] InstallationDate: Installed on 2021-10-02 (246 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2022 dmi.bios.release: 3.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.6.0 dmi.board.name: 0MK6WC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1977748/+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 2008149] Re: Bluetooth Audio Broken After Suspend
** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags added: kinetic ** Tags added: a2dp suspend-resume -- 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/2008149 Title: Bluetooth Audio Broken After Suspend Status in bluez package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: Release: Description: Ubuntu 22.10 Release: 22.10 Package Version: isa~ apt-cache policy bluez bluez: Installed: 5.65-0ubuntu1 Candidate: 5.65-0ubuntu1 Version table: *** 5.65-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status Hardware: = Model: Apple Inc. MacBookPro9,2 isa~ lsusb | grep -i blue Bus 002 Device 009: ID 05ac:821d Apple, Inc. Bluetooth USB Host Controller Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Kmods: == bluetooth 827392 54 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm Symptom: Pausing sound output (with bluetooth device as sink) will often lead to a failed suspend / resume that leaves audio in an unusable state. Logs indicate that suspend fails, but it looks like the failure path is broken in some way that renders audio unusable when this occurs. This requires a reconnect to recover in all cases, and occasionally even a reboot is required. I have attached debug logs from `bluetooth.service`. I assume hci logs are not required in this case, but if they are please let me know. I can test proposed fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2008149/+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 2008053] Re: Screen corruption and laggy mouse cursor in lower quarter of screen
*** This bug is a duplicate of bug 2007668 *** https://bugs.launchpad.net/bugs/2007668 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 2007668, 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) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 2007668 Intel 12th gen: Noisy screen corruption during some cursor movement in 5.19 kernels -- 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/2008053 Title: Screen corruption and laggy mouse cursor in lower quarter of screen Status in linux package in Ubuntu: New Bug description: After a software upgrade yesterday, I see screen glitches and a "stumbling" mouse cursor whenever I move the mouse in the lower quarter of my laptop screen. When I have connected an external display, the external display doesn't show any issues, but the problem remains on the laptop screen. (This is my first bug report and I used the "ubuntu-bug" utility to collect the necessary data. I hope it is attached here somewhere.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 08:58:07 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b04] InstallationDate: Installed on 2022-11-30 (83 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Latitude 5430 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 04X33N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd09/05/2022:br1.6:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn04X33N:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 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 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008053/+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 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: 1. Settings > Colour > turn off the toggle switch for your monitor. 2. Restart any affected apps. Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+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 1803840] Re: color calibration with huey pro greenish
*** This bug is a duplicate of bug 938751 *** https://bugs.launchpad.net/bugs/938751 ** This bug has been marked a duplicate of bug 938751 Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1803840 Title: color calibration with huey pro greenish Status in colord package in Ubuntu: Confirmed Bug description: First of all: Congratulations, after an absence due to bad configurability of my rig I came back to ubuntu and was very positively surprisedthere is one thing that bothers me: after using the calibration feature for my screens this leads to greenish displays, even a icc profile made with the same hardware under windows10 (where configurability decreased since my update to v10) makes the same effect used with ubuntu 16.04...am I not aware of some more setting or is this a bug? Please let me know what more information you need from me besides I am using a hp envy dv6 and a wacom cintiq 13 hd, the nvidia graphics card is turned off for displays, I am using it just for Blenders Cycles renderer. I am a left-handed CG enthusiast who needs the wacom buttons on the right-hand side... Thank you, Michael ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 17 23:43:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed nvidia, 390.77, 4.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:181b] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GF108M [GeForce GT 635M] [103c:181b] InstallationDate: Installed on 2018-11-11 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ENVY dv6 Notebook PC ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=befbe944-5e8a-4bfc-b541-c8ad84809dde ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181B dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv6NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn181B:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY dv6 Notebook PC dmi.product.version: 088A1230591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1803840/+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 2007830] Re: Display issue after boot - secondary screen not working since last kernel upgrade
Thanks for the bug report. It looks like Nvidia is your primary GPU and that driver is working fine. If you have any monitors not working then they might be connected to the Intel GPU. Your Intel graphics driver is reporting some unusual kernel errors I've never seen before but they sound related. It also looks like your BIOS has hidden/disabled the Intel GPU completely. So this is really only a bug if the secondary monitor is connected to the Nvidia GPU. Please run these commands: grep . /sys/class/drm/*/status > drmconn.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: i915 multigpu nvidia -- 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/2007830 Title: Display issue after boot - secondary screen not working since last kernel upgrade Status in Ubuntu: Incomplete Bug description: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.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 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 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/2007830/+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 2007791] Re: The screen goes dim
If you also see an 'Automatic Screen Brightness' option in the same settings panel then please disable that. ** Package changed: xorg (Ubuntu) => gnome-control-center (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/2007791 Title: The screen goes dim Status in gnome-control-center package in Ubuntu: New Bug description: The screen goes dim after 30 seconds of inactivity even after I've unchecked a switch in the Settings > Power > Power saving options > Dim screen. Basically, the system doesn't care about this switch and it's really annoying while I'm trying to read the article or something. Fix it please, I would really appreciate this. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.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 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 00:54:03 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TigerLake-H GT1 [UHD Graphics] [103c:88f9] NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GA107M [GeForce RTX 3050 Mobile] [103c:88f9] InstallationDate: Installed on 2023-02-13 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP Victus by HP Laptop 16-d0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=723d55ac-fbea-47b1-828f-4de6bed57aaa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2022 dmi.bios.release: 15.21 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88F9 dmi.board.vendor: HP dmi.board.version: 88.56 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 88.56 dmi.modalias: dmi:bvnAMI:bvrF.21:bd10/27/2022:br15.21:efr88.56:svnHP:pnVictusbyHPLaptop16-d0xxx:pvr:rvnHP:rn88F9:rvr88.56:cvnHP:ct10:cvrChassisVersion:sku4Y0Z9EA#AKD: dmi.product.family: 103C_5335M7 HP Victus dmi.product.name: Victus by HP Laptop 16-d0xxx dmi.product.sku: 4Y0Z9EA#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 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/gnome-control-center/+bug/2007791/+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 2007747] Re: dist-upgrade package yaru-theme-gnome-shell could not installed
*** This bug is a duplicate of bug 1971058 *** https://bugs.launchpad.net/bugs/1971058 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 1971058, 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) => yaru-theme (Ubuntu) ** This bug has been marked a duplicate of bug 1971058 package yaru-theme-gnome-shell ... failed to install/upgrade: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit status 1 -- 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/2007747 Title: dist-upgrade package yaru-theme-gnome-shell could not installed Status in yaru-theme package in Ubuntu: New Bug description: Sorry for my bad english, I am a german ;-) Yesterday I do a dist-upgrade from 20.04. LTS to 22.04 LTS. I do it with the gui "update management" or "Aktualisierungsverwaltung" in german During the process the following problems ocur: 1. During "package installation" a MessageBox pops up, with the following msg: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit status 1 2. During step "installing firefox snap" there is a second window over the normal one (snap install) that "hangs" After a while (~2min) I am able to abort this one (geting process hangs are You like to kill it) Problem 1, More details: After the upgrade, the system boots right into the logon screen, but I am unable to log in. When I click mei User and enter my passwd, the screen flickers and I get a message: Oh, no, something went wrong logout and try again I do this 3-5 times but always with the same result. Now i switch to a console (Ctrl-Alt-F2) Try to install the package manually sudo apt install yaru-theme-gnome-shell reports a "not owned" file in /usr/share/themes/Yaru-dark/gnome-shell I lock into this folder and found a file "gnome-shell.css.save". After I removed this installation worked and I am able to log into the GUI. That seems to fix problem 1, but not fully. When I try to login imediatly after the system has booted I got the same error as mentioned above. Only when I wait a bit (~20sec) login is possible. I belive that is some kind of timing problem Problem 2, More details: when I start firefox I got a "garbed" window, so it seams that firefox wasn't correctly installed. I will try to reinstall it later and report the result (That's not so importent for me, because I don't use firefox often, I use chrom). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 13:22:22 2023 DistUpgraded: 2023-02-17 17:22:37,443 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: r8125/9.004.01, 5.13.0-37-generic, x86_64: built r8125/9.004.01, 5.15.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) r8125/9.004.01, 5.15.0-60-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1da2:427e] InstallationDate: Installed on 2020-12-30 (780 days ago) InstallationMedia: MachineType: Gigabyte Technology Co., Ltd. B550 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=81474076-e235-45df-bf87-42ed2fb4c6a1 ro noplymouth resume=UUID=81474076-e235-45df-bf87-42ed2fb4c6a1 resume_offset=83408896 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-02-17 (0 days ago) dmi.bios.date: 12/18/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11p dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3
[Touch-packages] [Bug 2007668] Re: glitch on screen
I experience the same bug on Intel 12th gen. Please try adding kernel parameter: i915.enable_psr=0 which has fixed it for me on a different laptop. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - glitch on screen + Noisy screen corruption during some cursor movement -- 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/2007668 Title: Noisy screen corruption during some cursor movement Status in linux package in Ubuntu: Incomplete Bug description: This always happens when the cursor sweeps over a height range (approximately 960px ~ 990px from the top). Even when watching a video, the top of the screen sometimes glitches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 16:24:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b14] InstallationDate: Installed on 2022-08-13 (187 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=3ba28059-7aea-46a5-bf4e-44dd0203b83d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 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 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007668/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
** Tags added: a11y -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1689448] Re: bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch
Reopened. It's still crashing in current releases. ** Changed in: bluez (Ubuntu) Status: Fix Released => Confirmed ** Tags removed: wily yakkety zesty ** Tags added: jammy kinetic -- 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/1689448 Title: bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74228037aee5c1e95c18d26533f63d5396d48e3e 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689448/+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 1689460] Re: bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb
Reopened because we're still getting this crash on lunar. Just not very often. ** Tags added: lunar ** Changed in: bluez (Ubuntu) Status: Fix Released => Confirmed ** Tags removed: artful wily yakkety zesty ** Tags added: focal jammy kinetic -- 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/1689460 Title: bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b07fc39aa06a535581fad194d445c76f189364c1 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689460/+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 2007604] Re: Error al intentar abrir archivos en Visual Studio Code
Sorry, Visual Studio Code is not supported here. You will need to report the bug to Microsoft at: https://github.com/microsoft/vscode/issues ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2007604 Title: Error al intentar abrir archivos en Visual Studio Code Status in Ubuntu: Invalid Bug description: Buenas tardes, intento abrir un archivo desde Visual Studio Code, pero no me permite acceder a la pestaña de "Abrir archivo", tambien se congela el programa en cuestion hasta que quito la pestaña "Abrir archivo". Saludos ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 16:17:04 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-09-26 (143 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=dad03207-69a0-4d8a-9bdf-3ee6427bd77f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A85XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/31/2013:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A85XM-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2007604/+subscriptions -- Mailing list: https://launchpad.net/~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 2007580] Re: Extneral monitors stop working after screen lock
Thanks for the bug report. Next time the bug occurs, please use the workaround to recover and then run: journalctl -b0 > journal.txt And attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2007580 Title: Extneral monitors stop working after screen lock Status in Ubuntu: Incomplete Bug description: External monitors connected to dock WD19TB. It took me some time to get the external monitor to work with my dock after install of 22. After installing displaylink drivers and using wayland things seemed to go smoothly. When locking the desktop I am often forced to switch tty then back to get monitors to work. This morning this workaround does not seem to be doing the trick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX Open Kernel Module for x86_64 525.78.01 Release Build (dvs-builder@U16-J11-10-2) Mon Dec 26 05:50:21 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 16 09:11:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.12.0, 5.15.0-60-generic, x86_64: installed evdi/1.12.0, 5.19.0-32-generic, x86_64: installed nvidia/525.78.01, 5.15.0-60-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/525.78.01, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0] InstallationDate: Installed on 2023-02-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20TJS2BA00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=69d7fb7b-23e3-4a4c-8566-7df3bbb927be ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET42W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TJS2BA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrN2VET42W(1.27):bd01/03/2023:br1.27:efr1.11:svnLENOVO:pn20TJS2BA00:pvrThinkPadP1Gen3:rvnLENOVO:rn20TJS2BA00:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TJ_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TJS2BA00 dmi.product.sku: LENOVO_MT_20TJ_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: A query to find an object was unsuccessful version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Also be careful to not get confused with bug 1878076. -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
A draft fix for GTK4 is here: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4945 ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk4 (Ubuntu) Status: New => Triaged ** Changed in: gtk4 (Ubuntu) Importance: Undecided => Low -- 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/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Status in gtk4 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Sounds like you mean https://gitlab.gnome.org/GNOME/gtk/-/issues/4880 .. If that does fix this issue then it will be in GTK 4.7.2/4.8.0 and later, which is already in Ubuntu 22.10 and later. But that requires apps to use GTK4 instead of GTK3 in order to get the fix. So no there is no definite plan for this bug, but Ubuntu 22.04 is supported for another 9 years so never say never. ** Changed in: gtk4 (Ubuntu Kinetic) Status: Triaged => Fix Released -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4880 https://gitlab.gnome.org/GNOME/gtk/-/issues/4880 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/4880 Importance: Unknown Status: Unknown -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in GTK+: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q
While 22.04 isn't fixed yet, please try editing /etc/environment and add: MESA_LOADER_DRIVER_OVERRIDE=i965 then reboot. It might be a suitable workaround. ** Changed in: mesa (Ubuntu Jammy) Importance: Undecided => High -- 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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Triaged Bug description: [Impact] Gnome-shell is crashing on older gen Intel hw due to a memory leak. [Fix] An upstream commit that fixes the memleak in the crocus driver (which is only used on Intel 4th gen chips and older) [Test case] Either test this on an old Intel or see if there's a dent in the reported crashes. [Where things could go wrong] Mainly if this would not fix the crashes. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 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/mesa/+bug/1972977/+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 2007381] Re: Xorg freeze
Thanks for the bug report. Please check for crashes by following these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment But judging by the model of CPU and the version of Ubuntu, I think you're most likely to be experiencing bug 1972977. P.S. Your changes in 20-intel.conf are not usually recommended because Driver "intel" is deprecated and causes serious issues on newer Intel systems. On this machine however, it's probably fine and might even be a workaround to bug 1972977. ** 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/2007381 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and flashing cursor in top corner then stopped and started again with log in screen. As duel boot started laptop in Windows 10 and no problems so software problem. Reseached and found a fix which was putting in file, 1 - Creating a file "/etc/X11/xorg.conf.d/20-intel.conf" Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection This seems to have fixed the problem. I was running System Profile to watch Temps and also Mate System monitor with Firefox in the background. It did for a moment give a black screen but recovered so not sure if this was the problem resurfacing. Without this being a duel boot I would have had great difficulty identifying if it was software or a overheating/grapics card problem. Most users would scrap their hardware if they were presented with this problem. Hopefully my problem is fixed but if not could you please advise me further. All the Best DAvid ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: MATE Date: Wed Feb 15 12:00:06 2023 DistUpgraded: 2022-08-17 16:23:45,139 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 5.15.0-58-generic, x86_64: installed bcmwl/6.30.223.271+bdcom, 5.15.0-60-generic, x86_64: installed rtl8821ce/5.5.2.1, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [1179:ff50] Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1179:ff50] InstallationDate: Installed on 2021-08-21 (542 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: TOSHIBA Satellite M300 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=98dc102b-f3cc-4067-b9a3-75250f24163c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-08-17 (181 days ago) dmi.bios.date: 03/13/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.80 dmi.board.name: Satellite M300 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.80:bd03/13/2008:svnTOSHIBA:pnSatelliteM300:pvrPSMD0L-01N00M:rvnTOSHIBA:rnSatelliteM300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:sku: dmi.product.name: Satellite M300 dmi.product.version: PSMD0L-01N00M dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
This probably would hide all such shutdown crashes though:
https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/63
--
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/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mozjs102 package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
It's not fixed in lunar either. We're now seeing reports:
https://errors.ubuntu.com/?release=Ubuntu%2023.04=gnome-
shell=week
** Tags added: lunar
--
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/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mozjs102 package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 2007217] Re: error from xdiagnose application
I'm not seeing any problems in the attached files. If the main issue is not with Ubuntu but with Skype then please report that to Skype/Microsoft. ** 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/2007217 Title: error from xdiagnose application Status in Ubuntu: Incomplete Bug description: i have some problem run the skype application so i run the xdiagnose application and show this errors so i don't know what mean thanks in advance ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-202.213-generic 4.15.18 Uname: Linux 4.15.0-202-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Feb 14 08:14:11 2023 DistUpgraded: 2023-01-07 20:49:41,429 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1179:fdc0] Subsystem: Toshiba America Info Systems Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [1179:fdc0] InstallationDate: Installed on 2022-12-15 (60 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: TOSHIBA TOSHIBA NB500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-202-generic root=UUID=4e71438a-25ca-4b55-96a3-d60c7e8b980d ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2023-01-07 (37 days ago) dmi.bios.date: 12/21/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.40 dmi.board.name: PBU00 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.40:bd12/21/2010:svnTOSHIBA:pnTOSHIBANB500:pvrPLL50H-00401X:rvnTOSHIBA:rnPBU00:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB500 dmi.product.version: PLL50H-00401X dmi.sys.vendor: TOSHIBA 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.13 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: Sat Jan 7 18:33:56 2023 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 661 vendor LGD xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2007217/+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 2007268] Re: Wayland/Gnome doesn't DPMS screens on idle/screensaver wasting energy and burning LEDs
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 2003237, 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: wayland (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 2003237 Monitor does not turn off after idle timeout is reached -- 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/2007268 Title: Wayland/Gnome doesn't DPMS screens on idle/screensaver wasting energy and burning LEDs Status in mutter package in Ubuntu: New Bug description: In the 2022/2023 energy crisis era, this shall not happen. But... I haven't found solution other than "switch to X", which is not an options with my scaling settings for both 4K screens I'm using. On idle when the system blanks screen backlight remains on, wasting energy and burning LEDs in my screens. Please provide solution that would let Gnome set DPMS properly and actually send screens to proper sleep when OS goes idle (enables screen saver). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwayland-bin 1.20.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 14 11:59:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-58-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-60-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev d1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2023-01-04 (40 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zrhf1w@/vmlinuz-5.15.0-58-generic root=ZFS=rpool/ROOT/ubuntu_zrhf1w ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 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 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007268/+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 2006955] Re: Screens not detected anymore
Thanks for the bug report. Please try reinstalling this package: https://launchpad.net/ubuntu/+archive/primary/+files/linux-modules- extra-5.15.0-60-generic_5.15.0-60.66_amd64.deb and then reboot. If the problem persists after that then please run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Tags added: amdgpu ** Summary changed: - Screens not detected anymore + [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) ** 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/2006955 Title: [amdgpu] Screens not detected anymore in 5.15.0-60-generic (but 5.15.0-58-generic works) Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
It doesn't really help. I was just searching the code for an explanation
of the message.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in cairo package in Ubuntu:
Triaged
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
And I just realized the message "invalid value (typically too big)" is
from the Cairo library. It's the description for
CAIRO_STATUS_INVALID_SIZE.
** Also affects: cairo (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cairo (Ubuntu)
Status: New => Triaged
** Changed in: cairo (Ubuntu)
Importance: Undecided => Medium
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in cairo package in Ubuntu:
Triaged
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
Although this suggests the bug was in 20.04 as well:
https://gitlab.gnome.org/GNOME/gtk/-/issues/3050
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
GTK4 is already in Ubuntu and the GNOME developers are planning GTK5.
The bigger issue here is that apps haven't moved away from GTK3 yet. For
you that includes Desktop Icons NG, Firefox and Thunderbird.
If 22.04 worked then yes please do go back to that. It's also supported for
much longer:
https://wiki.ubuntu.com/Releases
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2006636] Re: Many Cyan Lines Cover Computer Screen
Thanks for the bug report. Please try adding a kernel parameter: i915.enable_psr=0 Please also attach a photo of the problem. ** Summary changed: - Many Cyan Lines Cover Computer Screen + [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen ** 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/2006636 Title: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen Status in linux package in Ubuntu: Incomplete Bug description: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 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 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006636/+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 2006590] Re: Xorg freeze after rebooting
Thanks for the bug report. Your system is stuck in recovery mode so you will need to access the grub menu (tap escape before Ubuntu starts just after the BIOS) and select the regular kernel to fix it. When done, your /proc/cmdline should not mention either "nomodeset" or "recovery". ** 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/2006590 Title: Xorg freeze after rebooting Status in Ubuntu: Incomplete Bug description: Suddenly this week, my GUI (ubuntu 22.10) does not open, stuck on the console text. I tried to free some space (by uninstall a app), then to check/update the paquets (dkpg). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-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 515.86.01 Wed Oct 26 09:12:38 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Feb 8 12:13:40 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2022-05-03 (280 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.4 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/2006590/+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 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few
Mir actually uses Wayland these days :) Also this bug is probably either still valid or might have been fixed. I don't have the time or interest to figure out which so "Won't Fix" is fine, unless RAOF wants to investigate. ** Changed in: mir Status: Fix Released => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1211700 Title: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few frames Status in Mir: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in mir package in Ubuntu: Won't Fix Bug description: GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and freedreno) cause the Mir server to slow, sometimes to a halt. This is seen as a frozen screen, unable to move surfaces, or unable to switch VTs (for a while). For example: mir_demo_client_egltriangle -n mir_demo_client_eglplasma -n The -n flag (swapinterval = 0) seems to cause the client to overload the mir server to the point where it cannot render physical frames very often. $ es2_info EGL_VERSION = 1.4 (Gallium) EGL_VENDOR = Mesa Project EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel GL_RENDERER: Gallium 0.4 on AMD CEDAR ... $ es2_info EGL_VERSION = 1.4 (Gallium) EGL_VENDOR = Mesa Project EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel GL_RENDERER: Gallium 0.4 on NVA8 ... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1211700/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
After you turn off fractional scaling you can still adjust font sizes
using the gnome-tweaks app.
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2006517] Re: Bluetooth works on desktop but not on ubuntu core
The locality to this apparmor denial suggests to me it's just the bluez snap that needs to request some extra privileges. Feb 07 23:50:34 ubuntu audit[1562]: AVC apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1562 comm="bluetoothd" family="alg" sock_type="seqpacket" protocol=0 requested_mask="create" denied_mask="create" Feb 07 23:50:34 ubuntu bluetoothd[1562]: src/advertising.c:read_adv_features_callback() Failed to read advertising features: Not Supported (0x0c) ** Package changed: linux (Ubuntu) => bluez (Ubuntu) -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
> would it be bad to enable developer updates / proposed kinetic
updates?
Yes that would be bad. You would get untested updates across all
packages. Doing so usually breaks your system after a while.
> Very odd, I'm only using a scale of 1.25
Ah you are right. Setting 125% I also see Xorg using a transform scale
of 1.6x. Perhaps I got my maths wrong or perhaps Xorg fractional scaling
is buggy. But the general idea for fixing this is still the same:
* Turn OFF fractional scaling; or
* Unplug some monitors
While this is a software bug in GTK 3.x, the developers have moved on to
GTK 4.x so I would not expect any significant changes to the design of
3.x that would fix this.
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1949075] Re: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 22.04
** Tags added: kinetic -- 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/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 22.04 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW 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: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+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 1878076] Re: GTK save-dialogs input-focus moves from filename to file search if a folder is selected
** Tags added: jammy -- 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/1878076 Title: GTK save-dialogs input-focus moves from filename to file search if a folder is selected Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Bug description: This bug is also reported on GNOME's GTK GitLab: https://gitlab.gnome.org/GNOME/gtk/issues/326 ## Steps to reproduce 1. Open any GTK app which uses save dialogs (e.g. gedit) 2. Press save 3. A save dialog appears and the filename is highlighted (if typing at this point you edit the file name) 4. Click on a different folder (e.g. Downloads) 5. The filename is still highlighted, hinting that the focus is still there 6. Type and find yourself searching for a file in the selected folder -- Current behavior -- The higlighting (on the file name) hints a focus which is not the actual input focus, and the actual input focus (the search bar) is hidden until one starts to type, which I think to be confusing and unexpected. Also, clicking back on the highlighted filename you lose the highlighting, so you have to highlight again some already highlighted text; I think this to be confusing and counterintuitive. -- Expected outcome -- Highlighting and focus need to match. If they don't that's a UX bug, and there are several options to solve it, some examples: - keep highlighting as is and keep focus on the filename, this whould require finding a different path for file search (I think this is the most productive option, because I assume a user wants to change the folder and eventually rename or name the file, which I consider more likely than a user wanting to search for a file within a save-file dialog); - keep filesearch as is, but show its bar before typing begins, and remove any highlighting from filename. For reference, Windows 10's native save-file dialogs disables the highlighting when clicking on a different folder. Typing does nothing at that point. Tested on gedit 3.36.1 on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-0 3.24.18-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon May 11 21:53:37 2020 InstallationDate: Installed on 2020-04-03 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1878076/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Medium
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Triaged
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
Out of curiosity, how did you configure a scaling factor of 1.6?
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
And yes that is an inefficient way to do fractional scaling. Only Xorg
does it that way out of necessity to fit in with legacy X11. Wayland
does not need such upscaling-then-downscaling so does fractional scaling
much more efficiently than Xorg sessions.
But Nvidia's Wayland support is still slightly too broken for me to
recommend Wayland right now:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-wayland
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Confirmed
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
Another suggestion is to use a scaling factor of 1.5 instead of 1.6.
That might simplify the required quotient to 3/2 (initially rendering at
3x resolution instead of 8x), so might be enough to have all three
monitors working.
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Confirmed
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
To achieve a scaling factor of 1.6 I suspect the logic is to render at
8x resolution and then downscale 5x (because 8/5 = 1.6). And GTK has
internal size limits of 65535 in each dimension, I think. So the maximum
window size is 65535 / 8 = 8191. That should be enough to have two 4K
(3840 px) monitors scaling 1.6x, but not three. So try unplugging one
monitor and positioning the remaining two next to each other.
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Confirmed
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
Tracking upstream in https://gitlab.gnome.org/GNOME/gtk/-/issues/3050
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Confirmed
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+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 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
I think this is a consequence of your desktop being 18432 pixels wide.
Each 4K monitor is 6144 logical pixels wide because of a custom Xrandr
scaling factor of 1.6.
Turning off screens wouldn't fix it, only unplugging them might. But
still this sounds like a GTK bug because modern Nvidia GPUs like yours
should be fine with an 18K desktop.
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #3050
https://gitlab.gnome.org/GNOME/gtk/-/issues/3050
** Also affects: gtk via
https://gitlab.gnome.org/GNOME/gtk/-/issues/3050
Importance: Unknown
Status: Unknown
** Changed in: gtk+3.0 (Ubuntu)
Status: Incomplete => Confirmed
--
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/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
Confirmed
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe
[Touch-packages] [Bug 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
I just noticed this is a shutdown crash, which isn't obvious until you
scroll down to frames #46-#54:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
Although that's probably not an excuse for letting this sneak into
jammy.
Another interesting note is that it looks like libnm is involved in
frames #22-#25 so it might be NetworkManager that got fixed in lunar?
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
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/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mozjs102 package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 2006370] Re: Terribly flicking and blicking HDMI-port display
Thanks for the bug report. It looks like this is probably a bug in the nouveau graphics driver, and most likely the HDMI port is connected to your Nvidia GPU. The nouveau driver is also logging errors which may or may not be related to this bug. Please open the 'Additional Drivers' app and use it to install an official Nvidia driver instead. ** Tags added: amdgpu dualgpu hybrid nouveau ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Terribly flicking and blicking HDMI-port display + [nouveau] Terribly flicking and blicking HDMI-port display -- 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/2006370 Title: [nouveau] Terribly flicking and blicking HDMI-port display Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have HP15 Gaming Pavilion bought 2-3 years ago. I had Windows 10 before (not it is the second OS due to this bug [I can't use Ubuntu with this bug]), and Win 10 has no problems. No solution [that I found over the internet] worked. I have to have at least two displays. My connection technology: PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external monitor) Win 10 have never had any problems with it (it has good drivers). When I add any input to the second screen - it blinks and flickers so terrible that I can see nothing - a white screen problem. If I do nothing - it will turn to some picture in some time, but if I make any action at the second monitor - flickering and the white screen problem appears again. I think these are drivers. I tested the equipment in Win 10 after I found this bug - and it works perfectly (so, the hardware is good). It is a typical notebook and this bug is crucial. I use two monitors to type codes and work on PC. I can't survive with just one monitor. Right now when I am typing you this message the second monitor became white again for quite a long time (I did nothing there). I hope you will be able to fix this bug :) Best wishes, Alex, Prague, Czech Republic, EU PS: When typing this message I found another bug compared to MS Windows. When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture even when you actually have the second monitor white all the time (so the screenshot is not how it is). I made an actual photo (and deleted some parts of the background not related to the monitors/computer). You can see a white screen, but the screenshot shows a "perfect world" with a perfect picture which is not how it is on the screen. Windows, on the contrary, makes actual screenshots. And Win 10 test of this monitor never have this white screen or any other monitor problems. Moreover, when the monitors stops to be white for a second it depicts different picture (more terrible image; it is disproportional, with font heavily readable, but the screenshot functions shows an "ideal world" a user can never see :) I made this detailed description to help Ubuntu. I think the project is great in concept, but poor in realization. Such bugs make it impossible for users to use Ubuntu (who can work on just one monitor? Who do not wish to make screenshots with what he/she actually sees on the monitor [rather than modified images with the pictures users do not actually see]?). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 6 19:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117M [103c:87b1] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87b1] InstallationDate: Installed on 2023-02-04 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10
