2018-09-21 07:55:00 |
Jean-Baptiste Lallement |
bug |
|
|
added bug |
2018-09-21 07:55:17 |
Jean-Baptiste Lallement |
tags |
amd64 apport-bug cosmic ubiquity-2.15.15 |
amd64 apport-bug cosmic rls-cc-incoming ubiquity-2.15.15 |
|
2018-09-21 09:22:28 |
Jean-Baptiste Lallement |
summary |
Proprietary drivers are installed locally instead of target system |
Proprietary drivers are installed locally and not on target system |
|
2018-09-21 09:24:12 |
Jean-Baptiste Lallement |
description |
On a system with hardware requiring proprietary drivers (eg nVidia graphics card), when the user selects to install restricted add-on and proprietary driver, ubuntu-drivers runs immediately the the installer exists the prepare step.
Doing so it installs the drivers on the live session while it should be installed on the target filesystem.
Therefore after installation the proprietary drivers are not installed on the system.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 21 09:49:29 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper --
InstallationDate: Installed on 2013-09-03 (1843 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: Upgraded to cosmic on 2018-01-26 (237 days ago) |
On a system with hardware requiring proprietary drivers (eg nVidia graphics card), when the user selects to install restricted add-on and proprietary driver, ubuntu-drivers runs immediately the the installer exists the prepare step.
Doing so it installs the drivers on the live session. However this step is not executed in the target filesystem afterward once its ready.
Therefore after installation the proprietary drivers are not installed on the system.
The installation of proprietary driver must happen in the live session for network drivers for example and in the target system for all the drivers supported by the system.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 21 09:49:29 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper --
InstallationDate: Installed on 2013-09-03 (1843 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: Upgraded to cosmic on 2018-01-26 (237 days ago) |
|
2018-09-21 09:24:21 |
Jean-Baptiste Lallement |
summary |
Proprietary drivers are installed locally and not on target system |
Proprietary drivers are installed locally and not on the target system |
|
2018-09-27 15:18:22 |
Steve Langasek |
ubiquity (Ubuntu): importance |
Undecided |
High |
|
2018-09-27 16:56:40 |
Jean-Baptiste Lallement |
description |
On a system with hardware requiring proprietary drivers (eg nVidia graphics card), when the user selects to install restricted add-on and proprietary driver, ubuntu-drivers runs immediately the the installer exists the prepare step.
Doing so it installs the drivers on the live session. However this step is not executed in the target filesystem afterward once its ready.
Therefore after installation the proprietary drivers are not installed on the system.
The installation of proprietary driver must happen in the live session for network drivers for example and in the target system for all the drivers supported by the system.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 21 09:49:29 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper --
InstallationDate: Installed on 2013-09-03 (1843 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: Upgraded to cosmic on 2018-01-26 (237 days ago) |
On a system with hardware requiring proprietary drivers (eg nVidia graphics card), when the user selects to install restricted add-ons and proprietary drivers, ubuntu-drivers runs immediately when the installer exits the prepare step.
Doing so it installs the drivers on the live session. However this step is not executed in the target filesystem afterward, once its ready.
Therefore, after installation, the proprietary drivers are not installed on the system.
The installation of proprietary drivers must happen in the live session, for network drivers for example, and in the target system for all the drivers supported by the system.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 21 09:49:29 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper --
InstallationDate: Installed on 2013-09-03 (1843 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: Upgraded to cosmic on 2018-01-26 (237 days ago) |
|
2018-09-28 12:33:55 |
Francis Ginther |
tags |
amd64 apport-bug cosmic rls-cc-incoming ubiquity-2.15.15 |
amd64 apport-bug cosmic id-5bacf4d167b9b07053633a4f rls-cc-incoming ubiquity-2.15.15 |
|
2018-12-20 00:03:28 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Bionic |
|
2018-12-20 00:03:28 |
Dimitri John Ledkov |
bug task added |
|
ubiquity (Ubuntu Bionic) |
|
2018-12-20 02:57:22 |
Launchpad Janitor |
ubiquity (Ubuntu): status |
New |
Fix Released |
|
2019-01-10 16:43:19 |
Steve Langasek |
ubiquity (Ubuntu Bionic): milestone |
|
ubuntu-18.04.2 |
|
2019-01-15 10:49:48 |
Dimitri John Ledkov |
description |
On a system with hardware requiring proprietary drivers (eg nVidia graphics card), when the user selects to install restricted add-ons and proprietary drivers, ubuntu-drivers runs immediately when the installer exits the prepare step.
Doing so it installs the drivers on the live session. However this step is not executed in the target filesystem afterward, once its ready.
Therefore, after installation, the proprietary drivers are not installed on the system.
The installation of proprietary drivers must happen in the live session, for network drivers for example, and in the target system for all the drivers supported by the system.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 21 09:49:29 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper --
InstallationDate: Installed on 2013-09-03 (1843 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: Upgraded to cosmic on 2018-01-26 (237 days ago) |
[Impact]
* Installing systems with nvidia graphics card, and opting to use it, does not end up setting it up in the installed system
[Test Case]
* Install on a system with nvidia graphics card
* Opt to use 3rd party & proprietary drivers
* Observe that nvidia dkms modules are installed in the target system
[Regression Potential]
* Installation of 3rd party drivers was not attempted before, and thus may now fail, however that is non-default codepath (opt-in).
* there are updates to flash-kernel & shim-signed which may regress that functionality under ubiquity, but shouldn't (see changelogs for those package updates)
[Other Info]
* original bug report:
On a system with hardware requiring proprietary drivers (eg nVidia graphics card), when the user selects to install restricted add-ons and proprietary drivers, ubuntu-drivers runs immediately when the installer exits the prepare step.
Doing so it installs the drivers on the live session. However this step is not executed in the target filesystem afterward, once its ready.
Therefore, after installation, the proprietary drivers are not installed on the system.
The installation of proprietary drivers must happen in the live session, for network drivers for example, and in the target system for all the drivers supported by the system.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 21 09:49:29 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper --
InstallationDate: Installed on 2013-09-03 (1843 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: Upgraded to cosmic on 2018-01-26 (237 days ago) |
|
2019-01-15 11:00:32 |
Dimitri John Ledkov |
ubiquity (Ubuntu Bionic): status |
New |
In Progress |
|
2019-01-15 20:39:09 |
Brian Murray |
ubiquity (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
2019-01-15 20:39:11 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2019-01-15 20:39:14 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
2019-01-15 20:39:18 |
Brian Murray |
tags |
amd64 apport-bug cosmic id-5bacf4d167b9b07053633a4f rls-cc-incoming ubiquity-2.15.15 |
amd64 apport-bug cosmic id-5bacf4d167b9b07053633a4f rls-cc-incoming ubiquity-2.15.15 verification-needed verification-needed-bionic |
|
2019-01-30 17:11:22 |
Dimitri John Ledkov |
tags |
amd64 apport-bug cosmic id-5bacf4d167b9b07053633a4f rls-cc-incoming ubiquity-2.15.15 verification-needed verification-needed-bionic |
amd64 apport-bug cosmic id-5bacf4d167b9b07053633a4f rls-cc-incoming ubiquity-2.15.15 verification-done verification-done-bionic |
|
2019-01-31 11:52:25 |
Launchpad Janitor |
ubiquity (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|