** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Public bug reported:
It seems whenever I try to run `prime-select nvidia` I get a blank
screen after the splash screen. When I am running under `prime-select
intel` - I have no problems.
I triple boot, two of them being Ubuntu (one for testing one for every
day use), and the problem seems to lie
** Also affects: nvidia-graphics-drivers-361 (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/1587699
Title:
Screen
Public bug reported:
The problem always happens when I try to use the nvidia graphics card
using the command prime-select nvidia. When using prime-select intel it
works fine.
The baffling part is that I dual boot 2 Ubuntu installs... And the other
one works fine. I can help try and figure out
** Description changed:
The problem always happens when I try to use the nvidia graphics card
using the command prime-select nvidia. When using prime-select intel it
works fine.
The baffling part is that I dual boot 2 Ubuntu installs... And the other
one works fine. I can help try
I've recently started getting this issue too. What is going on?? Ubuntu
shouldn't be doing this on the LTS.
** Also affects: libgnome-keyring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Sorry, I should have been more constructive with my comment. The
workaround in #10 seems to partially work. It doesn't allow the "login"
password keychain to be unlocked on login, but it at least let you see
the passwords in seahorse so that it can be unlocked manually - which in
turn prevents
I was wondering if there is anything I can to help regress the issue?
Even if it is just trying to load various different older versions?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgnome-keyring in
Ubuntu.
Hi @kaihengfeng thank you very much for commenting, much appreciated.
Yes, linux-modules-extra is installed:
$ uname -r
5.8.0-36-generic
$ sudo apt install linux-modules-extra-5.8.0-36-generic
[sudo] password for hazrpg:
Reading package lists... Done
Building dependency tree
Reading
I've done more digging and I think the regressing happened sooner, but I
only rebooted it on the day I noticed it wasn't working. I decided to
see when the system was actually last rebooted by using:
$ last reboot | less
reboot system boot 5.8.0-40-generic Fri Jan 22 11:44 still running
Forgot to mention in the original post, but trying to revert all updates
that caused the problem (as per the versions listed above) but that
didn't work because they no longer exist in the repo (and the system had
already cleared the cache). So I always get the error that the
package(s) were not
Public bug reported:
After a recent update, I now have a system that can no longer play audio
(via HDMI), my second monitor (DVI) is no longer being picked up, and
CPU/AGPU usage has lost a lot of performance (OBS is basically unusable
at this point).
Whatever has happened with the recent
Public bug reported:
Error displayed in the terminal is:
/usr/lib/python3/dist-packages/requests/__init__.py:89:
RequestsDependencyWarning: urllib3 (1.26.8) or chardet (3.0.4) doesn't match a
supported version!
warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
$ lsb_release -rd
Description: Ubuntu 20.04.4 LTS
Release: 20.04
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
$ apt-cache policy apport
Public bug reported:
Hi Devs,
Hope you're all keeping well.
The problem I have is similar to:
https://answers.launchpad.net/ubuntu/+question/699306
Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither the
laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB
dongle
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
bluez:
Installed: 5.64-0ubuntu1
16 matches
Mail list logo
