Salix OS

I've been using Gigolo a lot recently - both to connect to shares on my local network, and to connect using SSH to remote sites. On the 32-bit Salix, I've updated Gigolo to version 0.4.1. And suddenly, connections are not working.

I select a bookmark, tell it to connect. It opens the Gnome-keyring to access passwords, and I get a folder in the Gigolo window. However, I can't open the folder - double clicking or right-click > open both have no effect. If I look in ~/.gvfs, there are no directories created.

I've just gone back to the 64-bit version, which is still running Gigolo 0.4.0. No problem connecting to LAN shares, and I've also just been able to connect to simplynux.fr without any problems either.

I'm not going to upgrade the 64-bit version to 0.4.1, and I may back out 0.4.1 for the 32-bit version, just to see if the problem is fixed, but, so far as I can see, the only change I've made is to let the 0.4.1 update go through.

Anyone have any ideas?

Edit Ok, that looks like its a confirmed bug. Just tried Gigolo on my desktop machine (Salix 13.1.1 32-bit). Same problem with Gigolo 0.4.1. I then dug out the Salix CD and reverted to 0.4.0. Problem gone - I can use it to connect to local shares without problems. I'll revert the 32-bit installation on the laptop later just to confirm that the same applies to remote shares, but it looks pretty conclusive here.

Paul.

I updated to 0.4.1 before it was available on the repositories. It's working fine here with my samba shares.
Rich

laprjns wrote:I updated to 0.4.1 before it was available on the repositories. It's working fine here with my samba shares.
Rich

Well, its consistent here. I just booted back to the 32-bit version on the laptop, checked again - same problem. It appears to work, but no directories are created in ~/.gvfs and any attempt to open the share fails. Reverted to 0.4.0 and its working as it should.

Looking at the package log, I didn't make any other changes when I installed the update to 0.4.1 - it was the only change made on the 2nd of September.

Are you using the same package as the one in the repo? I built gvfs and gigolo 0.4.1 for Vector a couple of days ago, and 0.4.1 is working ok under Vector.

Must remember to PM you about your Unslung - I've recently acquired an NLSU2 and will need to flash it....

Paul.

toothandnail wrote:Are you using the same package as the one in the repo?

No, I installed a package from the mailing list requesting to test it. Downloaded it, installed it, rebooted and it connected to my samba shares.I reported back that the 32 bit version was working so I assume it was released to the repository based on my positive report. I did have to go into the gigilo network tab and open the "Connect to Server" dialog box for each share and reselect the "Server Type"
I will downgrade back to 0.4.0 and upgrade via slapt-get to 0.4.1 to see if I get different behavior.

Must remember to PM you about your Unslung - I've recently acquired an NLSU2 and will need to flash it....

lol... I'm in the process switching to Seagate Dockstar for my "green servers". I still have my Slugs running, but really haven't touch them in over a year. I got them up and running by following this: http://www.nslu2-linux.org/. I'm using the SlugOS.

Your right, there something wrong with the package, but I've got some information that may help someone fix it. I removed gigolo (leaving my config file in my users home directory). I then rebooted and installed gigolo 0.4.1 using slapt-get. When I start gigolo from the menu I get the same behavior that you're seeing. Also I get this message in /var/log/message: Now, if I start gigolo via the command line, it works without problems and no corresponding error message. Since I autostart gigiolo on boot up this is why it worked for me and therefore I don't believe there's anything different about the package that I got via the mail list.
Rich

laprjns wrote:Your right, there something wrong with the package, but I've got some information that may help someone fix it. I removed gigolo (leaving my config file in my users home directory). I then rebooted and installed gigolo 0.4.1 using slapt-get. When I start gigolo from the menu I get the same behavior that you're seeing. Also I get this message in /var/log/message:

Code: Select all

Sep  3 08:59:32 pine_hurst gnome-keyring-daemon[3389]: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files

Now, if I start gigolo via the command line, it works without problems and no corresponding error message. Since I autostart gigiolo on boot up this is why it worked for me and therefore I don't believe there's anything different about the package that I got via the mail list.
Rich

I found something similar. Upgraded the 64-bit version (just to check that the problem was consistent), then tried opening from a terminal, to see if any errors were reported. None were, and it worked.

I've also found the cause. If you look at /usr/share/applications/gigolo.desktop, you'll find that the exec command is this:
The old version just used 'gigolo'. Apparently, the change was required to make gigolo work with LDXE/Openbox. Unfortunately, it doesn't work with Xfce. Editing the EXEC command in the desktop file to just 'gigolo' fixes it, but it obviously needs a better solution to work with all the various environments.

Paul.

This should be fixed for all DEs with the new package that is now in the repos.

gapan wrote:This should be fixed for all DEs with the new package that is now in the repos.

Thanks George, its working here under Xfce.

Paul.