Spacefm

[Archie]

I am so sorry for my ignorance. I rebuilt the app again ... and I couldn't help test it as well (on KDE Minime 2012.02 and fully updated Test4) and it looks like I got it right. Take your pick:

http://dl.dropbox.com/u/32533806/spacefm-0.6.2/spacefm-0.6.2-2_archie_2012.i586.rpm
http://dl.dropbox.com/u/32533806/spacefm-0.6.2/spacefm-0.6.2-2_archie_2012.x86_64.rpm
http://dl.dropbox.com/u/32533806/spacefm-0.6.2/spacefm-hal-0.6.2-2_archie_2012.i586.rpm
http://dl.dropbox.com/u/32533806/spacefm-0.6.2/spacefm-hal-0.6.2-2_archie_2012.x86_64.rpm

Same warning and disclaimer as previously stated applies.

[Taco.22]

Having this bunch of packages in a system dedicated to build packages does not imply to have them in a system dedicated to current use. There are 2 sorts of requires : the required libs to go along with a package, and the ones required at build time.

I stand corrected.  Learn something all the time.

Just a query about Archie's new builds - do I need to uninstall and then clean install, or can I install over the previous?  Only ask because I found out the hard way that manual uninstall of external Spacefm before next test install was a good thing!!

[Archie]

Having this bunch of packages in a system dedicated to build packages does not imply to have them in a system dedicated to current use. There are 2 sorts of requires : the required libs to go along with a package, and the ones required at build time.

I stand corrected.  Learn something all the time.

Just a query about Archie's new builds - do I need to uninstall and then clean install, or can I install over the previous?  Only ask because I found out the hard way that manual uninstall of external Spacefm before next test install was a good thing!!

Unless your app was installed on /usr/local/ then you'll need to uninstall them because those RPMS are going to be installed at /usr - /usr/bin, /usr/share, etc.

If you used the previous RPMS, it would also be sound if you # apt-get remove spacefm then insstall the new RPMS.

[melodie]

Taco, I believe it is safer to remove first (when possible, depends what package it is about... if you do that with glibc, it would be an artistic way to destroy your system... :p). Also to be sure about what it will produce after, I would remove the configuration directory in /home/you/.config.

To be even sure the uninstall was really clean I do as root a "updatedb && locate spacefm". If I find anything I look what it is, and decide whether it has to be removed.

Note that some people don't do any of these, and don't meet with issues either.

Archie, great ! thanks for this work !

What was it that you ignored ? I think I missed a step...

Unless your app was installed on /usr/local/ then you'll need to uninstall them because those RPMS are going to be installed at /usr - /usr/bin, /usr/share, etc.

If you used the previous RPMS, it would also be sound if you # apt-get remove spacefm then insstall the new RPMS.

Archie, if you don't uninstall a program hand compiled from /usr/loca/ : would it not conflict with the one installed afterwards from a package ?

[Archie]

Taco, I believe it is safer to remove first (when possible, depends what package it is about... if you do that with glibc, it would be an artistic way to destroy your system... :p). Also to be sure about what it will produce after, I would remove the configuration directory in /home/you/.config.

To be even sure the uninstall was really clean I do as root a "updatedb && locate spacefm". If I find anything I look what it is, and decide whether it has to be removed.

Note that some people don't do any of these, and don't meet with issues either.

Archie, great ! thanks for this work !

What was it that you ignored ? I think I missed a step...

Unless your app was installed on /usr/local/ then you'll need to uninstall them because those RPMS are going to be installed at /usr - /usr/bin, /usr/share, etc.

If you used the previous RPMS, it would also be sound if you # apt-get remove spacefm then insstall the new RPMS.

Archie, if you don't uninstall a program hand compiled from /usr/loca/ : would it not conflict with the one installed afterwards from a package ?

Check your $PATH. Most likely you will have /usr/local/bin and /usr/bin. And if you have two of the same executable in both folder? What if the executable on /usr/local/bin was the good one and the one on /usr/bin was bad ... I can probably put it in two words - POSSIBLE CONFLICT.

[Taco.22]

Check your $PATH. Most likely you will have /usr/local/bin and /usr/bin. And if you have two of the same executable in both folder? What if the executable on /usr/local/bin was the good one and the one on /usr/bin was bad ... I can probably put it in two words - POSSIBLE CONFLICT.

Yep - the Spacefm.tar installs to /usr/local/bin.  Install instructions give uninstall info, and where all the bits are.  An accumulation of gunky bits can only lead to conflict - Cleanliness is next to Godliness - except for us heathens.  Oh oh - now that's going to get me into trouble .  Anyway, I found that doing that and removing the config file cleared the air.  With the installed rpm Synaptic should do the job - either that or rpm -e ...

[melodie]

Hi,
There is a 0.6.3 out at IgnorantGuru's place.
http://sourceforge.net/p/spacefm/blog/2012/02/063-released/

