Le 15.10.2013 12:42, Tazman Deville a écrit :
On Mon, Oct 14, 2013 at 02:22:06PM +0200, berenger.morel@neutralite.org wrote:Le 13.10.2013 13:44, Tazman Deville a écrit : >On Fri, Sep 27, 2013 at 08:11:10PM +0200, Tony Baldwin wrote: >>Friends, >> >>For some reason, when I try to use pcmanfm as my user, I can not. >>I can start it as other users on the system, or with gksu or sudo, >>but not for my user. So it must be a configuration problem, or other users would have the same problem.This is one of the first things I thought, but, as mentioned in my original message, I replaced MY configs with those of another user (and chowned them to me), and this made no difference.
Yes, but you only did this on pcmanfm's configuration files, right? I think the problem is not directly a pcmanfm's one, but maybe related to something it uses. This is why I suggested you to move all config files. Do something like that:
$ mkdir OLD_CONFIG $ mv .* OLD_CONFIG $ pcmanfmHere, pcmanfm should work. If so, you can move back files one after one until pcmanfm stop to work again, so that you could identify which file is making problem.
So far, I'd only tried replacing the configs, not just simply making then unavailable.
Making them unavailable will force the softwares to create the default ones, so you will have the default config.
... okay, moving the .config/pcmanfm contents to somewhere, thus leaving the directory empty (no configs) seems to make no difference.
Obviously. The problem does not come from pcmanfm, from what I can guess. pcmanfm not working is the consequence of the problem, not the problem itself.
You need pcmanfm-dbg to have symbols, it might help. However, I have never tried it myself.I do have that installed.
Honestly, I tried to use the *dgb files. I had no results, I was never able to understand their use. It seems that it is better to compile the software with the -g option, and debug the compiled version. At least, you will have the source code, with comments, which makes things really easier, and you also might use some IDE or a debugger with a real human usable interface. I do not say that gdb is bad, but it needs learning. Lot of RTFM for even simple debugging...
The debugger I use (which are, in fact, simple frontends to gdb) are the plug-in of codeblocks, and cgdb (I know prefer this last one, except that I still do not know how to interrupt a program, unlike in C::B.). You can also use ddd, or the debugging feature in qtcreator, for example. All of them uses gdb in background, but they are far easier to use than gdb.