PCManFM won't start for normal user, will start for Root [SOLVED]

[Just17]

/home/user/.config/pcmanfm  appears to be the only location for config files in the user account.

Those permissions were set for user to read & write.

So permissions appear to be OK, yet the misbehaviour continues.


Is the designation for launching apps in KDE not   %u  ?

Is this then a problem between the recognition of   %U  as  opposed to  %u ? ... this problem so far is only reported from installs with KDE and LXDE.

EDIT:
         Seems not  .........
         "%U refers to a list of URLs/URIs whereas %u refers t a single particular URL/URI"

[horusfalcon]

Hi, Just17, Neal, and All Readers,

Neal, feel free to jump in here if my understanding is yet imperfect, but, as I currently read it, the field code %U refers to a list of URLs/URIs whereas %u refers t a single particular URL/URI. 

In this case, they are (probably) effectively the same thing, because, in this case, the "list" %U points to only contains one element, namely, the user ID of the current user?

Still, it begs the question as to when %U is appropriate as opposed to %u (more reading...), but I think that's a detail that will become clearer later on (at least for me).

Just a semi-educated guess - I'm still reading about freedesktop.org.  They have an interesting reason for being and rationale.  I may be waaaay off-base here, yet, though.  I still haven't figured out where the alleged list %U points to resides, or, if it really does at all.

Just saw this from Neal:

I mentioned it earlier but perhaps not strongly enough --- check the ownership of all of your files and folders in your home.     

Explanation:     
Changing permissions will only affect those files and folders that are owned by you. If any config file is not owned by you, it will have no effect on your desktop, home or the app it is for. The ownership of any files or folders by any other user or by root renders it useless for any action by you.     

Okay,  this makes sense.  Seems I should leave the permissions I set on ~/ as they currently are (and ownership of that folder is already set correctly), but I need to look at all the stuff inside that folder and its subfolders and see if ownership got miss-set?  I can do that this evening (I gotta get ready for work right now or I'm gonna be late relieving the watch).

I believe the way to go here is start with the stuff in ~/.config/pcmanfm and its subfolders first, and then re-test, branching out from there step-wise so I can control changes and pinpoint the problem file or folder.  Sounds like that will take some time, so...

Later On,
D

[horusfalcon]

Just bumping this with my next steps:

Checked permissions and ownership of /home/xxxxxxxx - it is set as follows:

Code: [Select]

drwxr-xr-x 116 xxxxxxxx xxxxxxxx
Set permissions and ownership of all files/folders at and below /home/xxxxxxxx/.config/pcmanfm (individually) as follows:

*rwxr-xr-x xxxxxxxx xxxxxxxx

Attempted to start pcmanfm %U after each such change, still, "Error - no such file or directory".

Set permissions and ownership of all files/folders at and below /home/xxxxxxxx/.config/libfm (individually) as follows:

Code: [Select]

drwxr-xr-x 2 xxxxxxxx xxxxxxxx
Attempted to start pcmanfm %U after each such change, still, "Error - no such file or directory".

Worked late yesterday, so that's all I've really had time to do.  My ~/ is over 400 gigs, so this is going to take a long time unless I do it en masse if, indeed, I have to check/set every file and folder I have - I tend to think, though, that the problem lies somewhere in a config file and not any of my data files (e.g., documents, music, or video) - that will help winnow out the distractors, maybe?

At this point, I am considering creating a test account (another normal user) and just comparing what I see there with what I see in my account. 

Meanwhile, I have created a desktop shortcut without the %U in the exec line and it appears to be doing just fine (haven't tried any drag and drop stuff with PCManFM yet, though.  I did that earlier to look at some specific stuff in the configs, but didn't see anything that caught my attention - maybe another run at it with what I've learned so far will be more productive?

It's beginning to look as though the quickest "fix" for this will be to use my backup drive to move all my data out of my ~/ and just "strip it down" bit by bit.  (I'm overdue for a regular backup, anyway...)

If you folks think of anything that would contribute to a solution, please jot back.  Right now, I gotta get ready for work again or I'll be late.  Thanks for everything thus far!

Later On,
D

[Just17]

I just did some further experiments here:-

KDE with task LXDE applied

Launching PCManFM from the menu - which uses pcmanfm %U - works as expected.

Launching pcmanfm from a terminal - using the same command - causes the error.

This holds true for both my main user account and for a newly created account.


This type of result is not unique to pcmanfm.

For instance, try to launch VLC with the command that is used in the menu item.

The command is   
 /usr/bin/vlc %U

Using that from a terminal gives this interesting result

VLC could not open the file

"/home/user/%U". (No such file or directory)

Notice the lack of a 'space' before the %U in the error result above.

Your input can't be opened:
VLC is unable to open the MRL 'file:///home/user/%25U'

I have also had this same type of error when launching other apps from a script.


Another example:

From the menu entry    kshowmail %i -caption "%c"

From the terminal

Code: [Select]

kshowmail %i -caption "%c"
kshowmail: Unexpected argument '%i'.
kshowmail: Use --help to get a list of available command line options.


[Neal ManBear]

horusfalcon,     
In a terminal, as root issue the command:     

chown -R [OWNER][:[GROUP]] /home/xxxxxxxxx

     
chown = change owner     
-R = do this recursively -- all files and folders     
[OWNER] = your username     
[GROUP]] = your group -- usually the same as your username, unless you set it up differently     
/home/xxxxxxxxx --- does this need explaining?     

For more information and further options:     

chown --help

     

[horusfalcon]

Nah... that's pretty straightforward.

