nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| linux (Ubuntu) |
Undecided
|
Unassigned | ||
| nvidia-graphics-drivers (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Hello,
When installing `nvidia-340` there is an error is the postinst script:
philippe@
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade.
Need to get 0 B/51.9 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 309892 files and directories currently installed.)
Preparing to unpack .../nvidia-
Stopping nvidia-persistenced
nvidia-
Done.
(snip)
Setting up nvidia-340 (340.107-
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia-340
DEBUG:Parsing /usr/share/
DEBUG:Parsing /usr/share/
DEBUG:Parsing /usr/share/
Loading new nvidia-340-340.107 DKMS files...
Building for 4.15.0-70-generic
Building for architecture x86_64
Building initial module for 4.15.0-70-generic
Done.
The comment at https:/
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
Launchpad Janitor (janitor) wrote : | #2 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in nvidia-graphics-drivers (Ubuntu): | |
status: | New → Confirmed |
Wowbagger (ha87psc02) wrote : | #3 |
This is a stupid uninitialized variable error in the postinstall script:
case "$1" in
configure)
# Added manually, since we mangled the arguments, and dpkg-maintscrip
# won't work
if [ -n "$2" ] && `dpkg --compare-versions "$2" lt "340.106-
rm -f /etc/modprobe.
fi
Variable "KERNELS" is not defined, so when get_newest_kernel tries to use dpkg to look up the kernel version it fails.
Defining "KERNELS" to be CURRENT_KERNEL allows the configure to work:
case "$1" in
configure)
# Added manually, since we mangled the arguments, and dpkg-maintscrip
# won't work
if [ -n "$2" ] && `dpkg --compare-versions "$2" lt "340.106-
rm -f /etc/modprobe.
fi
Seriously - this has been an issue for over a year, and nobody bothered to look into it?
Note that the fix was mentionned in the original report.
I usually don't comment for this but I thought if there was more comments more people would notice :-)
Kevin K (stafio) wrote : apport information | #5 |
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/seq: kevin 1033 F.... pipewire
CasperMD5CheckR
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.10
InstallationDate: Installed on 2020-07-26 (99 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
Package: nvidia-
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.190
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: groovy
Uname: Linux 5.8.0-26-generic x86_64
UpgradeStatus: Upgraded to groovy on 2020-10-26 (7 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare scanner sudo
_MarkForUpload: True
dmi.bios.date: 08/23/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1104
dmi.board.
dmi.board.name: P8Z77-V LK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.
dmi.sys.vendor: System manufacturer
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: apport-collected groovy |
Kevin K (stafio) wrote : AlsaInfo.txt | #6 |
apport information
Kevin K (stafio) wrote : CRDA.txt | #7 |
apport information
Kevin K (stafio) wrote : CurrentDmesg.txt | #8 |
apport information
Kevin K (stafio) wrote : IwConfig.txt | #9 |
apport information
Kevin K (stafio) wrote : Lspci.txt | #10 |
apport information
Kevin K (stafio) wrote : Lspci-vt.txt | #11 |
apport information
Kevin K (stafio) wrote : Lsusb.txt | #12 |
apport information
Kevin K (stafio) wrote : Lsusb-t.txt | #13 |
apport information
Kevin K (stafio) wrote : Lsusb-v.txt | #14 |
apport information
Kevin K (stafio) wrote : PaInfo.txt | #15 |
apport information
Kevin K (stafio) wrote : ProcCpuinfo.txt | #16 |
apport information
apport information
Kevin K (stafio) wrote : ProcEnviron.txt | #18 |
apport information
Kevin K (stafio) wrote : ProcInterrupts.txt | #19 |
apport information
Kevin K (stafio) wrote : ProcModules.txt | #20 |
apport information
Kevin K (stafio) wrote : PulseList.txt | #21 |
apport information
Kevin K (stafio) wrote : UdevDb.txt | #22 |
apport information
Kevin K (stafio) wrote : WifiSyslog.txt | #23 |
apport information
Kevin K (stafio) wrote : acpidump.txt | #24 |
apport information
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1853977
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.