Hello sirs,
I discovered my specific problem was because actually the video card was
not initialized at a hardware level in motherboard.
So what happened was that I had Display plugged into Intel motherboard
onboard video output.
Linux started and video card was kinda not initialized, so then wh
Hello sirs,
Sorry for being so noob. I see comment by janitor says something like:
"in package version 1:0.9.6.2~0.22.04.2 this is fixed."
However I have package version
maurirope@ubuntuserver:~$ apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common: date.
Installed: 1:0.9.6.2~0.22.04.
This bug was fixed in the package ubuntu-drivers-common -
1:0.9.6.2~0.22.04.3
---
ubuntu-drivers-common (1:0.9.6.2~0.22.04.3) jammy; urgency=medium
* UbuntuDrivers/detect.py:
- Fix "882:5 local variable 'with_nvidia_kms' is assigned to
but never used" FTBFS (triggered by t
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.6.3.2
---
ubuntu-drivers-common (1:0.9.6.3.2) kinetic; urgency=medium
* UbuntuDrivers/detect.py:
- Fix "882:5 local variable 'with_nvidia_kms' is assigned to
but never used" FTBFS (triggered by tests/test_stat
I did the same thing for Jammy, with the same results:
:~$ ubuntu-drivers list
ERROR:root:aplay command not found
nvidia-driver-525-open
nvidia-driver-515
nvidia-driver-510
nvidia-driver-470-server
nvidia-driver-470
nvidia-driver-525-server
nvidia-driver-515-server
nvidia-driver-525
nvidia-driver-
Removing the alsa-utils package in Kinetic, I don't get the traceback
any more with the package in kinetic-proposed:
:~$ ubuntu-drivers list
ERROR:root:aplay command not found
nvidia-driver-515-open, (kernel modules provided by nvidia-dkms-515-open)
nvidia-driver-510, (kernel modules provided by
Hey Timo, unfortunately I had left an unused variable in Jammy and in
Kinetic, and that caused the test suite to trigger a FTBFS for both. The
unused variable is not there in Lunar.
Please accept my new uploads, so that we can proceed with the testing.
--
You received this bug notification becau
Hello Jeff, or anyone else affected,
Accepted ubuntu-drivers-common into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.6.2~0.22.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing t
Hello Jeff, or anyone else affected,
Accepted ubuntu-drivers-common into kinetic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.6.3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Also affects: ubuntu-drivers-common (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: New => In Progress
** Changed i
** Changed in: ubuntu-drivers-common
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1935070
Title:
Traceback during 'ubuntu-drivers list'
** Tags added: servcert-565
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1935070
Title:
Traceback during 'ubuntu-drivers list'
Status in Ubuntu Drivers Common:
Unkn
** Bug watch added: github.com/tseliot/ubuntu-drivers-common/issues #78
https://github.com/tseliot/ubuntu-drivers-common/issues/78
** Also affects: ubuntu-drivers-common via
https://github.com/tseliot/ubuntu-drivers-common/issues/78
Importance: Unknown
Status: Unknown
--
You rece
I made a PR on github to address the exception handling which I think is
the best course here. Adding a dependency on alsa-utils will result in
adding further unwanted desktop packages on systems where they don't
really belong (anything with Ubuntu Server installed).
Just removing the traceback t
I was about to file a new bug report about this issue.
It appears the ubuntu-drivers-common package is missing a dependency on
alsa-utils (which provides the aplay command).
The problem can be fixed by running
```
sudo apt-get install alsa-utils
```
but ideally the ubuntu-drivers-common package
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://
16 matches
Mail list logo
