@Wolfgang: No worries. And as an early and vocal critic of the
"$HOME/snap" directory (see post #14, for example), I share your
frustration. But I've come to realize that devs truly want to, and are
working to, resolve the issue. We (the users of this FREE software)
just need to be patient. An
Wolfgang (wolfgang-v) wrote:
>@jean-miguel and anyone else affected: Please report your feedback to
Ubuntu customer support too, so that they can draw their own conclusion
on how their product decisions affect their user base.
Wolfgang, you forgot to suggest that all dissatisfied users should
DEM
@polirecyliente,
Please allow me to reiterate what I wrote in post #265 of this thread:
>I was an early and vocal critic of the "$HOME/snap" directory who:
>
>(a) complained about this issue in numerous comments, including comment #14
>(posted 2017-04-16), >comment #15 (posted 2017-05-20), comme
I was an early and vocal critic of the "$HOME/snap" directory who:
(a) complained about this issue in numerous comments, including comment #14
(posted 2017-04-16), comment #15 (posted 2017-05-20), comment #19 (posted
2017-07-12), and comment #32 (posted 2017-10-22);
(b) reverted the status of
** Changed in: ubuntu-mate
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855896
Title:
Unable to install Ubuntu Mate and Vanilla Ubuntu together for dual
boot on
!!
Regards,
GizmoChicken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage notifications about this
@zyga
GREAT NEWS! THANK YOU!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
Please move the "$HOME/snap" directory to a less obtrusive location
To manage notifications about this b
Public bug reported:
I have two EFI System Partitions (ESPs) on my system: the first is at
sda2, and the other is at sda6. When installing Ubuntu MATE (the second
of two Ubuntu installations on my system), I specified "do not use the
partition" for sda2 in an attempt to prevent the /EFI/ubuntu th
** Description changed:
I want to dual boot between two Ubuntu installations (home vs work,
etc). Unfortunately, when using the "something else" installation mode
(which I must use for various reasons), the second Ubuntu installation
overwrites the /EFI/ubuntu (on ESP) from the first Ubunt
** Also affects: ubiquity (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/1855896
Title:
Unable to install Ubuntu Mate and Vanilla Ubuntu together
** Description changed:
I want to dual boot between two Ubuntu installations (home vs work,
etc). Unfortunately, when using the "something else" installation mode
(which I must use for various reasons), the second Ubuntu installation
overwrites the /EFI/ubuntu (on ESP) from the first Ubunt
** Description changed:
I want to dual boot between two Ubuntu installations (home vs work,
etc). Unfortunately, when using the "something else" installation mode
(which I must use for various reasons), the second Ubuntu installation
overwrites the /EFI/ubuntu (on ESP) from the first Ubunt
Ubfan wrote:
"don't forget, each disk may have an ESP, and if the installer's target
is not sda, then the question not only needs to be asked, but the
installer should use the provided input. It's another bug that this
input is just ignored."
I agree. And a fix to a bug that I report elsewhere co
Public bug reported:
I want to dual boot between two Ubuntu installations (home vs work,
etc). Unfortunately, when using the "something else" installation mode
(which I must use for various reasons), the second Ubuntu installation
overwrites the /EFI/ubuntu (on ESP) from the first Ubuntu installat
Could virt-manager, libvirt, and qemu all be rolled into a *single*
snap, allowing all these components to be simultaneously upgraded to the
latest versions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
Seems to me that packaging virt-manager as a snap would allow for
delivering the most current version across supported Ubuntu releases.
Could we get virt-manager packaged as a snap?
Note that qemu (with virgil enabled) is already available as a snap.
See https://snapcraft.io
Public bug reported:
Seems to me that packaging aqemu as a snap would allow for delivering
aqemu more easily across supported Ubuntu releases. Could we get aqemu
packaged as a snap?
Note that qemu (with virgil enabled) is already available as a snap.
See https://snapcraft.io/qemu-virgil
** Affec
@nmann84 I fully agree that this issue should be marked with a higher
priority. But as mentioned by @kwill in comment #22, there's a pretty
simple workaround, namely:
"Create a text file called ~/.hidden and put the word "snap" inside it.
"snap" will now be treated as a hidden folder by Nautilu
I just want to reiterate that, as mentioned by Stuart Bishop in Comment
#8 above, this bug also affects the Ubuntu Live USB/CD.
I've been using an Ubuntu Live USB for accessing LUKS volumes on my
systems for years. I hope that the Ubuntu 18.04 Live USB continues to
provide this functionality.
--
Hi Christian,
I notice that you and Serge Hallyn are members of the “Ubuntu
Virtualisation” team. See https://launchpad.net/~ubuntu-virt/+members
I'm curious. Is the “Ubuntu Virtualisation” team still active on
launchpad?
As you point out, diverging from Debian in the official repositories
pro
>I may be misunderstanding niemeyer's message, but just to be clear...
The key point can be found in message #40, namely:
"we're working on better ways to allow snaps to have access to read and
write data in the system in a controlled way. After that happens, we
WILL remove this directory from yo
** Summary changed:
- Please move snap user data from "$HOME/snap" to "$HOME/.snap" (or to
"$HOME/.local/share/snap" in accordance with the XDG spec)
+ Please move the "$HOME/snap" directory to a less obtrusive location
--
You received this bug notification because you are a member of Ubuntu
Bu
"Instead, we're working on better ways to allow snaps to have access to
read and write data in the system in a controlled way. After that
happens, we WILL remove this directory from your homes into a better
place."
Thanks much!
** Changed in: snapd
Status: Opinion => Confirmed
** Changed
"Rather than just moving it, please allow it to be configurable. Hard-
coding anything is a very bad idea."
With regard to a directory that is intended to be user accessible (as
opposed to one that contains configuration files), I'm all for
reconfigurability.
But with regard to the locations of p
Fixed for Firefox 57 (on Ubuntu 17.10) as of 2017-09-20. Thanks!
** Changed in: unity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711199
Title:
Globa
Now that Ubuntu uses a swap file instead of a swap partition, this bug
should be less of an issue for most users. But for when a swap
partition, rather then a swap file, is truly needed (for example, when
using a swap file unfriendly file system, like btrfs), here's a work
around:
Before installi
I still hope that this bug report will eventually receive some attention
from the Kubuntu devs.
But in the meantime, for those who want to create, and install into,
LUKS encrypted volumes during manual disk setup (as opposed to using the
default full disk encryption option), installing Ubuntu serv
Public bug reported:
Not a big deal, but I notice the Global Menu (and the Locally Integrated
Menu (LIM)) doesn't work with Firefox 56 or Firefox 57 on Ubuntu 17.10
running Unity7.
Interestingly, also on Ubuntu 17.10 running Unity7, Global Menu (and
Locally Integrated Menu (LIM)) DOES work proper
** Summary changed:
- Can't create LUKS encrypted volumes during manual disk setup in Kubuntu 17.10
(does not affect Ubuntu, Ubuntu MATE, or Ubuntu Budgie)
+ Bug in ubiquity-frontend-kde: Can't create LUKS encrypted volumes during
manual disk setup in Kubuntu 17.10 (does not affect Ubuntu, Ubunt
** Summary changed:
- Can't use crypto in manual disk setup Kubuntu 15.10
+ Can't create LUKS encrypted volumes during manual disk setup in Kubuntu 17.10
(does not affect Ubuntu, Ubuntu MATE, or Ubuntu Budgie)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 1510731 ***
https://bugs.launchpad.net/bugs/1510731
** This bug has been marked a duplicate of bug 1510731
Can't use crypto in manual disk setup Kubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: luks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510731
Title:
Can't use crypto in manual disk setup Kubuntu 15.10
To manage notifications about this bug go to:
https://bugs.launc
I filed Bug #1523194. It deals with something a bit different, namely
being unable to place /home in its own encrypted partition when using
ext4.
Also, when I filed Bug #1523194, I originally assigned it to ubiquity,
but someone reassigned it to partman-crypto. Honestly, I'm not
convinced that it
Just a guess, but this bug may be in the ubiquity-frontend-kde package.
If so, that would explain why the bug is NOT seen in Ubuntu, Ubuntu
MATE, Ubuntu Budgie, or in any of the flavors that use the ubiquity-
frontend-gtk package.
Unfortunately, the ubiquity-frontend-kde package doesn't seem to ha
** Tags removed: wily
** Tags added: artful ubiquity-frontend-kde
** Tags added: xenial
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510731
Title:
Can't use crypto in manual
*** This bug is a duplicate of bug 1510731 ***
https://bugs.launchpad.net/bugs/1510731
This bug report seems to include at least TWO distinct bugs.
1. "The installer refused a swap partition outside the crypto
partition" seems related to Bug #1490824 which affects all flavors
Ubuntu. A simpl
*** This bug is a duplicate of bug 1510731 ***
https://bugs.launchpad.net/bugs/1510731
** This bug has been marked a duplicate of bug 1510731
Can't use crypto in manual disk setup Kubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
*** This bug is a duplicate of bug 1510731 ***
https://bugs.launchpad.net/bugs/1510731
** This bug has been marked a duplicate of bug 1510731
Can't use crypto in manual disk setup Kubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
*** This bug is a duplicate of bug 1510731 ***
https://bugs.launchpad.net/bugs/1510731
** This bug has been marked a duplicate of bug 1510731
Can't use crypto in manual disk setup Kubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Because this bug also affects KDE neon, I filed the following bug report
on the KDE Bugtracking System:
https://bugs.kde.org/show_bug.cgi?id=383219
** Bug watch added: KDE Bug Tracking System #383219
https://bugs.kde.org/show_bug.cgi?id=383219
--
You received this bug notification because yo
I can confirm this bug exists in the latest daily build of Kubuntu 17.10
amd64 (downloaded 2017-08-06), both when installing onto a newer UEFI
system and when installing onto an older BIOS system.
This bug also exist in the latest build of KDE NEON User Edition, which
seems to use the same, or ver
@John Lenton, Thanks much the information. Good to know that this is
receiving consideration. Much appreciated!
I'm not certain how the "importance" scale works, or what actual effect
has. But so this doesn't get lost in the mix and forgotten, would you
please consider upgrading the importance
I agree with comments #2 and #3 regarding the urgency of this issue. As
John Wang points out, it would be best to address this issue before the
current data location becomes entrenched once more snaps are rolled out.
In comment #11, Mark Shuttleworth suggested that “$HOME/.snap” makes
sense. I to
** Changed in: snapd (Ubuntu)
Status: Opinion => Confirmed
** Changed in: snapd
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053
Title:
User data dir
I followed a link from AskUbuntu to make a case for "$HOME/.snap" as the
default directory.
But it looks like that's where things are headed, so I'm happy. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Thanks! That's helpful information.
So after learning that mesa isn't the problem, I searched a bit more and
found this related Debian bug report: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=839695
The submitter reports the same issue that I'm seeing, namely "GTK
support is disabled" see
I've updated from 16.10, and my host is now running Ubuntu 17.04 with
all packages up-to-date, including the following:
qemu (2.8+dfsg-3ubuntu2)
libvirglrenderer0 (0.5.0-2)
As mentioned in comment #7, my QEMU commands include the following:
-vga virtio \
-display gtk,gl=on \
A
I'm also unable to use the VirtIO GPU 3D (Virgil) on Ubuntu 16.10.
Does this bug still apply to Ubuntu 16.10? Or is some other issue
preventing me from using Virgil on Ubuntu 16.10?
My QEMU commands include the following:
-vga virtio \
-display gtk,gl=on \
When I try to start my VM usi
Okay, I was hoping that I'd be able to suggest, as a simple fix, trying
a newer driver. But I see that v304 is, indeed, the most recent Linux
driver available for your GPU.
http://www.nvidia.com/Download/Find.aspx?lang=en-us
--
You received this bug notification because you are a member of Ubun
Sorry if I missed this in your bug report, but what model Nvidia GPU are
you testing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675830
Title:
nvidia 304 graphics causes Login loop in Ubuntu Bud
nger enabled.
Thanks again for checking this for me!
GizmoChicken
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674271
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674271
Title:
[Feature Re
** Summary changed:
- [Feature Request] Compile kernel with KVMGT support
+ [Feature Request] Compile kernel 4.10 with KVMGT support
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
I haven't yet tested the version of kernel 4.10 that is being supplied
with Zesty, so what I am requesting may already be present. But if not
already present, please consider the following:
Please enable CONFIG_DRM_I915_GVT and CONFIG_DRM_I915_GVT_KVMGT in
".config", which de
"New → Fix Released"
That's great news. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659792
Title:
Wishlist: Please update to QEMU 2.8 for Zesty Zapus
To manage notifications about thi
Public bug reported:
QEMU 2.8.0 was released on December 20th, 2016 and is available for
Debian Sid, Stretch, and Jessie-backport.
Could we please get QEMU 2.8.0 (or later) in Zesty?
Sid: https://packages.debian.org/sid/qemu
Stretch: https://packages.debian.org/stretch/qemu
Jessie-backports:
I had this issue (nearly 100% CPU use by gvfsd-smb-browse) on a laptop
that is running Ubuntu 16.04.
In my case, removing the package "gvfs-backends" (which is needed for
Samba and other things) is a workaround for the CPU usage issue. I don't
use Samba on this laptop, and at least so far, I haven
U1604-2016-02-03.png is a screenshot showing sysmon running on a system
installed using the U1604 daily build from 2016-02-03.
** Attachment added: "U1604-2016-02-03.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1531387/+attachment/4583143/+files/U1604-2016-02-03.png
** Changed
U1604-2016-02-26.png is a screenshot showing sysmon running on a system
installed using the U1604 daily build from 2016-02-26.
** Attachment added: "U1604-2016-02-26.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1531387/+attachment/4583142/+files/U1604-2016-02-26.png
** Attachm
Looks like this bug/inconsistency has been fixed, at least for the time
being.
Just to clarify my previous observation…
Prior to the fix, when installing root (/) into an Ext4 formatted LUKS
partition, the system recognized the LUKS device as /dev/dm-0, rather
than as /dev/mapper/sdaX_crypt. The
Public bug reported:
Now that ZFS tools and support will be included by default in 16.04, it
would be great if we could install directly to a ZFS formatted disk
using the graphical installer.
Yes, I know that root can be manually installed to ZFS formated disk.
See https://github.com/zfsonlinux/p
onal input.
Thanks,
GizmoChicken
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
T
confirmed. If you would prefer not to work on this bug, then
please hand it off to someone else for triage. But please stop marking
the bug as "incomplete." You have enough information to reproduce the
bug if you would like to do so.
Best regards,
GizmoChicken
** Changed in: ubiquity
*** This bug is a duplicate of bug 1510731 ***
https://bugs.launchpad.net/bugs/1510731
** This bug has been marked a duplicate of bug 1510731
Can't use crypto in manual disk setup Kubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
ure how
to explain the situation better.
How about we leave this bug marked "incomplete" for now, and I'll get
back to you in a few days with more information and a better explanation
of what I suspect is going wrong?
Best regards,
GizmoChicken
--
You received this bug notification be
duplicate of Bug #1523194, which I hope will remain active until a fix
is released.
Best regards,
GizmoChicken
** This bug has been marked a duplicate of bug 1523194
Can't install /home into separate LUKS encrypted volume
--
You received this bug notification because you are a m
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manag
tion of /home into
separate LUKS encrypted volume, I have noticed that I am unable to
upgrade from a working (non-broken) installation of Ubuntu 15.04 in
which /home has been previously installed into separate LUKS encrypted
volume.
I hope that the above is of some help.
Best regards,
GizmoChick
I propose that Ubuntu create an OFFICIAL ppa at which the most recent
versions of virt-manager and qemu can be found, much like "ppa:graphics-
drivers/ppa" provides an official ppa at which the latest nvidia drivers
can be found.
But at least for me, Jacob Zimmermann's ppa (ppa:jacob/virtualisatio
I started report at Bug #1531387 to expand on comment #1 above.
I don't know what, if any, relation Bug #1531387 has to the current bug,
but here's a summary of Bug #1531387:
1) Installing root (/) into an Ext4 formatted LUKS partition creates
/dev/dm-0, rather than /dev/mapper/sdaX_crypt.
2) In
** Tags added: wily
** Tags added: xenial
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home i
** Tags added: wily xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531387
Title:
U1604: Installing root (/) into an Ext4 formatted LUKS partition
creates /dev/dm-0, rather than /dev/mapper/
The existing installation isn't broken. Rather, it is also not possible
to install /home into separate LUKS encrypted volume during upgrade OR
during a clean install. I've tried with Ubuntu 15.10 and 16.04, Lubuntu
15.10, and Kubuntu 15.10. Please see Bug #1523194 for my report
regarding Ubuntu.
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509877
Title:
crash when reinstalling broken lubuntu install - encrypted home on
This bug may also be related to Bug #1361951 related to mke2fs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manage notif
I'm not sure if this is related, but...
I get:
“Creating ext4 system for /home in partition #1 of Encrypted volume
(sda3_crypt)...”
and then my installation hangs forever,
when I:
1) create partitions using gparted (onto a non-UEFI system with a gpt formatted
drive) prior to attempting to ins
** This bug is no longer a duplicate of bug 1361951
mke2fs asks for input when formatting over a partition table
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home i
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531387
Title:
U1604: Installing root (/) into an Ext4 formatted LUKS partition
It boots. And like I said, I'm not sure if this constitutes a full bug.
But it certainly is an inconsistency.
That is:
1) Installing root (/) into an Ext4 formatted LUKS partition creates
/dev/dm-0, rather than /dev/mapper/sdaX_crypt.
2) Installing root (/) into a Btrfs formatted LUKS partition
This bug may also be related to Bug #1531387.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509877
Title:
crash when reinstalling broken lubuntu install - encrypted home on
separate partition
To
This bug may also be related to Bug #1531387.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523194
Title:
Can't install /home into separate LUKS encrypted volume
To manage notifications about this
Public bug reported:
Under Ubuntu 16.04, installing root (/) into an Ext4 formatted LUKS
partition creates /dev/dm-0, rather than /dev/mapper/sdaX_crypt.
On the other hand, installing root (/) into a Btrfs formatted LUKS
partition creates /dev/mapper/sdaX_crypt, rather than /dev/dm-0.
I'm under
Although perhaps not a "duplicate" of Bug #1509877 (assessed to be a
"critical" bug for Lubuntu), this bug and that bug at least seem to be
related. See
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1509877
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug seems related to, or is a duplicate of, the following:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1509820
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510731
Title:
Can't use
This bug seems related to, or is a duplicate of, the following:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1510731
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509820
Title:
Installin
I'll just add that, as a workaround, I installed Ubuntu only into boot
(/boot) and root (/). I then booted into the installed Ubuntu and
created a new auto-mountable LUKS-encrypted volume formatted with Ext4,
to which I moved my home directory.
The above approach works, but for some reason, Syste
Although perhaps not a "duplicate" of Bug #1523194 that I reported, the
two bugs at least seems related.
Have you tried installing only into boot (/boot) and root (/), and then
moving home to a separate auto-mountable encrypted partition after
installation has completed? (To get this to work, you
I can confirm that this is a bug because, although encrypted Ubuntu can
be installed alongside another OS in numerous ways to allow dual
booting, none of the ways of doing so is even remotely straightforward.
So I agree that that this should be fixed.
For those interested in attempting to accompli
89 matches
Mail list logo
