** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058622
Title:
[needs-packaging] lenovo-wwan-unlock
To manage notifications about
see Kubuntu Plasma Network Manager Bug:
https://bugs.kde.org/show_bug.cgi?id=486499
** Bug watch added: KDE Bug Tracking System #486499
https://bugs.kde.org/show_bug.cgi?id=486499
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lenovo-wwan-unlock_2.0.0.orig.tar.gz"
https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+attachment/5776882/+files/lenovo-wwan-unlock_2.0.0.orig.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lenovo-wwan-unlock_2.0.0-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+attachment/5776881/+files/lenovo-wwan-unlock_2.0.0-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
I packed version v2.0.0 and upload to the git repo. The files under
debian folder are all created by Canonical, I think it should be no
problem using GPL-3 license.
** Attachment added: "lenovo-wwan-unlock_2.0.0-0ubuntu1.dsc"
Public bug reported:
When I right-click on the opened window with the picture to get access to the
context menu, the window closes with an error message:
*** buffer overflow detected ***: terminated
lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:
Hi Lucas Kanashiro,
The source git repo is at https://git.launchpad.net/lenovo-wwan-unlock.
This package been requested to go through normal review & sponsorship into
multiverse. Will you suggest to use different template in the description.
--
You received this bug notification because you
** Tags added: needs-packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058622
Title:
[needs-packaging] lenovo-wwan-unlock
To manage notifications about this bug go to:
** Changed in: oem-priority
Assignee: (unassigned) => Dirk Su (dirksu)
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058192
** Tags added: oem-priority originate-from-1956804 sutton
** Changed in: oem-priority
Assignee: (unassigned) => Dirk Su (dirksu)
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Also affects: ubuntu
Importance: Undecided
Status: New
** Changed in: ubuntu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058622
Title:
Public bug reported:
[Availability]
The package lenovo-wwan-unlock build for the architectures it is designed to
work on.
It currently builds and works for architectures: amd64
Link to package https://launchpad.net/ubuntu/+source/lenovo-wwan-unlock
[Rationale]
- The package lenovo-wwan-unlock
I can confirm that the package virtualbox_7.0.14-dfsg-4_amd64.deb
contains
/usr/share/doc/virtualbox/UserManual.qch
/usr/share/doc/virtualbox/UserManual.qhc
(examined file:
http://de.archive.ubuntu.com/ubuntu/pool/multiverse/v/virtualbox/virtualbox_7.0.14-dfsg-4_amd64.deb)
--
You received this
In the meantime, this seems to have been fixed. The latest 5.4.0 kernel
does not have the problem anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914949
Title:
Resume from suspend not
Tested with Dell machine (202203-30028) which has problem ambient light
sensor. Import iio-sensor-proxy 2.8-1ubuntu2 from -proposed channel.
With iio-sensor-proxy debug turned on, iio-sensor-proxy use buffer ALS
to read light sensor value. Execute monitor-sensor can check ambient
light sensor
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946476
Title:
New on-demand default causes RTD3 never to be enabled
To manage
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942789
Title:
On-demand and
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Since this machine has all-in-one in chassis type, only
enabled
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942307
Title:
ubiquity uses
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946476
Title:
New on-demand
Installed nvidia-prime 0.8.16~0.20.04.2 from proposed channel. Tested
with command "prime-select on-demand | false" won't get error and
traceback information.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Since this machine has all-in-one in chassis type, only
enabled
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Since this machine has all-in-one in chassis type, only
enabled
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Since this machine has all-in-one in chassis type, only
enabled
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Check nvidia module parameter with "cat
/proc/driver/nvidia/params |
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Check nvidia module parameter with "cat
/proc/driver/nvidia/params |
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Check nvidia module parameter with "cat
/proc/driver/nvidia/params |
It was a mirage. The system is still locking up, something that did not
happen with an older kernel, and also not with other systems booting off
USB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
** Description changed:
As per LP: #1942307 we now set on-demand as the default. This however,
causes "prime-select on-demand", called by ubuntu-drivers, not to even
try to detect RTD3 and to enable it, since "on-demand" is already set.
We cannot make informed choices about RTD3 in the
Update. And I don't want to jinx it but ... it seems like 22.04 (to be)
has this fixed. Updated to it two days ago, and it seems fine with its
kernel 5.15.0-23-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- [Steps to reproduce]
- 1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
- 2. After the installation, press enter to reboot system
- 3. prime-select query
+ RTD3 is a nvidia GPU feature to support runtime suspend.
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
** Description changed:
- [Steps to reproduce]
- 1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
- 2. After the installation, press enter to reboot system
- 3. prime-select query
+ As per LP: #1942307 we now set on-demand as the default.
** Tags added: oem-priority originate-from-1954400 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962731
Title:
No SYS%LPI residency in suspend when ethernet is connected
To manage
Test plan had been updated to cover the nvidia-driver-390 case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942789
Title:
On-demand and RTD3 need to be separated
To manage notifications about
Setup impish on 201606-22344 in cert pool, this system's GPU can
supported both with nvidia-driver-390 and nvidia-driver-470. Installed
ubuntu-drivers-common, nvidia-settings from impish-proposed repository.
With nvidia-driver-390, try to setup on-demand mode with "prime-select
on-demand", system
Setup focal on 201606-22344 in cert pool, this system's GPU can
supported both with nvidia-driver-390 and nvidia-driver-470. Installed
ubuntu-drivers-common, nvidia-settings from focal-proposed repository.
With nvidia-driver-390, try to setup on-demand mode with "prime-select
on-demand", system
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
Setup impish on 201606-22459 in cert pool. Then doing same test as #3,
test result is positive. GPU will keep in nvidia mode, and glxinfo works
normally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Installed nvidia-driver-390 on target system (201606-22459 in cert.
poll). Then install nvidia-settings and ubuntu-drivers-common mentioned
in #2. Try to switch on-demand mode with "prime-select on-demand" and
nvidia-settings UI. After system reboot, GPU will keep in nvidia mode.
And glxinfo works
With test on Dell Vostro 5568 witch got GPU can be supported by nvidia-
driver-390 package. Install nvidia-driver-390 via ubuntu-drivers install
nvidia:390. The default GPU mode will be nvidia. Manually switch GPU
mode to on-demand, and running glxinfo will get "Error: couldn't find
RGB GLX visual
Bump. This bug is still open AFAICT. And I just realized that the real
cost to me on this machine (which otherwise runs great with the old 4.*
kernel) is that I cannot launch Docker containers any more. Which
stinks.
Machine otherwise happy and stable under 21.10 *provided I run the
ancient
** Tags added: originate-from-1954392 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955566
Title:
iris driver doesn't load correctly on intel pci_id 0x4688
To manage notifications
** Changed in: oem-priority
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946434
Title:
SRU: Set on-demand as default, enable RTD3 only on laptops and
** Changed in: oem-priority
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/1946440
Title:
SRU: enable RTD3 only on laptops
To manage notifications about this bug go
Tested on SKU 0B11 with focal and impish. After upgrade udev from focal-
proposed and impish-propsed, monitor-sensor show there is no
accelerometer. The results are as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Test with machine which supports Dell privacy. Mic mute key works well
in Impish
[kernel version]
linux-image-5.14.0-1011-oem
[systemd version]
248.3-1ubuntu8.1
** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish
--
You
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942788
Title:
Nvidia doesn't
Create iso with live-build and import ubuntu-drivers-common
0.9.0~0.20.04.4 from focal-proposed. Install Ubuntu with "third-party
packages" enabled. After installation finished,
'/run/nvidia_runtimepm_supported' had been created and use 'prime-select
query' get 'on-demand'
** Tags removed:
Tested with iso built from live-build and import ubuntu-drivers-common
from focal-proposed. After installation finished, check
/var/log/installer/syslog can see error log as attachment. It says
"ubiquity: chroot: failed to run command ‘prime-select’: No such file or
directory", because
Tested with 202106-29207 in Cert pool. It works fine with proposed
channel and pull in linux-oem-20.04b
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of
@Brian
I updated the description. Do you think the information in description is
enough to continue the SRU process?
And the packages is uploaded to queue.
Focal:
https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes
Hirsute:
@Brian
I updated the description. Do you think the information in description is
enough to continue the SRU process?
And the packages is uploaded to queue.
Focal:
https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes
Hirsute:
@Brian
I updated the description. Do you think the information in description is
enough to continue the SRU process?
And the packages is uploaded to queue.
Focal:
https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes
Hirsute:
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
** Description changed:
- RTD3 is a nvidia GPU feature to support runtime suspend.
+ [Steps to reproduce]
+ 1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
+ 2. After the installation, press enter to reboot system
+ 3. prime-select query
** Description changed:
- As per LP: #1942307 we now set on-demand as the default. This however,
- causes "prime-select on-demand", called by ubuntu-drivers, not to even
- try to detect RTD3 and to enable it, since "on-demand" is already set.
+ [Steps to reproduce]
+ 1. Install 20.04.3 with
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
Previous discussion was at
https://chat.canonical.com/canonical/pl/1mgrhibwpj8ojxk89tbpztjdar. Due
to the design of ubiquity, it only use ubuntu-driver to get package list
and install package in 31ubuntu_driver_packages. But ubuntu-driver not
only install packages but also create configurations of
For historical interest, I note that I don't see (2) in ocrfeeder 0.8.1
under Xenial. Fixing (1) by reverting gs to 9.25 or replacing with a
patched 9.50 solved my issue with ocrfeeder in that configuration. I
presume it's running under Python 2.7.17.
--
You received this bug notification
** Changed in: oem-priority
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942307
Title:
ubiquity uses performance mode for nvidia driver
To manage
My kind back-porter
(https://launchpad.net/~savoury1/+archive/ubuntu/graphics) applied the
GS commit
http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=24ec06a27df63297796a379c95ee5d4b39040410
to his PPA GS 9.50 build (Focal -> Xenial) and that has worked fine.
Thanks for pushing this.
--
You
** Description changed:
ubiquity calls
```
ubuntu-drivers install $FREEONLY $NOOEM --package-list
/run/ubuntu-drivers.autoinstall
```
to generate package list during live system but "ubuntu-drivers install" not
only install packages but also create some config files for switching
ther Info]
+
+ * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to
+ https://bugs.launchpad.net/oem-priority/+bug/1942788
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Assignee: (unassigned) => Dirk Su (dirksu)
--
You received this bug notification because you
** Changed in: ubuntu-drivers-common (Ubuntu Hirsute)
Assignee: (unassigned) => Dirk Su (dirksu)
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Assignee: (unassigned) => Dirk Su (dirksu)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
According to Nvidia README, the RTD3 doesn't support on non-laptop
machine.
https://github.com/tseliot/ubuntu-drivers-common/issues/55
We need to check chassis type before enabling RTD3.
---
[Impact]
* According to Nvidia README, the RTD3
Tested on desktop and notebook machine with Nvidia graphic card. On
notebook machine (chassis type 10), configuration file
'/run/nvidia_runtimepm_supported' is created. On desktop (chassis type
3) machine did not generate the configuration file. Only notebook
machine will enable runtime PM.
**
** Changed in: oem-priority
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942788
Title:
Nvidia doesn't support RTD3 on non-laptops
To manage notifications
** Tags added: oem-needs-upload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925013
Title:
[MIR] oem-stella.cmit-camerupt-meta
To manage notifications about this bug go to:
tion file
'/run/nvidia_runtimepm_supported' will be created.
+ * Execute "prime-select query" should get "on-demand"
+
+ [Where problems could occur]
+
+ * With non-laptop machine use RTD3 supported GPU may use more power
+
+ [Other Info]
** Changed in: oem-priority
Assignee:
debdiff for focal
** Patch added: "ubuntu-drivers-common_0.9.0~0.20.04.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816/+attachment/5537831/+files/ubuntu-drivers-common_0.9.0~0.20.04.3.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
** Description changed:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
** Description changed:
[Impact]
* Ubuntu will set GPU mode to performance as default which may use more power
* User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
* According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Test
** Description changed:
As per LP: #1942307 we now set on-demand as the default. This however,
causes "prime-select on-demand", called by ubuntu-drivers, not to even
try to detect RTD3 and to enable it, since "on-demand" is already set.
We cannot make informed choices about RTD3 in the
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
** Description changed:
According to Nvidia README, the RTD3 doesn't support on non-laptop
machine.
https://github.com/tseliot/ubuntu-drivers-common/issues/55
We need to check chassis type before enabling RTD3.
---
[Impact]
- * According to Nvidia README, the RTD3
** Description changed:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
** Description changed:
[Impact]
* According to Nvidia README, the RTD3 (Runtime D3) doesn't support on
non-laptop machine
- * Patch make system not enable RTD3 unless it's a laptop
+ * Patch make system not enable RTD3 unless it's a laptop
[Test Plan]
* Install Ubuntu on
** Description changed:
As per LP: #1942307 we now set on-demand as the default. This however,
causes "prime-select on-demand", called by ubuntu-drivers, not to even
try to detect RTD3 and to enable it, since "on-demand" is already set.
We cannot make informed choices about RTD3 in the
** Changed in: oem-priority
Assignee: jeremyszu (os369510) => Dirk Su (dirksu)
** Description changed:
According to Nvidia README, the RTD3 doesn't support on non-laptop
machine.
https://github.com/tseliot/ubuntu-drivers-common/issues/55
We need to check chassis type bef
** Changed in: oem-priority
Assignee: jeremyszu (os369510) => Dirk Su (dirksu)
** Description changed:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.
** Changed in: oem-priority
Assignee: jeremyszu (os369510) => Dirk Su (dirksu)
** Description changed:
As per LP: #1942307 we now set on-demand as the default. This however,
causes "prime-select on-demand", called by ubuntu-drivers, not to even
try to detect RTD3
** Changed in: oem-priority
Assignee: jeremyszu (os369510) => Dirk Su (dirksu)
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press en
** Description changed:
[Impact]
- * According to Nvidia README, the RTD3 doesn't support on non-laptop
- machine
+ * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on
non-laptop machine
+ * Patch make system not enable RTD3 unless it's a laptop
[Test Plan]
-
If anybody has a hypothesis of what could be causing the lock, I would
be game to trying different kernel builds (or parameterizations). So
far I mostly glad I can run the machine again, even if it needs a 4.*
kernel.
Otherwise, is there a particular crash I could enable to diagnose? The
** Tags removed: oem-needs-upload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925013
Title:
[MIR] oem-stella.cmit-camerupt-meta
To manage notifications about this bug go to:
** Tags removed: oem-scripts-1.16
** Tags added: oem-needs-upload oem-scripts-1.17
** Changed in: oem-priority
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This issue appeared first under 21.04, and I (wrongly) suspected a bug
in the window manager or graphics stack. I posted on askubuntu at
https://askubuntu.com/questions/1346317/ubuntu-21-04-and-21-10-lock-
hard-with-basic-gui-redrawing-using-standard-intel-g
and even
"Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1946573"
Done. Sorry, that it takes 2 weeks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Alberto
Could we apply the modification in focal and hirsute?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943816
Title:
"ubuntu-drivers install" needs to be used when installing nvidia-
Upload debdiff for hirsute
** Patch added: "nvidia-prime_0.8.16.2~0.21.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1946434/+attachment/5534071/+files/nvidia-prime_0.8.16.2~0.21.04.1.debdiff
--
You received this bug notification because you are a member of
debdiff for hirsute
** Patch added: "ubuntu-drivers-common_0.9.0~0.21.04.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1946440/+attachment/5533073/+files/ubuntu-drivers-common_0.9.0~0.21.04.2.debdiff
--
You received this bug notification because you are a
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946440
Title:
SRU: enable RTD3 only on laptops
To manage notifications about this bug go
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
Upload debdiff for focal
** Description changed:
[Impact]
- * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
- * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+ * Ubuntu will set GPU mode to performance as default which
** Description changed:
As per LP: #1942307 we now set on-demand as the default. This however,
causes "prime-select on-demand", called by ubuntu-drivers, not to even
try to detect RTD3 and to enable it, since "on-demand" is already set.
We cannot make informed choices about RTD3 in the
1 - 100 of 1892 matches
Mail list logo
