On 2/3/20 8:52 AM, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 19:11 +0800, Ed Greshko wrote:
On 2020-02-03 19:06, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 07:03 +0800, Ed Greshko wrote:
On 2020-02-03 06:24, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 03:41 +0800, Ed Greshko wrote:
On 2020-02-03 02:27, Patrick O'Callaghan wrote:
No, the login appears to work, but always shows this pop-up.
Nevertheless, nothing seems to be disabled. In fact I often don't
notice it because it's behind some other window. It's an annoyance
rather than a showstopper.
In your initial post you said. "the pop-up just talks about "an application needing
authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
I agree.
If instead of logging in to a KDE session you ssh in or login from a console session
do you get a request to supply your pw a second time? Is /home mounted when you
login in that way?
On a fresh boot, logging into a text console with root, /home is
mounted.
On logging into my KDE session, the pop-up appears. A screenshot can be
seen at:
https://drive.google.com/open?id=1NqOQLgkf1dqBFd3hp4hhP59-y66kwrf2
Well, it seems related to udisks2.
What processes are running at pids 1942 and 944?
$ sudo ls -l /proc/944/exe /proc/1942/exe
lrwxrwxrwx. 1 poc poc 0 Feb 3 11:04 /proc/1942/exe -> /usr/bin/kded5
lrwxrwxrwx. 1 root root 0 Feb 3 11:04 /proc/944/exe -> /usr/libexec/udisks2/udisksd
Shot in the dark....after reading a few, scattered google hits, what happens if you change
UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 to the actual partition definition?
I'll try that in a while after I reboot.
OK....
The odd thing I see in another answer is the output of mount. It has....
/dev/sda5 on /home type ext4 (rw,relatime,seclabel)
Which seems not to be related to LVM
Further to that:
$ ls -l /dev/disk/by-uuid/929f2710-cb9e-44d4-bdd8-52f733a408e6
lrwxrwxrwx. 1 root root 10 Feb 3 16:30 /dev/disk/by-uuid/929f2710-cb9e-44d4-bdd8-52f733a408e6 -> ../../dm-1
$ sudo dmsetup ls
fedora_localhost--live-home (253:1)
fedora_localhost--live-swap (253:0)
fedora_localhost--live-root (253:2)
I also tried your suggestion of mounting the partition (dev/sda5)
directly rather than via the UUID entry and it made no difference (on a
fresh boot).
Patrick,
Some quick notes about lvm. The essence of LVM is the volume group
(VG). Volume groups contain logical volumes (LV). Volume groups are
defined by specifying the raw devices, the physical volumes (PV), that
provide the storage. In order to attach a PV to a VG the raw device
/dev/sdX must be tagged as a PV. Until that is done (pvcreate) a raw
device cannot be part of a VG. Once within a VG the raw device isn't
really mountable because the filesystem on it is created at the LV
level, not the raw device level.
Now as to sd5: try the command "pvs". It will show the tagged (defined)
PVs AND it will show which, if any, VGs that they belong to.
If sda5 is NOT listed by "pvs" then your mount environment is mixed
raw/LVM. Any way you look at it, you may mount both the raw device and
the LV at the same point but only the most recent will be visible. I
also have a hunch that mounting a raw device that is part of a VG is an
invitation to disaster.
I hope that clarifies a bit where LVM fits into all this.
:m
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