Let me "read it back to you" though:  you want me to change the owner and group for every file and folder residing under /home/xxxxxxxx.  Hang on a tick...  issuing command:

Code: [Select]

[xxxxxxxx@localhost ~]$ su
Password:
[root@localhost xxxxxxxx]# chown -R xxxxxxxx:xxxxxxxx /home/xxxxxxxx
chown: cannot access `/home/xxxxxxxx/.gvfs': Permission denied
[root@localhost xxxxxxxx]#

Huh... .gvfs...  I've got that feeling of Deja' Poo (like I've seen this crap before... )  Do I need to switch users and do this file from the actual root account?  Let's try it:

Nope.  Got exactly the same error - .gvfs must be some high-powered stuff to deny root access to it... worry about it later.

Huh... I just checked and permissions/ownership of /home/xxxxxxxx/.gvfs are as follow:

dr-x------ 2 xxxxxxxx xxxxxxxx 0 Sep 11 17:47 /home/xxxxxxxx/.gvfs/

(and that 0 Sep 11 is not a typo.)

Trying pcmanfm %U from a normal user shell prompt still net me the same, "Error - no such file or directory"

Okay, so either .gvfs is a part of the problem, or ownership and group membership are not part of the problem.

I think I'll stop right here for now, go created a new user account and attempt to make some config file comparisons.

Later On,
D

[Neal ManBear]

Using File Manager Superuser Mode, right click the hidden file .gvfs, choose Properties, click the Permissions tab and change the Owner and Group lines to your username and group. Click OK.     

[pags]

Using File Manager Superuser Mode, right click the hidden file .gvfs, choose Properties, click the Permissions tab and change the Owner and Group lines to your username and group. Click OK.     

Maybe he shouldn't worry about .gvfs...  this is used with the Gnome Virtual File System (transparently access noetwork sahres, etc.), and uses fusefs to handle to mounting...it is showing as owned by the correct user, and is it normal the root might have trouble "seeing" it (as the userspace process is running under the user account, not root's)...

It's quite messed up, but not abnormal.
 

[horusfalcon]

Using File Manager Superuser Mode, right click the hidden file .gvfs, choose Properties, click the Permissions tab and change the Owner and Group lines to your username and group. Click OK.     

Dude, it's already there:

dr-x------ 2 xxxxxxxx xxxxxxxx 0 Sep 11 17:47 /home/xxxxxxxx/.gvfs/

The x's represent my user name (just for security).  Would you rather I use a different representation that's more understandable?  They don't represent just any user name.  In other words, xxxxxxxx represents one particular combination of characters which I don't want to reveal to the world at large.

[Neal ManBear]

Using File Manager Superuser Mode, right click the hidden file .gvfs, choose Properties, click the Permissions tab and change the Owner and Group lines to your username and group. Click OK.     

Maybe he shouldn't worry about .gvfs...  this is used with the Gnome Virtual File System (transparently access noetwork sahres, etc.), and uses fusefs to handle to mounting...it is showing as owned by the correct user, and is it normal the root might have trouble "seeing" it (as the userspace process is running under the user account, not root's)...

It's quite messed up, but not abnormal.
 

     
LXDE uses gvfs.     

[Neal ManBear]

Using File Manager Superuser Mode, right click the hidden file .gvfs, choose Properties, click the Permissions tab and change the Owner and Group lines to your username and group. Click OK.     

Dude, it's already there:

dr-x------ 2 xxxxxxxx xxxxxxxx 0 Sep 11 17:47 /home/xxxxxxxx/.gvfs/

The x's represent my user name (just for security).  Would you rather I use a different representation that's more understandable?  They don't represent just any user name.  In other words, xxxxxxxx represents one particular combination of characters which I don't want to reveal to the world at large.

     
I was responding to the "Permission denied."     

[horusfalcon]

Using File Manager Superuser Mode, right click the hidden file .gvfs, choose Properties, click the Permissions tab and change the Owner and Group lines to your username and group. Click OK.     

Dude, it's already there:

dr-x------ 2 xxxxxxxx xxxxxxxx 0 Sep 11 17:47 /home/xxxxxxxx/.gvfs/

The x's represent my user name (just for security).  Would you rather I use a different representation that's more understandable?  They don't represent just any user name.  In other words, xxxxxxxx represents one particular combination of characters which I don't want to reveal to the world at large.

     
I was responding to the "Permission denied."     

Hey... it happens.  Makes me wonder what might still be wrong, though.  I now own every file in my ~/ folder.  (I had already tried File Manager Super User mode, too - same thing.  I think it's probably like Pags said.  Funny part is that there is nothing in the .gvfs folder at all.)

I'm goin' to bed.  13.5 hours last night and all of it busy.

Later On,
D

[Neal ManBear]

Following Darryl's suggestion should do the job.     

[Just17]

Creating a test user on this install, as I have reported previously, gives the following

launching PCManFM from the menu ......  OK

launching PCManFM using the command   pcmanfm %U  from a terminal gives the error message pop-up.

So essentially there is no difference here between my normal user and a newly created test user.

Both give the same results when using the %U with the command -- the error message!

Using the pcmanfm command without the %U will cause PCManFM to launch correctly.

This is a KDE install with task-lxde added.

[horusfalcon]

Y'all forgive me if I wait until tomorrow to implement anything on my end - still working crazy hours and don't feel like I'm really very coherent right now.

Thanks for the guidance - I was headed toward just what is described in TBercaht's post.  Seems like it may hold the best clue as to what caused this (which is more important to me than just getting PCManFM to work - I want to know how it happened so I can avoid doing it again!)

Anyhoo, I'll see you all...

Later On,
D