[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-12 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Sure,I get it. The work around of using Xorg does not resolve the issue on this setup, Wayland and Xorg both suffer different problems. Just wanted to call that out! Simple open questions: 1. The NVIDIA

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Appears to be a red herring, VirtualBox apparently experiences random guest crashes when split lock detection is enabled on the Host OS. ( I am able to verify this ) Reference: "Random crashes with Windows

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 This may be unrelated -- but I am also seeing "x86/split lock detection" errors. Is this just a red herring ? Only seeing these when using the VirtualBox to drive the GPU. [Tue Jul 11 14:50:44 2023] usb 2

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Notably, when I "enable 3d" with a windows 10 guest on VirtualBox, I can see the GPU being actively used! Now, if there was only a way to use it with Xorg on the Host machine, not just the guest. -- You r

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Then onto check why the GPU is not even being detected ... beadon@semiauto:~$ sudo nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest N

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 setting the PRIME profile back into place for NVIDIA. This causes the gdm issues, I suspect because this promotes the eGPU to primary and there is some kind of resource sharing problem. So, the way it MUST

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
driver problem we are chasing, and PRIME was just selecting the NVIDIA GPU for some reason and flailing ..' Hmm running into a bit of a snag : beadon@semiauto:~$ sudo nvidia-settings [sudo] password for beadon: ERROR: NVIDIA driver is not loaded (nvidia-settings:3802): GLib-GObject-CRI

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 I am also seeing a couple things like this .. options nvidia-drm modeset=1 Perhaps this is a path I need to take and specify PRIME vs non-prime ? https://forums.developer.nvidia.com/t/prime-and-prime-sync

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 worse still , now I cannot get a gdm login unless I disconnect the USB-C eGPU (this NVIDIA GPU enclosure). I am reading up further on "prime" and "reverse prime" GPUs. The behavior here may be similar: ht

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Notably -- there seems to be a known issue with DisplayPort connectivity 1.3 and 1.4 and NVIDIA GPUs recently. I am seeing a firmware update issued by NVIDIA on June 26 2023 for SOME NVIDIA chipsets: https

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 As expected I am using Xorg now, beadon@semiauto:~$ echo $XDG_SESSION_TYPE x11 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in

[Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-11 Thread beadon
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 I was unable to select the "Ubuntu on Xorg" as a configuration option, so I did it manually. I modified /etc/gdm3/custom.conf current configuration: # GDM configuration storage # # See /usr/share/gdm/gdm

[Bug 2026790] [NEW] Slow refresh rate (5-6hz) on Display managed by gnome-shell

2023-07-10 Thread beadon
Public bug reported: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available across a Thunderbolt 3 link. Here is what the Nvidia Drivers are reporting: beadon@semiauto:~$ nvidia-smi Mon Jul 10 20:35:25

[Bug 2016046] [NEW] connecting to samba fileshare fails if smb1(now deprecated) is not supported by the server

2023-04-12 Thread beadon
Public bug reported: When connecting with Nautilus to "smb://hostname.lan/" note - not the full path to the samba share, and this is a resolvable ".lan" name handled by the local DNS server - then gvfsd fails, and doesn't send a proper error back to nautilus. This display in Nautilus is simply "F

[Bug 2006070] Re: incredibly high memory usage

2023-03-07 Thread beadon
Ok, somewhat good news. I have been watching the memory usage on the machine as many applications start / stop , and am tracking the growth and management. A tool to tweak the behavior --- One system parameter I had tweaked before reporting this issue was vm.swappiness , I had moved this down to

[Bug 2006070] Re: incredibly high memory usage

2023-02-06 Thread beadon
Yes, I killed the process as it approached 6GB after I filed this report. I will report back with the growth over the next few days. I suspect it occured when I switched between different wireless networks and physical locations, but I would need to run a series of tests to conslude this for cert

[Bug 2006070] Re: incredibly high memory usage

2023-02-06 Thread beadon
Ok, one better, sorted results (lots of chrome tabs appear, fyi). ps auxw --sort -rss > psall.txt See attached file, since gnome-software has restarted, in 1 day it's up to 501+MB and written ~1.9GB to disk (why??). ** Attachment added: "psall.txt" https://bugs.launchpad.net/ubuntu/+source/g

[Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

2023-01-18 Thread beadon
I have blacklisted this now using: sudo vim /etc/modprobe.d/blacklist-nouveau.conf adding: blacklist nouveau options nouveau modeset=0 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs

[Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

2023-01-17 Thread beadon
Should I open this as a different issue with the Core X Chroma Thunderbolt 3 enclosure ? It's very similar. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2003031 Title: gnome-shel

[Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

2023-01-17 Thread beadon
f the attachment, then detachment of this enclosure. Note that on re-attaching the enclosure the USB devices which previously worked fine attached to the enclosure no longer function (perhaps not deregistered properly?). Details for HW info beadon@semiauto:~$ hwinfo --gfxcard --short graphics

[Bug 1870597] Re: libinput says "your system is too slow"

2023-01-17 Thread beadon
I am seeing this issue in Ubuntu 22.10 , specifically for a Razer Deathadder mouse : Jan 17 17:59:28 semiauto /usr/libexec/gdm-x-session[2147]: (EE) event20 - Razer Razer DeathAdder: client bug: event processing lagging behind by 24ms, your system is too slow Which information do you need to tro

[Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

2023-01-17 Thread beadon
I have applied the workaround for mutter : MUTTER_DEBUG_FORCE_KMS_MODE=simple I am seeing no further logs at the moment. I will continue to monitor for issues. To address any low-level issues I also have applied the system firmware update, available via ISO from the Lenovo support site "n32ur2

[Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

2023-01-17 Thread beadon
Yes, there is a USB-C "port extender" (dock) attached to this Lenovo laptop. The model is the MUC-0501B. It is this exact device : https://amzn.to/3XA5u5N -- "USB C Adapters for MacBook Pro/Air,Mac Dongle with 3 USB Port,USB C to HDMI, USB C to RJ45 Ethernet,MOKiN 9 in 1 USB C to HDMI Adapter,10

[Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"

2023-01-17 Thread beadon
Spelling error : "When I woke the machine..." -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the ker