[Archie]

I'd rather see some feedback from the tests of the available RPMS than embark on another update with something still not working. Thank you.

[Taco.22]

Bit the bullet and now have Spacefm running the "desktop" in Bonsai.  Disabled Pcmanfm and nitrogen, rebooted and set preferences.  Sets my wallpaper of choice, doesn't make conky sad, and mounts stalonetray as it should.  I don't do panels or icons, and even the tray is a frivolous luxury!  All is good.

I had a look at the extras in the Spacefm 0.6.3 package - might be worth checking out how it differs, Archie.  Probably just cosmetic, but I would be quite happy to try an updated rpm - 32bit with --enable-hal.  I suspect we are stuck with that until hal goes away.  I could be wrong - does the non-hal version work with mount/unmount on other DEs?  Has anyone else tried this?       

[Archie]

Bit the bullet and now have Spacefm running the "desktop" in Bonsai.  Disabled Pcmanfm and nitrogen, rebooted and set preferences.  Sets my wallpaper of choice, doesn't make conky sad, and mounts stalonetray as it should.  I don't do panels or icons, and even the tray is a frivolous luxury!  All is good.

I had a look at the extras in the Spacefm 0.6.3 package - might be worth checking out how it differs, Archie.  Probably just cosmetic, but I would be quite happy to try an updated rpm - 32bit with --enable-hal.  I suspect we are stuck with that until hal goes away.  I could be wrong - does the non-hal version work with mount/unmount on other DEs?  Has anyone else tried this?       

I've tested it (non-hal) as well on KDE Minime 2012.02 and honestly, I cannot remember but vaguely ... I think it does what it is suppose to do. I will have to recheck.

Silly question ... what is stationetray?

Were you able to mount/umount drives and removables without issues?

In a week, there were 3 released versions. I will take a look at the Changelog of version 3 and if nothing of significance has changed, we'll just wait for the version with a worthwhile improvement. Latest versions do not really mean they're better.

Peace and much respect,
Archie

[melodie]

Hello,

I will first try this one : spacefm-0.6.2-2_archie_2012.i586.rpm

I just removed all files from the hand install I had done and installed this one version. This is in the machine I use each day, main system.

I'll be back for a report as soon as I will have tested it long enough.

Keep on well,
Mélodie

[Neal ManBear]

To any new users reading this thread:     
You should not use your main/production install for testing new software. If you are going to test, use a test / throw-away install. Installing from outside sources renders your system officially unsupported. If you know how to fix your system, this will not be a big problem for you. If not, a test install can be formatted without loss of your data.     

[melodie]

Hi,
Is it allowed to talk about the 64bits testing versions here ? I would like and need to make comparison between the behavior of the internal mount features of spacefm without hal enabled in my 32bits install and the behavior of pcmanfm internal mount features (no spacefm there) in my 64bits install. There is something very strange about those behaviors which are interesting to compare : where can I talk about it ?

[Neal ManBear]

This thread only.     

[melodie]

Very well.

In 64bits Lxde and Openbox only (not yet announced, I am doing a mini before announcing both), when I mount a partition in pcmanfm, then unmount, the mount directory stays in /media. Is not removed. Then, when I mount again, then unmount, a new directory with the same name with a _ added is created, then once unmounted is not removed, and the empty directory remains. The following has for name name__ (2 underscore) and so on... I have 6 internal drives, so after 3 times I have 18 directories in /media, (root root and 700) so I can remove them by hand.

In 32bits Openbox, after I installed the version spacefm no hal enabled I get the same behavior...

In both 64bits and 32bits, I also have to add the following authorizations to the file:
/etc/polkit-1/localauthority/50-local.d/55-myconf.pkla

org.freedesktop.udisks.filesystem-mount-system-internal
org.freedesktop.udisks.filesystem-unmount-others

which makes it look like that:

[Storage Permissions]
Identity=unix-group:polkituser
Action=org.freedesktop.udisks.filesystem-mount;org.freedesktop.udisks.drive-eject;org.freedesktop.udisks.drive-detach;org.freedesktop.udisks.luks-unlock;org.freedesktop.udisks.inhibit-polling;org.freedesktop.udisks.drive-set-spindown;org.freedesktop.udisks.filesystem-mount-system-internal;org.freedesktop.udisks.filesystem-unmount-others;
ResultAny=yes
ResultActive=yes
ResultInactive=no

to avoid being prompted for the root password when clicking to mount an internal drive.

A few nights ago I tried during several hours to find what was the problem in Openbox 64 and Lxde 64, without finding a clue. I have compared with the KDE 64 test4, and there, with Dolphin, no such problem: partitions mounted and unmounted without a glitch, without leaving any empty directory behing. Just perfect. I also tried to use different authentication agents (not sure it was even relevant) : either polkit-gnome or lxpolkit, (started from the autostart.sh file) but this didn't make a difference.

Any thoughts on this ?