Upgrade from 16.04 to 18.04 broke apt
How I got to where I am now:
I started the upgrade from Ubuntu GNOME 16.04 to 18.04.
Everything went fine until I was asked to reboot.
It got stuck at displaying /dev/sdb6: clean 723689/3620864 files, 11918552/14478592 blocks.
I switched into tty4.
There it said
Welcome to Ubuntu 18.04 LTS....
...
...
*** System restart required ***...
...
So following some other Ask Ubuntu answers I tried
sudo dpkg --configure -a
which didn't work. Then I did
sudo dpkg --configure -a --force-depends
After that, I did
sudo apt --fix-broken
Then I rebooted. It booted correctly into Ubuntu GNOME.
I did apt update
The actual problem:
apt seems to be broken:
When I do apt upgrade it returns:
Some package could not be installed. This may mean
that you have requested an impossible situatio
or if you are using the unstable distribution that some required
packages have not been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-aptdaemon.pkcompat : Conflicts: packagekit
Conflicts: packagekit:i386
E: Broken packages
How could I fix that?
If you need more information, feel free to ask.
(Also, if this is somehow important: DNS wasn't working until I manually added 8.8.8.8 to resolv.conf)
apt 18.04 upgrade
asked Jan 20 at 21:23
Unknown UserUnknown User
144
add a comment |
How I got to where I am now:
I started the upgrade from Ubuntu GNOME 16.04 to 18.04.
Everything went fine until I was asked to reboot.
It got stuck at displaying /dev/sdb6: clean 723689/3620864 files, 11918552/14478592 blocks.
I switched into tty4.
There it said
Welcome to Ubuntu 18.04 LTS....
...
...
*** System restart required ***...
...
So following some other Ask Ubuntu answers I tried
sudo dpkg --configure -a
which didn't work. Then I did
sudo dpkg --configure -a --force-depends
After that, I did
sudo apt --fix-broken
Then I rebooted. It booted correctly into Ubuntu GNOME.
I did apt update
The actual problem:
apt seems to be broken:
When I do apt upgrade it returns:
Some package could not be installed. This may mean
that you have requested an impossible situatio
or if you are using the unstable distribution that some required
packages have not been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-aptdaemon.pkcompat : Conflicts: packagekit
Conflicts: packagekit:i386
E: Broken packages
How could I fix that?
If you need more information, feel free to ask.
(Also, if this is somehow important: DNS wasn't working until I manually added 8.8.8.8 to resolv.conf)
apt 18.04 upgrade
asked Jan 20 at 21:23
Unknown UserUnknown User
144
Hello and welcome to Ask Ubuntu! Looks likekicad-libraryit's not present in any official repository, did you install one or more PPAs? If that's the case, they should be upgraded to the new version, as they won't get upgraded automatically when changing versions.
– Mr Shunz
Jan 22 at 16:48
I could remove the kicad part by doingapt install kicad
– Unknown User
Jan 22 at 21:52
add a comment |
How I got to where I am now:
I started the upgrade from Ubuntu GNOME 16.04 to 18.04.
Everything went fine until I was asked to reboot.
It got stuck at displaying /dev/sdb6: clean 723689/3620864 files, 11918552/14478592 blocks.
I switched into tty4.
There it said
Welcome to Ubuntu 18.04 LTS....
...
...
*** System restart required ***...
...
So following some other Ask Ubuntu answers I tried
sudo dpkg --configure -a
which didn't work. Then I did
sudo dpkg --configure -a --force-depends
After that, I did
sudo apt --fix-broken
Then I rebooted. It booted correctly into Ubuntu GNOME.
I did apt update
The actual problem:
apt seems to be broken:
When I do apt upgrade it returns:
Some package could not be installed. This may mean
that you have requested an impossible situatio
or if you are using the unstable distribution that some required
packages have not been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-aptdaemon.pkcompat : Conflicts: packagekit
Conflicts: packagekit:i386
E: Broken packages
How could I fix that?
If you need more information, feel free to ask.
(Also, if this is somehow important: DNS wasn't working until I manually added 8.8.8.8 to resolv.conf)
apt 18.04 upgrade
asked Jan 20 at 21:23
Unknown UserUnknown User
144
How I got to where I am now:
I started the upgrade from Ubuntu GNOME 16.04 to 18.04.
Everything went fine until I was asked to reboot.
It got stuck at displaying /dev/sdb6: clean 723689/3620864 files, 11918552/14478592 blocks.
I switched into tty4.
There it said
Welcome to Ubuntu 18.04 LTS....
...
...
*** System restart required ***...
...
So following some other Ask Ubuntu answers I tried
sudo dpkg --configure -a
which didn't work. Then I did
sudo dpkg --configure -a --force-depends
After that, I did
sudo apt --fix-broken
Then I rebooted. It booted correctly into Ubuntu GNOME.
I did apt update
The actual problem:
apt seems to be broken:
When I do apt upgrade it returns:
Some package could not be installed. This may mean
that you have requested an impossible situatio
or if you are using the unstable distribution that some required
packages have not been created or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-aptdaemon.pkcompat : Conflicts: packagekit
Conflicts: packagekit:i386
E: Broken packages
How could I fix that?
If you need more information, feel free to ask.
(Also, if this is somehow important: DNS wasn't working until I manually added 8.8.8.8 to resolv.conf)
apt 18.04 upgrade
apt 18.04 upgrade
asked Jan 20 at 21:23
Unknown UserUnknown User
144
asked Jan 20 at 21:23
Unknown UserUnknown User
144
edited Jan 22 at 21:52
Unknown User
asked Jan 20 at 21:23
Unknown UserUnknown User
144
asked Jan 20 at 21:23
Unknown UserUnknown User
144
asked Jan 20 at 21:23
Unknown UserUnknown User
144
144
Hello and welcome to Ask Ubuntu! Looks likekicad-libraryit's not present in any official repository, did you install one or more PPAs? If that's the case, they should be upgraded to the new version, as they won't get upgraded automatically when changing versions.
– Mr Shunz
Jan 22 at 16:48
I could remove the kicad part by doingapt install kicad
– Unknown User
Jan 22 at 21:52
add a comment |
Hello and welcome to Ask Ubuntu! Looks likekicad-libraryit's not present in any official repository, did you install one or more PPAs? If that's the case, they should be upgraded to the new version, as they won't get upgraded automatically when changing versions.
– Mr Shunz
Jan 22 at 16:48
I could remove the kicad part by doingapt install kicad
– Unknown User
Jan 22 at 21:52
Hello and welcome to Ask Ubuntu! Looks like
kicad-library it's not present in any official repository, did you install one or more PPAs? If that's the case, they should be upgraded to the new version, as they won't get upgraded automatically when changing versions.– Mr Shunz
Jan 22 at 16:48
Hello and welcome to Ask Ubuntu! Looks like
kicad-library it's not present in any official repository, did you install one or more PPAs? If that's the case, they should be upgraded to the new version, as they won't get upgraded automatically when changing versions.– Mr Shunz
Jan 22 at 16:48
I could remove the kicad part by doing
apt install kicad– Unknown User
Jan 22 at 21:52
I could remove the kicad part by doing
apt install kicad– Unknown User
Jan 22 at 21:52
add a comment |
1 Answer
1
active
oldest
votes
You should remove the packages that give you errors, and then retry:
sudo apt purge python3-aptdaemon.pkcompat
sudo apt update
sudo apt upgrade # to make sure that any remaining packages get updated
After that, you should also do
sudo apt autoremove
to remove any stale package that is no more needed in the new version.
As always, it might help to do
sudo dpkg --configure -a
sudo apt --fix-broken install
again after apt update works correctly.
answered Jan 23 at 8:19
Mr ShunzMr Shunz
2,47621922
So it is safe to remove that specific package?
– Unknown User
Jan 26 at 14:59
I did what you said. After a reboot I can't use the normal GNOME anymore. Only GNOME Classic works. If login into to normal GNOME, the screen turns black and the login page opens again.
– Unknown User
Jan 26 at 15:52
(running apt upgrade returns: pastebin.com/nhyssLaE )
– Unknown User
Jan 26 at 16:03
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111486%2fupgrade-from-16-04-to-18-04-broke-apt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should remove the packages that give you errors, and then retry:
sudo apt purge python3-aptdaemon.pkcompat
sudo apt update
sudo apt upgrade # to make sure that any remaining packages get updated
After that, you should also do
sudo apt autoremove
to remove any stale package that is no more needed in the new version.
As always, it might help to do
sudo dpkg --configure -a
sudo apt --fix-broken install
again after apt update works correctly.
answered Jan 23 at 8:19
Mr ShunzMr Shunz
2,47621922
So it is safe to remove that specific package?
– Unknown User
Jan 26 at 14:59
I did what you said. After a reboot I can't use the normal GNOME anymore. Only GNOME Classic works. If login into to normal GNOME, the screen turns black and the login page opens again.
– Unknown User
Jan 26 at 15:52
(running apt upgrade returns: pastebin.com/nhyssLaE )
– Unknown User
Jan 26 at 16:03
add a comment |
You should remove the packages that give you errors, and then retry:
sudo apt purge python3-aptdaemon.pkcompat
sudo apt update
sudo apt upgrade # to make sure that any remaining packages get updated
After that, you should also do
sudo apt autoremove
to remove any stale package that is no more needed in the new version.
As always, it might help to do
sudo dpkg --configure -a
sudo apt --fix-broken install
again after apt update works correctly.
answered Jan 23 at 8:19
Mr ShunzMr Shunz
2,47621922
So it is safe to remove that specific package?
– Unknown User
Jan 26 at 14:59
I did what you said. After a reboot I can't use the normal GNOME anymore. Only GNOME Classic works. If login into to normal GNOME, the screen turns black and the login page opens again.
– Unknown User
Jan 26 at 15:52
(running apt upgrade returns: pastebin.com/nhyssLaE )
– Unknown User
Jan 26 at 16:03
add a comment |
You should remove the packages that give you errors, and then retry:
sudo apt purge python3-aptdaemon.pkcompat
sudo apt update
sudo apt upgrade # to make sure that any remaining packages get updated
After that, you should also do
sudo apt autoremove
to remove any stale package that is no more needed in the new version.
As always, it might help to do
sudo dpkg --configure -a
sudo apt --fix-broken install
again after apt update works correctly.
answered Jan 23 at 8:19
Mr ShunzMr Shunz
2,47621922
You should remove the packages that give you errors, and then retry:
sudo apt purge python3-aptdaemon.pkcompat
sudo apt update
sudo apt upgrade # to make sure that any remaining packages get updated
After that, you should also do
sudo apt autoremove
to remove any stale package that is no more needed in the new version.
As always, it might help to do
sudo dpkg --configure -a
sudo apt --fix-broken install
again after apt update works correctly.
answered Jan 23 at 8:19
Mr ShunzMr Shunz
2,47621922
answered Jan 23 at 8:19
Mr ShunzMr Shunz
2,47621922
answered Jan 23 at 8:19
Mr ShunzMr Shunz
2,47621922
answered Jan 23 at 8:19
Mr ShunzMr Shunz
2,47621922
2,47621922
So it is safe to remove that specific package?
– Unknown User
Jan 26 at 14:59
I did what you said. After a reboot I can't use the normal GNOME anymore. Only GNOME Classic works. If login into to normal GNOME, the screen turns black and the login page opens again.
– Unknown User
Jan 26 at 15:52
(running apt upgrade returns: pastebin.com/nhyssLaE )
– Unknown User
Jan 26 at 16:03
add a comment |
So it is safe to remove that specific package?
– Unknown User
Jan 26 at 14:59
I did what you said. After a reboot I can't use the normal GNOME anymore. Only GNOME Classic works. If login into to normal GNOME, the screen turns black and the login page opens again.
– Unknown User
Jan 26 at 15:52
(running apt upgrade returns: pastebin.com/nhyssLaE )
– Unknown User
Jan 26 at 16:03
So it is safe to remove that specific package?
– Unknown User
Jan 26 at 14:59
So it is safe to remove that specific package?
– Unknown User
Jan 26 at 14:59
I did what you said. After a reboot I can't use the normal GNOME anymore. Only GNOME Classic works. If login into to normal GNOME, the screen turns black and the login page opens again.
– Unknown User
Jan 26 at 15:52
I did what you said. After a reboot I can't use the normal GNOME anymore. Only GNOME Classic works. If login into to normal GNOME, the screen turns black and the login page opens again.
– Unknown User
Jan 26 at 15:52
(running apt upgrade returns: pastebin.com/nhyssLaE )
– Unknown User
Jan 26 at 16:03
(running apt upgrade returns: pastebin.com/nhyssLaE )
– Unknown User
Jan 26 at 16:03
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111486%2fupgrade-from-16-04-to-18-04-broke-apt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hello and welcome to Ask Ubuntu! Looks like
kicad-libraryit's not present in any official repository, did you install one or more PPAs? If that's the case, they should be upgraded to the new version, as they won't get upgraded automatically when changing versions.– Mr Shunz
Jan 22 at 16:48
I could remove the kicad part by doing
apt install kicad– Unknown User
Jan 22 at 21:52