Well, my guess is that it doesn't have to do with pcmanfm itself, but with pup-volume-monitor, probably the same problem could appear with Thunar.belham2 wrote:Well, crap, I knew there was a reason I wanted that pcmanfm out of these dpup-stretch builds. It just never has acted well, in fact, in my description of the ISO in the 1st message, I said this very thing in the nicest way I could when I wrote right at the beginning under my philosophy for this build:
Quote:
"2) provide lots of easy right-click functionality (via ROX, pcman is included, but it, at its present structure in woof-CE pups, leaves a lot to be desired at the moment);
It just seems like pcmanfm was thrown into the default choice as part of the woof-CE dpup stretch builds and we (builders & users) were/are left to work out its numerous problems. Hate that, it is almost like Microsoft mentality and here it is being reproduced by woof-CE. Not good. Wish this wouldn't happen, but what is there to do? At the moment, the next ISO I upload for this, I am inclined to remove pcmanfm completely. It's the only thing I can think to do....he!!, I'd rather have Thunar in there (in any woof-CE build, for that matter) than to deal with pcmanfm's constant headaches Sad
Thank you, Fred, you've went way and above the call of testing. I really do appreciate it....
Code: Select all
(pcmanfm:17761): GLib-GObject-WARNING **: Two different plugins tried to register 'PupVolumeMonitor'.
EDIT:
Just a wild guess that it might have to do with the fact that (after my audacious install) libglib-2.0 is in two places now, see on left side of pic (is mounted puppy_stretch_7.0.0a1.sfs) it's in /usr/lib and on right side (is my savefolder) it's in /lib (looking from the outside now using DebianDog).
Btw, I think this is a serious bug, libglib-2.0 is just an example, I didn't investigate further but wouldn't be surprised if there are much more "double installs"
Fred