KDE connect dosn't see any devices

[kubicle]

The df command reveals nothing about the permission or ownership of the /home/vince/.locale/share/user-places.xbel file.
Paste the output of
vdir /home/vince/.locale/share/user-places.xbel
in your reply. It should tell us who owns that file and what its permissions are.

The path should actually be /home/vince/.local/share/user-places.xbel (not ".locale")...it could be a bug if something wants to write to ".locale".

Also, why did you put /usr/local and /var on separate partitions? That is very wasteful of disk space.

There are use cases where separate /var and /usr/local could make sense...especially on a machine that is also used as a server (not saying this is the case here, though)

And what are you doing with geoclue? (ID = 119).

System User IDs 100-999 are not standardized, but are dynamically allocated (software that needs to create a user gets the first free uid in this range)...IOW, even if 119 is geoclue on one machine, it can be something completely different in another machine (more info: http://www.debianhelp.co.uk/usersid.htm Debian, but also applies to *buntus)

[GreyGeek]

Good catch on that "locale", Kubicle! My eyes glazed right over it.

As far as using separate partitions for various subdirectories of /, Oshunluver gives a good reason why having /boot on its own partition is a good idea if you are running Btrfs and want to install several OS's. For most Linux users running laptops and desktops that are not servers Oshunluver's use is about the only one I'd consider doing, given the Tb size of today's HDs.

A long time ago there were cases for putting /opt or /usr on separate partitions, the primary reason being that if you filled up /opt, for example, your OS wouldn't stop running.

https://askubuntu.com/questions/5163...ctories-on-sep

Long long time ago...... There was a time when people used to install Linux and configure it by hand for their specific needs. Some of this is true even today for servers. The choices you see in gparted are some of the popular ones for those who had very different needs as compared with the average desktop users, the intended audience for Ubuntu desktop.
Let us take these one at a time. I will skip the ones I don't know much about.

1. /boot there was a time when the Linux file system was fragile and hard drives were small. People were afraid that the hard drive would fill up or get corrupted and Ubuntu won't boot. Keeping the kernels in a separate partition helped the system to boot when other things went wrong. In those days Linux users used to compile their own kernel and clean up old ones. These days I find it a bit counter productive. On a desktop that gets all the updates, a small /boot partition tends to get filled up with old kernels and the system stops booting unless one cleans it periodically. See what happens if you have a separate /boot partition and forget to clean it regularly: How do I free up more space in /boot?
2. On the other hand, if you want to encrypt the / partition (to safeguard the secret software you are working on), you will need a separate (and unencrypted) /bootpartition. Otherwise the system won't boot. Similarly, if you have a RAID drive, keeping /boot in a non-RAID partition may be useful. Many people thinks having a separate /boot partition is a very good idea for these and other reasons.
3. /home Keeping home in a separate partition still makes some sense. This folder/partition has your personal files and having it in a separate partition allows you to format / and reinstall Ubuntu while keeping your files untouched. Recent versions of the Ubuntu installation software includes a choice of update from DVD/USB. This option keeps /homeintact even it it is not on a separate partition. If you run out of space in your primary drive with / partition. You may want to add a new drive and create a single /home partition in the new drive.
4. /tmp is where temporary files go. If you are running a server that creates large temp files, they may fill up all the disk space and bring your server to a halt. Keeping it in a separate partition will only fill up that partition and may stop the process that was creating the big temp files but will not stop the rest of the system. I am told it is easier to deal with a filled up /tmp partition than a temporary folder under / partition.
5. /usr/, /opt/, and /usr/local are all places where programs and apps are kept under different conditions. If you develop software for Linux, it may make sense to keep these in separate partitions, so that if you reinstall Ubuntu, you won't delete the programs you have written or have been working on.
6. Keeping /opt/ and /usr/local in separate partition also makes sense if you install programs from source (your own or from somewhere else) and want to use them in another distribution (say Red Hat) installed in the same computer in its own partition. Then both the distributions, Ubuntu and Red Hat can share the /opt and /usr/localpartitions. (Thanks Rmano!)
7. /srv and /var are particularly useful as separate partitions if you run servers or develop web pages. For the average desktop user these folders don't take up much space and does not hold anything that is of value to the user. For a web developer losing /var/www may mean losing her job.

To be sure, these are not the only directories one can mount as partitions. In Linux, one can mount a partition as any folder anywhere. Partitions are often mounted as sub-directories of /mnt/ and /media.

[steve7233]

This is an old laptop from 2008, so It doesn't have a big HD. 300 GB before the system was installed.

Should I rename /home/vince/.locale/share/ or create a .local directory under /home/. This might have something to do with varius problems as thing might be broken just because of typo in some programs resulting in bad pathing and a miss named directory in the installer! Maybe the Ubuntu Devs need this pointed out. It might be the reason discovery segfaults!

[GreyGeek]

Try renaming ~/.local to ~/.local_bkup and then log out and back in and see what was created. If you DE fails to load then go into the recovery mode, log in as root and change the fs to rw, then from root log in as yourself and revert ~/.local_bkup to ~/.local and log out and back in.