Artix Linux Forum

So I installed Dolphin and all drives show in Dolphin. What gives?

Code: [Select]

[localhost ᒤᕞᕹᓸ]# pacman -Sii thunar
Repository      : extra
Name            : thunar
Version         : 1.6.12-1
Description     : Modern file manager for Xfce
Architecture    : x86_64
URL             : http://thunar.xfce.org
Licenses        : GPL2  LGPL2.1
Groups          : xfce4
Provides        : None
Depends On      : desktop-file-utils  libexif  hicolor-icon-theme  libnotify  libgudev  gtk2  exo  libxfce4util  libxfce4ui  libpng
Optional Deps   : gvfs: for trash support, mounting with udisk and remote filesystems
                  xfce4-panel: for trash applet
                  tumbler: for thumbnail previews
                  thunar-volman: manages removable devices
                  thunar-archive-plugin: create and deflate archives
                  thunar-media-tags-plugin: view/edit id3/ogg tags
Required By     : thunar-archive-plugin  thunar-media-tags-plugin  thunar-volman  xfdesktop
Optional For    : None
Conflicts With  : None
Replaces        : None
Download Size   : 880.70 KiB
Installed Size  : 5166.00 KiB
Packager        : Evangelos Foutras <evangelos@foutrelis.com>
Build Date      : Friday 30 June 2017 06:31:04 PM CDT
MD5 Sum         : d15011a04885956b9cb0978d2bc18010
SHA-256 Sum     : b1d908f0e7ab91420ac566b75d24fbe1621bfbaf5c4bd193507c9fe0df719e16
Signatures      : 51E8B148A9999C34

Thunar needs gvfs for mounting support, as it is listed under optional dependancies. Same with pcmanfm. Dolphin's support is run through the underlying kde packages necessary to intall any kde program/app.

Gnome lets you choose and pick what you want/need. Kde is a whole package that shares its resources/support through its base. Difference in philosophies. /shrug

Here is a list of gvfs optional packages:

Code: [Select]

[localhost ᒤᕞᕹᓸ]# pacman -Ss gvfs
extra/gvfs 1.34.1-1 (gnome) [installed]
    Virtual filesystem implementation for GIO
extra/gvfs-afc 1.34.1-1 (gnome) [installed]
    Virtual filesystem implementation for GIO (AFC backend; Apple mobile devices)
extra/gvfs-goa 1.34.1-1 (gnome)
    Virtual filesystem implementation for GIO (Gnome Online Accounts backend; cloud storage)
extra/gvfs-google 1.34.1-1 (gnome)
    Virtual filesystem implementation for GIO (Google Drive backend)
extra/gvfs-gphoto2 1.34.1-1 (gnome) [installed]
    Virtual filesystem implementation for GIO (gphoto2 backend; PTP camera, MTP media player)
extra/gvfs-mtp 1.34.1-1 (gnome) [installed]
    Virtual filesystem implementation for GIO (MTP backend; Android, media player)
extra/gvfs-nfs 1.34.1-1 (gnome) [installed]
    Virtual filesystem implementation for GIO (NFS backend)
extra/gvfs-smb 1.34.1-1 (gnome) [installed]
    Virtual filesystem implementation for GIO (SMB/CIFS backend; Windows client)

I made a table of my partitions and drives and put it in fstab, commenting out the line of the / partition for each particular installation (if you have more than one) and mount all volumes through fstab.  I use /media to make the mountable directories.
I remember struggling with gvfs and udisk to be able to have them on pcmanfm but gave up as they came and went.
It helps to have labels on the partitions (gparted or else will do that)

This will gave you the data for the table

Code: [Select]

ls -lh /dev/disk/by-uuid 
and 
ls -lh /dev/disk/by-label

This is the format to add to fstab

Code: [Select]

UUID=00000011111	/media/DevuanAscii		ext4		defaults,noatime 0 2
UUID=00000111111	/media/DevuanCeres 	ext4		defaults,noatime 0 2
UUID=00001111111	/media/ManjaOpenRC	ext4		defaults,noatime 0 2
UUID=00011111111	/media/Artix2	        	ext4		defaults,noatime 0 2

You have to create the list of empty directories first so they can be mounted
mount -a  will mount them after you finish without a reboot

Thank you. I had the idea using fstab, but it was late last night,
Again, find it strange that file manager does not come with this support out of the box.

Thank you all. I am now realizing that this is not for me. Too many things need to be tweaked manually, too many things don't work, and too many things are missing.
Life is too short and time flies at my age
best to you all!

Things are not simple when you take arch and try to remove systemd as arch is not interested why should they.
Remember Artix is at the infancy of its life and will take a while to stabilize its aim is to take arch packages rebuild them systemd free in their own repros this will take time, In the mean time we have to report what does not work, I you install Cinnamon it works out the box as things like gvfs are part of the basic install. lxdm also works fine with it.
Take care come back in a few months by the way I'm 68 and never use age as a excuse don't let nothing beat me.

Do you have the required file system installed?
To mount my phone, I use mtpfs.
If you use gvfs then try gvfs-mtp.
And maybe use a mtp transfer program like gmtp or android-file-transfer.

As a user you may not but as root you should be able to.
If sudo works try sudo pcmanfm
If not try $ su, login with root pw,
then pcmanfm

But if you change things around on that device and you don't know what it is you are doing you may never get it functional again.
By default the first user on the system gets the ID# 1000, the second 1001 and so on.  If you see 1001 then you only have one username and 1001 is unassigned.  If the second user was Roxy then you would see Roxy as the owner instead of 1001.
I don't know what ssdm is but the number of the user on that phone may match a system account on your main system.
Or is it sddm?  :)

You mean other drives of other linux systems?
I think sddm is user 999 unless this number is already taken by other "users".  So on some other system where 999 maybe LXDM while you are browsing through on your file manager it may appear as the owner is sddm just because on your artix system user 999 is assigned to the label sddm.

Not just sddm in particular, any DM, has a peculiar responsibility to be authorized/privileged to provide real login users with an appropriate configuration of X to enter into a specific desktop environment.  It is like a middleman between root and the user.

If you think this is weird wait till you see what systemd does, it manufactures users on the fly who login and out of your system, write logs, and you have no control of what and when they do stuff.  You seat around idleing with nothing running (that you know of) and users go in and out of the task-list. 

If you login console as root, who starts sddm?  Who is authorized to log you in as a user?  Should root be able to read the user's emai?

Those are advanced system-design questions that I am clueless about and prefer to stay this way :)

I don't know much about this stuff, what is right or wrong Linux philosophy. All I know is that I am always able to access my main current home folder (Manjaro OpenRC) from any other Linux I install on one of my drives. All that is required is either user or root password. I am not sure which one since I use same password for my user account and root.
But here, in Artix I cannot access my Manjaro OpenRC home folder. It's owned by whatever, 1001 or sddm.

For your phone make sure that these entries are in groups uucp:x:14: user name  adbusers:x:996:user name  storage:x:95:user name
android:x:1001:user name

I was talking about folder ownership of my other drives, not the phone. I just thought that not being able to mount phone storage has something to do with ownership.
ssdm was typo, it's sddm. Why would sddm be owner of any folder on my other drives?  I've never seen that before.
Thanks for being kind and trying to help.

For your phone make sure that these entries are in groups uucp:x:14: user name   adbusers:x:996:user name  storage:x:95:user name
android:x:1001:user name