[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

I have the same problem... And mine is worse - picking Ubuntu on XOrg has no effect. ThinkPad P1 Gen3 has all HDMI/USBC monitors connected to NVidia only. So I cannot use external monitor in any way shape or form. This is new, btw. XDG_SESSION_DESKTOP=ubuntu-xorg XDG_SESSION_TYPE=x11 $

[Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100]

I'll reproduce later today after hours. Will also try to install 22.04 to see if it helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor

[Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100]

@vanvugt - USB-C port seems to be wired to NVIDIA GPU on this laptop. I cannot use the monitor, if I switch to Intel GPU (`prime-select intel`) - it doesn't even identify that a monitor was connected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1960865] Re: System freeze

@vanvught 1. I can literally reproduce the crash. It's 100% reproducible. 2. The whole system freezes and the logs get a bunch of zeros. (attached is the file with extract from syslog from the moment I attach the screen to crash) ** Attachment added: "syslog"

[Bug 1960865] [NEW] System freeze

Public bug reported: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a

[Bug 1846334] Re: cupsd assert failure: free(): invalid pointer

This has been happening for ages now. 18.04 to 20.10 are all affected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer To manage

[Bug 1901024] Re: Crash on startup using linux 5.8.0-25

@rmoisto - I have the same issue. It's not your system error, it's 5.8.0_25 + AMD driver issue. 5.4 kernel works well. ** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => xf86-video-amd -- You received this bug notification because you are a member

[Bug 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop

Still here with Ubuntu 18.04 on ThinkPad P51s $ cat /proc/asound/card*/codec* | grep Codec Codec: Realtek ALC298 Codec: Intel Kabylake HDMI $ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Lenovo Sunrise

[Bug 1688032] Re: systemd-resolved DHCP: does not change DNS servers

Nevermind. Found a config issue. Network Manager fails silently ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688032 Title:

[Bug 1688032] Re: systemd-resolved DHCP: does not change DNS servers

Adding additional DNS servers via NetworkManager config - also has 0 effect on `systemd-resolve --status` DNS Domains are changed, though. Here is systemd-resolve --status: Global DNS Servers: 8.8.8.8 8.8.4.4 2001:4860:4860::

[Bug 1688032] [NEW] systemd-resolved DHCP: does not change DNS servers

Public bug reported: When I connect to Corporate WiFi(Enterprise PEAP with certificate, MSCHAPv2) and acquire a DHCP lease, the DNS servers are never changed by systemd-resolved from Google's servers. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received

[Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

PS: The connection to the speaker is made without issues, only Pulseaudio is causing the failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire()

[Bug 1577197] [NEW] Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

Public bug reported: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and

[Bug 1176359] [NEW] NetowrkManager does not connect/diconnect/reconnect randomly

Public bug reported: Upgraded from 12.10 hoping that this issue would be fixed. After some time being connected to a WiFi network, network manager indicator will stop responding to commands - disconnect, connect and Edit connections A restart/logout helps, but the indicator stops showing the

[Bug 1069246] Re: Ubuntu's Software center doesn't even starts.

Same issue. Seems that the OAuth token isn't getting returned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069246 Title: Ubuntu's Software center doesn't even starts. To manage notifications