[Bug 1136281] New: Cannot create user directory because /home is not a btrfs sub volume
http://bugzilla.opensuse.org/show_bug.cgi?id=1136281 Bug ID: 1136281 Summary: Cannot create user directory because /home is not a btrfs sub volume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: j.r.hudson@virginmedia.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- When adding a new user, YaST says it cannot create a user directory because /home is not a btrfs sub volume. I still have /home on an XFS partition having done online upgrades from earlier versions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1136281 Joachim Brod <joachim@abraksas.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joachim@abraksas.net -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1136281 http://bugzilla.opensuse.org/show_bug.cgi?id=1136281#c8 --- Comment #8 from John Hudson <j.r.hudson@virginmedia.com> --- As the first Leap 15.1 user to report this bug, I can confirm that the patch works. However, I had installed and been running Leap 15.1 for some days before the patch arrived and I applied it. I suspect people need to install Leap 15.1, apply all outstanding patches and reboot before attempting to create a new user directory. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1136281 http://bugzilla.opensuse.org/show_bug.cgi?id=1136281#c9 --- Comment #9 from Joachim Wagner <jwagner@computing.dcu.ie> --- No luck trying to reproduce the bug in a VM this time even though I succeeded last year (bug #1136776). Checking /usr/share/YaST2/modules/Users.pm, the patch in comment 2 of #1136776 has not been applied, i.e. the code that caused the bug is present on the install media. There probably are some difference in the installation choices, e.g. last time I probably partitioned manually from scratch while this time I modified the proposed partitions to add /home. This may be why the bug is not triggered this time. To decide how to modify the "most annoying bugs" list, one would need to know whether this bug only comes in after installation or can also be triggered during installation while creating the initial users because instructions "run updates before creating users" only work for after the installation. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com