pk-client-error-quark: Error while installing package: 1.1494 (313)
Same thing happened when downloading the 510 drivers from the ubuntu additional drivers repo. I had started out using the 470 drivers. Everything was working fine except that I couldn't use my nvidia Geforce 1030 graphics card as an encoder for OBS. I checked the Nvidia drivers webpage and found that there were more up to date drivers available, namely the 510. I installed it through the Ubuntu software and updates "additional drivers" tab and thought everything was okay. I tried running minecraft but couldn't get past the initial loading page in the launcher before the computer crashed. I rebooted and tried again a few times to no avail. I tried switching back to the 470 driver through the same means as earlier, which resulted in a system program error message pop up. I cancelled the report problem prompt and then cancelled the driver install process then rebooted the computer again. On boot, after an ubuntu loading screen that usually only pops up during updates then a scrolling screen of commands, a command prompt popped up with the previous line saying,
" /dev/(4 charateres, first one was a d the third was a 2, cannot remember the rest) :Clean big number/ bigger number Files big number/ bigger number (i think this one said Programs) ".
After a few seconds it disappeared and brought me to the login screen as per usual, except the system no longer had a graphics driver in use and each time I attempted to install either the 470 or the 510, the system program error would pop up along with another prompt that told me something was wrong with the dpkg and to run "dpkg --configure -a" to fix it. I did so then tried to install again only to receive another error message stating "pk-client-
Release of ubuntu in use :
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
1. The message during boot showing something like
/dev/sda1: clean, 552599/6111232 files, 7119295/24414464 blocks
is perfectly normal and does not indicate any problem or error.
It is the result of running a file system check which normally happens at every boot. Depending on your graphics adapter and driver and speed of hard disk, the message may be shown very short only or longer.
2. For diagnosing the driver problem and the dpkg message:
Please open a terminal window and enter the following commands:
uname -a
lsb_release -crid
sudo dpkg --configure -a
and then copy all output and paste it into this question document.
Revision history for this message
|
#2 |
uname -a
Linux user01-OptiPlex-790 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal
sudo dpkg --configure -a
[sudo] password for user01:
dpkg: error processing package libnvidia-
package libnvidia-
Errors were encountered while processing:
libnvidia-
Revision history for this message
|
#3 |
Ok, please execute the commands
sudo dpkg --audit
sudo apt install -f
and copy/paste the output as done before.
Revision history for this message
|
#4 |
sudo dpkg --audit
The following packages are in a mess due to serious problems during
installation. They must be reinstalled for them (and any packages
that depend on them) to function properly:
libnvidia-
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
libnvidia-
sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libxnvctrl0 nvidia-settings screen-
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0 B/31.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
dpkg: error processing package libnvidia-
package libnvidia-
te-470:amd64 is not ready (current status 'half-installed')
Errors were encountered while processing:
libnvidia-
E: Sub-process /usr/bin/dpkg returned an error code (1)
Revision history for this message
|
#5 |
Run the commands
sudo apt install --reinstall libnvidia-
and report the results.
Revision history for this message
|
#6 |
sudo apt install --reinstall libnvidia-
[sudo] password for user01:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libxnvctrl0 nvidia-settings screen-
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0 B/31.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for libnvidia-
Revision history for this message
|
#7 |
ok, next attempt with:
sudo apt install --reinstall libnvidia-
Revision history for this message
|
#8 |
sudo apt install --reinstall libnvidia-
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libxnvctrl0 nvidia-settings screen-
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 0 B/31.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
E: Internal Error, No file name for libnvidia-
Revision history for this message
|
#9 |
That message is a bit unexpected.
Try
sudo dpkg --purge libnvidia-
sudo apt install --reinstall libnvidia-
Revision history for this message
|
#10 |
sudo dpkg --purge libnvidia-
[sudo] password for user01:
(Reading database ... 359170 files and directories currently installed.)
Removing libnvidia-
Processing triggers for libc-bin (2.31-0ubuntu9.9) ...
sudo apt install --reinstall libnvidia-
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libxnvctrl0 nvidia-settings screen-
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/31.5 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 359158 files and directories currently installed.)
Preparing to unpack .../libnvidia-
deb ...
Unpacking libnvidia-
9.06-0ubuntu0.
Setting up libnvidia-
Processing triggers for libc-bin (2.31-0ubuntu9.9) ...
So do I try installing the graphics driver again now? If so, do I try the one I was using before being the 470, or should I go for the more up to date driver, the 510?
Revision history for this message
|
#11 |
Ok, the package management system is back in a consistent status.
My suggestion is using the command line instead of the "additional drivers" tab in software center, because you get more error messages in case that something goes wrong.
The commands to execute are
sudo apt install nvidia-driver-470
and/or
sudo apt install nvidia-driver-510
I cannot give recommendations which driver to try, because I do not own such NVidia device myself.
Revision history for this message
|
#12 |
I installed the 510 driver and it worked. I rebooted the computer and tried accessing nvidia-settings and everything seems to be in order until I tried to run minecraft again. Just as before, on start up in the launcher page, the computer crashes. Is this a Nvidia problem at this point or Ubuntu?
Revision history for this message
|
#13 |
What are the symptoms of the crash? Error messages? Complete freeze? Anything in the system logs?
Revision history for this message
|
#14 |
After hitting the play button on the game launcher, it starts loading like usual until it trys to bring up the actual game window, at which point my screen goes black for a few seconds before bringing me back to the computer log in screen. After log in I receive a system error message that asks if I want to send a report in. I can recreate the crash if you can tell me how to check the logs.
Revision history for this message
|
#15 |
In such case you should see something in the system logs.
When that happens and you log in again, what is the output of the command
dmesg | tail
and what is the command of the command
ls -l /var/crash
Revision history for this message
|
#16 |
dmesg | tail
[ 113.639912] audit: type=1326 audit(165332356
[ 115.014071] audit: type=1107 audit(165332356
[ 115.014575] audit: type=1107 audit(165332356
[ 115.026865] audit: type=1107 audit(165332356
[ 115.027210] audit: type=1107 audit(165332356
[ 115.117738] audit: type=1400 audit(165332356
ls -l /var/crash
total 5124
-rw-r----- 1 root whoopsie 217297 May 22 12:41 libnvidia-
-rw-r--r-- 1 root whoopsie 0 May 22 12:41 libnvidia-
-rw------- 1 whoopsie whoopsie 37 May 22 12:41 libnvidia-
-rw------- 1 root whoopsie 408326 May 22 14:08 libnvidia-
-rw-r----- 1 root whoopsie 4606221 May 23 12:32 _usr_lib_
-rw-r--r-- 1 root whoopsie 0 May 22 12:41 _usr_lib_
-rw------- 1 whoopsie whoopsie 37 May 22 12:41 _usr_lib_
Revision history for this message
|
#17 |
Not really helpful.
I suggest to repeat it this way:
sudo rm /var/crash/*
start minecraft such that it crashes
log in again and execute
dmesg | tail -n 30
Revision history for this message
|
#18 |
dmesg | tail -n 30
[ 2273.935155] audit: type=1400 audit(165332586
[ 2273.935206] audit: type=1400 audit(165332586
[ 2273.935298] audit: type=1400 audit(165332586
[ 2273.935425] audit: type=1400 audit(165332586
[ 2285.814603] kauditd_printk_skb: 8 callbacks suppressed
[ 2285.814606] audit: type=1400 audit(165332588
[ 2285.814781] audit: type=1400 audit(165332588
[ 2285.814785] audit: type=1400 audit(165332588
[ 2286.423787] audit: type=1400 audit(165332588
[ 2286.560644] audit: type=1400 audit(165332588
[ 2287.227808] audit: type=1400 audit(165332588
[ 2287.227816] audit: type=1400 audit(165332588
[ 2292.804686] audit: type=1107 audit(165332588
[ 2292.805003] audit: type=1107 audit(165332588
[ 2294.363162] rfkill: input handler enabled
[ 2294.631331] rfkill: input handler disabled
[ 2300.191999] rfkill: input handler enabled
[ 2303.064133] rfkill: input handler disabled
[ 2303.638053] audit: type=1326 audit(165332589
[ 2304.453847] audit: type=1107 audit(165332589
[ 2304.454145] audit: type=1107 audit(165332589
[ 2304.465077] audit: type=1107 audit(165332589
[ 2304.465379] audit: type=1107 audit(165332589
[ 2304.557167] audit: type=1400 audit(165332589
Revision history for this message
|
#19 |
Because of those apparmor messages the important messages are hard to see.
Try again with the command
dmesg | grep -v 'audit:' | tail -n 30
Revision history for this message
|
#20 |
dmesg | grep -v 'audit:' | tail -n 30
[ 4251.715605] ata1.00: supports DRM functions and may not be fully accessible
[ 4251.716351] ata1.00: Trusted Computing capability qword not valid!
[ 4251.716737] ata1.00: supports DRM functions and may not be fully accessible
[ 4251.717329] ata1.00: Trusted Computing capability qword not valid!
[ 4251.717332] ata1.00: configured for UDMA/133
[ 4251.717941] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 4251.736084] ata3.00: configured for UDMA/100
[ 4252.105140] rfkill: input handler disabled
[ 4252.234951] e1000e 0000:00:19.0 eno1: NIC Link is Down
[ 4255.349763] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 4255.349862] IPv6: ADDRCONF(
[ 4335.626364] kauditd_printk_skb: 8 callbacks suppressed
[ 4344.322968] rfkill: input handler enabled
[ 4344.579874] rfkill: input handler disabled
[ 4349.859932] rfkill: input handler enabled
[ 4352.710538] rfkill: input handler disabled
[ 4355.947476] rfkill: input handler enabled
[ 4356.707159] rfkill: input handler disabled
[ 4362.695514] rfkill: input handler enabled
[ 4365.206185] rfkill: input handler disabled
Revision history for this message
|
#21 |
Try again with
dmesg | grep -v -e 'audit:' -e rfkill -e dbus-daemon | tail -n 100
immediately after logging in after a crash
Revision history for this message
|
#22 |
dmesg | grep -v -e 'audit:' -e rfkill -e dbus-daemon | tail -n 100
[ 2122.801410] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 2122.801417] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 2122.801422] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 2122.958784] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2122.959077] ata1.00: supports DRM functions and may not be fully accessible
[ 2122.959819] ata1.00: Trusted Computing capability qword not valid!
[ 2122.960212] ata1.00: supports DRM functions and may not be fully accessible
[ 2122.960856] ata1.00: Trusted Computing capability qword not valid!
[ 2122.960860] ata1.00: configured for UDMA/133
[ 2122.961058] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2122.979232] ata3.00: configured for UDMA/100
[ 2123.460273] e1000e 0000:00:19.0 eno1: NIC Link is Down
[ 2126.634681] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 2126.634740] IPv6: ADDRCONF(
[ 2285.814603] kauditd_printk_skb: 8 callbacks suppressed
[ 4250.153150] PM: suspend entry (deep)
[ 4250.160503] Filesystems sync: 0.007 seconds
[ 4250.160613] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 4250.162782] OOM killer disabled.
[ 4250.162783] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 4250.164030] printk: Suspending console(s) (use no_console_suspend to debug)
[ 4250.199677] serial 00:03: disabled
[ 4250.200097] e1000e: EEE TX LPI TIMER: 00000011
[ 4250.268957] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 4250.269483] sd 0:0:0:0: [sda] Stopping disk
[ 4251.303311] ACPI: Preparing to enter system sleep state S3
[ 4251.303557] PM: Saving platform NVS memory
[ 4251.303575] Disabling non-boot CPUs ...
[ 4251.303973] IRQ 30: no longer affine to CPU1
[ 4251.304980] smpboot: CPU 1 is now offline
[ 4251.305756] IRQ 27: no longer affine to CPU2
[ 4251.306762] smpboot: CPU 2 is now offline
[ 4251.307523] IRQ 18: no longer affine to CPU3
[ 4251.308531] smpboot: CPU 3 is now offline
[ 4251.309810] ACPI: Low-level resume complete
[ 4251.309831] PM: Restoring platform NVS memory
[ 4251.310876] Enabling non-boot CPUs ...
[ 4251.310919] x86: Booting SMP configuration:
[ 4251.310919] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 4251.314024] CPU1 is up
[ 4251.314052] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 4251.317170] CPU2 is up
[ 4251.317196] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 4251.320416] CPU3 is up
[ 4251.322678] ACPI: Waking up from system sleep state S3
[ 4251.381255] serial 00:03: activated
[ 4251.390480] sd 0:0:0:0: [sda] Starting disk
[ 4251.507661] OOM killer enabled.
[ 4251.507662] Restarting tasks ...
[ 4251.508085] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 4251.508090] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 4251.508095] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 4251.508099] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 4251.509224] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 4251.509229] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 4251.509234] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 4251.509238] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 4251.509276] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 4251.509278] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 4251.509282] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 4251.509286] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 4251.509301] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 4251.509304] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 4251.509308] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 4251.509310] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 4251.509324] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 4251.509327] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 4251.509330] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 4251.509334] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 4251.509441] pci_bus 0000:02: Allocating resources
[ 4251.509453] pci_bus 0000:03: Allocating resources
[ 4251.509456] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 4251.509458] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 4251.509462] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 4251.509465] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 4251.509506] pci_bus 0000:01: Allocating resources
[ 4251.509513] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 4251.509515] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 4251.509520] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 4251.509523] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 4251.509586] pci_bus 0000:04: Allocating resources
[ 4251.509589] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 4251.509591] pci 0000:00:1e.0: bridge window [io 0x6000-0x6fff]
[ 4251.509595] pci 0000:00:1e.0: bridge window [mem 0xe4c00000-
[ 4251.509598] pci 0000:00:1e.0: bridge window [mem 0xe4e00000-
[ 4251.515344] done.
[ 4251.515373] PM: suspend exit
[ 4251.715317] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 4251.715605] ata1.00: supports DRM functions and may not be fully accessible
[ 4251.716351] ata1.00: Trusted Computing capability qword not valid!
[ 4251.716737] ata1.00: supports DRM functions and may not be fully accessible
[ 4251.717329] ata1.00: Trusted Computing capability qword not valid!
[ 4251.717332] ata1.00: configured for UDMA/133
[ 4251.717941] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 4251.736084] ata3.00: configured for UDMA/100
[ 4252.234951] e1000e 0000:00:19.0 eno1: NIC Link is Down
[ 4255.349763] e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 4255.349862] IPv6: ADDRCONF(
[ 4335.626364] kauditd_printk_skb: 8 callbacks suppressed
[ 5648.644087] kauditd_printk_skb: 8 callbacks suppressed
Revision history for this message
|
#23 |
I am sorry, but I am at my wits' end. I do not see anything in the dmesg log that is related to the crash. I assume that he big gaps (2285.814603 to 4250.153150 and 4335.626364 to 5648.644087) are the periods around the crash.
Are there now again files in /var/crash?
Revision history for this message
|
#24 |
only this
ls -l /var/crash
total 5272
-rw-r----- 1 root whoopsie 5395517 May 23 13:46 _usr_lib_
Revision history for this message
|
#25 |
What you could try is using that crash file for reporting again.
Maybe an expert picks it up and is able to identify the root cause.
sudo ubuntu-bug /var/crash/
Revision history for this message
|
#26 |
Crash file reported. Thank you for helping me out with this. If I am able to figure out what the problem was and how to fix it, should I leave it as a comment to this thread?
Revision history for this message
|
#27 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.