Lubuntu makes /bin and /sbin symlinks

[Hadmut Danisch]

I was just hunting a bug and noticed, that a Lubuntu 20.04 system installed with the Lubuntu 20.04 image does not have /bin and /sbin directories. Both are just symlinks to /usr/bin and /usr/sbin.

I don't think this conforms to common Linux standards.

I recently had the problem that the Lubuntu installer creates /tmp as a ramdisk, which definitely is not allowed and breaks functionality.

The Lubuntu installer causes severel problems and seems to be written by someone mostly ignorant of Linux file system standards.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1898302/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Chris Guiver (guiverc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

You haven't given any specifics as to which install media you are talking about, you do specify Lubuntu 20.04, but not
- the original 20.04 media,
- updated 20.04.1, or
- a daily image (and then which one)

It could be added via running the following command only once (from your installed system, or the 'live' iso), as it will automatically gather debugging information, in a terminal:

apport-collect 1898302

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Lubuntu has used the `calamares` installer since 18.10, however I suspect this issue impacts more than Lubuntu. A QA-test install of Xubuntu groovy beta appears to have the same as what you're describing). I'm unsure of correct package sorry.

[Chris Guiver (guiverc)]

Probably most useful to explain what Ubuntu (and Debian) are doing

https://wiki.debian.org/UsrMerge

(provided & thanks to @sarnold)

[Hadmut Danisch (hadmut)]

It was the original 20.04 (without .1) released Lubuntu install medium.

Usually I do use ubuntu-bug and name the package. But I don't know which package to name if reporting bugs about crime commited by the install medium's installer.

It is not that obvious where to report bugs against the Lubuntu installation process, and there's more bugs. Or how it is named. I have reported bugs about this installer/Lubuntu for 19.10 before (e.g. occupying gid 1000 with a system group or incomplete desktop app paths), but nobody really seems to care.

Sorry, but I did not notice the changes between ubuntu-bug functionality from 18.04 to 20.04. ubuntu-bug from 18.04 did not offer the choice of reporting installer bugs.

And, btw., the update from 18.04 to 20.04 already cost me lots of headache and debugging time. Never ever before since the earliest days of debian and ubuntu I've had so much overhead and problems with a release upgrade.

[Launchpad Janitor (janitor)]

[Expired for lubuntu-meta (Ubuntu) because there has been no activity for 60 days.]