aptdeaemon 1.1.1-1ubuntu5.2 is crashing
searching google, I do not see a recent solution to why aptdeaemon 1.1.1-1ubuntu5.2 is crashing each time I do an upgrade from either the desktop or the command line using 'apt-get dist-upgrade'. How do I repair my system?
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Ubuntu aptdaemon Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Please provide the full output of the commands
uname -a
lsb_release -crid
sudo apt-get update
sudo apt-get dist-upgrade
when executed in a terminal window.
Revision history for this message
|
#2 |
sudo apt-get dist-upgrade just abends without running, lsb_release-crib is
not installed, let me know how, and I'll install it if necessary:
rollingw@
rollingw@
Linux rollingw-
10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
rollingw@
lsb_release-crib: command not found
rollingw@
[sudo] password for rollingw:
Ign http://
Ign http://
Get:1 http://
Ign http://
Ign http://
Hit http://
Hit http://
Get:2 http://
Get:3 http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:4 http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Get:5 http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Get:6 http://
Hit http://
Ign http://
Hit http://
Get:7 http://
Hit http://
Ign https:/
Ign https:/
Hit http://
Hit http://
Hit http://
Get:8 http://
B]
Hit http://
Ign https:/
Hit https:/
Get:9 http://
Hit https:/
Get:10 http://
[5,939 B]
Get:11 http://
B]
Hit http://
Hit http://
Hit https:/
Ign http://
Hit https:/
Hit https:/
Hit https:/
Hit http://
Get:12 http://
kB]
Get:13 http://
kB]
Hit http://
Hit http://
Ign http://
Hit https:/
Hit http://
Hit https:/
Hit https:/
Get:14 http://
B]
Hit http://
Ign http://
Hit https:/
Hit https:/
Ign http://
Get:15 http://
Packages [15.9 kB]
Get:16 http://
kB]
Hit http://
Hit https:/
Hit https:/
Get:17 http://
[360 kB]
Get:18 http://
Hit https:/
Get:19 https:/
Hit http://
Get:20 http://
Packages [13.2 kB]
Get:21 http://
Get:22 http://
kB]
Ign http://
Get:23 http://
Get:24 http://
[13.0 kB]
Hit http://
Ign http://
Hit http://
Get:25 http://
[15.6 kB]
Get:26 http://
[129 kB]
Get:27 http://
[361 kB]
Ign https:/
Ign http://
Hit http://
Get:28 http://
[4,978 B]
Ign https:/
Ign https:/
Ign https:/
Get:29 http://
[13.6 kB]
Get:30 http://
kB]
Get:31 http://
kB]
Ign http://
Hit http://
Ign https:/
Hit http://
Get:32 http://
[12.7 kB]
Get:33 http://
Translation-en [7,227 B]
Get:34 http://
Translation-en [3,699 B]
Ign https:/
Hit http://
Get:35 http://
[129 kB]
Get:36 http://
[189 kB]
Hit http://
Hit http://
Get:37 http://
[5,168 B]
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Ign https:/
Hit http://
Hit http://
Hit http://
Hit http://
Ign https:/
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Fetched 4,859 kB in 9s (539 kB/s)
Reading package lists... Done
W: GPG error: http://
signatures couldn't be verified because the public key is not available:
NO_PUBKEY A1715D88E1DF1F24
W: There is no public key available for the following key IDs:
1397BC53640DB551
rollingw@
On Fri, May 27, 2016 at 8:43 AM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Please provide the full output of the commands
>
> uname -a
> lsb_release -crid
> sudo apt-get update
> sudo apt-get dist-upgrade
>
> when executed in a terminal window.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#3 |
You better use copy and paste, because you mistyped one of my commands (does not really matter in this case).
I do not see any "crash", just a warning about a missing cryptographic key.
Execute the command
sudo apt-key adv --recv-keys --keyserver keyserver.
and then re-try
sudo apt-get update
sudo apt-get dist-upgrade
and copy/paste all output into this question document.
Revision history for this message
|
#4 |
below, after printing 'calculating upgrade', a modal dialog box appears on
the desktop saying Ubuntu has experienced a problem, with buttons to report
the issue:
rollingw@
Linux rollingw-
10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
rollingw@
lsb_release-crib: command not found
rollingw@
[sudo] password for rollingw:
Ign http://
Ign http://
Get:1 http://
Ign http://
Ign http://
Hit http://
Hit http://
Get:2 http://
Get:3 http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:4 http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Get:5 http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Get:6 http://
Hit http://
Ign http://
Hit http://
Get:7 http://
Hit http://
Ign https:/
Ign https:/
Hit http://
Hit http://
Hit http://
Get:8 http://
B]
Hit http://
Ign https:/
Hit https:/
Get:9 http://
Hit https:/
Get:10 http://
[5,939 B]
Get:11 http://
B]
Hit http://
Hit http://
Hit https:/
Ign http://
Hit https:/
Hit https:/
Hit https:/
Hit http://
Get:12 http://
kB]
Get:13 http://
kB]
Hit http://
Hit http://
Ign http://
Hit https:/
Hit http://
Hit https:/
Hit https:/
Get:14 http://
B]
Hit http://
Ign http://
Hit https:/
Hit https:/
Ign http://
Get:15 http://
Packages [15.9 kB]
Get:16 http://
kB]
Hit http://
Hit https:/
Hit https:/
Get:17 http://
[360 kB]
Get:18 http://
Hit https:/
Get:19 https:/
Hit http://
Get:20 http://
Packages [13.2 kB]
Get:21 http://
Get:22 http://
kB]
Ign http://
Get:23 http://
Get:24 http://
[13.0 kB]
Hit http://
Ign http://
Hit http://
Get:25 http://
[15.6 kB]
Get:26 http://
[129 kB]
Get:27 http://
[361 kB]
Ign https:/
Ign http://
Hit http://
Get:28 http://
[4,978 B]
Ign https:/
Ign https:/
Ign https:/
Get:29 http://
[13.6 kB]
Get:30 http://
kB]
Get:31 http://
kB]
Ign http://
Hit http://
Ign https:/
Hit http://
Get:32 http://
[12.7 kB]
Get:33 http://
Translation-en [7,227 B]
Get:34 http://
Translation-en [3,699 B]
Ign https:/
Hit http://
Get:35 http://
[129 kB]
Get:36 http://
[189 kB]
Hit http://
Hit http://
Get:37 http://
[5,168 B]
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Ign https:/
Hit http://
Hit http://
Hit http://
Hit http://
Ign https:/
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Fetched 4,859 kB in 9s (539 kB/s)
Reading package lists... Done
W: GPG error: http://
signatures couldn't be verified because the public key is not available:
NO_PUBKEY A1715D88E1DF1F24
W: There is no public key available for the following key IDs:
1397BC53640DB551
rollingw@
rollingw@
rollingw@
keyserver.
[sudo] password for rollingw:
rollingw@
Ign http://
Ign http://
Ign http://
Hit http://
Hit http://
Hit http://
Get:1 http://
Hit http://
Hit http://
Get:2 http://
Ign http://
Ign http://
Get:3 http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Get:4 http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:5 http://
B]
Get:6 http://
Get:7 http://
Hit http://
Ign https:/
Hit http://
Ign https:/
Ign https:/
Hit https:/
Hit https:/
Get:8 http://
B]
Hit https:/
Ign http://
Hit http://
Hit http://
Hit https:/
Ign http://
Ign http://
Get:9 http://
kB]
Get:10 http://
B]
Hit http://
Hit http://
Hit https:/
Ign http://
Hit https:/
Ign http://
Get:11 http://
Packages [15.9 kB]
Ign http://
Hit http://
Get:12 http://
kB]
Hit https:/
Hit http://
Hit https:/
Get:13 http://
[360 kB]
Hit http://
Hit https:/
Get:14 http://
B]
Hit http://
Hit https:/
Get:15 http://
Packages [13.2 kB]
Hit http://
Get:16 http://
kB]
Get:17 http://
kB]
Hit http://
Hit https:/
Hit https:/
Hit http://
Hit http://
Hit https:/
Get:18 http://
[15.6 kB]
Hit http://
Get:19 http://
[361 kB]
Hit https:/
Get:20 http://
[13.0 kB]
Hit http://
Hit http://
Get:21 http://
[13.6 kB]
Get:22 http://
[129 kB]
Get:23 https:/
Hit http://
Hit http://
Ign https:/
Ign https:/
Ign https:/
Ign https:/
Get:24 http://
[4,978 B]
Hit http://
Hit http://
Hit http://
Get:25 http://
kB]
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:26 http://
[12.7 kB]
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign https:/
Get:27 http://
[129 kB]
Ign http://
Hit http://
Ign http://
Hit http://
Hit http://
Ign https:/
Hit http://
Get:28 http://
[5,168 B]
Ign http://
Hit http://
Hit http://
Ign https:/
Hit http://
Hit http://
Hit http://
Ign https:/
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Fetched 4,259 kB in 9s (464 kB/s)
Reading package lists... Done
W: There is no public key available for the following key IDs:
1397BC53640DB551
W: GPG error: http://
signatures couldn't be verified because the public key is not available:
NO_PUBKEY A1715D88E1DF1F24
rollingw@
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... rollingw@
dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... rollingw@
On Sat, May 28, 2016 at 9:13 AM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> You better use copy and paste, because you mistyped one of my commands
> (does not really matter in this case).
>
> I do not see any "crash", just a warning about a missing cryptographic
> key.
>
> Execute the command
>
> sudo apt-key adv --recv-keys --keyserver keyserver.
>
> and then re-try
>
> sudo apt-get update
> sudo apt-get dist-upgrade
>
> and copy/paste all output into this question document.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#5 |
Strange.
The command
sudo apt-key adv --recv-keys --keyserver keyserver.
should provide a few lines of output or an error message. In your case it doesn't show anything.
Try again with
sudo apt-key adv --recv-keys --keyserver keyserver.
and for completeness' sake please provide also the output of the other command which should have been
lsb_release -crid
Revision history for this message
|
#6 |
rollingw@
keyserver.
[sudo] password for rollingw:
rollingw@
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty
rollingw@
On Sat, May 28, 2016 at 9:32 AM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Strange.
>
> The command
> sudo apt-key adv --recv-keys --keyserver keyserver.
> should provide a few lines of output or an error message. In your case it
> doesn't show anything.
>
> Try again with
>
> sudo apt-key adv --recv-keys --keyserver keyserver.
> E1DF1F24
>
> and for completeness' sake please provide also the output of the other
> command which should have been
>
> lsb_release -crid
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#7 |
Please provide also the output of
sudo apt-key adv --recv-keys --keyserver keyserver.
as asked in the last response.
Revision history for this message
|
#8 |
again, no response:
rollingw@
keyserver.
[sudo] password for rollingw:
rollingw@
is there a space between 1 and E?
On Sat, May 28, 2016 at 12:07 PM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Please provide also the output of
>
> sudo apt-key adv --recv-keys --keyserver keyserver.
> E1DF1F24
>
> as asked in the last response.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#9 |
It should have been two groups of eight characters with a space between, but also with a wrong key value it should not show 'no output'
What output do you get for the command
sudo sh -x /usr/bin/apt-key adv --recv-keys --keyserver keyserver.
Revision history for this message
|
#10 |
odd, same result
rollingw@
keyserver.
[sudo] password for rollingw:
rollingw@
I just installed a screen capture app, and it kicked some errors but then
worked.
On Sun, May 29, 2016 at 11:07 AM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> It should have been two groups of eight characters with a space between,
> but also with a wrong key value it should not show 'no output'
>
> What output do you get for the command
>
> sudo sh -x /usr/bin/apt-key adv --recv-keys --keyserver
> keyserver.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#11 |
Please provide the output of
sudo sh -x /usr/bin/apt-key adv --recv-keys --keyserver keyserver.
as asked in my last response.
Revision history for this message
|
#12 |
Hi, sorry about that:
rollingw@
--recv-keys --keyserver keyserver.
[sudo] password for rollingw:
+ set -e
+ unset GREP_OPTIONS
+ GPG_CMD=gpg --ignore-
+ mktemp -d
+ GPGHOMEDIR=
+ CURRENTTRAP= rm -rf '/tmp/tmp.
+ trap rm -rf '/tmp/tmp.
TERM
+ chmod 700 /tmp/tmp.vr5kJ1wXlJ
+ SECRETKEYRING=
+ touch /tmp/tmp.
+ GPG_CMD=gpg --ignore-
--homedir /tmp/tmp.vr5kJ1wXlJ
+ gpg --ignore-
/tmp/tmp.vr5kJ1wXlJ --quiet --check-trustdb --keyring
/tmp/tmp.
+ rm -rf /tmp/tmp.vr5kJ1wXlJ
rollingw@
On Mon, May 30, 2016 at 1:03 AM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Please provide the output of
>
> sudo sh -x /usr/bin/apt-key adv --recv-keys --keyserver
> keyserver.
>
> as asked in my last response.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#13 |
On my system that command produces much more output.
It seems that the first gpg command on your system leads to an abort of the script.
What is the output of
gpg --version
Revision history for this message
|
#14 |
It's abending:
rollingw@
gpg: symbol lookup error: /usr/local/
symbol: UP
rollingw@
On Mon, May 30, 2016 at 8:17 AM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> On my system that command produces much more output.
> It seems that the first gpg command on your system leads to an abort of
> the script.
>
> What is the output of
>
> gpg --version
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#15 |
Ok, it seems that this is the root cause. Apparently you have mixed program versions from different sources, that now do not correctly cooperate. (libreadline.so.6 should be in /lib/x86_
Now we have to find a way to repair it.
What is the output of the commands
sudo updatedb
locate libreadline
which gpg
ldd `which gpg`
apt-cache policy gpg libreadline6
Revision history for this message
|
#16 |
sorry for the delay, completely missed your reply here. Here's the output:
rollingw@
rollingw@
[sudo] password for rollingw:
rollingw@
/home/rollingw/
/home/rollingw/
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
/opt/hdd-
/usr/lib/
/usr/lib/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
/var/lib/
rollingw@
/usr/bin/gpg
rollingw@
linux-vdso.so.1 => (0x00007fff1f9b
libresolv.so.2 => /lib/x86_
libz.so.1 => /lib/x86_
libbz2.so.1.0 => /lib/x86_
libreadline.so.6 => /usr/local/
libdl.so.2 => /lib/x86_
libusb-0.1.so.4 => /lib/x86_
(0x00007fdadb12
libc.so.6 => /lib/x86_
/lib64/
rollingw@
libreadline6:
Installed: 6.3-4ubuntu2
Candidate: 6.3-4ubuntu2
Version table:
*** 6.3-4ubuntu2 0
500 http://
100 /var/lib/
N: Unable to locate package gpg
rollingw@
On Mon, May 30, 2016 at 9:17 AM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Ok, it seems that this is the root cause. Apparently you have mixed
> program versions from different sources, that now do not correctly
> cooperate. (libreadline.so.6 should be in /lib/x86_
> not in /usr/local/lib)
>
> Now we have to find a way to repair it.
>
> What is the output of the commands
>
> sudo updatedb
> locate libreadline
> which gpg
> ldd `which gpg`
> apt-cache policy gpg libreadline6
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#17 |
Do you have an idea where the /usr/local/
What is the output of
echo $LD_LIBRARY_PATH
cat /etc/ld.so.conf /etc/ld.so.conf.d/*
ls /usr/local/lib
Revision history for this message
|
#18 |
No idea on where that's from, here's the output:
rollingw@
rollingw@
include /etc/ld.
/usr/lib/
/usr/lib/
# Multiarch support
/lib/i386-linux-gnu
/usr/lib/
/lib/i686-linux-gnu
/usr/lib/
# libc default configuration
/usr/local/lib
# Multiarch support
/lib/x86_
/usr/lib/
/usr/lib/
/usr/lib/
# Legacy biarch compatibility support
/lib32
/usr/lib32
# Legacy biarch compatibility support
/libx32
/usr/libx32
rollingw@
elixir libhistory.so.6.3 libreadline.so.6 python2.7
libhistory.a libhistory.
libhistory.old libreadline.a libreadline.
libhistory.so libreadline.old node_modules
libhistory.so.6 libreadline.so perl
rollingw@
On Fri, Jun 10, 2016 at 7:42 AM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Do you have an idea where the /usr/local/
> stems from?
>
> What is the output of
> echo $LD_LIBRARY_PATH
> cat /etc/ld.so.conf /etc/ld.so.conf.d/*
> ls /usr/local/lib
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#19 |
I suggest that you delete all libreadline.* files from /usr/local/lib, then run "sudo ldconfig" and finally retry "gpg --version"
I hope that this will not break anything else.
Revision history for this message
|
#20 |
I'm going to purchase a NAS backup device and do a test restore just to be
safe, I don't want to lose my system, I use it for trading. Please keep
this ticket open and I'll give this a try once I have a backup and restore
in place.
On Fri, Jun 10, 2016 at 12:02 PM, Manfred Hampl <
<email address hidden>> wrote:
> Your question #294478 on aptdaemon in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> I suggest that you delete all libreadline.* files from /usr/local/lib,
> then run "sudo ldconfig" and finally retry "gpg --version"
>
> I hope that this will not break anything else.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#21 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.