Installing desktop without updating Ubuntu 22.04 can break a desktop system. #1272
Comments
|
Thanks for the report @krsche we're investigating. Did you install 22.04 fresh or upgrade from an earlier version of Ubuntu? As I think of other questions I'll update. |
|
I had a similar experience. I'm on a fresh install of Ubuntu 22.04(not upgraded), and attempted to install I tried to re-install Then an attempt to run |
|
Just added the logs to the top post. It can clearly be seen that lots of seemingly important stuff got removed. I haven't really checked the output of what is to be installed / removed before confirming it, since the list is super long and I know that the ros installation is big. Probably should've done that :) I assume the problem with the kernel panic is related to the removal of initramfs and it not configuring correctly. But for now I'm planning with installing a clean Ubuntu again. I made a backup of @nuclearsandwich it was fresh install, no upgrade - also added kernel versions to the top post |
|
@krsche can you pull We're still trying to figure out which actual packages in the chain are causing it but performing an We're trying to figure out which packages that desktop depends on are causing the conflicts in an un-upgraded Jammy installation. |
nuclearsandwich
changed the title
|
@krsche with assistance from @mjcarroll, @cottsay, @clalancette, and @tfoote we've got a good idea of what's happening. The package The current version of When installing ros-humble-desktop one if its dependencies is We haven't yet determined why apt opts to remove packages from the system rather than refuse installation of the requested packages. Performing a system upgrade or allowing the installation process to upgrade packages as the installation runs prevents the issue by installing the current systemd and udev packages from the To mitigate this issue I'm about to open a PR to the ros2_documentation recommending completing system updates generally before installing ROS 2 and explicitly call out the risk of borking the system if updates are not performed before installing Humble on 22.04. We are also looking at the possibility of updating ROS packages so that they conflict with the early versions of systemd or udev in the jammy repository in the hope that we can make ROS 2 uninstallable rather than "installable" but destructive. |
nuclearsandwich
changed the title
|
@cottsay just pointed out that this must affect ros-rolling-desktop as well since they share many dependencies on this platform. |
|
@nuclearsandwich @mjcarroll @cottsay @clalancette @tfoote you are real heros, never would've thought of such a quick response and resolution! Last time I manually upgraded the packages on my machine was on April 21st, aparently a few days to early. So I tried this on a (headless) VM, but the other way around --> downgrading libudev1 from Interestingly I can't reproduce the same with the docker containers I think tracking it down by installing the pkgs from the 'removed' section into the container and re-triggering Lesson learned for me, for now, is definitely if |
|
I have successfully isolated the problem to an interaction between udev and init |
nuclearsandwich
added a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272
|
I've opened ros2/ros2_documentation#2581 and ros2/ros2_documentation#2582 by way of resolving this issue through advice. I'm also working on a Launchpad issue to see if this is something that could be protected upstream. |
nuclearsandwich
added a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
* Add recommendation to update systems before installing ROS 2. Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272 * Add system upgrade admonition to alternative installation methods. * Extract upgrade admonitions into a snippet. * Add upgrade admonitions to alternative installation methods.
mergify bot
pushed a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
* Add recommendation to update systems before installing ROS 2. Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272 * Add system upgrade admonition to alternative installation methods. * Extract upgrade admonitions into a snippet. * Add upgrade admonitions to alternative installation methods. (cherry picked from commit b4527c0)
mergify bot
pushed a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
* Add recommendation to update systems before installing ROS 2. Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272 * Add system upgrade admonition to alternative installation methods. * Extract upgrade admonitions into a snippet. * Add upgrade admonitions to alternative installation methods. (cherry picked from commit b4527c0)
mergify bot
pushed a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
* Add recommendation to update systems before installing ROS 2. Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272 * Add system upgrade admonition to alternative installation methods. * Extract upgrade admonitions into a snippet. * Add upgrade admonitions to alternative installation methods. (cherry picked from commit b4527c0) # Conflicts: # source/Installation/Alternatives/RHEL-Development-Setup.rst # source/Installation/Alternatives/RHEL-Install-Binary.rst # source/Installation/RHEL-Install-RPMs.rst
clalancette
pushed a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
…#2583) * Add recommendation to update systems before installing ROS 2. Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272 * Add system upgrade admonition to alternative installation methods. * Extract upgrade admonitions into a snippet. * Add upgrade admonitions to alternative installation methods. (cherry picked from commit b4527c0) Co-authored-by: Steven! Ragnarök <nuclearsandwich@users.noreply.github.com>
clalancette
pushed a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
…#2584) * Add recommendation to update systems before installing ROS 2. Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272 * Add system upgrade admonition to alternative installation methods. * Extract upgrade admonitions into a snippet. * Add upgrade admonitions to alternative installation methods. (cherry picked from commit b4527c0) Co-authored-by: Steven! Ragnarök <nuclearsandwich@users.noreply.github.com>
clalancette
pushed a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
* Add recommendation to update systems before installing ROS 2. Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272 * Add system upgrade admonition to alternative installation methods. * Extract upgrade admonitions into a snippet. * Add upgrade admonitions to alternative installation methods. (cherry picked from commit b4527c0) # Conflicts: # source/Installation/Alternatives/RHEL-Development-Setup.rst # source/Installation/Alternatives/RHEL-Install-Binary.rst # source/Installation/RHEL-Install-RPMs.rst
clalancette
pushed a commit
to ros2/ros2_documentation
that referenced
this issue
May 19, 2022
…#2585) * Add recommendation to update systems before installing ROS 2. Installing ROS 2 packages without updating the system first can lead to conflicts due to package version differences. This is generally useful but of particular importance on Ubuntu Jammy: ros2/ros2#1272 * Add system upgrade admonition to alternative installation methods. * Extract upgrade admonitions into a snippet. * Add upgrade admonitions to alternative installation methods. (cherry picked from commit b4527c0) # Conflicts: # source/Installation/Alternatives/RHEL-Development-Setup.rst # source/Installation/Alternatives/RHEL-Install-Binary.rst # source/Installation/RHEL-Install-RPMs.rst Co-authored-by: Steven! Ragnarök <nuclearsandwich@users.noreply.github.com>
This was referenced May 19, 2022
|
Between the bug open with Canonical, and the mitigations we put in elsewhere, I think we can call this fixed. I'm going to close it out, but feel free to reopen if you disagree. |
|
After a fresh install of Ubuntu Server 22.04 on a Raspberry Pi 3 B+, I am still getting this error when following the installation instructions from here: https://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html I might have made an error during the installation and start with a fresh installation again soon. |
|
This behavior is now showing up with Humble desktop, but with a few more conflicting packages related to QT versions being missing as well. I am configuring a new machine that has been apt upgraded before attempting to install. Here is the output of the installation of desktop: @clalancette or @nuclearsandwich anything on your end with this? It renders Humble un-installable right now. |
I just tried installing Are you exactly following the instructions at https://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html ? Do you have any other third-party apt repositories enabled? How did you initially install Ubuntu 22.04? |
|
If you are having trouble installing ROS 2 on your system. The appropriate way to request support is by asking a question on ROS Answers. So far all of these problems, including the one first reported in this issue, have not originated within ROS 2 and bumping a closed issue with new, different problems, is not a reliable way to get support. If the discussion in ROS Answers, does reveal an actual bug in ROS 2 or its packaging and distribution, it would of course make sense to open a new issue with details but should not be the first step. |
|
The system was installed fresh from a USB stick flashed with the canonical amd64 image. The only other non-stock repository (with no packages installed from it at the time) is the docker repository for installing docker engine onto the computer. Otherwise, the instructions in https://docs.ros.org/en/humble/Installation/Ubuntu-Install-Debians.html were followed step by step.
The reason I brought this here, was that it seemed to be related to the issue outlined above. Sorry if that should not have been the case. |
|
I have the same exact issue, fresh install today from a usb stick and posted a ros answers question: https://answers.ros.org/question/402781/ros-humble-ubuntu-2204-apt-install-issue/ |
|
Similar issue with |
|
I too am facing a similar issue in a VS Code 22.04 DevContainer. It was working in the past... |
|
@jakkaj Can you point to the specific container you used as well as the exact commands you ran so we can reproduce? Have you tried a |
|
same problem (Started with an Xubuntu 22.04 iso -> apt update && apt-dist-upgrade :-( |
|
Today after another apt-get update && apt-get dist-upgrade, things worked as expected;-) |
|
It looks like there's a fix coming from upstream too: https://salsa.debian.org/apt-team/apt/-/merge_requests/248 there was an apt resolution issue. |
I aslo have one of the kind today though I don't know whether to same the system is fresh cause it two months now |
|
I am still facing the same issue on Ubuntu 22.04. I was following the steps here -> https://docs.ros.org/en/iron/Installation/Ubuntu-Install-Debians.html Terminal output for "sudo apt install ros-iron-desktop"-> ros2_issue.txt Using 'sudo apt --fix-broken install' doesn't work as well Terminal output -> ros2_broken.txt |
|
Why do you play with humble & iron at the same time?! What does |
|
OK, update your |
|
Hello, the play with humble and iron might be unintended error, I didn't even realize that (still don't!). This is the output of - sudo apt-get install python3-catkin-pkg-modules python3-rospkg-modules I do get that the latest one is vailable at the ros2 repo, great if you can let me know how to update to that. Reading package lists... Done |
|
What does |
|
Hello, Thank you for the response. This is the output of the This is the output of Also, using |
|
Two problems above:-( On your 'sudo apt update`, it looks like you also have a ROS1 repo configured, which does not exist for Jammy/22.04:-( That's the reason, the 'apt upgrade On your 'fiix-broken' attempt, you run into the issue with the old |
|
Okay, I commented out the line from these two files - Looks like the The output of This doesn't change the situation for all previous commands :-( |
|
It kind of does:-( I don't know, why you have all those old packages around. But you now found the next one:-( I actually don't have 'python3-rospkg' installed at all. But there is also a version 1.5 in the ros2 repos. so you should try to add it to the install list ( |
|
Hello, |
|
You might have both now;-) You can check with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Required Info:
prime-select intel)5.15.0-30-generic(checked after install failed); recovery mode only works on5.15.0-27-genericand lowerSteps to reproduce issue
Follow the installation instructions for humble from the documentation until the step where you actually install it:
sudo apt install ros-humble-desktopOne minor deviation from the instructions:
LC_ALL=, but everything else was UTF8, default Ubuntu 22.04 install.Expected behavior
Install via apt works without breaking my OS :)
Actual behavior
ip link listreported that my wifi device was down and I couldn't bring it up anymoreRendered my distro unusable and I wasn't able to recover it yet.
Additional information
Raw apt logs:
Edited apt logs (similar content as raw logs, but split to one pkg per line):
Newly installed packages (`Install:`)
Upgraded packages (`Upgrade:`)
Removed packages (`Remove:`)
The text was updated successfully, but these errors were encountered: