[Bug 1760121] [NEW] Package with ultra ancient version does not make any sense
Public bug reported: Package with ultra ancient version does not make any sense. Instead please provide an installer for the latest version from here: https://packages.erlang-solutions.com Thanks. ** Affects: elixir-lang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760121 Title: Package with ultra ancient version does not make any sense To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elixir-lang/+bug/1760121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760120] [NEW] Package with ultra ancient version does not make any sense
Public bug reported: This package with an ultra ancient version does not make any sense. It would be better to provide an installer for the latest LTS release. This is wasted work done here, please instead focus your efforts on stabilizing important system features, thank you! ** Affects: nodejs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760120 Title: Package with ultra ancient version does not make any sense To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1760120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760074] [NEW] Will the bugfix releases for 2.4 come up in 18.04 packages or do I have to add the ppa?
Public bug reported: Well the question is in the subject, again: Will the bugfix releases for 2.4 come up in 18.04 packages or do I have to add the ppa? I am not sure about how this works - is ist enough to wait for regular bionic updates or is the version in 18.04 doomed to have bugs forever and I have to add the ppa to get new releases? It would be very appreciated to read some info about this, thanks! ** Affects: darktable (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760074 Title: Will the bugfix releases for 2.4 come up in 18.04 packages or do I have to add the ppa? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1760074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759962] Re: Can not mount old hd after new installation because of multiple VGs found with the same name skipping xubuntu-vg
To the group that produced this extremely short-sighted install procedure - here is one thing that you can do to save your honor. The procedure to get out of that described situation is so extremely annoying waste of time for non-guru users that I think it is appropriate to demand some remedy from the producer - you are faced here with a situation where people can not access their data because of your decision to use always the same name for a lvm volume group - I believe that is enough motivation to put some true effort into this issue to save the name "Ubuntu". Similar to a car producing company that has to recall lots of cars because of some production error Ubuntu should deliver some kind of repair script that comes with the installer. Please add an option to the installer to make old Ubuntu installs that were created with this installer accessible by changing the volume group name and making appropriate changes to /etc/fstab and grub files - and please TEST that with real people and real installations before! It seems like nobody @Ubuntu puts some effort into testing these kind of real life scenarios. This lvm mis-configuration is such an obvious footgun that would have been easy to avoid if just one person tried to add an old system hard drive to a newly installed system - a very expected real life situation - many people do migrate to new systems with a new hard disk and then copying data from the old hard disk to the new one is a totally expected thing to happen. Please put more real life testing into your production workflows. BTW there also should exist some kind of "migration assistant" that would copy all the settings from an old $HOME - its kind of annoying that these stupid things still have to be done manually, despite the fact that it would be very easy for you to automate this. You are missing one low hanging fruit to user happiness here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759962 Title: Can not mount old hd after new installation because of multiple VGs found with the same name skipping xubuntu-vg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1759962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759962] [NEW] Can not mount old hd after new installation because of multiple VGs found with the same name skipping xubuntu-vg
Public bug reported: This is an old one a a really totally destroying showstopper, it leads to this: Users after installing a new version of Ubuntu on a new hard disk can not access their files on the old hard disk because the lvm volume has THE SAME NAME! The procedure to rename the vg is absolutely not doable by an average user, much too complicated with editing grub.cfg etc. I am really disappointed by this. The installer makes it easy for users to encrypt their hard drives - but then this comes with such an annoying time bomb, leaving people with an unsolvable problem, not able to access their data. The installer should of course create lvm names with some random part, so it is no problem to mount your old disk and copy your data. Thinking about it one more question comes up: why on earth is LVM not able to mount volumes with the same name? It is using that user given string as an ID? Really? What are people with hundreds of archive disks doing? They have a notebook with all the volume names, so they now which name not to pick for a new hard disk? come on... ** Affects: base-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759962 Title: Can not mount old hd after new installation because of multiple VGs found with the same name skipping xubuntu-vg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1759962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757321] Re: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic]
This was the first real shock moment today trying the bionic beta - I could not believe how good everything seems to be, but then this really FAT one! Unable to get any files from the backup disks... horrible moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757321 Title: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759906] [NEW] Why is this not in bionic 18.04?
Public bug reported: TLDR: Please give us a ssh tunnel manager gui! Why is this software not in bionic anymore? What was the problem and who could / would like to fix that? >From what I understand there is no visual ssh tunnel manager by default in Ubuntu 18.04 - this is a big usability problem, as no normal user ever understands what a ssh tunnel is - but with a visual manager I was able to provide averagge people with the ability to establish ssh tunnels. There is one alternative by Brandon Williams: https://code.launchpad.net/~opensource-subakutty/tunnelmanager/devel if you just throw out such an important gui tool it would be great to consider replacing it with something similar to not produce a lack of options. Ubuntu is great, but these little tools make advanced tech available for average users and that makes it magic! Please consider adding the tunnel manager by Brandon to the release or please build gstm for 18.04. Also any advice would be very appreciated about any alternative - I did some research if network-manager could replace a tunnel manager gui, and there is one simple ssh plugin, but it can not compete with the both softwares mentioned above, as it lacks the possibility to setup multiple tunnels for one connection. gstm was just ok, Brandons tool is also very nice and maybe he feels motivated to polish it when used as an official package. Thank you very much for your attention! ** Affects: gstm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759906 Title: Why is this not in bionic 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstm/+bug/1759906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
