(solved) mount permission in spacefm

Forum Forums General Software (solved) mount permission in spacefm

  • This topic has 34 replies, 3 voices, and was last updated Jan 23-5:32 pm by Anonymous.
Viewing 15 posts - 16 through 30 (of 35 total)
  • Author
    Posts
  • #5321
    Member
    clickbr
      Helpful
      Up
      0
      ::

      as the permissions are for the demo user, it prevents me from saving damaged inside the external hd.

      Attachments:
      #5323
      Member
      clickbr
        Helpful
        Up
        0
        ::

        this error persists in both live and installed. The same error also occurs in internal ext3 partitions as in external USB usb.

        #5334
        Forum Admin
        anticapitalista
          Helpful
          Up
          0
          ::

          I’m not seeing the same as you.

          Attached screenshots of spacefm show correct permissions of the media files on the usb device.

          Philosophers have interpreted the world in many ways; the point is to change it.

          antiX with runit - leaner and meaner.

          #5344
          Member
          clickbr
            Helpful
            Up
            0
            ::

            I’m not seeing the same as you.

            Attached screenshots of spacefm show correct permissions of the media files on the usb device.

            Actually, we are seeing different things.

            #5348
            Member
            clickbr
              Helpful
              Up
              0
              ::

              I am in the antix live, I created the user jpgamer and this is what I visualize in the permissions of the external disk. He is really riding as a user demo.

              Attachments:
              #5350
              Member
              clickbr
                Helpful
                Up
                0
                ::

                this is my passwd file

                Attachments:
                #5353
                Member
                clickbr
                  Helpful
                  Up
                  0
                  ::

                  this is my fstab file

                  Attachments:
                  #5355
                  Member
                  clickbr
                    Helpful
                    Up
                    0
                    ::

                    it seems that the montage is taking the UID of the user demo in the live. But it also happens when it is installed. Something is happening with the montage.

                    #5356
                    Member
                    clickbr
                      Helpful
                      Up
                      0
                      ::

                      I already discovered that it seems to happen only with ext3 partitions, with ntfs partitions there are no problems.

                      Attachments:
                      #5372
                      Member
                      clickbr
                        Helpful
                        Up
                        0
                        ::

                        the assembly is using udevil, is not it? It would not be some udevil conf? I also do not understand why only I have problems with permits in the assembly or someone else will have?

                        Attachments:
                        #5374
                        Anonymous
                          Helpful
                          Up
                          0
                          ::

                          the assembly is using udevil, is not it? It would not be some udevil conf?
                          For non-root user mount operations, IIRC pmount is used.

                          why only I have problems
                          The multi-user features are probably seldom used. You are likely just discovering corners which no one else has yet noticed and reported.

                          cd /home/jp2gamer
                          grep -ir “demo:demo”
                          grep -ir “demo”

                          Do you find anything (any configuration file) with a hard-coded reference to “demo”?

                          On a relatively fresh antiX17 system, I checked:
                          cd /etc/skel
                          grep -ir “demo:demo” none
                          grep -ir “demo”
                          {———– (unrelated to your mount problem, but) YES, several hard-coded /home/demo …roxicons paths found within configfiles

                          #5375
                          Member
                          clickbr
                            Helpful
                            Up
                            0
                            ::

                            $ grep -ir “demo” > demo.txt
                            $ cat demo.txt

                            Attachments:
                            #5377
                            Anonymous
                              Helpful
                              Up
                              0
                              ::

                              Toward replicating your result and troubleshooting, a few questions:

                              1) spacefm + multiple user accounts + mount ext3
                              ^—- (ignoring exact v1.0.5 spacefm version) No problems with this exact scenario on other distros, yes?

                              2) jp2gamer account was created during livesession, or was created after installation to disk?
                              3) Does demo account still exist?
                              4) (if demo account still exists) Is autologin enabled… and “demo” is the default auto-logged account?

                              I do not know if I’m true, per spacefm uses pmount or udisksctl to mount as partitions.
                              It may be that these commands are not correctly assigning permissions to assembly with other types of users.

                              http://ignorantguru.github.io/spacefm/spacefm-manual-en.html

                              Device Manager * – Programmable device management
                              Single-click mounting and unmounting of devices *
                              Optional automatic mounting and opening of devices on insert *
                              Programmable event-based manager runs any commands or apps you specify on device or media insertion, mount, and removal *
                              ———- SNIP ————-
                              Built-in udev (or eudev) support – can be used with udevil (a mount tool designed specifically for SpaceFM), pmount, udisks, or your custom mount solution *
                              When used without udisks, there is no need for policykit, consolekit, devicekit, gvfs, and other troublesome components susceptible to frequent breakage and misconfiguration
                              Add custom Device and Protocol handlers, and mount options based on fstype or device *

                              With version 0.7.5 in April 2012, SpaceFM replaced udisks with direct udev support for device detection and information, and support for multiple mount solutions including udevil (a mount program developed specifically for SpaceFM), pmount, udisks v1 or v2, or any program you specify.

                              seems to happen only with ext3 partitions
                              Aha, that a great observation toward troubleshooting.
                              As a betester and a user, I have only tested ext4, FAT32, and ntfs. (I did find, and report, a bug specific to FAT32, but i don’t recall the details).
                              To test, I would need to create an ext3 partition (not today)

                              http://ignorantguru.github.io/spacefm/spacefm-manual-en.html#handlers-dev

                              another except from the spacefm User Manual

                              Mount Options
                              Mount Options opens a dialog which allows you to set default mount options. These options may be used in Device Handlers via the substitution variable %o, and are used by the default mount command for all mounts, including auto-mounts.
                              In addition to regular options, you can also specify options to be added or removed for a specific filesystem type by using the form OPTION+FSTYPE or OPTION-FSTYPE.
                              For example, this set of options:
                              nosuid, sync+vfat, sync+ntfs, noatime, noatime-ext4
                              will add nosuid and noatime for all filesystem types, add sync for vfat and ntfs only, and remove noatime for ext4.
                              Note that only handlers which use the %o substitution variable will use options specified here. They will not apply to mounts performed by other handlers.
                              Note that some options, such as nosuid or noatime, may be added by your mount program even if you don’t include them. For example, if using udevil, you may need to also change the default options in /etc/udevil/udevil.conf. Also, options specified in /etc/fstab may take precedence over options specified in Mount Options.
                              pmount does not support conventional mount options, so when using pmount as the mount command, options set here will be ignored. Instead, you can include pmount’s command line options in the appropriate Device Handler.

                              #5382
                              Member
                              clickbr
                                Helpful
                                Up
                                0
                                ::

                                1) spacefm + multiple user accounts + mount ext3
                                ^—- (ignoring exact v1.0.5 spacefm version) No problems with this exact scenario on other distros, yes?

                                2) jp2gamer account was created during livesession, or was created after installation to disk?
                                3) Does demo account still exist?
                                4) (if demo account still exists) Is autologin enabled… and “demo” is the default auto-logged account?

                                1- Yes
                                2- I did both
                                3- Yes. But I did some tests in which I excluded the demo account.
                                4- No. I have predetermined the new account as automatic.

                                #5392
                                Forum Admin
                                anticapitalista
                                  Helpful
                                  Up
                                  0
                                  ::

                                  As well as chown, did you chmod 777 the device?

                                  Philosophers have interpreted the world in many ways; the point is to change it.

                                  antiX with runit - leaner and meaner.

                                Viewing 15 posts - 16 through 30 (of 35 total)
                                • You must be logged in to reply to this topic.